Payments

Use XPay Payments to create a payment on the merchant backend, collect payment details through XPay Element, confirm the payment from the customer interface, and reconcile the final result on the backend.

How the resources relate#

Merchant order
    └── PaymentIntent
          ├── Customer
          ├── XPay Element confirmation
          ├── Payment status
          ├── Payment token, when requested
          └── Refund, when created

A PaymentIntent represents one payment journey. The merchant stores its ID against the related order and uses its status to decide whether the payment needs another method, customer action, later capture, or has succeeded.

Payment flow#

1. Create a PaymentIntent on the merchant backend.
2. Collect payment details with XPay Element in the merchant frontend.
3. Confirm the payment with the selected XPay SDK.
4. Handle customer authentication when XPay requires it.
5. Verify the asynchronous result through XPay webhooks.
6. Retrieve or store the current PaymentIntent status before fulfillment.

Choose a payment task#

• Accept your first payment for the minimum Web integration.
• PaymentIntent lifecycle and statuses to interpret payment states.
• Capture a payment later to separate authorization from capture.
• Tokenization to save, manage, and charge reusable payment methods.
• Customers to reuse customer identity across payments, tokenization, and subscriptions.
• BIN discounts to evaluate a card BIN against merchant discount configuration.
• Refund a payment to return an amount from a captured transaction.
• Payment webhook events

API details#

Workflow pages show only the fields required for their task. Use the XPay API reference for complete schemas, optional parameters, and response objects.