Level up your Twilio API skills in TwilioQuest, an educational game for Mac, Windows, and Linux. Download Now

Menu

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

<Pay> Connectors

<Pay> Connectors are integrations with Payment Gateways that allow you to tokenize payment details and create charges on credit and debit cards. In a matter of minutes, a merchant or ISV (independent software vendor) can start accepting payments over a phone call without having to become PCI Compliant.

pay-diagram-1-final.png

<Pay> Connectors are available as a part of Twilio Programmable Voice. You can choose your preferred Payment Gateway and instantly install it for free. Once installed, you must authorize Twilio to initiate transactions on your behalf.

1-pay-connectors-1.png

Supported products

Twilio <Pay> Connectors are currently supported only by Programmable Voice. Navigate to <Pay> Connectors in Twilio console to see list of available connectors.

If you have an existing integration with a Payment Provider and want Twilio to build a <Pay> Connector for it then request it here.

Install and configure a <Pay> Connector

Install <Pay> Connectors

Twilio's available <Pay> Connectors can be found here in the Console. To get started, click on your preferred <Pay> Connector and install it. This creates an instance of the <Pay> Connector that you can configure with a Unique Name (Not treated as PII by Twilio).

stripe-connector-change-default

Configuration and authorization

Each <Pay> Connector instance must be given a unique name as highlighted in the above diagram. The Unique Name must be unique to this Twilio account. If you enter Default, then when you invoke <Pay> you don't have to specify a paymentConnector attribute.

If you have multiple instances of paymentConnectors then you should use the paymentConnector attribute to reference the unique name in the invocation of the <Pay> verb. See here to learn how to use <Pay>.

For example, to use a connector instance with a unique name of Stripe_Connector_1, use the following:

        
        
        
        
        Capture payment using a named connector instead of the default.

        Use a named <Pay> Connector

        Capture payment using a named connector instead of the default.

        To initiate transactions from Twilio to the Payment Gateway, you must first have an account set up with the Payment Gateway. Make sure to authorize Twilio to initiate transactions on your behalf.

        When you configure the <Pay> Connector instance you will do one of the following:

        1. Provide your secret keys.
        2. Authorize Twilio using a revocable access token.

        When possible, please provide authorization that is scoped to only tokenization or charges. Not all Payment Providers make this possible.

        Create multiple instances of a <Pay> Connector

        Twilio supports creating multiple instances of a <Pay> Connector. This means that you can create one instance of a <Pay> Connector for your production environment, another for your staging environment, and the third instance for your development environment.

        If using Stripe, you might create the following three instances:

        #

        Environment

        <Pay> Connector Instance

        Unique Name

        Stripe Mode

        1

        Production

        Stripe_Prod

        Live

        2

        Staging

        Stripe_Stage

        Test

        3

        Development

        Stripe_Dev

        Test

        Terms of Service

        <Pay> Connectors are provided and supported by Twilio. As a part of the <Pay> Connector installation process, you are required to accept Twilio’s Terms of Service.

        The <Pay> Connector is provided under https://twilio.com/PCI. Documentation specific to each Payment Gateway can be found on the Console under the documentation tab of the corresponding <Pay> Connector.

        Don’t see the Payment Gateway you’re looking for?

        Help us prioritize our next <Pay> Connector to your preferred Payment Gateway by requesting here.

        What's next?

        Learn how to capture your first payment using <Pay> here.

        Rate this page:

        Need some help?

        We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.