{"id":485,"date":"2024-08-08T19:43:56","date_gmt":"2024-08-08T19:43:56","guid":{"rendered":"https:\/\/lddpay.com\/?post_type=docs&p=485"},"modified":"2024-08-10T09:00:20","modified_gmt":"2024-08-10T09:00:20","password":"","slug":"s2s-apm","status":"publish","type":"docs","link":"https:\/\/lddpay.com\/zh\/docs\/s2s-apm\/","title":{"rendered":"S2S VPG"},"content":{"rendered":"

S2S VPG<\/h1>\n\n\n\n

Version: 3.3.4
Released: 2024\/07\/01<\/p>\n\n\n\n

Copyrighted by lddPay<\/p>\n\n\n\n

Introduction<\/h2>\n\n\n\n
\n\n\n\n

This document describes integration procedures and VIRTUAL PAYMENT GATEWAY protocol usage for e-commerce merchants.<\/p>\n\n\n\n

VIRTUAL PAYMENT GATEWAY protocol implements acquiring payments (purchases) with using specific API interaction.<\/p>\n\n\n\n

Integration Process<\/h2>\n\n\n\n
\n\n\n\n

Integration process<\/h3>\n\n\n\n

With all Payment Platform POST requests at Notification URL the Merchant must return the string OK if he\/she successfully received data or return ERROR.<\/p>\n\n\n\n

\u26a0\ufe0f Pay attention<\/strong><\/p>\n\n\n\n

\n

Note that the notification URL may be temporarily blocked due to consistently receiving timeouts in response to the callback. If five timeouts accumulate within five minutes for a merchant\u2019s notification URL, it will be blocked for 15 minutes. During this block, all merchants associated with the URL will not receive notifications. The block automatically lifts after 15 minutes. Additionally, it is possible to manually unblock the URL through the admin panel by navigating to Configuration \u2192 Merchants \u2192 Edit Merchant. In this case, the block will be removed immediately. The timeout counter resets if a callback response is successfully processed. For instance, if there are four timeouts within five minutes but a successful response on the sixth minute, the counter resets.<\/em><\/p>\n<\/blockquote>\n\n\n\n

\u26a0\ufe0f Pay attention<\/strong><\/p>\n\n\n\n

\n

In the case of cascading, the logic for sending callbacks differs. If cascading is triggered for the order, you will receive callbacks for the first payment attempt, where the decline occurred and which caused the cascading, as well as for the last payment attempt, where the final status of the order (settled or declined) is determined. Additionally, for the last attempt, the callback will include only the final status. That is, callbacks regarding 3DS or redirects will not be sent. Callbacks for intermediate attempts (between the first decline and the last payment attempt) are not sent.<\/em><\/p>\n<\/blockquote>\n\n\n\n

Client Registration<\/h3>\n\n\n\n

Before you get an account to access Payment Platform, you must provide the following data to the Payment Platform administrator.<\/p>\n\n\n\n

Data<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
Callback URL<\/td>URL which will be receiving the notifications of the processing results of your request to Payment Platform<\/td><\/tr>
Contact e-mail<\/td>Client`s contact email<\/td><\/tr>
IP List<\/td>List of your IP addresses, from which requests to Payment Platform will be sent.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

With all Payment Platform POST requests at Callback URL the Client must return the string “OK” if he\/she successfully received data or return “ERROR”.<\/p>\n\n\n\n

You should get the following information from administrator to begin working with the Payment Platform.<\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
CLIENT_KEY<\/td>Unique key to identify the account in Payment Platform (used as request parameter). In the administration platform this parameter corresponds to the “Merchant key” field<\/td><\/tr>
PASSWORD<\/td>Password for Client authentication in Payment Platform (used for calculating hash parameter). In the administration platform this parameter corresponds to the “Password” field<\/td><\/tr>
PAYMENT_URL<\/td>URL to request the Payment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Protocol Mapping<\/h3>\n\n\n\n

It is necessary to check the existence of the protocol mapping before using the S2S integration. Merchants can\u2019t make payments if the S2S VPG protocol is not mapped.<\/p>\n\n\n\n

Payment Platform Interaction<\/h3>\n\n\n\n

For the transaction you must send the server to server HTTPS POST<\/strong> request to the Payment Platform URL (PAYMENT_URL). In response Payment Platform will return the JSON (http:\/\/json.org\/)<\/a>) encoded string.<\/p>\n\n\n\n

List of possible actions in Payment Platform<\/h3>\n\n\n\n

When you make request to Payment Platform, you need to specify action that needs to be done. Possible actions are:<\/p>\n\n\n\n

Action<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
SALE<\/td>Creates SALE transaction<\/td><\/tr>
CREDITVOID<\/td>Creates REFUND transaction<\/td><\/tr>
VOID<\/td>Creates VOID transaction<\/td><\/tr>
CREDIT2VIRTUAL<\/td>Creates CREDIT2VIRTUAL transaction<\/td><\/tr>
GET_TRANS_STATUS<\/td>Gets status of transaction in Payment Platform<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

List of possible transaction results and statuses<\/h3>\n\n\n\n

Result – value that system returns on request. Possible results are:<\/p>\n\n\n\n

Result<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
SUCCESS<\/td>Action was successfully completed in Payment Platform<\/td><\/tr>
DECLINED<\/td>Result of unsuccessful action in Payment Platform<\/td><\/tr>
REDIRECT<\/td>Additional action required from requester<\/td><\/tr>
ACCEPTED<\/td>Action was accepted by Payment Platform, but will be completed later<\/td><\/tr>
ERROR<\/td>Request has errors and was not validated by Payment Platform<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Status – actual status of transaction in Payment Platform. Possible statuses are:<\/p>\n\n\n\n

Status<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
PREPARE<\/td>Status is undetermined, final status will be sent in callback<\/td><\/tr>
REDIRECT<\/td>The transaction awaits SALE<\/td><\/tr>
SETTLED<\/td>Successful transaction<\/td><\/tr>
VOID<\/td>Transaction for which void was made<\/td><\/tr>
REFUND<\/td>Transaction for which refund was made<\/td><\/tr>
DECLINED<\/td>Not successful transaction<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Transactions requests<\/h1>\n\n\n\n

SALE request<\/h2>\n\n\n\n
\n\n\n\n

Use SALE request to create a payment in the Payment Platform.<\/p>\n\n\n\n

If you want to send a payment for the specific sub-account (channel), you need to use channel_id<\/code> that specified in your Payment Platform account settings.<\/p>\n\n\n\n

This request is sent by POST in the background (e.g. through PHP CURL).<\/p>\n\n\n\n

Request Parameters<\/h3>\n\n\n\n
Parameter<\/strong><\/th>Description<\/strong><\/th>Limitations<\/strong><\/th>Required<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>Action to perform (=SALE)<\/td>= SALE<\/td>+<\/td><\/tr>
client_key<\/code><\/td>Unique client key (CLIENT_KEY)<\/td><\/td>+<\/td><\/tr>
channel_id<\/code><\/td>Payment channel (Sub-account)<\/td>String up to 16 characters<\/td>–<\/td><\/tr>
brand<\/code><\/td>Brand through which the transaction is performed<\/td>String up to 36 characters(Appendix B)<\/td>+<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Clients system<\/td>String up to 255 characters<\/td>+<\/td><\/tr>
order_amount<\/code><\/td>The amount of the transaction<\/td>Format depends on currency.
Send Integer type value for currencies with zero-exponent.
Example:<\/strong> 1000
Send Float type value for currencies with exponents 2, 3, 4.
Format for 2-exponent currencies: XX.XX
Example:<\/strong> 100.99
Pay attention<\/strong> that currencies ‘UGX’, ‘JPY’, ‘KRW’, ‘CLP’ must be send in the format XX.XX, with the zeros after comma.
Example:<\/strong> 100.00
Format for 3-exponent currencies: XXX.XXX
Example:<\/strong> 100.999.
Format for 4-exponent currencies: XXX.XXXX
Example:<\/strong> 100.9999<\/td>		+<\/td><\/tr>
order_currency<\/code><\/td>Currency<\/td>3-letter code<\/td>+<\/td><\/tr>
order_description<\/code><\/td>Description of the transaction (product name)<\/td>String up to 1024 characters<\/td>+<\/td><\/tr>
identifier<\/code><\/td>Extra parameter for transaction. It could be token, account information, additional descriptor etc<\/td>String up to 255 characters<\/td>+<\/td><\/tr>
payer_first_name<\/code><\/td>Customer’s name<\/td>String up to 32 characters<\/td>–<\/td><\/tr>
payer_last_name<\/code><\/td>Customer’s surname<\/td>String up to 32 characters<\/td>–<\/td><\/tr>
payer_address<\/code><\/td>Customer’s address<\/td>String up to 255 characters<\/td>–<\/td><\/tr>
payer_house_number<\/code><\/td>Customer’s house or building number<\/td>String up to 9 characters<\/td>–<\/td><\/tr>
payer_country<\/code><\/td>Customer’s country<\/td>2-letter code<\/td>–<\/td><\/tr>
payer_state<\/code><\/td>Customer’s state<\/td>String up to 32 characters<\/td>–<\/td><\/tr>
payer_city<\/code><\/td>Customer’s city<\/td>String up to 40 characters<\/td>–<\/td><\/tr>
payer_district<\/code><\/td>Customer’s district of city<\/td>String up to 32 characters<\/td>–<\/td><\/tr>
payer_zip<\/code><\/td>ZIP-code of the Customer<\/td>String up to 32 characters<\/td>–<\/td><\/tr>
payer_email<\/code><\/td>Customer’s email<\/td>String up to 256 characters<\/td>–<\/td><\/tr>
payer_phone<\/code><\/td>Customer’s phone<\/td>String up to 32 characters<\/td>–<\/td><\/tr>
payer_birth_date<\/code><\/td>Customer’s birthday<\/td>Date format is “YYYY-MM-DD”<\/td>–<\/td><\/tr>
payer_ip<\/code><\/td>IP-address of the Customer. Both versions, IPv4 and IPv6, can be used. If you are sending IPv6, make sure the payment provider that processes the payments supports it.<\/td>XXX.XXX.XXX.XXX<\/td>+<\/td><\/tr>
return_url<\/code><\/td>URL to which Customer should be returned after operation in third-party system<\/td>String up to 1024 characters<\/td>+<\/td><\/tr>
parameters<\/code><\/td>Array of the parameters for specific brand<\/td>(Appendix B)<\/td>+<\/td><\/tr>
custom_data<\/code><\/td>Array with the custom data
This block duplicates the arbitrary parameters that were passed in the payment request<\/td>		Format:
custom_data [param1]: value1<\/code>
custom_data [param2]: value2<\/code>
custom_data [paramN]: valueN<\/code><\/td>		–<\/td><\/tr>
hash<\/code><\/td>Special signature to validate your request to Payment Platform<\/td>See Appendix A, Sale signature.<\/td>+<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Response Parameters<\/h3>\n\n\n\n

You will get JSON encoded string with transaction result.<\/p>\n\n\n\n

Successful sale response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>SUCCESS<\/td><\/tr>
status<\/code><\/td>SETTLED<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Payment Platform<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
descriptor<\/code><\/td>This is a string which the owner of the credit card will see in the statement from the bank. In most cases, this is the Customers support web-site<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Unsuccessful sale response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>DECLINED<\/td><\/tr>
status<\/code><\/td>DECLINED<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Payment Platform<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
decline_reason<\/code><\/td>The reason why the transaction was declined<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Redirect transaction response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>REDIRECT<\/td><\/tr>
status<\/code><\/td>REDIRECT<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Payment Platform<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
redirect_url<\/code><\/td>URL to which the Client should redirect the Customer<\/td><\/tr>
redirect_params<\/code><\/td>Array of specific parameters<\/td><\/tr>
redirect_method<\/code><\/td>The method of transferring parameters (POST or GET)<\/td><\/tr>
amount<\/code><\/td>Order<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Undefined sale response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>UNDEFINED<\/td><\/tr>
status<\/code><\/td>REDIRECT \/ PREPARE<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Merchant’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Payment Platform<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
descriptor<\/code><\/td>This is a string which the owner of the credit card will see in the statement from the bank. In most cases, this is the Customers support web-site<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Callback parameters<\/h3>\n\n\n\n

Successful sale response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>SUCCESS<\/td><\/tr>
status<\/code><\/td>SETTLED<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
descriptor<\/code><\/td>This is a string which the owner of the credit card will see in the statement from the bank.In most cases, this is the Customers support web-site<\/td><\/tr>
exchange_rate<\/code><\/td>Rate used to make exchange<\/td><\/tr>
exchange_rate_base<\/code><\/td>The rate used in the double conversion to convert the original currency to the base currency<\/td><\/tr>
exchange_currency<\/code><\/td>Original currency<\/td><\/tr>
exchange_amount<\/code><\/td>Original amount<\/td><\/tr>
hash<\/code><\/td>Special signature to validate callback. See Appendix A, Callback signature.<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr>
custom_data<\/code><\/td>Object with the custom data.
This block duplicates the arbitrary parameters that were passed in the payment request<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Unsuccessful sale response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>DECLINED<\/td><\/tr>
status<\/code><\/td>DECLINED<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
descriptor<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
decline_reason<\/code><\/td>Description of the cancellation of the transaction<\/td><\/tr>
hash<\/code><\/td>Special signature to validate callback. See Appendix A, Callback signature.<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr>
custom_data<\/code><\/td>Object with the custom data.
This block duplicates the arbitrary parameters that were passed in the payment request<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Redirect transaction response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>REDIRECT<\/td><\/tr>
status<\/code><\/td>REDIRECT<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Client’s system<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
redirect_url<\/code><\/td>URL to which the Client should redirect the Customer<\/td><\/tr>
redirect_params<\/code><\/td>Array parameters<\/td><\/tr>
redirect_method<\/code><\/td>The method of transferring parameters (POST or GET)<\/td><\/tr>
hash<\/code><\/td>Special signature to validate callback. See Appendix A, Callback signature.<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr>
custom_data<\/code><\/td>Object with the custom data.
This block duplicates the arbitrary parameters that were passed in the payment request<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Undefined sale response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>SALE<\/td><\/tr>
result<\/code><\/td>UNDEFINED<\/td><\/tr>
status<\/code><\/td>REDIRECT \/ PREPARE<\/td><\/tr>
order_id<\/code><\/td>Transaction ID in the Merchant’s system system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Payment Platform<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
descriptor<\/code><\/td>TDescriptor from the bank, the same as cardholder will see in the bank statement<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Order currency<\/td><\/tr>
custom_data<\/code><\/td>Object with the custom data.
This block duplicates the arbitrary parameters that were passed in the payment request<\/td><\/tr>
hash<\/code><\/td>Special signature, used to validate callback, see Appendix A, Formula 2<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

CREDIT2VIRTUAL request<\/h2>\n\n\n\n
\n\n\n\n

CREDIT2VIRTUAL request is used to create CREDIT2VIRTUAL transaction in Payment Platform.<\/p>\n\n\n\n

This operation transfers money from merchants account to customer account.<\/p>\n\n\n\n

If you want to send a payout for the specific sub-account (channel), you need to use channel_id<\/code> that specified in your Payment Platform account settings.<\/p>\n\n\n\n

This request is sent by POST in the background (e.g., through PHP CURL).<\/p>\n\n\n\n

Request Parameters<\/h3>\n\n\n\n
Parameter<\/strong><\/th>Description<\/strong><\/th>Values<\/strong><\/th>Required<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>CREDIT2VIRTUAL<\/td>CREDIT2VIRTUAL<\/td>+<\/td><\/tr>
client_key<\/code><\/td>Unique client key (CLIENT_KEY)<\/td><\/td>+<\/td><\/tr>
channel_id<\/code><\/td>Payment channel (Sub-account)<\/td>String up to 16 characters<\/td>–<\/td><\/tr>
brand<\/code><\/td>Brand through which the transaction is performed<\/td>String up to 36 characters<\/td>+<\/td><\/tr>
order_id<\/code><\/td>Order ID in the Clients system<\/td>String up to 255 characters<\/td>+<\/td><\/tr>
order_amount<\/code><\/td>The amount of the transaction<\/td>Format depends on currency.
Send Integer type value for currencies with zero-exponent.
Example:<\/strong> 1000
Send Float type value for currencies with exponents 2, 3, 4.
Format for 2-exponent currencies: XX.XX
Example:<\/strong> 100.99
Pay attention<\/strong> that currencies ‘UGX’, ‘JPY’, ‘KRW’, ‘CLP’ must be send in the format XX.XX, with the zeros after comma.
Example:<\/strong> 100.00
Format for 3-exponent currencies: XXX.XXX
Example:<\/strong> 100.999.
Format for 4-exponent currencies: XXX.XXXX
Example:<\/strong> 100.9999<\/td>		+<\/td><\/tr>
order_currency<\/code><\/td>Currency<\/td>3-letter code<\/td>+<\/td><\/tr>
order_description<\/code><\/td>Description of the transaction (product name)<\/td>String up to 1024 characters<\/td>+<\/td><\/tr>
parameters<\/code><\/td>Array of the parameters for specific brand<\/td>(Appendix C)<\/td>+<\/td><\/tr>
hash<\/code><\/td>Special signature to validate your request to Payment Platform<\/td>See Appendix A, Credit2Virtual signature.<\/td>+<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Response Parameters<\/h3>\n\n\n\n

You will get JSON encoded string with transaction result.<\/p>\n\n\n\n

Successful response<\/strong><\/p>\n\n\n\n

Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
action<\/code><\/td>CREDIT2VIRTUAL<\/td><\/tr>
result<\/code><\/td>SUCCESS<\/td><\/tr>
status<\/code><\/td>SETTLED<\/td><\/tr>
order_id<\/code><\/td>Order ID in the Client\u2019s system<\/td><\/tr>
trans_id<\/code><\/td>Transaction ID in the Payment Platform<\/td><\/tr>
trans_date<\/code><\/td>Transaction date in the Payment Platform<\/td><\/tr>
amount<\/code><\/td>Order amount<\/td><\/tr>
currency<\/code><\/td>Currency<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

\n <\/h2>\n\n
\n
\n

CREDIT2VIRTUAL Response Parameter<\/h2>\n<\/div>\n
  • \n
    <\/path><\/svg><\/path><\/svg><\/div> \n Response Example (Successful result) <\/span>\n <\/div>\n
    \n

    {<\/p>\n

    “action”: “CREDIT2VIRTUAL”,<\/p>\n

    “result”: “SUCCESS”,<\/p>\n

    “status”: “SETTLED”,<\/p>\n

    “order_id”: “1613117050”,<\/p>\n

    “trans_id”: “e5098d62-6d08-11eb-9da3-0242ac120013”,<\/p>\n

    “trans_date”: “2021-02-12 08:04:15”,<\/p>\n

    “amount”: “0.19”,<\/p>\n

    “currency”: “USD”<\/p>\n

    }<\/p>\n<\/div>\n<\/div><\/li><\/ul>