Hosted Checkout

Hosted Checkout is a first-class integration in which Maxana owns the buyer’s checkout page.

Flow

1. Your server creates a checkout session with the pages that receive the buyer after success or cancellation:

   {
     "amount": "49.95",
     "currency": "USD",
     "external_order_id": "order_1001",
     "description": "Order 1001",
     "success_url": "https://checkout.example.com/orders/order_1001/success",
     "cancel_url": "https://checkout.example.com/orders/order_1001/cart",
     "allowed_origins": ["https://checkout.example.com"]
   }

2. Your application sends the buyer to the response’s checkout_url.

3. After payment or cancellation, the buyer returns to the corresponding success_url or cancel_url. Your return experience shows a pending or confirmation state without treating the browser redirect as settlement proof.

4. Your backend reconciles the payment through the API and webhooks.

Use Hosted Checkout when redirecting is compatible with your user experience and you want Maxana to own the checkout page. The same session can also provide an embed_url; choose one presentation intentionally rather than switching based on buyer input.

Current limits

Hosted Checkout does not keep the buyer on a page your application renders. You control the server-created session and return experience, but not the checkout document or its layout. A browser return is navigation, not proof that the payment was captured; reconcile through your server and webhooks.