Verified payouts with name and transaction verification
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 28 May 2025 | Payouts | All |
Verified Payouts enables you to pay out to a known, verified beneficiary. For example, you may want to make a payout to the same bank account previously used to make a deposit, even if the user initially paid with a debit card.
You can use this feature to verify an account holder's name and/or a particular transaction within certain parameters.
Reversal fields visible in GET Payment responses
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 21 May 2025 | Payments | All |
If you make a GET Payment request and the payment in the response has been reversed, you now receive reversed_at
and reversal_reason
in the response.
New business_client option inside submerchants object in Create Payment endpoint
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 19 May 2025 | Payments | All |
If you are a PSP, you can now specify a business_client
inside the Create Payment request. This enables you to specify and include information about a merchant that you are partnered with, when a user makes a payment to that merchant.
Statement_reference for mandates
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 14 May 2025 | VRP | All |
You can now supply a custom reference for a mandate that you create, for easier reconciliation and to contextualise a payment on your user's bank statements.
Web SDK v1
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 17 April 2025 | Payments | Web SDK |
Web SDK v1 is a new version of the Web SDK. In Web SDK v1, the Web SDK is initialized without initiating a payment.
When the user taps the Pay button, we invoke the onStartFlow()
callback. When this happens, you can create the payment and pass it to the Web SDK.
Read the migration guide for more information.
payment_reversed
webhook
payment_reversed
webhookChange type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 28 March 2025 | Payments | All |
On the rare occasions that a customer reverses a payment, you now receive [a webhook] after payment_settled
informing you when the reversal happens.
Value-based settlement notifications
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 23 March 2025 | Payments | All |
You can now configure creditable notifications to arrive a certain amount of time after payment settlement for only transactions above a value that you choose.
For example, you might only add the post settlement delay for payments above £500 in value. This means that high-value payments are much less likely to be reversed after you receive a creditable
webhook, but the instant experience is not lost for lower-value payments.
PLN merchant accounts
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 6 February 2023 | Console, Payouts | All |
We now support merchant accounts in the PLN currency, accessible via Console.
Note that the PLN currency is only usable with Payouts.
AIS + PIS flow for React
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 3 February 2025 | Payments | Mobile SDKs (React) |
To make the user experience simpler, you can now give your user the option of creating an additional Data connection when they consent to a payment. This flow appears for some German banks when your user would need to input an IBAN at the authorisation stage.
Custom statement references
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 29 January 2025 | Payments | All |
When you create a payment, you can now fill in the statement_reference
field inside the beneficiary
object. This controls what your customer sees on their bank statement, in the ‘reference’ field, after a closed-loop payment.
If you leave this field empty, a random 18-character string appears on the end user's bank statement. Therefore, we strongly recommend that you include a useful reference value in this field.
New functionality for payment cancellation in Ireland
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 23 January 2025 | Payments | All |
If a payment in Ireland is not yet authorised, you can now call the /cancel
endpoint up to and including the authorised
status. This brings the functionality of this endpoint for Irish payments in line with the UK.
Payouts reliability improvements
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 23 January 2025 | Payouts | All |
We've addressed an edge case where a payout creation request could return a 202 status code but fail silently without creating a resource. This scenario now correctly causes a 500 status code.
AIS + PIS flow for Android and iOS
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 15 January 2025 | Payments | Mobile SDKs |
To make the user experience simpler, you can now give your user the option of creating an additional Data connection when they consent to a payment. This flow appears for some German banks when your user would need to input an IBAN at the authorisation stage.
Console changes — metadata in reports
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 7 January 2025 | Console | N/A |
You can now include metadata fields in the Merchant Account Transactions reports that you download from Console.
If you want to include this information in reports, click the cog icon at the top of the Merchant Account historical balances table, on the Merchant Account tab.
creditable_at
in GET Payment requests
creditable_at
in GET Payment requestsChange type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 12 December 2025 | Payments | All |
You can now see when a payment was considered creditable
when you make a successful GET Payment request (with a 200 code). This value displays when your payment reaches the executed
status or later.
Scheme_id
no longer provided in provider selection
Scheme_id
no longer provided in provider selectionChange type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 15 November 2024 | Payments | All |
You no longer need to pass a scheme_id
within the provider_selection
object when you create a payment.
Instead, to specify a particular payment scheme, use the scheme_selection
object and set the type
value to preselected
.
Scheme_id
now provided with payouts when you call the merchant-account/{id}/transactions
endpoint
Scheme_id
now provided with payouts when you call the merchant-account/{id}/transactions
endpointChange type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 12 November 2024 | Payments, Payouts | All |
When you call the /transactions
endpoint, if a payout or refund has executed, you now receive the scheme_id
to indicate what scheme the payout was made through.
Credit notifications for suspense accounts
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 14 October 2024 | Payments | All |
You can now use credit notifications (the payment_creditable
webhook) alongside pre-settlement verification. This means that you receive a payment_creditable
webhook only if pre-settlement verification is complete.
Authorisation expiry for Signup+ in Finland
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 15 October 2024 | Signup+ | All |
If you are making a Signup+ payment in Finland, you can now receive the authorization_expired
error response if a payment expires, alongside authorization_expired
webhooks.
Scheme selection for payouts
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 20 September 2024 | Payouts | All |
You can now choose how a payout settles using scheme selection. You can select a payment scheme for your payout by using the scheme_selection
object inside the Create payout request.
Retry options removed for new UIs (web SDK and hosted page) when retry isn’t available
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
Fix | 20 September 2024 | Payments | Web SDK, hosted page |
In some geographies, payment retries are not supported yet. When you do not pass a retry object in a payment request, the UI changes to remove actions that your user cannot perform without retries.
First-party webviews now supported by Web SDK
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 20 September 2024 | Payouts | All |
The Web SDK is now compatible with first-party webviews.
Payout and refund metadata from the merchant account /transactions endpoint
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 20 September 2024 | Payouts | All |
When you call the /transactions
endpoint, you can now see the metadata associated with any payouts or refunds.
NRB supported in payments requests
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 19 September 2024 | Payouts | All |
NRB is now a type of account_identifier
that you can use in payouts to an external account.
Provider availability webhook
Change type | Date of change | Affected products | Affected auth flows |
---|---|---|---|
New feature | 9 September 2024 | Payments | All |
When a provider changes status (from healthy to unhealthy or vice versa), you now receive a webhook which describes the event.
Note that TrueLayer UIs all automatically indicate, and disallow users from selecting, unhealthy providers.