Direct Bank Transfer settlement flow, ETN 2FA support, and more

April 22, 2026

Direct Bank Transfer: Settlement Confirmation Flow

We have added a new Settlement Confirmation Flow section to the Direct Bank Transfer manage payment guide.

Direct Bank Transfer uses a deferred settlement model: the charge transaction stays in a pending state after the customer completes payment and only moves to success once the bank confirms that funds have settled. The new documentation covers:

• Payment lifecycle stages — from customer payment through settlement confirmation, timeout, and late settlement recovery.
• Settlement timeline — settlement confirmation typically arrives within 1 business day; the maximum wait is 7 days, after which the charge fails with SETTLEMENT_TIMEOUT.
• Webhook sequence — the charge.succeeded webhook is sent only after settlement is confirmed, not immediately after the customer pays. The guide explains when each event (payment.completed, charge.pending, charge.succeeded, charge.failed) is sent and how to use them to drive order fulfillment logic correctly.

ETN file download: 2FA support and token expiration

The ETN file download guide has been updated with two additions:

• 2FA support — If your Unzer Insights account has two-factor authentication enabled, you now need to include the totp_code parameter in your /auth.token request. The code is a six-digit, time-based value generated from your 2FA setup key (RFC 6238). The guide includes an example using the oathtool CLI to generate the code, and the 2FA setup screen where you can find your key.

• Token expiration behavior — The authentication token behavior is now documented in detail:

  • The token expires after 30 minutes of inactivity.
  • Only one active token per user account is allowed at a time. Logging in to Unzer Insights in the browser invalidates an active API token, and vice versa.
  • Always obtain a fresh token before making API calls rather than storing a previously issued one.

Payment Pages V2: shopName field also used on Apple Pay payment sheet

The Payment Pages V2 API reference has been updated to clarify that the shopName field is not only shown on the payment page itself but also used as the short text name on the Apple Pay payment sheet.

Merchants integrating Apple Pay via Payment Pages V2 should review the value they pass in shopName to ensure it is appropriate for both contexts.

Legacy integration docs moved to a dedicated section

Payment Pages V1 and UI Components V1 documentation has been reorganized into a dedicated Legacy section under Online Payments. The content is unchanged — only the location in the navigation and the URLs have been updated.

If you have bookmarked or linked directly to these pages, update your links to the new paths:

• Payment Pages V1
• UI Components V1