For developers
One payments API. Integrate once.
Build against a consistent API for checkout, payments, refunds, invoices, links and subscriptions. Allidian routes each transaction to the merchant's approved provider, so your integration doesn't change when providers do.
One application. No sales call. Build in a free sandbox while your provider reviews it.
What gets in the way
Every provider has a different API and webhook format
Retries must never double-charge or double-refund
You need a real sandbox and fast feedback on your integration
Allidian
How we help
REST API + OpenAPI
Predictable resources, stable error codes and request IDs. Generate a client from the OpenAPI 3.1 spec.
Learn moreIdempotency everywhere it matters
Idempotency-Key on every money-moving POST; retries return the original response.
Learn moreAutomated connection tests
One click checks your keys, webhook signature handling and a full sandbox payment, decline and refund.
Learn moreSelf-service
Apply once. Get matched. Integrate once. Accept payments.
- 1
Get test keys
Sign up and create a sandbox secret key.
- 2
Create a checkout session
One server call; redirect or embed.
- 3
Verify webhooks
Copy the verification code for Node, Python or PHP.
- 4
Run the connection tests
Fix anything flagged, then go live with live keys.
Allidian is payment software. Payments are processed by a licensed provider under your own account with them, and the provider decides whether to approve your business. How provider-powered payments work
Frequently asked questions
Which providers does the API support?
One licensed provider is supported today. The API is provider-neutral, so additional providers are added as adapters without changing your integration.
Are sandbox and live separated?
Yes. Keys carry their environment in the prefix (…_sk_test_ or …_sk_live_), and each key can only see objects from its own environment.
Is there an SDK?
There's a browser SDK for embedded checkout (script tag and React component), plus copyable server examples. Any HTTP client works with the REST API.
Related
- Use casesEmbedded checkoutEmbed secure, customizable checkout in your website or React app with a script tag or component. Card data goes straight to the provider.Learn more
- Use casesMulti-provider paymentsIntegrate payments once and route to supported providers through independent adapters. Each payment stays with the provider that processed it.Learn more
- SolutionsSaaS companiesRecurring billing, trials, invoices, hosted or embedded checkout and signed webhooks for SaaS products. Build in a free sandbox, no sales call.Learn more
Apply once. Start accepting payments.
Tell us about your business in one short application. We match you with a licensed payment provider, and your tools switch on when they approve you.
No sales call required. Create an account and access your developer sandbox.
- Payment succeeded$248.00 · Hosted checkout
- Invoice paidINV-0142 · $5,616.00
- Webhook deliveredpayment.succeeded · 200 OK