SMS Verification Service

FAQ

Q: The console shows that the message was sent successfully, but the phone did not receive it. Or, I cannot receive test messages when I select a specific region. What should I do?

A:

• SMS delivery occurs only when you call the SendSmsVerifyCode operation. Obtaining an AccessKey pair or binding a phone number in the console does not trigger message delivery on its own.

• You do not need to change the service endpoint when you call the API. Use the default endpoint. Switching regions (for example, between Hangzhou and Shanghai) does not affect message delivery.

• If delivery fails because of signature real-name registration issues, you can use the SMS Delivery Failure Diagnostics tool to self-check whether your signature is compliant.

Differences between SMS Verification Service and Short Message Service

SMS Verification Service and Short Message Service are independent products with isolated API endpoints and resources. Note the following when you use SMS Verification Service:

• API usage: SMS verification must be implemented by calling the SendSmsVerifyCode and CheckSmsVerifyCode operations of PNVS (Dypnsapi). Do not call the SendSms operation of Short Message Service (Dysmsapi) for SMS verification scenarios. Otherwise, errors such as isv.SMS_TEMPLATE_ILLEGAL (template not found) or "no matching template under this account" may occur.

• Resource isolation: Free signatures and free templates provided by SMS Verification Service can be used only with the SendSmsVerifyCode operation. They cannot be used with the SendSms operation. Likewise, custom signatures and templates created in Short Message Service cannot be used with SMS Verification Service operations.

• Parameter format: The TemplateParam parameter of the SendSmsVerifyCode operation must be a JSON string, for example, {"code":"##code##","min":10}. The validity period of the verification code is determined by the ValidTime parameter.

• Integration method: SMS Verification Service is called only through server-side API operations. It does not involve client SDK integration or the creation of an authentication scheme. If your frontend (such as H5 or a React Native Expo app) needs to trigger SMS verification, the frontend must forward the request through your backend server. Do not call the API operations directly from the frontend.

FAQ

Q: I purchased a resource plan, but I cannot use it, or my API calls fail. What should I do?

A: Check the following items:

• Account status: Make sure that your Alibaba Cloud account balance is greater than 0. If your account is in arrears, the resource plan cannot be used to offset charges.

• Permission configuration: If you use a RAM user, make sure that the RAM user is granted the AliyunDypnsFullAccess permission.

• API operation and parameters: Make sure that you call SendSmsVerifyCode instead of SendSms, and that the TemplateParam parameter is in the correct format.

• Signature and template pairing: Make sure that you use a free signature together with a free template provided by the system. Do not mix free and custom signatures or templates.

Q: I have enabled Converged Authentication. Can I use only SMS verification and disable the other authentication methods?

A: If you need only the SMS verification code capability, we recommend that you integrate directly with the SMS Verification API of PNVS. This is a pure server-side API that requires no client SDK integration and gives you full control over the authentication flow. You do not need to disable the other methods in Converged Authentication. Note that SMS Verification Service provides only verification code generation, delivery, and verification capabilities. It does not include business logic such as handling network disconnection and reconnection. You must implement such logic yourself on the business side.