1
Get your API keys
Sign in to the Accelebit Dashboard and navigate to Developers > API Keys. You will see two types of keys:
All API requests require your secret key in the
X-API-Key header. During development, use a test key (prefixed smtgw_sk_test_) — it will never trigger real charges.2
Create a customer
Before processing payments, create a customer record. The Save the returned
externalId field is your own identifier for this customer — for example, your internal user ID.id — you will pass it as customerId in the next step.3
Create a test payment
Send a A
POST /v1/payments request with the card details, billing address, and the customer ID from the previous step. Pass amounts as decimal strings (for example, "55.00", not the integer 5500)."status": "captured" response means the payment was authorised and captured successfully.If the response contains
"threeDsRequired": true, the cardholder must complete a 3D Secure challenge before the payment can be captured. Follow the redirect instructions in the 3D Secure guide to complete the flow.4
Handle webhooks
Configure a webhook endpoint in the Dashboard to receive real-time payment notifications. When a payment completes, Accelebit sends a Use webhooks rather than polling to update your order state reliably. See Webhooks for signature verification and retry behavior.
payment.captured or payment.failed event to your endpoint:5
Check payment status
You can query the current status of any payment at any time using its This is useful for reconciliation or to confirm a payment’s final state after a webhook event.
id:Next steps
Authentication
Understand API key types, key management, idempotency, and rate limits.
Server-to-server guide
Complete integration walkthrough including 3D Secure handling.
Webhooks
Set up signature verification and understand retry behavior.