Create a custom-provider PaymentSession as a server
Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.
All HTTP operationsCreates the bounded server-only bridge for a caller-managed payment provider. This is not integration-managed execution and does not expose provider credentials.
publishableKeyserverSecretKeyX-Publishable-Key<token>Tenant publishable key for authentication (sent via X-Publishable-Key header)
AuthorizationBearer <token>Public integration credential: opaque sk01_ secret API key only; PAT and Customer JWT are not supported by this scheme. Requires tenant binding and the read or write scope named by the operation.
X-Idempotency-Key*stringCaller-generated retry identity. Reuse the same key only when retrying the same logical operation.
^(?:[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-4[0-9a-fA-F]{3}-[89aAbB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|ik_[A-Za-z0-9_-]{22})$length <= 255application/json- body
provider*string^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$1 <= length <= 64checkoutToken*string1 <= length <= 512Create a custom-provider PaymentSession as a server result
application/json- response
id*string1 <= length <= 255provider*string^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$1 <= length <= 64providerSessionId*string\S1 <= lengthmoney*Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.
curl -X POST 'https://api.01.software/api/orders/custom-payment-sessions' \ -H 'X-Idempotency-Key: string' \ -H 'Content-Type: application/json' \ -d '{ "provider": "string", "checkoutToken": "string"}'{ "id": "string", "provider": "string", "providerSessionId": "string", "money": { "amountMinor": 0, "currency": "string" }}