Pay.nl Transaction Gateway API
★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbasic12 EndpointsREST
For Agents
Create and manage Pay.nl payment orders, process captures, voids, and refunds, handle multi-step payment approval flows, and track transaction status across European payment methods.
Use for: I need to create a Pay.nl payment order for 49.99 EUR, Check the status of a Pay.nl order, Capture a payment after shipping the product, Issue a partial refund for a returned item
Not supported: Does not handle recurring subscriptions, invoicing, or complex multi-merchant marketplace splits — use for single-merchant payment order processing with standard capture/void/refund workflows only.
Pay.nl Transaction Gateway API enables merchants to create and manage payment orders across multiple European payment methods. The API handles the full payment lifecycle from order creation through capture, void, and refund operations. Merchants can update order amounts before payment, approve or decline orders manually, retry failed transactions, and track order status in real time. The gateway supports flexible payment workflows including partial captures by amount or product line item.
Install Jentic One Beta
Connect the Pay.nl Transaction Gateway API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pay.nl Transaction 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Pay.nl Transaction Gateway API.
Create payment orders with service ID, amount, return URL, and optional payment method selection
Update order details including amount and description before payment is completed
Retrieve order status with full payment history and state information
Approve or decline pending orders for manual fraud review workflows
Capture full order amount or specific amounts with partial capture support
Capture specific product line items for split fulfillment scenarios
Void authorized orders before capture to release held funds
Abort orders in progress to cancel the transaction flow
Retry failed orders to give buyers a second payment attempt
Add additional payments to existing orders for split payment flows
Manage order lifecycle from creation through final settlement with detailed status tracking
Use Cases
Patterns agents use Pay.nl Transaction Gateway API for, with concrete tasks.
★ European E-Commerce Checkout
Online merchants in the Netherlands, Belgium, and Germany integrate Pay.nl to accept local payment methods like iDEAL, Bancontact, and SEPA. The merchant creates an order with POST /orders including the cart total and shopper return URL, then redirects to the payment page. After the buyer completes payment, the merchant captures the order or voids it if the order is cancelled. The gateway supports both immediate capture and authorize-then-capture flows.
Create a Pay.nl order for €89.99 with iDEAL as the payment method and redirect the customer to complete payment
Delayed Capture for Physical Goods
Merchants selling physical products authorize payment at checkout but delay capture until items ship. After creating the order, they call PATCH /orders/{id}/approve to pass fraud checks, then PATCH /orders/{id}/capture when the warehouse confirms shipment. If the order is cancelled before shipping, they call PATCH /orders/{id}/void to release the authorization without charging the buyer.
Authorize a payment for €150, hold the funds, and capture them only after the warehouse confirms shipment — or void if the item goes out of stock
Partial Capture for Split Fulfillment
When orders contain multiple items that ship separately, merchants use partial capture to charge for each fulfilled batch. After creating the order for the full amount, they call PATCH /orders/{id}/capture-products with the specific product IDs that shipped, or PATCH /orders/{id}/capture-amount with the dollar amount. Unshipped items remain authorized and can be captured or voided later.
Capture €45 from a €120 order when the first two items ship, then capture the remaining €75 when the backordered item arrives
AI Agent Payment Operations
Through Jentic, AI agents can manage Pay.nl transactions — creating orders, checking status, capturing payments, and processing refunds — without holding the merchant's API credentials directly. Jentic isolates the basic auth token per call and returns structured responses that agents can reason over, enabling automated payment workflows for European commerce platforms.
Search Jentic for 'create pay.nl order', load the schema for POST /orders, and execute it for a €59 test transaction with iDEAL
Key Endpoints
12 endpoints — pay.
METHOD
PATH
DESCRIPTION
POST
/orders
Create a new payment order
GET
/orders/{id}/status
Check order status with payment details
PATCH
/orders/{id}
Update order amount or description
PATCH
/orders/{id}/capture
Capture full order amount
PATCH
/orders/{id}/capture-amount
Capture specific amount
PATCH
/orders/{id}/void
Void an authorized order
POST
/orders
Create a new payment order
GET
/orders/{id}/status
Check order status with payment details
PATCH
/orders/{id}
Update order amount or description
PATCH
/orders/{id}/capture
Capture full order amount
PATCH
/orders/{id}/capture-amount
Capture specific amount
PATCH
/orders/{id}/void
Void an authorized order
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Pay.nl basic auth credentials (API token or Service ID) are stored encrypted in the Jentic vault. Agents receive scoped access at execution time — the credentials never enter the agent's context, which matters for PCI compliance and partner contracts.
Intent-based discovery
Agents search Jentic by intent (e.g., 'create a european payment order') and Jentic returns the matching Pay.nl operation with its parameter schema, so the agent picks the right endpoint without reading Pay.nl docs.
Time to first call
Direct Pay.nl integration: 2-4 days for auth, order creation, capture, void, and refund handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Global payments platform with European method support via Payment Methods API.
Use Stripe for global reach and unified reporting across regions. Use Pay.nl for regional-specific merchant terms and dedicated European support.
Alternative
Adyen API
Enterprise payment platform with European acquiring and local method routing.
Pick Adyen for large-scale merchants needing global acquiring. Choose Pay.nl for mid-market European merchants with simpler integration needs.
FAQs
Specific to using Pay.nl Transaction Gateway API through Jentic.
What authentication does the Pay.nl API use?
Pay.nl uses HTTP Basic authentication with an API token (AT-code) or Service ID (SL-code) as credentials, encoded into the Authorization header. Through Jentic, the basic auth credential is stored encrypted in the vault and injected at execution time.
Can I do partial captures with the Pay.nl API?
Yes. After creating an order, use PATCH /orders/{id}/capture-amount to capture a specific amount, or PATCH /orders/{id}/capture-products to capture only the line items that have shipped. The remaining authorized amount stays on hold for later capture or void.
What payment methods does Pay.nl support?
Pay.nl supports major European payment methods including iDEAL (Netherlands), Bancontact (Belgium), SEPA Direct Debit, credit cards, and other local options. The payment method can be specified when creating the order or selected by the buyer on the hosted payment page.
How do I void a payment before capture?
Call PATCH /orders/{id}/void to release an authorized payment without charging the buyer. This is typically used when an order is cancelled before fulfillment or when a fraud review flags the transaction.
What are the rate limits for the Pay.nl API?
Pay.nl does not publish hard rate limits in the public spec. For production workloads, expect to handle a few requests per second per merchant. Back off on HTTP 429 responses and use queue-based patterns for high-volume checkout flows.
How do I create a payment order through Jentic?
Search Jentic for 'create pay.nl order', load the schema for POST /orders, and execute the call with the service ID, amount, and return URL. Jentic returns the order ID and redirect link so your app can send the customer to the payment page.
GET STARTED