Scheme_id no longer provided in provider selection

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

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

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

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

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

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

The Web SDK is now compatible with first-party webviews.

Payout and refund metadata from the merchant account /transactions endpoint

When you call the /transactions endpoint, you can now see the metadata associated with any payouts or refunds.

NRB supported in payments requests

NRB is now a type of account_identifier that you can use in payouts to an external account.

Provider availability webhook

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.

iOS SDK v3.2.0

If there is an issue meaning that the iOS SDK isn’t available, it now falls back to the HPP in a web view to ensure a payment is always possible.

See the iOS SDK release history.

Android SDK v3.2.0

If there is an issue meaning that the Android SDK isn’t available, it now falls back to the HPP in a web view to ensure a payment is always possible.

See the Android SDK release history.

Transactions table in Console

On August 5th, we updated the Transactions table accessible through the merchant account dashboard. These updates include quality of life improvements, such as infinite scrolling and improve accessibility support. Additionally, you can now query a date range rather than seeing transactions for a single day.

Console user interface update

The user interface and navigation experience in Console has been updated, along with several other changes. The Console-related documentation on this site has also been updated.

In addition to the visual update, there are also new features:

• You can click the initial in the top-left corner to switch between the organisations you're a member of.
• In the Settings page within an app, you can enable or disable legacy products and features.

Provider icon styles

When you make a request to any provider-related endpoints, such as /v3/payments-providers/search or /v3/payments/{id}/authorization-flow, you can now specify the type of icon you want to receive for the banking providers.

The available options are:

• default: The bank logo in SVG format with no background.
• extended: The bank logo in SVG format with a solid background colour.
• extended_small: The bank logo in JPEG format with a solid background colour with 192x192px dimensions.
• extended_medium: The bank logo in JPEG format with a solid background colour with 432x432px dimensions.
• extended_large: The bank logo in JPEG format with a solid background colour with 864x864px dimensions.

Read more in our docs on how to get information about providers.

Bank Identification Numbers in /payments-providers/search response

The response from the /v3/payments-providers/search endpoint now includes a bin_ranges array, which contains a full list of the Bank Identification Numbers used by the provider. This typically refers to the first 8 numbers on cards issued by the provider.

Start authorization_flow at payment creation

We've added documentation for a new authorisation flow you can use as part of a direct API integration. In a direct API integration, you previously had to use the /v3/payments/{id}/authorization-flow endpoint to start the sequence of requests and responses that authorised a payment.

You can now use the authorization_flow parameter when you create a payment to start the authorisation flow. You provide the same information in. the authorisation_flow parameter as you do in the /v3/payments/{id}/authorization-flow endpoint.

Configurable waiting time for payment result screen on web

You can now change the waiting period before the payment result screen displays in the HPP or EPP. This can be useful if you want to confirm something before finalising a payment.

👍

This behaviour applies to all new and integrations (and the associated client_ids) created from 15 April 2024. For any integrations created before this date, you need to contact us if you want to enable this behaviour.

You can see if a payout or refund has been returned in several places:

• The returned failure reason in the payout_failed and refund_failed webhooks.
• When you make a GET request to retrieve information from the /v3/payouts/{id} or /v3/payments/{payment_id}/refunds/{refund_id} endpoints.
• The Console payments view.
• The returned_for and returned_by fields when you make a GET request to the /v3/merchant-accounts/{id}/transactions endpoint.

React Native SDK v2.1.0

This version of the React Native SDK has been updated to use the underlying Android and iOS SDK version 3.1.0.

The most significant change in this release is the addition of the resultShown property to the processorResult type. This means that you can see which payment or mandate result screen was displayed to the user.

You can download v2.1.0 of the React Native SDK on GitHub.

Dynamic merchant logos in the HPP and EPP

It's now possible to dynamically select a merchant logo when users authorise a payment or mandate through the hosted payment page and embedded payment page. To do this, you need to provide a URL with the required merchant logo at payment or mandate creation (which we need to approve the domain of).

Learn how to implement dynamic logos in the HPP and EPP.

Returns for payouts and refunds

As of 15 April 2024, payouts and refunds can now transition from executed to failed in some rare cases. This happens when the bank 'returns' the payment. For example, when the beneficiary account has been closed.

Learn more about how payout and refund returns work.

👍

This behaviour applies to all new and integrations (and the associated client_ids) created from 15 April 2024. For any integrations created before this date, you need to contact us if you want to enable this behaviour.

You can see if a payout or refund has been returned in several places:

• The returned failure reason in the payout_failed and refund_failed webhooks.
• When you make a GET request to retrieve information from the /v3/payouts/{id} or /v3/payments/{payment_id}/refunds/{refund_id} endpoints.
• The Console payments view.
• The returned_for and returned_by fields when you make a GET request to the /v3/merchant-accounts/{id}/transactions endpoint.

iOS SDK v3.1.0

This version of the iOS SDK includes some visual changes, bug fixes, improvements so you can see the result screen shown to the user, and improvements to provider search for users:

• Improved the UI for users to learn more about how VRP mandates work.
• Added an a new resultShown enum to the processSinglePayment and processMandate completion handlers. This tells you which payment or mandate result was shown to the user if the result screen is enabled.
• Users can now search for countries when selecting a provider by using a 2- or 3-letter country code.
• Branch searching has been improved for users to make it easier to find an intended branch.
• Default colours for primary and secondary buttons have been changed.
• An error now displays in rare cases where there is no additional input available for a user to select.

Download v3.1.0 of the iOS SDK on GitHub.

Android SDK v3.1.0

This version of the Android SDK includes some UX improvements, improvements so you can see the result screen shown to the user, and some bug fixes:

• Improved the UI for users to learn more about how VRP mandates work.
• There is a new ResultShown callback you can use to see the payment or mandate result that the user received.
• Fixed an issue where users would be forced to update all fields if one was incorrect. For example, users would have to update both username and password if validation found that one was incorrect.

You can download v3.1.0 of the Android SDK on GitHub here.

React Native SDK v2.0.0

The latest major version of the React Native SDK contains a variety of minor improvements and bug fixes. It also includes the following larger changes, which align it with the latest versions of the iOS and Android SDKs:

• The introduction of the payment and mandate result screens.
  This is enabled by default and you need to explicitly disable it.
• The UI now displays Signup+ specific wording when signupplus is specified as a related_product at payment creation.
• Made optimisations to the decoupled authorisation flow for payments in Spain.
• Added localisation for the Italian language.
• Added a default merchant logo if one hasn't been uploaded in Console.

You can download v2.0.0 of the React Native SDK on GitHub here

iOS SDK v3.0.1

The latest major version of the iOS SDK contains a variety of minor improvements and bug fixes. It also includes the following larger changes:

• The introduction of the payment and mandate result screen for the iOS SDK.
  This is enabled by default and you need to explicitly disable it.
• The position of the merchant and bank icons was swapped on the payment confirmation screen.
• The UI now displays Signup+ specific wording when signupplus is specified as a related_product at payment creation.
• Made optimisations to the decoupled authorisation flow for payments in Spain.
• Added localisation for the Italian language.
• Added a default merchant logo if one hasn't been uploaded in Console.

You can download v3.0.0 of the iOS SDK on GitHub here

Android SDK v3.0.1

The latest major version of the Android SDK contains a variety of minor improvements and bug fixes. It also includes the following larger changes:

• Updated the payment result screen for the Android SDK. There's now a mandate result screen in the Android SDK too. It's enabled by default, but you can disable the result screens in your integration.
• The Android SDK no longer supports the Material Theme adaptor.
• The UI now displays Signup+ specific wording when signupplus is specified as a related_product at payment creation.
• Made optimisations to the decoupled authorisation flow for payments in Spain.
• Added localisation for the Italian language.
• Added a default logo in case the merchant doesn't upload a logo in Console.

You can download v3.0.0 of the Android SDK on GitHub here.

Removal of Material Theme adaptor for Android SDK

In v3.0.0 of the Android SDK, we removed the Material Theme adaptor. If you used that, you need to migrate to Compose when you update to the latest version of the Android SDK.

New /payment-providers/search endpoint

Previously, if you wanted to get a full list of providers, you had to use one of the following options:

• The Providers page in Console.
• The /single-immediate-payments-providers endpoint.
• Check the response you receive before the provider selection action in a direct API integration.

You can now use a new Payments API v3 endpoint, /payment-providers/search, to generate a list of providers and resources for payment authorisation.

Learn more about how to use the endpoint.