Skip to main content

​
Product FAQs

To begin collecting payments, refer to the onboarding section of our documentation. It will guide you step-by-step through the process.
xPay is compatible with over 100+ countries including the United States, United Kingdom, India, Germany, France, Canada, and many more.
xPay supports transactions in 20+ currencies like USD, EUR, GBP, INR, and many others. You can find the full list of supported currencies in the Currencies Supported.
Yes, xPay supports subscription and recurring payments.
Recurring payments functionality is being expanded, with more features coming soon.
xPay automatically detects whether a customer’s device supports Apple Pay or Google Pay and displays those options in real time. Both Apple Pay and Google Pay are device-specific payment methods, since the card details are securely stored on the customer’s device.

If you’re expecting to see Apple Pay but don’t, make sure you’re opening the payment link on an iOS device with a VPN set to a country where apple pay is support (eg. USA) and have apple wallet app set up correctly. Apple Pay is not supported in India.

Similar to above, If you’re expecting to see Google Pay but don’t, make sure you’re opening the payment link on an Android device with a US VPN and have Google Pay app set up correctly.
Google Pay in India is different from Google Pay used internationally. In India, it functions as a UPI app, while outside India it works as a digital wallet for cards.
No. Separate whitelisting for apple pay is not required.

​
Tech FAQs

We follow Basic Auth RFC for authentication.In basic HTTP authentication, a request contains a header field in the form of Authorization: Basic <credentials>, where <credentials> is the Base64 encoding of <xPay Public Key> and <xPay Private Key> joined by a single colon :.For a detailed explanation of how to use xPay keys, refer to the Authentication Page.
All values in the amount field must be in the smallest currency unit. For example: - If the transaction is in USD, 1 USD = 100 cents, so to charge USD 2, you should set the amount to 200. - Similarly, for EUR, 1 EUR = 100 cents.
A 400 Bad Request error usually means there’s something wrong with the request. This can be due to:
  • Incorrect parameters
  • Missing required fields
  • Issues with authentication or malformed data
Check your API call and ensure all required parameters are correct and properly formatted. Also, verify your xPay API keys and ensure they’re correctly included in the header.For a more detailed description of error codes and troubleshooting tips, refer to the Errors.
You can integrate xPay with your platform using our well-documented API. The integration process includes authentication, creating a payment intent, handling the payment process, and confirming the payment. Refer to the API Integration Guide for step-by-step details.
xPay collects essential billing details required to complete and verify payments. This includes:
  • Full name
  • Email address
  • Contact number (optional)
  • ZIP code
  • Country These details help ensure accurate billing and compliance with payment regulations.
Yes. You can export up to two years of transaction and payout data directly from your xPay dashboard in CSV format. This is helpful for accounting, audits, or internal reporting.

​
Payment Failure Messages

This message comes directly from the customer’s bank, usually when their card is not enabled for international transactions. Ask the customer to check with their bank and enable international payments.

​
Product Guides

If you need more assistance or have additional questions, feel free to contact our support team at hello@xpaycheckout.com.
⌘I