Technical documentation

Take card payments from your own system.

Three ways to integrate, a contract verified against the live API every day, and ready-made clients for PHP, TypeScript and Python. Everything technical is here and public: you do not need an account to read it, or to try it.

See connectors Start integrating

On a known platform, you write no code

Download the connector, paste your key, and you are taking cards.

WooCommerceDescargable OdooBeta ShopifyPlanificado PrestaShopPlanificado

MagentoPlanificado SAP Business OneA pedido

ZohoPlanificado QuickBooksPlanificado

SalesforceA pedido

See the setup steps for each one →

The three ways to charge

1Hosted checkoutCreate the payment and redirect to a ROKI page. No frontend work and no exposure to card data.

2Embedded componentsROKI renders the card fields in an iframe on your own site. The customer never leaves your page.

3Saved cardsCharge a card the customer already saved, with them not present. Requires per-merchant authorisation.

For coding agents

If you integrate with a coding assistant, ROKI publishes a Model Context Protocol server carrying the same contract as this documentation, plus a validator and a sandbox that makes real calls using no key of yours:

claude mcp add --transport http roki-connect https://mcp.roki.la/mcp

The specification, this guide in markdown and an index for agents are published too.

What breaks most often

Quickstart →...Creating a payment →7.1 Required fields Field Type Rule amount number Minimum 0.01. Decimal units, not cents (150.50 = L 150.50). No ma...Webhooks →They are the authoritative confirmation of a charge. Without them, an integration depends on the customer returning...Error catalogue →HTTP When Shape 401 Missing Authorization or invalid key {"message": "..."} 404 (application) The payment does not ...