SDKs

Ideal for: Building the integration yourself, in your own language, without writing HTTP calls or handling card data directly. SeerBit’s SDKs wrap the same APIs documented elsewhere in these docs. They carry the same security properties as Simple Checkout and Standard Checkout — sensitive data goes to SeerBit, never through your own storage.

​

SDK or a direct integration?

An SDK is a convenience layer, not a different product — a payment taken through one appears in your dashboard exactly like any other.

​

Server libraries

Use these on your backend, where your secret key lives. They wrap token generation, payment initialisation and verification.

Keep your secret key on the server. These libraries are for backend use — see authentication.

​

Web frameworks

Drop-in components that open the SeerBit checkout from your front end. Card details are entered inside SeerBit’s own form, so they never touch your code.

​

Mobile

Each mobile platform offers two builds. The web view builds are recommended — they render SeerBit’s hosted checkout inside your app, so they pick up new payment methods automatically and keep card entry out of your codebase. The native builds give you more control over the interface, at the cost of maintaining it.

​

Notes

• All SDKs carry the same security properties as the other integration methods, and none of them require PCI DSS certification — card details are entered in SeerBit’s own form.
• Your public key belongs in client code; your secret key does not. Web and mobile SDKs need only the public key.
• SDKs use the same keys and modes as everything else. Test keys give you test transactions — see test and live modes.
• No SDK for your platform? Every one of these wraps the same REST API, so you can integrate directly — start with Accept Payments.