girocard — Online PIN — 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.
Merchant Management API — Shop external ID — 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.
Wero — Capture type on authorization — 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.
girocard — 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.
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.
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.
Pay by Link — 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 Pay by Link, Update Invoice, and Delete Invoice.
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.