Payout Matching

Each SumUp settlement posts a batch of card transactions to your account. A Beam agent reads the payout and its underlying transactions, then applies your rule for pairing each amount with the sale or invoice it belongs to. Where the connector exposes the fields, it writes the matched reference back and marks the record settled. A payout that lands short, arrives split across days, or carries a fee the rule does not recognize goes to a finance reviewer with the figures attached, so a person decides before the books close instead of the agent forcing a doubtful match.

Refund Handling

When a customer asks for money back, a Beam agent locates the original SumUp transaction by reference, amount, or card detail the connector allows, and checks it against your refund policy: window still open, amount within limit, order not already credited. Cases that pass get queued for the refund your permissions permit, with the reason recorded on the transaction. Anything outside policy, a partial claim, an expired window, or a disputed charge, is escalated to a support agent with the transaction history, so a human approves the exception rather than the rule deciding it alone.

Failed Payment Follow-up

A declined or incomplete SumUp charge signals the agent to read the attempt and the buyer record behind it. Following your rule, it notes the reason code, marks the order unpaid, and prepares an outreach message asking the customer to try again, using only the contact details the account exposes. Repeated declines from the same card, a suspected duplicate charge, or a high-value order stalling at payment are routed to a person with the full attempt log, so someone judges whether to chase, hold, or cancel the sale before anything else happens.