For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
GuidesAPI ReferenceSDKs
GuidesAPI ReferenceSDKs
  • Get Started
    • Overview and Solutions
    • Choose an Integration
    • Quickstart
    • Branding Guidelines
    • Get Support
  • Accept Payments
    • Instant Payments
    • Trustly Pay
    • Recurring Payments
    • Scan and Pay
    • Remember Me
    • Payment Integration Checklist
  • Send Money
    • Send Payouts Using Online Banking
    • Send Payouts Using Account Information
    • International Transfers
  • Retrieve Data
    • Verify Accounts Using Online Banking
    • Verify Accounts Using Micro-Deposits
    • Retrieve Bank and User Information
    • Tokenize Bank Information
    • Trustly ID
    • Insights Data
  • Core Concepts
    • Key Concepts
    • The Establish Data Object
    • Transactions and Transaction IDs
    • Tokens and Account Security
    • Redirect URLs and Return Flow
    • Webhooks and Events
    • Content Strings
  • API Fundamentals
    • Authentication and OAuth
    • Secure Requests and Signature Validation
    • Idempotency
    • Testing
    • Status codes and type definitions
  • Manage Your Integration
    • Go-Live Checklist
    • Merchant Portal
    • Reports and Reconciliation
    • Refresh Bank Authorization
    • Override Risk Declines
    • VIP Tiers
    • Financial Institution Status
Dashboard
Products
PaymentsDataPayouts
Company
AboutCareersContact Sales

Terms of Use | Privacy Policy | © 2026 Trustly, Inc.

Developer-friendly docs for your API
GitHub|Contact Support|Business Help Center|Merchant Portal
Terms of Use|Privacy Policy|© 2026 Trustly, Inc.
Developer-friendly docs for your API
LogoLogo
North AmericaEurope
North AmericaEurope
On this page
  • Prerequisites
  • Detect a required refresh
  • Common indicators
  • Relaunch the Lightbox
  • Required parameters
  • Implementation example
Manage Your Integration

Refresh bank authorization

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

VIP Program

Next

Override risk declines

Built with

If a customer’s bank authorization expires or is invalidated (for example, due to a password change or a security update at the bank), you must re-authenticate the customer to continue processing payments.

Trustly provides a mechanism to detect these scenarios and relaunch the Lightbox to restore connectivity without requiring the customer to re-enter all their details.

Prerequisites

Before you attempt to refresh an authorization, ensure you have the following data from the original transaction:

  • Original Transaction ID: The ID of the transaction that requires re-authentication. If you are missing the ID, use the List transactions endpoint to search for the original transaction using your merchantReference.

Detect a required refresh

When you attempt a capture or a data refresh request, you may receive a failure response indicating that the session is no longer valid.

Common indicators

Monitor your API responses and event notifications for the following statuses:

  • paymentProviderTransaction.status: SW057 (Expired Split Token)
  • paymentProviderTransaction.status: SW051 (Invalid or corrupt Split Token)

When you encounter these errors, you must prompt the customer to re-authenticate.

Relaunch the Lightbox

To refresh the authorization, you must launch the Trustly Lightbox again using the specific parameters associated with the original transaction. This flow differs slightly from the initial setup because you are updating an existing connection rather than creating a new one.

Required parameters

The following table lists the parameters required to relaunch the Lightbox for a refresh flow.

ParameterDescription
paymentTypeSet to Verification, indicating that you are verifying the customer access to the bank account to refresh the bank authorization.
transactionIdThe ID of the customer authorization transaction you are attempting to refresh.
authTokenSet to new, indicating that the customer must re-authenticate and the merchant will receive a new split token.

Implementation example

Call the establish method from the appropriate SDK with the required parameters to trigger the refresh flow.

1var refreshData = {
2  accessId: 'YOUR_ACCESS_ID',
3  merchantId: 'YOUR_MERCHANT_ID',
4  merchantReference: 'refresh-order-123',
5  paymentType: 'Verification', 
6  transactionId: '1002636615', // The original transaction ID
7  authToken: 'new'
8};
9
10Trustly.establish(refreshData, {
11  closeButton: true,
12  dragAndDrop: false,
13  widgetContainerId: 'widget-container'
14});

Once the customer successfully completes the workflow, Trustly issues a new Authorize event with a fresh splitToken. You must update your system with this new token for future requests.