# Introduction (/en) 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? [#what-is-xpay] Take Visa and Mastercard alongside local methods like Valu and Fawry. 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. Take a payment, manage the customer, issue refunds, and pay yourself out. All in one dashboard and one API, from sale to bank. 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 [#what-xpay-handles-for-you] Visa, Mastercard, Valu, Fawry, and more. One API for every method on offer. The 3DS challenge runs inside the hosted checkout. We deal with the bank redirect, the iframe, and the result. Subscribe once. We notify you the moment a payment succeeds, fails, or refunds. Signed payloads, automatic retries, replayable from the dashboard. Issue full or partial refunds from the dashboard or the API. The customer gets their money back through the original payment method. A fully separate environment with its own keys, customers, and transactions. Use the test card list to simulate any outcome you need. Settled funds land in your bank account on the schedule you configure. Every cent is tracked through the balance ledger. ## Quick start [#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. The fastest path through XPay end to end. Five steps, all from the dashboard. ## Pick your integration path [#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. 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. Your server creates a Checkout Session and redirects the customer to XPay's hosted page. The simplest path that involves any code. The hosted checkout opens as a modal on top of your site, or embeds inline as an iframe. The customer never leaves your domain. Build a fully custom checkout UI using XPay's `PaymentElement` component. Most control, most code. ## Built for builders [#built-for-builders] When you outgrow the basics, every layer is exposed. 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. Click **Resend** on any past delivery. Your handler gets a fresh, signed event without you having to re-trigger the original payment. Every API call your account made: method, path, status, headers, body, response. Filter by error code, drill in by request ID. Stable error codes paired with deep-link doc URLs. The dashboard tooltip and your own error logs both link straight to the explanation. Recent failures grouped by root cause, sorted by frequency. Spot a deploy regression in seconds. `@xpayeg/sdk` for vanilla, `@xpayeg/react` for React. Lightweight, typed, framework-agnostic. ## Where to next [#where-to-next] Take your first test payment in five minutes, no code required. A side-by-side comparison of the four patterns with a decision tree at the top. Pick once and don't look back. The mental map: how Checkout Session, Payment Intent, Charge, Refund, and Customer fit together, and which IDs to keep on your order record. Every endpoint, every field, every status code. Generated from the live OpenAPI spec, never out of date.