Learn how to get started, handle authentication, and manage sandbox or live environments.
Comprehensive documentation of all API endpoints, request parameters, and responses.
Go to API Reference →Explore additional services available through the gateway.
Go to Optional Services →Recent API and platform changes from the release notes.
v3.21.5
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 →v3.20.37
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 →v3.20.36
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 →v3.20.35
The hosted checkout page and payment forms now support Croatian (hr). See Locales.
Read more →