Buckaroo Checkout JSON Gateway API

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

✓ Official Vendor SpecPaymentsPayment 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 call

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

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

GET STARTED

Start building with Buckaroo Checkout JSON Gateway API API

Explore with Jentic

View OpenAPI Document

Buckaroo's Checkout JSON Gateway is the European payment gateway API used to create transactions across iDEAL, credit cards, SEPA Direct Debit, Bancontact, Klarna, Apple Pay, and other European payment methods. The spec covers transaction creation, status polling for single and multiple keys, cancellation, refund and invoice lookup, data request operations for KYC and additional consumer information, and IBAN/BBAN validation tools. It is the primary integration surface for online merchants who need to accept payments in the Netherlands and broader EU through Buckaroo.

Use Cases

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

★ European Checkout with iDEAL and SEPA

Accept payments in the Netherlands and the wider EU by creating a transaction on /json/Transaction with the chosen Service (e.g. ideal, sepadirectdebit, paybycard) and the order amount, currency, and invoice number. Buckaroo returns either a final status or a redirect URL for the consumer to authorise the payment, which a checkout flow can present and then poll via getTransactionStatus. 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, an AmountDebit of 49.99, Currency EUR, and an Invoice number, then return the redirect URL

Refund and Invoice Reconciliation

Reconcile completed transactions with finance records by calling getRefundInfo for any transaction key needing a refund, and getInvoiceInfo for invoice keys to retrieve credit invoice details. Combined with getMultipleTransactionStatuses for batch polling, this powers nightly reconciliation jobs and customer-service refund tooling without screen-scraping the Buckaroo dashboard.

Call getRefundInfo on /json/Transaction/RefundInfo/{transactionKey} for a customer's transaction, confirm refundable amount, then create the refund transaction

Pre-Payment KYC and IBAN Validation

Reduce failed direct-debit attempts and fraud by running a Buckaroo data request via performDataRequest for KYC, age, or address verification, and validating the consumer's IBAN with /json/Tools/IbanConverter/{iban} before submitting the payment. This is especially useful for SEPA Direct Debit flows where invalid IBANs cause downstream chargebacks. Validation happens in a single round trip per consumer.

Call validateIban on /json/Tools/IbanConverter/{iban} with the customer's IBAN and reject the checkout if the response indicates an invalid IBAN

AI Agent Payment Initiation Through Jentic

Allow an AI agent to initiate a Buckaroo payment on a user's behalf without ever holding the merchant's website key or secret key. Through Jentic, the agent searches for transaction creation, loads the createTransaction 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 createTransaction 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 to create transactions across ideal, credit cards, sepa direct debit, bancontact, klarna, apple pay, and other european payment methods.

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

POST

/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

POST

/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 createTransaction 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.

Complementary

Buckaroo Plaza API

Buckaroo's merchant-management surface complementing the Checkout JSON Gateway

Use the Plaza API alongside the Checkout JSON Gateway when an agent needs to manage merchant settings rather than process individual transactions

Complementary

Bud Financial API

Open Banking aggregation that can verify account ownership before a Buckaroo 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 is operating 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 Buckaroo 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 getRefundInfo 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 the OriginalTransactionKey field.

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.