Payment details
/payment/{payment_reference}Get the payment details. This is an alternative way to get the current status of the payment, aside from the webhook.
Path Parameters
Unique payment reference number given by the Payment Request
Query Parameters
Flag to display the associated transaction information
0 - txs property will not be included.
1 - txs property will be included.
Response
Success
The type of payment request.
Use:
triplea- when integrating with external URL Payment Form.widget- when integrating with Widget Payment Form.
Unique Payment Reference Number that identifies this payment
Cryptocurrency that the payer will pay
Address that the customer must send the cryptocurrency funds to. Each address will only be used to receive a single payment
Amount of cryptocurrency to be sent to the address
Currency that the merchant will receive. This should be a 3-character ISO 4217 currency code
The amount of currency that the merchant wants to receive
Exchange rate that is used to calculate the required crypto_amount
The status describe the overall state of the payment and are related to Instant Confirmation. These are the status codes:
-
none- no payment has been detected (yet). The merchant should not deliver the goods and services. -
short- the payment is short of the requested amount. The merchant should not deliver the goods and services. -
hold- the payment is equal to or greater then the requested amount, but the payment cannot be instantly confirmed. The merchant should not deliver the goods and services. -
good- the payment is equal to or greater then the requested amount and Triple-A has determined that you can now deliver the goods and services to the buyer. Your funds are now guaranteed. -
invalid- the payment was unable to be processed. This is a very rare occurence.
Date and time the status was updated
Amount received in the order_currency
Alias for status
Date of the Payment Tier
The 3-character currency code of the guaranteed amount. This is also the merchant’s preferred currency.
Guaranteed amount of local currency that the merchant will
receive. Even if the status remains as short or hold
or later becomes invalid.
Amount of cryptocurrency that the merchant has received.
Indicates if an invalid payment is refundable or non-refundable.
Shopping Cart
a unique sequence of characters that identify the details or payment destination of the payment request
How long, in seconds, until the access_token expires
and the hosted payment page becomes inaccessible
Name of the merchant
Webpage to redirect the customer to on successful payment.
The payment_reference will be provided as part of the
query string
Webpage to redirect the customer to on cancelled payment.
The payment_reference will be provided as part of the
query string
Data that is used to customize the hosted payment page. Can be ignored
The remaining crypto amount that has not been paid
The merchant needs to provide a unique ID for each payer. If the merchant does not have a unique ID then use the payer’s email address.
We need a unique payer ID to track total spends for KYC purposes
Payer’s name.
For a triplea or widget integration, the payer’s name is not
required. However, if provided, it can make the checkout
experience better as the payer will not have to enter their name
if we need to collect it.
If you do not have the payer’s name, then leave this
key out of the JSON object. Do not submit an empty string "".
Payer’s email address.
For a triplea or widget integration, the payer’s email is not
required. However, if provided, it can make the checkout
experience better as the payer will not have to enter their email.
If you do not have the payer’s email,
then leave this key out of the JSON object. Do not submit an empty
string ""
Payer’s phone number in E.164 format.
For a triplea or widget integration, the payer’s phone number is not
required. However, if provided, it can make the checkout
experience better as the payer will not have to enter their email.
If you do not
have the payer’s phone number, then leave this key out of the JSON
object. Do not submit an empty string ""
Payer’s address. If you do not
have the payer’s address, then leave this key out of the JSON
object. Do not submit an empty string ""
URL to the payer’s Proof-Of-Identity (POI). Our system will download the payer’s POI from this link.
For a triplea or widget integration, the payer’s POI is not
required. However, if provided, it can make the checkout
experience better as the payer will not have to upload their POI. If it is not provided here and the payment or order amount is above SGD 1500 or equivalent, the POI will be asked in the payment form.
If you do not
have the payer’s POI, then leave this key out of the JSON
object. Do not submit an empty string ""
Note : Please do not use the URL example provided below as the payer_poi value in production. It is only for testing purpose.
IP address of the payer
If you do not have the payer’s ip location,
then leave this key out of the JSON object. Do not submit an empty
string ""
Data that is used by the hosted payment page to know if it needs to collect data. Can be ignored
Array of transactions received by the payment request.
Not authorized
No permission to access this payment
Payment not found