Introduction
Payments for Egypt businesses. Take cards and local methods via API, hosted checkout, or your own UI.
XPay is a payment platform for online businesses across Egypt. We take card payments and local methods, handle the 3D Secure challenge, and pay out to your bank account when the money settles. There are four ways to integrate, and you pick based on how much code you want to write.
What is XPay?
Built for Egypt
Take Visa and Mastercard alongside local methods like Valu and Fawry. One account works across the region with no separate setup per country.
A modern API
Stripe-shaped resources, real SDKs, and a hosted checkout page that looks like a polished consumer product. If you've integrated Stripe before, you'll feel at home in an afternoon.
Payment to payout
Take a payment, manage the customer, issue refunds, and pay yourself out. All in one dashboard and one API, from sale to bank.
Branded checkout out of the box
Hosted forms in English or Arabic, mobile-first, themed with your logo and colors. No design work required to launch.
What XPay handles for you
Cards & local methods
Visa, Mastercard, Valu, Fawry, and more. One API for every method on offer.
3D Secure 2
The 3DS challenge runs inside the hosted checkout. We deal with the bank redirect, the iframe, and the result.
Webhooks
Subscribe once. We notify you the moment a payment succeeds, fails, or refunds. Signed payloads, automatic retries, replayable from the dashboard.
Refunds
Issue full or partial refunds from the dashboard or the API. The customer gets their money back through the original payment method.
Test mode
A fully separate environment with its own keys, customers, and transactions. Use the test card list to simulate any outcome you need.
Payouts
Settled funds land in your bank account on the schedule you configure. Every cent is tracked through the balance ledger.
Quick start
Five minutes from a fresh signup to a successful test payment, no code involved. You'll create a product, generate a Payment Link, pay yourself with a test card, and watch the transaction land in your dashboard.
Open the Quickstart
The fastest path through XPay end to end. Five steps, all from the dashboard.
Pick your integration path
There are four ways to take a payment with XPay. They share the same underlying Checkout Session, so the API call and the webhook you receive are identical across all four. The only thing that changes is how much frontend code you write.
If you're not sure which to pick, start with Payment Links. You can move to a richer integration later without rewriting your backend.
Payment Links
Share a URL. No code at all. Best for invoices, social media checkouts, and proving the integration works before you write a line of it.
Hosted Checkout
Your server creates a Checkout Session and redirects the customer to XPay's hosted page. The simplest path that involves any code.
Drop-in
The hosted checkout opens as a modal on top of your site, or embeds inline as an iframe. The customer never leaves your domain.
Elements
Build a fully custom checkout UI using XPay's <PaymentElement />. Most control, most code.
Built for builders
When you outgrow the basics, every layer is exposed.
Inspector
Paste any XPay ID and see the full graph of related resources, the events that fired against it, and the request logs that touched it.
Webhook replay
Click Resend on any past delivery. Your handler gets a fresh, signed event without you having to re-trigger the original payment.
Per-request logs
Every API call your account made: method, path, status, headers, body, response. Filter by error code, drill in by request ID.
Structured errors
Stable error codes paired with deep-link doc URLs. The dashboard tooltip and your own error logs both link straight to the explanation.
Health monitoring
Recent failures grouped by root cause, sorted by frequency. Spot a deploy regression in seconds.
SDKs and framework support
@xpay/sdk-js for vanilla, @xpay/sdk-react for React. Lightweight, typed, framework-agnostic.
Where to next
Quickstart
Take your first test payment in five minutes, no code required.
Choose your integration
A side-by-side comparison of the four patterns with a decision tree at the top. Pick once and don't look back.
Object model
The mental map: how Checkout Session, Payment Intent, Charge, Refund, and Customer fit together, and which IDs to keep on your order record.
API Reference
Every endpoint, every field, every status code. Generated from the live OpenAPI spec, never out of date.