Direct checkout - Darwin

Direct checkout keeps the merchant’s existing payment experience in control. Darwin opens a reviewed merchant or provider flow, waits for server-side confirmation, and then resumes the same Action.

Follow the direct route

payment_required -> review bound terms -> open provider checkout
                 -> provider confirms -> Darwin verifies
                 -> same Action resumes

When the interaction requires a browser step, the planned Pay operation returns a first-party webLink. That page can redirect into a merchant-hosted or payment-provider-hosted checkout after an explicit user gesture.

Keep authority with the merchant

The merchant calculates the cart, taxes, fees, delivery terms, and final amount. The merchant or its provider processes the payment and remains merchant of record. Darwin does not rewrite those terms, hold funds, or infer success from a closed window.

Confirm the result

Read the same actionId after checkout. Only backend confirmation can move the bound interaction forward. If the amount, merchant, currency, cart, or expiry changes, Darwin presents a new interaction for review. Use Darwin Pay when the selected capability supports a coordinated tokenized or protocol-native route.

Last modified on September 22, 2026