Charges: Get
Notice about specification changes
From the 16th of January 2023, the specifications will change as follows; the status of the security code (CVV authentication) will change from “Canceled” to “Authorized”.
We recommend to use the transaction token: GET to check the result.
Request
GET https://api.univapay.com/stores/{storeId}/charges/{chargeId}
Parameters:
Parameters | |
polling | boolean Tells the API to internally poll for the status of a charge until it’s status has changed from Pending (its initial status) to something else. |
Headers:
Authorization: Bearer {secret}.{jwt}
Body:
curl --request GET \
--url https://api.univapay.com/stores/af857264-180c-11e7-9be2-276aea4fed28/charges/0fe1e42a-1845-11e7-9b1f-d3bd0c055a99 \
--header 'Authorization: Bearer {secret}.{jwt}'
Response
Code: 200
Headers:
Content-Type: application/json
Body:
{
"id": "0fe1e42a-1845-11e7-9b1f-d3bd0c055a99",
"store_id": "af857264-180c-11e7-9be2-276aea4fed28",
"transaction_token_id": "06e076b6-1845-11e7-a7bf-67a3521ea48c",
"transaction_token_type": "recurring",
"subscription_id": null,
"requested_amount": 1000,
"requested_currency": "JPY",
"requested_amount_formatted": 1000,
"charged_amount": 1000,
"charged_currency": "JPY",
"charged_amount_formatted": 1000,
"status": "successful",
"error": null,
"metadata": {
"customer_id": 12345,
"shipping_details": "Customer wants it now"
},
"mode": "test",
"created_on": 1491207055635
}