Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Payments / Pay.nl Transaction Gateway API
Pay.nl Transaction Gateway API logo

Pay.nl Transaction Gateway API

✓ Official Vendor SpecPaymentsPayment Processingbasic10 EndpointsREST

For Agents

Manage Pay.nl payment orders including creation, capture, void, refund, and status tracking across the European payment gateway.

Use for: I need to create a payment order for a customer checkout, Capture a payment after order fulfillment, Check the status of a payment order, Issue a refund for a completed payment

Not supported: Does not host checkout pages, validate payment methods, or process actual fund transfers — use for order management, capture, refund, and status operations only. Payment processing happens on Pay.nl infrastructure.

Pay.nl is a European payment gateway that processes online payments through various methods including iDEAL, credit cards, and local payment options. The Transaction Gateway API provides comprehensive order management capabilities including creation, updates, capture, void, refund, and status tracking. Authentication uses basic auth with API tokens or Service IDs, and the API follows RESTful conventions with JSON payloads.

Jentic One on GithubView OpenAPI Document

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 | sh
2

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 instance

Jentic 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 and manage payment orders with multiple payment methods

Capture full or partial order amounts with product-level granularity

Void and decline pending orders before capture

Process full and partial refunds with optional descriptions

Track order status and payment states in real-time

Configure test mode for development and staging environments

Add multiple payments to a single order

Update order amounts, descriptions, and reference fields

Manage expiration times and return/exchange URLs

Approve or decline orders for risk management

Use Cases

Patterns agents use Pay.nl Transaction Gateway API for, with concrete tasks.

★ E-commerce Checkout Integration

Integrate Pay.nl into an e-commerce checkout flow by creating orders with POST /orders when customers initiate payment. Include the cart amount, return URL for successful payments, and exchange URL for server-side webhooks. Once the customer completes payment through the redirect link, capture the full amount with PATCH /orders/{id}/capture or a partial amount with PATCH /orders/{id}/capture-amount. GET /orders/{id}/status provides real-time payment state for order confirmation pages.

POST /orders with amount, serviceId, returnUrl, and exchangeUrl to create the order. The response includes a redirect link for the customer. After payment completion notification via exchangeUrl, call PATCH /orders/{id}/capture to finalize.

Partial Refund Processing

Process full or partial refunds for customer returns and cancellations using the refund endpoints. PATCH /orders/{id}/refund issues a full refund, while PATCH /orders/{id}/refund-amount allows specifying the exact amount to return. PATCH /orders/{id}/refund-products enables product-level granularity by refunding specific line items and quantities. Each refund can include a description field for internal tracking and customer communication.

To refund specific items, call PATCH /orders/{id}/refund-products with an array of products containing id and quantity. For a flat amount refund, use PATCH /orders/{id}/refund-amount with the Amount object. Include description for audit trails.

Pre-Authorization and Capture Workflow

Implement a two-stage payment flow where authorization happens at order time but capture occurs only after fulfillment. Create the order with POST /orders including testMode: false for production. The order enters an authorized state. When goods ship or services complete, call PATCH /orders/{id}/capture-products to capture only the items being fulfilled, useful for partial shipments. Monitor status via GET /orders/{id}/status to ensure the capture succeeded before finalizing the order.

POST /orders creates the authorization. After fulfillment, call PATCH /orders/{id}/capture-products with the products array specifying which line items and quantities to capture. GET /orders/{id}/status confirms capture completion.

Fraud Prevention and Order Approval

Implement manual order review for high-risk transactions using the approve and decline endpoints. After order creation, orders flagged by internal fraud systems can remain in pending state. Use PATCH /orders/{id}/approve to allow legitimate orders to proceed or PATCH /orders/{id}/decline to cancel suspicious transactions. PATCH /orders/{id}/void provides an additional mechanism to cancel orders before capture. Combined with GET /orders/{id}/status, this enables human-in-the-loop fraud review workflows.

After risk analysis, call PATCH /orders/{id}/decline for orders that fail checks or PATCH /orders/{id}/approve for those that pass. Use PATCH /orders/{id}/void to cancel authorized but not-yet-captured orders.

AI Agent for Payment Operations

Let an AI agent handle routine payment operations for an e-commerce platform — creating orders at checkout, capturing payments post-fulfillment, processing refunds for returns, and checking order status for customer service inquiries. Through Jentic, the agent loads only the specific payment operations it needs and credentials are injected securely without appearing in prompts.

Use the Jentic search query 'create a payment order' to find POST /orders, load its schema, and execute with the checkout details including amount and return URLs.

Key Endpoints

10 endpoints — pay.

METHOD

PATH

DESCRIPTION

POST

/orders

Create a new payment order with amount, service ID, and URLs

PATCH

/orders/{id}/capture

Capture the full authorized amount for an order

PATCH

/orders/{id}/refund

Issue a full refund for a captured order

GET

/orders/{id}/status

Check the current status and action state of an order

PATCH

/orders/{id}/void

Void an authorized but not-yet-captured order

PATCH

/orders/{id}/capture-amount

Capture a specific partial amount from an authorized order

PATCH

/orders/{id}/refund-products

Refund specific products by ID and quantity

POST

/orders

Create a new payment order with amount, service ID, and URLs

PATCH

/orders/{id}/capture

Capture the full authorized amount for an order

PATCH

/orders/{id}/refund

Issue a full refund for a captured order

GET

/orders/{id}/status

Check the current status and action state of an order

PATCH

/orders/{id}/void

Void an authorized but not-yet-captured order

PATCH

/orders/{id}/capture-amount

Capture a specific partial amount from an authorized order

PATCH

/orders/{id}/refund-products

Refund specific products by ID and quantity

Why Jentic?

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

Credential management

Credential isolation

Pay.nl API credentials (API tokens or Service IDs) are stored encrypted in the Jentic vault and injected as HTTP Basic auth at execution time. Raw credentials never appear in agent prompts, transcripts, or response payloads.

Intent-based discovery

Intent-based discovery

Agents search by intent such as 'create a payment order' or 'refund a payment' and Jentic returns the matching endpoint with its schema and any required path parameters.

Time to first call

Time to first call

Direct Pay.nl integration: 1-2 days to model order creation, capture, refund, and status workflows. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Stripe provides global payment processing with similar authorization and capture workflows but broader geographic coverage.

Choose Stripe for global reach and extensive payment methods; choose Pay.nl for European focus with strong iDEAL and local payment support.

Alternative

Mollie API

→

Mollie offers European payment processing with similar iDEAL and local payment method support to Pay.nl.

Both serve European merchants with strong iDEAL support; choose based on existing merchant relationships and pricing.

Alternative

Adyen API

Adyen provides enterprise-grade global payment processing with more complex integration requirements than Pay.nl.

Choose Adyen for large-scale global commerce; choose Pay.nl for European SMBs needing simpler integration.

Alternative

Checkout.com API

Checkout.com offers global payment processing with unified API across payment methods and geographies.

Choose Checkout.com for unified global processing; choose Pay.nl for European-focused merchants with local payment priorities.

FAQs

Specific to using Pay.nl Transaction Gateway API through Jentic.

What authentication does the Pay.nl API use?

The Pay.nl API uses HTTP Basic authentication with either an API token (AT-code) or Service ID (SL-code) as credentials. Through Jentic, credentials are stored encrypted and injected as the Authorization header at execution time so they never enter the agent's context.

Can I process partial refunds through the Pay.nl API?

Yes. Use PATCH /orders/{id}/refund-amount to refund a specific amount in cents, or PATCH /orders/{id}/refund-products to refund by product ID and quantity. Both support partial refunds while PATCH /orders/{id}/refund issues a full refund.

Does Pay.nl support test mode for development?

Yes. Include testMode: true in the POST /orders request body to create test orders that process through the Pay.nl sandbox environment without charging real payment methods.

How do I implement a two-stage payment flow with Pay.nl through Jentic?

Search Jentic for 'create payment order' to find POST /orders for authorization, then search 'capture payment after fulfillment' to find PATCH /orders/{id}/capture. Jentic injects credentials automatically and handles the authorization-then-capture workflow.

What payment methods does Pay.nl support?

Pay.nl supports iDEAL, credit cards, and various European local payment methods. The specific payment methods available depend on your Pay.nl merchant account configuration and are selected via paymentMethodId in the order creation request.

Can I void an order before it's captured?

Yes. Use PATCH /orders/{id}/void to cancel an authorized order before capture, or PATCH /orders/{id}/decline to reject an order through the approval workflow. Both prevent the payment from being captured.

GET STARTED

Start building with Pay.nl Transaction Gateway API

Explore with Jentic
View OpenAPI Document