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.

Can I limit what my agent is allowed to do with the Pay.nl API?

Yes. Because you run Jentic One yourself, your own rules decide which Pay.nl operations the agent may call, so you can grant read-only access to GET /orders/{id}/status while withholding capture, void, and amend operations. Since Pay.nl puts the order id in the URL path, a rule can pin the agent to reading the status of a single order. Capturing, capture-amount, and void requests are excluded unless you explicitly add them.