In the dashboard
Open Ramps in the sidebar. The Transactions page opens first.- Set Source to Widget payments. The environment switch in the sidebar chooses Sandbox or Live.
- Filter by status, or paste a reference into Transaction reference to find one payment.
- Open a row for the amounts, the provider, timestamps and, for failed payments, the reason.
- Use Export to download the loaded rows as CSV.
Statuses
Your reference and ours
Each payment has an Onstacks reference, shown in the dashboard and in webhooks. Theref you pass when opening the widget comes back to your page in onCompleted and onFailed; it isn’t shown in the dashboard today. If you need to match payments to orders on your side, record the pair when the callback runs.
Browser callbacks are not confirmation
onCompleted and onFailed report what the widget showed the customer, in the customer’s browser. Anyone can trigger them from the page’s developer tools. Use them to update your page, for example to show a thank-you message. Before you release goods, credit an account or pay anything out, confirm the payment in the dashboard or through a webhook.
Optional: webhooks for your server
If your server needs to know when a payment succeeds, register an endpoint under Developer in the dashboard. You receive aramp.payment.<status> event each time a widget payment changes status, with the payment in data:
ramp.payment.succeeded with channel: "widget". Verify the signature on every delivery, respond with 2xx, and ignore event types you don’t recognise: Webhooks. Sandbox and Live webhooks are registered separately.