A service asks for a phone number or verification code: what should I do?

Who is asking for the code

A phone or SMS request can come from different systems: the merchant’s own account verification, Apple Wallet or Google Wallet card enrollment, or 3D Secure for a specific card payment. The steps and code-delivery channels are not necessarily the same.

The service is verifying your phone number

This can occur when registering or signing in to a service such as Airbnb, or when a service uses Google account verification. Use a phone number that you control and that the service genuinely supports. Some services may require a number capable of receiving SMS, not a data-only connection. Check the exact country-code format and the service’s own phone-verification requirements.

If a service refuses the number or the SMS does not arrive, follow the service’s recovery options or contact the service’s support. SafePay does not control third-party login SMS messages.

Apple Wallet or Google Wallet asks to verify the card

Use the delivery method actually displayed in Wallet and follow the issuer’s instructions. A code may be delivered through a channel supported for that request; do not assume every Wallet SMS is sent to Telegram or to SafePay. If verification fails, record the request time and error and ask SafePay Support for guidance. Never send a verification code to support.

Checkout asks for 3D Secure

This is a payment authorization request, not the same as an account sign-up SMS. Keep the merchant checkout open, review the merchant and amount and complete the SafePay confirmation shown for that specific payment. Reject any authorization you did not initiate.