Synchronously attempt a payment on a payment intent
This is the same endpoint but the payment is handled synchronously, it means it will wait for the provider response before returning the status of the payment intent. This endpoint is not the favored way to integrate our api and is not available for all merchants and for all providers.
Headers
Your api key. To create a key, please get into our dashboard. If you don't have access to it, please reach the Support team.
Your merchant ID. This information is available in our dashboard. If you don't have access to it, please reach the Support team.
Allow you to choose between the sandbox mode to perform some tests or the live mode for real world transactions.
live, sandbox Path Parameters
Identifier of the payment intent on which the payment attempt is made.
Body
The token which identify a payment intent. This is a field returned at payment intent creation.
The method selected by the customer to make the payment.
mobile_money, credit_card Two-letter ISO country code. Represents the country where the selected provider is located.
The name of the selected provider in lowercase. The list of supported providers can be found at /data/providers
Only for credit-card payment using redirection workflow: the url used to redirect the user when the transaction is cancelled
Only for credit-card payment using redirection workflow: the url used to redirect the user after the transaction is finished
This field is mandatory for merchants that have the corresponding setting enabled, It allows to send a custom name
Response
Unique identifier for the PaymentIntent
Identifier of the merchant owning this PaymentIntent
Datetime in UTC timezone at which this object was created. Follows the Datetime ISO.
Datetime in UTC timezone at which this object was updated for the last time . Follows the Datetime ISO.
A unique JSON Web Token allowing to attempt a Payment on the PaymentIntent on a client-side application.
A reference provided by the client during the creation of this PaymentIntent
A reference provided by the client during the creation of this PaymentIntent. It is a reference to the customer for who this PaymentIntent was created.
The current status of this PaymentIntent
action_required, canceled, payment_required, processing, successful Amount intended to be collected by this PaymentIntent. A positive integer representing how much to charge in the smallest currency unit (e.g., 100 cents to charge €1.00 or 100 to charge FCFA100, a zero-decimal currency).
Three-letter ISO currency code.
List of Payment attempts made on this PaymentIntent
Mode in which this PaymentIntent exists. The sandbox mode can be used during the integration phase and is available as soon as the merchant account is created. No real transactions are made in this mode. The live mode has to be used to make real transactions.
live, sandbox Action required to execute to continue the processing of the current Payment on this PaymentIntent. The action allows the customer to validate the Payment. - A redirection action provides all the information to redirect the customer to an external page, - A ussd action provides a message to display to the user for the validation of the Payment. He will receive a USSD message on his phone describing how to make the validation, - A otp action requires that you display an input to the customer to collect an OTP. A message is provided to explains to the user how to get this OTP. Then, the client will have to send the authentication request.
In case of a Payment attempt failure, this object will describe the reason of the failure
For Aggregator, name of the merchant