Buckaroo Checkout JSON Gateway API

Name: Buckaroo Checkout JSON Gateway API API
Brand: Buckaroo Checkout JSON Gateway API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey15 EndpointsREST

For Agents

Create and track payment transactions, run KYC data requests, and validate IBANs across European payment methods on the Buckaroo gateway.

Quickstart

Get started with Buckaroo Checkout JSON Gateway API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an iDEAL payment"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Buckaroo Checkout JSON Gateway API API.

Create a payment transaction with iDEAL, card, SEPA Direct Debit, Klarna, or other Buckaroo-supported services

Poll transaction status by key or fetch statuses for multiple transaction keys in one request

Cancel a single transaction or batch-cancel multiple transactions in one call

Fetch refund eligibility and pre-filled refund info for a transaction key before issuing the refund

GET STARTED

Start building with Buckaroo Checkout JSON Gateway API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Buckaroo Checkout JSON Gateway API, keeping it validated and agent-ready.

Buckaroo's Checkout JSON Gateway is the European payment gateway API used by Dutch and EU merchants to create transactions across iDEAL, credit cards, SEPA Direct Debit, Bancontact, Klarna, and Apple Pay. The spec covers transaction creation, single and multi-key status polling, cancellation, refund and invoice lookup, KYC and verification data requests, and IBAN validation. This buckaroo.nl import describes the same gateway base URL exposed at checkout.buckaroo.nl and is the integration surface for online checkouts that need to settle in EUR through Buckaroo.

Use Cases

Patterns agents use Buckaroo Checkout JSON Gateway API API for, with concrete tasks.

★ Dutch and EU Online Checkout

Accept payments in EUR for Dutch and broader EU consumers by creating a transaction on /json/Transaction with the chosen Service such as ideal, paybycard, or sepadirectdebit. Buckaroo returns either a final status or a redirect URL the consumer follows to authorise the payment, after which the merchant polls /json/Transaction/Status/{transactionKey} until the transaction settles. End-to-end integration takes a few days when the merchant already has a Buckaroo contract.

POST to /json/Transaction with Services.ServiceList containing ideal, AmountDebit 49.99, Currency EUR, and the order Invoice number, then return the redirect URL

Batched Status Reconciliation

Reconcile end-of-day transaction state by sending a list of transaction keys to /json/Transaction/Statuses to retrieve the current status for each in a single request. This is faster than polling each key individually, especially for merchants processing thousands of daily transactions, and feeds nightly batch jobs that update an internal ledger.

POST a list of transaction keys from the day's orders to /json/Transaction/Statuses and update the internal ledger with each returned status

Pre-Payment KYC and IBAN Validation

Reduce failed direct debits and chargebacks by running a Buckaroo data request via postDataRequest for KYC, age, or address checks, and validating the consumer's IBAN with /json/Tools/IbanConverter/{iban} before submitting the payment. For Dutch BBAN inputs, /json/Tools/BbanToIbanConverter/{bban} converts to the full IBAN format required by SEPA. Validation happens in a single round trip.

GET /json/Tools/IbanConverter/{iban} with the customer-supplied IBAN and reject the checkout if the response indicates the IBAN is invalid

AI Agent Payment Initiation Through Jentic

Allow an AI agent to initiate a Buckaroo payment on a user's behalf without holding the merchant's website key or secret key. Through Jentic, the agent searches for transaction creation, loads the postTransaction schema, and executes against /json/Transaction with the order details. The Buckaroo HMAC Authorization header is computed by Jentic from the secret stored in the vault so the credentials never enter the agent's context.

Use Jentic to search 'create a Buckaroo iDEAL payment', load the postTransaction schema, and execute with the order amount and Service ideal

Key Endpoints

15 endpoints — buckaroo's checkout json gateway is the european payment gateway api used by dutch and eu merchants to create transactions across ideal, credit cards, sepa direct debit, bancontact, klarna, and apple pay.

METHOD

PATH

DESCRIPTION

POST

/json/Transaction

Create a new payment transaction with a chosen service

GET

/json/Transaction/Status/{transactionKey}

Get the status of a single transaction

POST

/json/Transaction/Statuses

Get statuses for multiple transaction keys

GET

/json/Transaction/Cancel/{transactionKey}

Cancel a pending transaction

GET

/json/Transaction/RefundInfo/{transactionKey}

Retrieve refund eligibility and amount for a transaction

POST

/json/DataRequest

Run a KYC or verification data request

GET

/json/Tools/IbanConverter/{iban}

Validate an IBAN string

GET

/json/Transaction/InvoiceInfo/{invoiceKey}

Retrieve credit invoice details by invoice key

POST

/json/Transaction

Create a new payment transaction with a chosen service

GET

/json/Transaction/Status/{transactionKey}

Get the status of a single transaction

POST

/json/Transaction/Statuses

Get statuses for multiple transaction keys

GET

/json/Transaction/Cancel/{transactionKey}

Cancel a pending transaction

GET

/json/Transaction/RefundInfo/{transactionKey}

Retrieve refund eligibility and amount for a transaction

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Buckaroo website key and secret key are stored encrypted in the Jentic vault. Jentic computes the per-request HMAC-SHA256 Authorization header at execution time so the raw secret key never enters the agent's context, prompts, or logs.

Intent-based discovery

Agents search by intent (e.g., 'create an iDEAL payment') and Jentic returns the matching postTransaction operation with its Services schema, so the agent calls /json/Transaction without learning Buckaroo's HMAC signing rules.

Time to first call

Direct Buckaroo integration: 3-5 days for HMAC signing, redirect handling, status polling, and error-code mapping. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Buckaroo Checkout JSON Gateway API

Same Buckaroo Checkout JSON Gateway sourced from the buckaroo.io vendor docs

Choose the buckaroo.io spec when you prefer the vendor-official documentation source; both target the same gateway

Complementary

Bud Financial API

Open Banking aggregation that can verify account ownership before a SEPA Direct Debit

Pair Bud with Buckaroo when an agent should confirm a payer's bank account before initiating a SEPA mandate

Alternative

Buddy PT API

Alternative payments-adjacent integration for a different European market

Choose when the merchant operates outside Buckaroo's primary Benelux footprint

FAQs

Specific to using Buckaroo Checkout JSON Gateway API API through Jentic.

What authentication does the Buckaroo Checkout JSON Gateway API use?

Buckaroo uses an apiKey-style Authorization header that contains an HMAC-SHA256 signature computed from the website key, secret key, request method, URL, timestamp, nonce, and request body hash. Through Jentic the website key and secret key are stored encrypted in the vault and the signature is computed at execution time so the secret key never enters the agent's context.

Can I create an iDEAL payment with the Buckaroo API?

Yes. POST to /json/Transaction with Services.ServiceList containing ServiceName 'ideal', the AmountDebit, Currency 'EUR', Invoice number, and ClientIP. Buckaroo returns a RequiredAction with a RedirectURL for the consumer's bank, plus a transaction key you can poll on /json/Transaction/Status/{transactionKey} to confirm settlement.

What are the rate limits for the Buckaroo API?

Buckaroo does not publish a global per-second rate limit in the spec. Production traffic is shaped by the merchant agreement and abuse-protection limits applied to the gateway. If a request is throttled the API returns an error response and clients should back off before retrying.

How do I check a Buckaroo transaction status through Jentic?

Install the SDK with pip install jentic, search for 'check Buckaroo transaction status', load the getTransactionStatus schema, and execute it against /json/Transaction/Status/{transactionKey} with the transaction key. Jentic computes the HMAC Authorization header from the vault and returns the parsed status response.

Can I refund a transaction with this API?

Yes. First call getTransactionRefundInfo on /json/Transaction/RefundInfo/{transactionKey} to confirm the refundable amount and pre-filled fields, then create a new refund transaction via /json/Transaction with the appropriate refund Service and the original transaction key in OriginalTransactionKey.

Can I validate an IBAN before charging?

Yes. GET /json/Tools/IbanConverter/{iban} returns whether the IBAN is structurally valid and, where supported, the bank name. For Dutch BBAN inputs, /json/Tools/BbanToIbanConverter/{bban} converts to full IBAN. Use this before initiating SEPA Direct Debit to avoid downstream chargebacks for invalid account numbers.