Checkout API sessions are payments started through the checkout API. A pending payment on this list is not money received. The list is not in the left menu. Transaction History still shows them under the source Checkout API.

Who can use this. Open /dashboard/checkout_sessions when your user can reach it. Super admin can open dashboard routes. If the page is forbidden, use Transaction History instead.

Before you start. You need the session or the transaction reference. Do not use this list to invent a storefront order that the dashboard does not show.

Steps

1. Open Transaction History and set the source to Checkout API.
2. Or open /dashboard/checkout_sessions. The title is Checkout API.
3. Filter by date, customer, and status All, Pending, Paid, Expired, or Failed.
4. Open attempts on the session when you need the device decision.
5. Read Paid At, guest, card last 4 digits, and transaction reference when those columns are filled.

After you save or submit. The successful checkout handler does not send the checkout-session-paid email. Use the session status and Transaction History, not an email, as the result.

Example. Example only: a fictional checkout for 16.00 shows Failed, and Transaction History has an ND row with source Checkout API. The order is not paid. A different fictional session shows Paid and an APPROVAL row. That one is paid.

Troubleshooting

• The menu has no Checkout API item. Use Transaction History, source Checkout API, or open the address directly if your user is allowed.
• The customer says they paid but the session is Pending. Do not fulfill. Search Transaction History for an APPROVAL at that time.

Related

• Payment attempts