experienced an error communicating with the payment processor or gateway Max attempts reached when capturing the payment information successfully captured the payment data and either tokenized or processed the payment The body of this request will contain the standard request parameters, along with the additional parameters listed in the table below. Twilio's POST request to your action URL twilios-post-request-to-your-action-url page anchorĪfter a successful transaction, Twilio will send a POST request to your action URL. If you made a charge transaction, Twilio's request to your application will include a PaymentConfirmationCode parameter with the confirmation code received from the payment processor/gateway. These fields contain the tokenized information received from the Payment Gateway. If you made a tokenize transation, Twilio's request to your application will include the PaymentToken and/or ProfileId parameter. The attribute only accepts https protocol for the URL. If no action is provided, Twilio will by default make a POST request to the current document URL. The body of the request includes the standard request parameters and the additional parameters described in the Twilio's POST request to your action URL section below. When the verb has successfully tokenized or created a charge, Twilio will make a POST request to the action URL. The action attribute takes an absolute or relative URL as value. The URL where Twilio will send a POST request for the next set of TwiML instructions after a successful transaction. String containing one or more of the following values separated by a space: visa mastercard amex maestro discover optima jcb diners-club enroute "consumer-checking" "consumer-savings" "commercial-checking"įor credit card payments, possible values are: English: The verb supports the following attributes to modify its default behavior:Ĭurrent document URL. To create a tokenize transaction, you must set the Note that tokens are provided by your payment gateway or processor. Tokens are typically stored so that you can charge the user in the future without having to ask for the credit card information again. credit card) in return for the goods or services you offer.Īttribute in your verb to a decimal value greater than 0.Ī tokenize transaction means you want to obtain a token based on the user's supplied credit card information from the payment processor instead of posting any charge. can create two types of transactions, charge and tokenize.Ī charge transaction means you want to immediately capture funds from the customer's supplied payment method (i.e. Twilio will continue the current call using the TwiML returned in the response from the action URL. When finishes collecting a customer's valid payment information or is terminated with a * keypress, Twilio will immediately send a webhook (an HTTP POST request) to the action URL. will terminate when DTMF * keypress is received at any point. Once finishes collecting a customer's valid payment information, information about the transaction result will be sent via webhook to your statusCallback URL and/or your action URL. Once all required credit card or ACH data is captured, will send the payment information to your payment processor or gateway via a Pay Connector installed and configured on your account. In addition to managing necessary interactions when there is timeout or invalid input, will send webhooks to your statusCallback URL to keep you informed of the progress of. will prompt your customer to enter their payment information and will handle retries if a piece of information is invalid. You can use TwiML's verb to capture and process both ACH and credit card data during a call. This TwiML verb is only supported in the default US1 Twilio Region Ireland (IE1) and Australia (AU1) are not yet supported.įor more information on supported features in Twilio Regions, go to the Global Infrastructure docs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |