Skip to main content
Developer Portal — Technical guides, integration workflows, and API references.

OneAPI Documentation

Learn how to get started, handle authentication, and manage sandbox or live environments.

API Reference

Comprehensive documentation of all API endpoints, request parameters, and responses.

Go to API Reference →

Payment Methods

This section explains usage of different payment methods

Go to Payment Methods →

Resources

Useful resources for your integrations.

Go to Resources →

Optional Services

Explore additional services available through the gateway.

Go to Optional Services →

Integrations

Find out how to integrate our API

Available soon →

Guides

Get help for different use cases

Available soon →

Latest release notes

Recent API and platform changes from the release notes.

September 10, 2026

v3.21.15

Merchant Management API — Update Merchant

Partners can now change a sub-merchant's details via PUT /v2/merchants/{id} instead of the dashboard. name and email are required on every call; type is fixed at creation and is ignored if sent, so a representation read from Show Merchant can be sent straight back. Two behaviours to be aware of before you integrate: a field you **omit** keeps its current value while a field you send **empty** is cleared, and changing email reassigns dashboard access — the new address is linked to the merchant (created and sent confirmation instructions if no account exists yet) and the previous address is unlinked from that merchant, though its account and any other merchants it belongs to are untouched. All merchant responses — list, show, create and update — now also return an updated_at timestamp. See Update Merchant.

Read more →
September 8, 2026

v3.21.5

Wero — Capture event on authorization

wero_capture_event is an optional parameter on Wero authorization requests (POST /rest/authorize). One of: SHIPPING, DELIVERY, AVAILABILITY, SERVICE_FULFILMENT, OTHER. When missing, falls back to OTHER. This information is displayed to the end user when making the payment. It is not accepted on payment or other requests. See Authorize API and Wero.

Read more →
July 28, 2026

v3.20.37

Jetztzahlen — Invoice activation

Invoices can be activated or deactivated via PUT/PATCH /rest/invoices/:invoice_number using the active flag. Deactivating an invoice stops its payment link and blocks further e-mails. amount and active can only be changed while the invoice is pending and has never had a payment plan attached. Creating or importing an invoice with an existing number in the same channel automatically deactivates the previous active invoice. Number-addressed endpoints always resolve to the active invoice (falling back to the most recently created). An invoice with an active payment plan cannot be deleted until the plan is cancelled. See Jetztzahlen, Update Invoice, and Delete Invoice.

Read more →
July 27, 2026

v3.20.36

Merchant Management API — Payment Methods

Partners can now discover and configure payment methods for their sub-merchants via the API. Browse the catalogue of available methods, processors and their field schema with GET /v2/payment-methods, then configure a method for a merchant or an individual shop (list, show, set and remove) via /v2/merchants/{merchant_id}/payment-methods and /v2/merchants/{merchant_id}/shops/{shop_id}/payment-methods. See Merchant Management API.

Read more →