Incoming payment handling

This records money customers pay you through Xendit. When a payment settles, a Beam agent reads the transaction, matches it to the invoice or order your rule points to, and marks that record paid in your system. Clean, matched payments update on their own and are logged. Partial amounts, overpayments, or payments with no clear invoice are not forced onto a record; the agent flags them for a person to resolve. Refund and chargeback decisions are always left to your team, since moving money back to a customer is a judgment call the agent will not make alone.

Payout dispatch

This sends money out to recipients through Xendit. When a payout meets the conditions you approved, such as an amount within limits to a known recipient, the agent creates the disbursement and updates your ledger with its status. It records who was paid, how much, and when. Payouts above your threshold, to new recipients, or missing required details are held and routed to a person for approval before anything leaves the account. The agent moves routine, in-policy payments and stops at anything carrying real financial risk, keeping a human on every exception.

Transaction status alerts

This keeps your team informed as payments move through their stages. The agent reads status changes from Xendit, applies your notification rule, and updates the linked order or invoice, sending an alert only when your rule says it matters. Successful settlements can post quietly while failures or long pending states raise a message to the right owner. Repeated failures on one account are grouped so nobody is buried in notices. When a transaction sticks in a state the agent cannot interpret, it escalates the case to a person rather than guessing what went wrong.