Retrieve a PaymentIntent object
This endpoint allows you to fetch an existing payment intent from our database. You must either provide the “id” or the “token” for us to find that payment intent. Retrieving using the “token” is the fastest way and is not rate limited, depending on your needs, that’s probably the best solution.
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 to retrieve.
Query Parameters
You can also use this token parameter to retrieve a payment intent. This is especially useful for a client-side application when you don't want your api key to be disclosed in.
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