Website payments
Create a payment on your server, send the browser to
checkout_url, and take the verdict from the
webhook. Card numbers never reach your page.
Take mobile money and card on your website, in your app, or through a link you can send. Pay the sellers who earned it from the same balance.
Start with the one that matches how your customer already buys. The API, the balance and the webhook are the same whichever you add next.
Create a payment on your server, send the browser to
checkout_url, and take the verdict from the
webhook. Card numbers never reach your page.
@paygate/mobile opens the payment and resolves only
once your server has confirmed it. No native modules, and no
secret key in the app bundle.
Split a payment to the seller who earned it, hold it until delivery, then settle to their mobile money or bank. A payout can never overdraw the balance.
Payouts and releasesNo integration at all: create a fixed-price link, send the URL, and see what it collected. The buyer pays in the same checkout everything else uses.
Create a link
POST /v1/payments with an amount and your own
reference. Every write takes an idempotency key, so a retry is a
replay, never a second charge.
Mobile money prompts their phone; cards finish on a page we host. You never write a provider integration and never store card data.
succeeded only appears after the provider confirms
it. Poll the payment, or take the signed webhook and ignore the
noise.
Running a marketplace? Release the payment when the work is delivered and settle to the seller's own destination. How payouts work →
Create sandbox credentials yourself — no operator, no waiting. Sandbox payments run on the simulator, so you can build the whole flow before a provider account exists. The signup page issues a scoped, revocable key; the quickstart creates and confirms a payment in about five minutes.
Building with an AI agent? Point it at llms.txt and llms-full.txt for the whole integration guide as plain text.