Where a user gets stuck, and what unblocks them
The business rules behind these messages are the same ones you already know from your own integration — an amount over the limit, an account not enabled, a refund already registered. If you need the authoritative behaviour for one of them, the Ramps API reference is where it is specified.
Session lifetime
The session token you mint has a limited life. A user who leaves the widget open long enough will be told the session ended and asked to start again from your platform — which is why the widget cannot be embedded once and left running. Mint a token when the user is ready to transact.Support from inside the widget
The user can open a support form from most screens and describe what went wrong, with a short summary and a longer description. It opens a ticket against their identity, so Ripio’s support team already knows who they are and which operations they have. You are not cut out of it. Tickets raised this way are visible through the same public surface as the ones you create yourself:- Create Support Ticket — raise one on a customer’s behalf from your own backend.
- Support Ticket Webhook Events —
SUPPORT_TICKET.CREATEDandSUPPORT_TICKET.FAILED, so your support team can see that a user reached out.
A user in the recovery flow whose emailed link has expired has no way to request a new one, so support is their route. See Recovering a rejected payout.