Developer Portal — Technical guides, integration workflows, and API references.
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 →This section explains usage of different payment methods
Go to Payment Methods →Useful resources for your integrations.
Go to Resources →Explore additional services available through the gateway.
Go to Optional Services →Find out how to integrate our API
Available soon →Get help for different use cases
Available soon →Recent API and platform changes from the release notes.
v3.21.33
girocard payments can now be verified with online PIN. The terminal sends the encrypted PIN in pos_data.pin_block (key_derivation: "TDES-UKPT", format: "ISO-0", block, derivation_data, key_id, key_version) when the chip data reports online PIN. See girocard.
Read more →v3.21.31
Shops now have an optional external_id, a caller-defined identifier like the one on merchants. Set it when creating a shop (POST /v2/merchants/{merchant_id}/shops) or change it later (PUT /v2/merchants/{merchant_id}/shops/{id}); all shop responses now return it, as null for shops without one. See Create Shop and Update Shop.
Read more →v3.21.26
wero_capture_type is an optional parameter on Wero authorization requests (POST /rest/authorize). Valid values: PAY (pay the full amount) and PAY_UP_TO (allows partial captures). Falls back to PAY if missing. It is not accepted on payment or other requests. See Authorize API and Wero.
Read more →v3.21.21
Card-present payments with the girocard debit scheme can now be processed through POS terminals and SoftPOS devices. Supported operations: payment and refund. See girocard.
Read more →