01. What SMS configuration is

SMS configuration connects the institution's own SMS provider to Finger Manager.

The institution prepares the account information provided by the SMS provider and completes the configuration in Finger Manager so the system can send SMS through that provider.

Common providers include Twilio, AWS SNS, Vonage, MessageBird, Alibaba Cloud SMS, Tencent Cloud SMS, local carriers in different countries or regions, and other providers that support API or standard SMS interfaces.

The actual integration scope depends on the SMS channels supported by the current Finger Manager environment.

02. Why use your own SMS service

Finger Grid can provide platform-side SMS delivery, but platform SMS may be affected by sending quota, regional coverage, and pricing rules.

An institution may instead connect its own SMS provider account.

With an institution-owned SMS service, the institution uses its own SMS account, settles fees directly with the provider, chooses routes for different countries or regions, manages its own quota, uses custom Sender ID where supported, and Finger Grid does not charge an additional fee for that SMS channel.

03. Configure SMS service

Open System Settings -> SMS and fill in the connection information required by the selected SMS provider.

Fields may differ by provider. Common fields include Provider, API Key, API Secret, Access Key, Access Secret, Account SID, Auth Token, Sender ID, Sender Number, Messaging Service ID, API Endpoint, and Region.

The exact values should follow the provider console and API documentation.

04. API Key and Secret

Most SMS providers use API Credentials to verify sending requests.

Common formats include API Key + API Secret, Access Key + Access Secret, or Account SID + Auth Token.

These credentials are usually created in the provider console. Create a dedicated SMS credential for Finger Manager instead of sharing one credential with other business systems.

05. Sender ID

Sender ID is the sender identity shown to the SMS recipient.

Depending on country, carrier, and provider rules, it may appear as a company name, brand name, short code, long number, virtual number, or provider-managed number.

Whether custom Sender ID is allowed depends on local telecom regulations and provider policy. Some countries require registration or review before use.

06. SMS use cases

After SMS service is configured, it can be used by Finger Grid functions that support SMS delivery.

Typical scenarios include phone verification codes, registration verification, login verification, password recovery, security verification, abnormal login alerts, account status notifications, system notifications, targeted user notifications, user group notifications, operating messages, and service reminders.

The exact scope depends on the products and system functions enabled for the Organization.

07. Difference from Finger Grid system SMS

An institution can choose either platform SMS or its own SMS channel according to business needs.

Finger Grid system SMS requires no provider application by the institution, is easy to enable, but may involve quota, usage fees, and regional coverage limits.

An institution-owned SMS service uses the institution's provider account, route selection, quota, and billing relationship. Finger Grid does not charge an additional SMS sending fee for that channel.

08. International SMS

SMS rules vary greatly between countries and regions.

Requirements may include Sender ID registration, enterprise verification, template review, marketing SMS permission, short code application, international routing limits, opt-out handling, and local telecom regulations.

If the institution sends SMS to multiple countries, confirm provider coverage and compliance requirements for each target region in advance.

09. SMS templates

Some SMS providers require templates to be created and approved before sending.

For example, a login verification template may state that the verification code is valid for a limited time and should not be shared.

If template review is enabled by the provider, SMS content sent by Finger Manager must match the approved template rules, otherwise delivery may fail.

10. Verification code SMS

Verification codes are one of the most common SMS use cases.

Examples include registration codes, login codes, phone number verification, password changes, and high-risk operation confirmation.

For verification SMS, configure expiry time, sending frequency limits, consecutive request limits, avoid logging full codes directly, and apply risk controls to abnormal sending behavior.

11. Quota and fees

SMS cost is usually affected by target country, carrier, message length, message type, international or local routing, Sender ID type, and provider pricing.

If Finger Grid's SMS channel is used, fees follow the platform service rules.

If the institution uses its own SMS provider, fees are settled directly between the institution and that provider.

12. SMS length

The number of billable SMS segments may not equal the number of messages shown to the user.

Long messages may be split into multiple billable segments, and character encoding can affect the number of characters allowed in one segment.

Keep SMS content concise, remove unnecessary long text, keep verification SMS focused, and use email or other notification channels for long-form content.

13. Test SMS

After SMS service configuration is complete, send a test SMS before using it in production.

During testing, confirm API connectivity, phone number format, Sender ID display, message completeness, verification code correctness, delivery to numbers in different countries, and provider-side sending records.

Use the SMS channel for production notifications only after testing succeeds.

14. Organization-level independent configuration

SMS service is configured independently by Organization.

Different institutions can connect different SMS providers, such as Broker A using Twilio, Broker B using AWS SNS, and Broker C using a local carrier SMS service.

Accounts, credentials, quota, and SMS channels remain independent between Organizations.

15. Credential security

SMS API Key, Secret, Token, and related credentials are sensitive information.

Use dedicated API Credentials, avoid sharing credentials with other systems, rotate keys regularly, apply minimum permissions, restrict backend configuration permissions, and revoke leaked credentials immediately.

For production use, avoid using personal development accounts as long-term SMS sending accounts.

16. Delivery failure

If SMS delivery fails, check whether API Key is correct, Secret or Token is valid, account balance is sufficient, phone number format is correct, the target country is supported, Sender ID is approved, SMS template is approved, provider account has sending restrictions, or rate limits and risk controls were triggered.

Finger Manager handles delivery status according to the result returned by the SMS provider.

17. Permissions

SMS configuration is a sensitive system-level setting.

Only administrators with the required System Settings permissions should view or edit SMS service settings.

Access should be strictly controlled for API Key, API Secret, Auth Token, Sender ID, provider account information, and other sensitive settings.