Fast API integration
A plugin in minutes or a clean REST API in a day, depending on how your site is built.
If you run WooCommerce, PrestaShop or Magento, you install a plugin and enter your keys. If you have your own platform, you work against a REST API with predictable responses and detailed documentation.
The sandbox is available immediately after approval, so integration can run in parallel with the paperwork.
What you get
REST API
Versioned, stable endpoints.
Webhooks
Signed real-time notifications with retries.
SDKs
PHP, Node.js and Python.
Ready plugins
WooCommerce, PrestaShop, Magento, OpenCart.
Idempotency keys
Protection against double charging on a repeated request.
Sandbox
A full test environment with test cards.
How it works
Keys
You get sandbox keys right after approval.
Integration
Plugin or API, whichever suits your platform.
Testing
Verify a payment, a refund and the webhook.
Production
Swap the keys and go live.
A plugin in minutes or an API in a day
The choice depends on how your site is built, not on how good your developer is.
If you run WooCommerce, PrestaShop or OpenCart, the plugin is the right answer. Install it, paste the keys from the panel, pick which methods to show and you are done. The plugin supports refunds straight from the shop admin, so you are not in two panels for one operation.
If you have your own application, a non-standard basket or you sell across several channels at once, the REST API gives you the control you need. Requests are JSON, responses are JSON, errors have stable codes rather than free text that shifts between versions.
Either way there is a test environment with cards for every scenario: success, insufficient funds, expired card, failed 3-D Secure, chargeback. You test the whole flow before a single real payment goes through.
Three things that save days of debugging
Idempotency. Every payment request carries a key you generate. If the connection drops and the customer presses again, the same key returns the same result instead of creating a second payment. This is the most common cause of double charges with providers that lack it.
Webhooks instead of polling. When a payment's state changes, we send you a message. You do not have to ask every thirty seconds whether anything happened. Every message is signed, so you can verify it really came from us.
Stable error codes. A decline for insufficient funds and a decline for a blocked card carry different codes and deserve different handling. If your system treats them alike, you lose sales that were recoverable.
What your developer should prepare
The list is short, and it is better cleared before the start than halfway through.
HTTPS across the whole site, not just the payment page. Somewhere to keep our keys outside the code, environment variables for instance. A webhook endpoint that answers quickly and returns 200 even when the internal processing takes time. Logs that never contain card data. And a decision about what the system does when a payment succeeds but your server was unreachable at that moment.
That last one is the most underestimated and is exactly what produces orders that are paid but not recorded. Webhooks are retried on failure, so with correct handling such an order closes itself.
What to test before going live
A successful payment tests itself, because everybody tries it first. The trouble comes from the scenarios nobody checks until they happen in real life.
Decline for insufficient funds. Does your site show an understandable message or a raw error code. Does the basket survive so the customer can try another card.
Interrupted 3-D Secure. The customer was redirected to the bank and closed the tab. What happens to your order. It must not sit pending forever.
Double submit. Press the button twice quickly. If you get two payments, the idempotency key is not wired correctly.
Webhook with your server down. Stop your server, make a payment, bring it back. The message should be redelivered and the order should close itself.
Refunds, partial and full. Check too that the amount is offset correctly in the next settlement.
The test environment has cards for every one of these, so the whole list takes an hour.
What your developer gets on day one
Everything is available as soon as the account is opened, with no waiting and no phone calls.
- Keys for the test and the live environment
- Documentation with curl, PHP and JavaScript examples
- Test cards for every scenario, including declines
- Ready plugins for WooCommerce, PrestaShop and OpenCart
- A tool for inspecting webhook messages
- Direct contact with someone who knows the integration
Questions about this
How long does integration really take?
With a plugin, about an hour. With your own API, usually one business day for a standard payment flow. If you have subscriptions, saved cards and refunds, set aside two to three days for unhurried testing.
Is there a request limit?
There is a sensible limit that normal trading never touches. If you expect a spike, a campaign or a ticket on-sale for instance, tell us in advance and we raise it.
How do I verify a webhook came from you?
Every message carries a signature made with the shared secret from the panel. Your developer computes the signature and compares. Examples are in the documentation for all three languages.
What happens when your API changes?
Versions are preserved. Breaking changes ship under a new version while the old one keeps working. You do not wake up to a broken checkout.
Can you do the integration for us?
For standard cases we help with setup and a code review at no charge. For a non-standard project we agree separately, but it usually turns out faster for your own developer to do it with our support.
Do you provide an SDK for a particular language?
The documentation carries curl, PHP and JavaScript examples, which cover most cases. For Python, .NET or Java we supply working examples on request, rather than maintaining libraries that age faster than the API itself.
How do I keep test and live transactions apart?
The two environments have separate keys and separate panels. A test transaction cannot land in your live report even with a mixed-up key, because the key decides the environment.
Ready to start accepting payments?
Send us an enquiry and you will get a concrete quote with calculated fees for your business, usually within one business day.