Buckaroo Checkout JSON Gateway API
62
AI ReadinessAI-Aware (B-)62/100
Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey15 EndpointsREST
For Agents
Create and track payment transactions, run KYC data requests, and validate IBANs across European payment methods on the Buckaroo gateway.
Use for: Create an iDEAL payment for 49.99 EUR on Buckaroo, I need to check the status of a Buckaroo transaction by its key, Cancel a pending Buckaroo transaction, Validate a Dutch IBAN before initiating a SEPA payment
Not supported: Does not handle merchant onboarding, payout reporting, or accounting reconciliation files - use for transaction creation, status, refunds, and IBAN validation only.
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.
Install Jentic One Beta
Connect the Buckaroo Checkout JSON Gateway API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buckaroo Checkout JSON Gateway API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbuckaroo.io%2Fbuckaroo-io" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbuckaroo.io%2Fbuckaroo-io" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Buckaroo Checkout JSON Gateway 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
Retrieve invoice information for issued credit invoices via invoice key
Run a Buckaroo data request for KYC, age verification, or address verification before payment
Validate or convert IBAN and BBAN strings via the gateway's tools endpoints
Use Cases
Patterns agents use Buckaroo Checkout JSON Gateway 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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
Buckaroo Checkout JSON Gateway API
- AI-Aware (B-)62/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility42
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
42
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
19%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Buckaroo JSON Gateway by hand means computing the per-request HMAC-SHA256 Authorization header from your website key and secret and coordinating transaction, status, and refund endpoints yourself. Through Jentic you install once, import the Buckaroo Checkout JSON Gateway API from the API Directory, store the website key and secret once, and your agent calls it.
Permission scoping
Buckaroo puts the transaction key in the URL path (/json/Transaction/Status/{transactionKey}, /json/Transaction/Cancel/{transactionKey}), so a rule can pin your agent to one transaction: it can read that transaction's status and refund info and nothing else. You choose the operations it may call, so creating or cancelling a transaction is not included unless you add it.
Credential isolation
Your Buckaroo website key and secret are stored once, encrypted, by your own Jentic One instance, which computes the HMAC-SHA256 Authorization header at execution time. The secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an iDEAL payment', and Jentic returns the matching createTransaction operation with its Services schema so the agent calls /json/Transaction without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Buckaroo Checkout JSON Gateway 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.
Can I limit what my agent is allowed to do with the Buckaroo Checkout JSON Gateway API?
Yes. Because you run Jentic One yourself, your own rules decide which Buckaroo operations and credentials the agent may use, so you can allow only what a task needs. Since the transaction key sits in the URL path on operations like /json/Transaction/Status/{transactionKey} and /json/Transaction/RefundInfo/{transactionKey}, a rule can pin the agent to a single transaction and let it read only that status and refund info. Creating a payment on /json/Transaction or cancelling one on /json/Transaction/Cancel/{transactionKey} stays off limits unless you explicitly grant it, and your website key and secret are held by your instance rather than the agent.
GET STARTED