Payments table changes in Console

There are multiple changes to the way that the Payments table displays in Console:

• Refreshed UI
• You can now add metadata to a refund in the same way that you can for a payment
• When you refund a specific payment, the new View refund details button takes you to the refund in the payments table
• The table is now more accessibly designed thanks to easier keyboard navigation
• The Payment ID column has been renamed to ID. For refunds, the ID that displays is the ID of the refund, not the ID of the payment that was refunded. The transaction ID remains unchanged

Test redirect page for new hosted page

You can now test the new hosted page in a webview using the test redirect page.

Max_wait_for_result field in hosted_page object

When using the hosted_page object inside the Create payment request, you can now set the maximum period to wait before displaying a result screen.

Merchant account name change

It is now possible to change the name of your merchant account. Contact us to enable this feature.

expires_at field in payment_disputed webhook

When you receive a payment_disputed webhook, you now receive a field that informs you when the dispute expires.

New Mobile SDK versions

The newest versions of Android, iOS and React mobile SDKs have been released. The user experience is improved, with new functionalities for retrying payments and simplified returning user journeys.

onBankRedirect callback

If you are using the Web SDK in a webview, use the onBankRedirect callback. This callback passes the redirection URL back to your app so it can open the link in an external browser. This ensures that app-to-app flows work correctly.

Ad hoc business account payouts

You can now make a one-off payout into your business account from your merchant account to your business account.

To make a one-off, or ad hoc, business account payment, go to the Merchant Accounts tab inside your app and navigate to Manage funds.

Changed behaviour for refunds

You can now create a refund from the authorized status onwards, to happen automatically as soon as the payment settles.

The refund will have the pending status until the payment settles. All queued refunds are initiated in the order that the corresponding payments settle.

Payment_funds_received webhook

You now receive this webhook when a Direct Debit payment arrives in your merchant account. Note that the payment can still be reversed at this stage.

Docs || API reference

Verified payouts with name and transaction verification

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.

Docs // API specs

Reversal fields visible in GET Payment responses

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.

Docs // API specs

New business_client option inside submerchants object in Create Payment endpoint

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.

API specs

Statement_reference for mandates

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.

Docs // API specs

Web SDK v1

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

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

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

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

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

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

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

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

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

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

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.