Verification, not custody

Verify Checkout connects a merchant-owned receiving account, a branded checkout, and Verify.et transaction verification. It does not collect, hold, transfer, or settle customer money.

1. Merchant backend

   Creates a deposit and receives a checkout URL.

2. Customer

   Pays the displayed merchant-owned account and submits a reference.

3. Verify.et

   Checks that reference with the selected payment provider.

4. Merchant backend

   Receives the outcome and credits its own ledger once.

Who owns what

Receiving-account routing

At deposit creation, Verify Checkout selects from the workspace's active receiving accounts. If you pass payment_method, checkout is limited to that provider. Otherwise the response can contain several payment_options and the customer chooses on the hosted page.

Checkout lifecycle

1. 1Step 1:

   awaiting_transfer

   Checkout is waiting for a valid reference.
   In progress
2. 2Step 2:

   verification_pending

   A submitted reference is being verified.
   In progress
3. 3Step 3:

   succeeded

   Verification succeeded; reconcile and credit once.
   Terminal · credit
4. 4Step 4:

   failed · expired

   Do not credit. Create a new deposit if the customer needs another attempt.
   Terminal · stop
5. 5Step 5:

   review_required

   Hold fulfillment until the result is resolved.
   Terminal · hold

A checkout link expires 60 minutes after creation. A verification credit is consumed when a valid reference starts a verification attempt—not when the link is created, refreshed, polled, or delivered by webhook.