Payment Instruction
Fund Transfer
Used to transfer bookings from accounts already registered in ESPay or from the balance deposits of partners in ESPay to the desired account number
API URL |
Development : https://sandbox-api.espay.id/b2b/transfer/fund |
Production : https://api.espay.id/b2b/transfer/fund |
The format of the submitted message must be in the form of an encoded URL. Description for each field in the HTTP POST message:
Fund Transfer Request Data:
Name Field | Attribute | Mandatory | Description |
rq_uuid | ANS 255 | Yes | Request Identifier. Unique ID to identify the request message with other messages. Format : Client ID + Unique ID Ex : CLIENTID123abc-def456 |
rq_datetime | ANS 19 | Yes | The date and time in the client application server when the massage is sent. Format : YYYY-MM-DD HH:MM:SS Ex : 2014-12-17 12:30:45 |
sender_id | AN 32 | Yes | The unique identity of Client applications listed on the ESPay system |
signature | AN 255 | Yes | Signature (view Signature Validation) |
transfer_type | N 1 | Yes | 0: Online transmission 1: SKN 2: RTGS (If not specified, Espay will determine this as an online transfer.) |
source_bank_code | AN 32 | No | Source Bank Code, if not filled ESPay system execute to default account |
source_account_number | AN 32 | No | Source Account Number, if not filled ESPay system execute to default account |
beneficiary_bank_code | AN 5 | Yes | Destination Bank Code |
beneficiary_account_number | AN 32 | Yes | Destination account number |
amount | NUM 15,2 | Yes | Transaction amount Format: 1000000.00 |
transaction_id | AN 32 | Yes | Transaction ID Client. It is required to be different for each transaction |
transfer_reff | AN 32 | No | Reference Number from service Inquiry Name (if any) |
description | AN 255 | No | Transaction description |
description_detail | AN 255 | No | Transaction Description (added) |
AN 255 | No | Destination Email Address | |
address1 | AN 255 | No | Destination Address1 |
address2 | AN 255 | No | Destination Address2 |
After making a request with the example above, the client will get a response with details and examples as follows :
Fund Transfer Response Data:
Name Field | Attribute | Mandatory | Description |
rq_uuid | ANS 255 | Yes | Request Identifier. Unique ID to identify the request message with other message (obtained from request). Format : Client ID + Unique ID Ex : CLIENTID123abc-def456 |
rs_datetime | ANS 19 | Yes | The date and time in the client application server when the message is sent. Format : YYYY-MM-DD HH:MM:SS Ex : 2014-12-17 12:30:45 |
error_code | ANS 4 | Yes | Error code |
error_message | ANS 255 | Yes | Error description |
source_bank_code | AN 32 | No | Source Bank Code, if not filled ESPay system will execute to default account |
source_account_number | AN 32 | No | Source account number, if not filled ESPay system will execute to default account |
beneficiary_bank_code | AN 5 | Yes | Destination Bank Code |
beneficiary_account_number | AN 32 | Yes | Destination account number |
transaction_id | AN 32 | Yes | Transaction code Client |
reference_id | AN 32 | Yes | Reference ESPay System |
reference_bank | AN 32 | No | Reference Code bank |