In response to popular demand from our community, we are pleased to announce that we have updated the SMS sender name for OTP verification. The default sender name for all One Time Password (OTP) SMS verifications has now been changed from "REAP" to "AUTHOTP".
What's changing:
The sender name for SMS verifications is now "AUTHOTP" for all BIN configurations, including:
3DS checkout verification flow
Digital wallet provisioning flow
The sender name is the name that appears as the sender on your clients' (cardholders') mobile phones when they request an OTP via SMS for identity verification.
For example, when a cardholder adds a card to Apple Pay and requests an OTP via SMS for verification, the sender name in the SMS will now appear as "AUTHOTP".
Why it matters:
The previous sender name was proving to be confusing for cardholders. We hope that a neutral, non-branded sender name could smoothen this experience for your business and customers.
What you need to do:
The update is automatic, and all OTP SMS verifications will now use "AUTHOTP" as the sender name. No configuration or further action is needed from your tech team.
Timeline:
This update went live on 11/09/2024. Cardholders will now see "AUTHOTP" as the default sender name for OTP SMS requests in most countries. However, for certain countries listed below, local regulations require legal name registration for the sender name at an organisational level. Our team is actively working on this registration process.
It may take several months to complete the registration and officially use "AUTHOTP" as the sender name in these countries. During this transition period, we advise you to use email as the default channel for receiving verification OTP for cardholder identity verification.
The list of countries where legal registration is required:
Belarus
China
Egypt
India
Jordan
Kuwait
Philippines
Qatar
Russia
Saudi Arabia
Singapore
Sri Lanka
Thailand
Turkey
United Arab Emirates
Vietnam
Authentication flow best practices
While this update enhances the cardholder's experience, please note that SMS delivery reliability isn't entirely within our control. Successful delivery depends on local mobile carriers. For an optimal user experience, we strongly recommend using email as the preferred verification channel for sending verification codes to your cardholders. Email verification offers greater reliability and can help minimise potential disruptions in the verification process.
Read more about using email as the default channel for identity verification in our API documentation:
For any questions or additional information, please reach out to your relationship manager or our customer success team via hello@reap.global