Two credential types.
#Server client (all money operations)
A registered Ed25519 key pair. Exchange a signed client assertion for a short-lived access token, then prove possession on every request with DPoP.
POST /v1/auth/tokenwith your client assertion and a DPoP proof. The response containsaccess_tokenandtoken_type: "DPoP".- Send
authorization: DPoP <access_token>and a freshdpop: <proof>header on every request.
The proof is bound to the token and to the request URL and method. Reusing a proof is rejected.
You do not need to implement this by hand. @paygate/server does the key handling, token exchange and proofs for you. Use the raw flow only if you are writing a client in another language.
#Publishable key (browser and mobile bundles)
pk_sandbox_... or pk_live_.... Read-only and origin-bound:
- Allowed:
GET /v1/payment_methods. - Refused: anything that moves money (
403 publishable_key_forbidden).
It is safe to ship in a bundle because it can only read methods, and only from the origins registered when the key was created.