XPay Element renders XPay-hosted payment fields inside a merchant web or mobile application. Choose the client SDK that matches the customer interface, while keeping API authentication and PaymentIntent creation on the merchant backend.
How XPay Element fits into the payment flow
- The merchant backend creates a PaymentIntent.
- The frontend receives the PaymentIntent client secret and encryption key.
- The selected XPay SDK renders XPay Element.
- The customer enters payment details inside the element.
- The SDK confirms the payment.
- The merchant backend reconciles the result through verified webhooks.
Choose a platform
The Web integration uses SDK v5. A v4 or v4.1 integration should follow Upgrade to XPay Web SDK v5.
Use Configure displayed payment methods to combine or separately render cards, JazzCash, EasyPaisa, Google Pay, and BaadMay in Web SDK v5.
Client credential boundary
Client SDKs may receive only credentials explicitly designated by XPay as publishable. Keep x-api-key, the API signature secret, and the Webhook HMAC secret on the merchant backend.
Next steps
- Follow Accept your first payment.
- Learn how to collect payment details with XPay Element.
- Use the XPay API reference for server endpoint schemas.