Documentation
Documentation for the gateway that actually exists.
These pages now describe the current Marseille UPG codebase as implemented in this repository. They do not claim features, SDKs, or public APIs that are not present in the running gateway.
Gateway routes only/No fictional SDKs/No invented OpenAPI spec/Live status linked
Gateway API
Public payment entrypoints currently exposed by the gateway: create payment, query order, provider callback, and status.
Open page
Integration flow
How merchants call the gateway, how the gateway calls providers, and how your notify URL receives signed callbacks.
Open page
Operational status
Real runtime health of the gateway, PostgreSQL, Redis, and configured provider connectivity.
Open page
Scope
What these docs do and do not cover.
- This site documents the current gateway implementation in this repository, not a larger product roadmap.
- There is no public refund API, events API, tenant header API, OAuth flow, or official SDK package documented here because those are not exposed by the running gateway.
- Merchant integrations authenticate either with appId + appSecret or the legacy signed mode using timestamp, nonce, and sign.
- Provider callbacks hit the gateway first at /v1/gateway/callback/:provider. Merchant systems receive the gateway's downstream notify payload after internal verification.
Next steps
Start with the real routes and payloads.
If you are integrating right now, go to the API reference first. If you are validating the merchant flow, go to the integration guide.