SDKs and plugins
SDKs in three languages and a shop plugin generated against the same operation table as the API, so an SDK cannot describe a call the platform does not have.
Developers who would rather ship this week, and shop owners who want a checkout without hiring one.
Part of the platform itself: it is present wherever BitriPay runs.
The problem
Every integration re-implements the same plumbing, and each re-implementation is a fresh opportunity to get webhook verification subtly wrong in a way that nobody notices until it matters.
How it works
- Install the SDK for your language, or the plugin for your shop.
- Authentication, idempotency and signature verification are handled for you.
- Create an intent and handle the webhook with typed objects rather than raw JSON.
- Test against the sandbox with the documented magic numbers before going near a real payment.
What you can check
Facts about the running platform rather than adjectives. Each one is visible in the product, the API reference or the ledger.
- SDKs are generated against the same operation table that serves the requests, so they cannot describe a call the platform does not have.
- Webhook signature verification is implemented in the SDK, which is where most hand-rolled integrations get it wrong.
- The shop plugin ships in the repository rather than being distributed separately, so its version matches the API it was built against.
- The Node SDK has no dependencies, so adding payments does not add a supply chain.
What it costs
Free. Open code in the repository, and no licence to use them.
Questions
Do I have to use an SDK?
No. The API is plain HTTP with JSON and is documented completely. The SDKs exist to save you from writing signature verification again, not to hide anything.
Which languages?
Node, PHP and Python, plus a WooCommerce plugin for shops. The Node SDK deliberately has no dependencies.
Will the SDK fall behind the API?
It is generated against the same operation table the API is served from, so it cannot describe a call that does not exist. Where a brand-new capability has not reached an SDK yet, the raw call always works.
Read next
The gateway API
A payments API whose documentation is generated from the same table that serves the requests, so the reference can never describe an endpoint the platform does not have.
Signed webhooks
Deliveries you can verify two independent ways, replay yourself from the dashboard, and receive on a built-in inbox if you have nowhere to host an endpoint yet.
Hosted checkout
A checkout that offers the payer only the rails that can actually complete their payment, decided at the moment they arrive rather than listed hopefully on a page.