IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

Allowing developers to choose the SMS Gateway that they want to use in their applications would provide the option for adjusting Identity Platform's authentication services based on the cost and availability that better suits developers.

For example: A developer may choose to use Identity Platform's SMS verification in their app for specific regions and add a different SMS Gateway (e.g.: MessageBird, Twilio's SMS API, GatewayAPI) where Identity Platform is too expensive or unavailable.

If applicable, reasons why alternative solutions are not sufficient:

Currently, using Identity Platform for authentication purposes forces developers to stick with the platform's costs and availability. Workflows in which developers want to use SMS verification are greatly affected by this:

1. Firstly, developers have to comply with the platform's pricing. This may be inconvenient for developers as the current rates can be modified every month, leaving less than 7 days for developers to adapt in case that the new rate doesn't align with their requirements:

To view pricing for the previous, current, and next month, see For phone authentication and multi-factor authentication. We typically publish a preview for the next month's pricing five days before the next month begins.

2. Secondly, Identity Platform's SMS services may be restricted to certain regions or service providers/carriers, which could block developers from releasing their apps in some regions if they decide to use Identity Platform.

Other information (workarounds you have tried, documentation consulted, etc):

A workaround for using a custom provider for SMS services is to add SMS verification through a 3rd party provider (examples provided above) and then authorize users into Cloud Identity with a custom token.