How OneGate works
The model you integrate against, independent of any single provider.
| Host | Purpose |
|---|---|
api.onegate.am | The REST API your server calls, and the endpoint providers send callbacks to. |
pay.onegate.am | Hosted checkout your customers are redirected to. |
app.onegate.am | Dashboard: connections, keys, webhooks, payments, refunds. |
docs.onegate.am | This documentation and the OpenAPI document. |
Objects
- Payment — what you charge (amount, currency, your
order_id). Its status is the source of truth. - Attempt — one try to pay with one method and provider. A payment can have several.
- Provider connection — your credentials for one provider, in Test or Live.
- Refund — a separate object linked to a completed payment.
- Event — an immutable record of a change, delivered to your webhook endpoints.
Provider-independent integration
You never call a bank or wallet directly. Create a payment; checkout shows the methods your active connections support for that amount and currency. Adding, removing or switching a provider is a dashboard change: your code, webhooks and statuses stay the same.
OneGate is non-custodial. Providers settle to your account under your own agreements; OneGate never holds funds.
Sources of truth
OneGate combines provider callbacks with active status checks (reconciliation) and only applies valid state transitions. The return_url redirect is a convenience for the customer, not a payment confirmation — rely on webhooks or GET /v1/payments/{id}.