Use this endpoint to submit a card payment through Accelebit. You provide the card details, billing information, amount, and currency, and Accelebit routes the transaction to the optimal upstream provider based on currency and availability. The response tells you whether the payment was captured immediately, requires 3D Secure authentication, or failed.Documentation Index
Fetch the complete documentation index at: https://docs.accelebit.com/llms.txt
Use this file to discover all available pages before exploring further.
Always supply a unique
Idempotency-Key on every request. If a request is retried with the same key, Accelebit returns the original response without creating a duplicate payment.Headers
Your secret API key. Starts with
smtgw_sk_.A unique key to prevent duplicate payments. Use a UUID or an order-specific identifier.
Must be
application/json.Request body
Payment amount as a decimal string. For example:
"55.00" or "100.50". Maximum two decimal places.Three-letter ISO 4217 currency code. Automatically uppercased. For example:
"EUR", "USD", "GBP".Payment method type. One of
card or stored_card.Your external customer identifier. Used to resolve or create a customer record in Accelebit.
Card details. Required when
paymentMethod is card.UUID of a previously stored card. Required when
paymentMethod is stored_card.Billing information for the cardholder.
Your own reference ID, such as an order number. You can use this value to look up the payment later via
GET /v1/payments?merchantRef=....URL to redirect the customer to after 3D Secure authentication completes. Required if your integration handles 3DS flows.
Device fingerprint string. Maximum 128 characters. Passed to the upstream provider for fraud scoring.
Arbitrary key-value pairs to attach to this payment. Stored by Accelebit but not forwarded to providers.