October 16th, 2026 | Reading time: 4 minutes

Confirm important payment actions with an extra authentication step

When you carry out certain payment or recipient-management actions in Redpin Payments, you may now be asked to enter a one-time passcode before the action is submitted.

This additional confirmation is part of Strong Customer Authentication. It adds an extra authentication step to relevant actions, helping confirm that the person carrying them out is authorised to do so. It also supports regulatory requirements that apply to relevant payment activity.

OTP_Confirmation



Extra protection, built into every payment you make

Property transactions can involve significant payments and sensitive recipient details. When you are about to submit an important payment instruction or change where money will be sent, an additional confirmation step gives you a clear opportunity to authenticate the action before it goes ahead.

You will not be asked for a one-time passcode for everything you do in Redpin. The additional check applies only to specific payment and recipient-management actions included in this release.


What this looks like in practice

Imagine you are a lawyer preparing to send the proceeds of a property sale to the seller.

You have received the seller’s destination account details and are ready to submit the payment. Before the relevant recipient details or payment instruction are accepted, Redpin may ask you to enter a one-time passcode.

This adds an authentication step at the point the important instruction is being confirmed.

OTP_Entry


OTP_Mobile

How it works

You continue to prepare your payment or recipient details in Redpin as usual.

When an action requires additional authentication:

  • Review the details of the payment or recipient.

  • Submit the action when you are ready to continue.

  • We’ll send a one-time passcode to the mobile number registered with your Redpin account.

  • Enter your passcode when prompted.

  • Once authentication is completed, Redpin can continue with the instruction.

Make sure the mobile number registered with Redpin is up to date so you can receive your passcode when you need it. If you no longer have access to that number, please contact the Redpin Support team.

The additional step only appears for actions that require it.


What’s included in this release?

Strong Customer Authentication applies to relevant actions across a number of Redpin Payments journeys, including:

  • Submitting disbursements, including payments to one or multiple recipients.

  • Sending money through supported Redpin payment journeys.

  • Responding to a payment request when a buyer or seller submits their payment.

  • Adding or changing recipient details where additional authentication applies.

  • Confirming destination account details in supported seller and property-professional journeys.

Supported wallet-to-wallet payments, foreign-exchange-and-send journeys and relevant Portugal tax-payment submissions are also included.

Some related actions are not included in this phase. For example, creating a payment request as a property professional does not currently require the additional authentication step, although the buyer or seller submitting the payment does.

If you add a new payee and make the payment within the same journey, only the payment is authenticated in this phase.

Frequently asked questions

No. The additional authentication applies only to certain payment and recipient-management actions. You can continue using other parts of Redpin without being asked for a one-time passcode each time.

You may be asked for one when carrying out actions such as submitting a payment or disbursement, responding to a payment request, or adding or changing relevant recipient details.

We’ll send it to the mobile number registered with your Redpin account. Please make sure your registered number is up to date so you can receive the code when you need it.

Please contact the Redpin Support team. They can help you update the mobile number linked to your account so you can receive your one-time passcode.

Not in the current phase. A property professional creating a payment request will not receive this additional authentication step.

However, a buyer or seller submitting a payment in response to that request is included.

If you add the payee and make the payment as part of the same journey, only the payment receives the additional authentication step in the current phase.

Additional authentication specifically for saving that payee within the same journey is planned for a later phase.

No. Payment-link creation is outside the scope of this release.

No. Granting that access is outside the scope of the current release.

You will need to create a new disbursement. Redpin does not treat this as retrying the original disbursement.