espay logo

Payment Instruction

Fund Transfer





Download Image

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 255 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)
email 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 








































Example Request:

	
	POST /b2b/transfer/fund HTTP/1.1
	Host: sandbox-api.espay.id
	Connection: keep-alive
	Content-Length: 293
	Authorization: Basic Um9tZW86SnVsaWV0
	Content-Type: application/x-www-form-urlencoded
	Accept: */*
	rq_uuid=CLIENTIDUUID171214003&rq_datetime=2017-12-14 15:34:00&signature= 547b56a2a2ff08dab4d3baa73beff19a9c93f615ca912579d2bc64beba67b633
	&sender_id=CLIENTID&beneficiary_bank_code=002&beneficiary_account_number=720801001600505&amount=1000000.00
	&description=Transaction Payment TRX171214001&transaction_id=TRX171214001


	
	









































Example Respone:

		
		{
		  "rq_uuid":"CLIENTIDUUID171214003",
		  "rs_datetime":"2017-12-14 15:30:02",
		  "error_code":"0000",
		  "error_message":"Success",
		  "beneficiary_bank_code":"002",
		  "beneficiary_account_number":"720801001600505",
		  "transaction_id":"TRX171214001",
		  "reference_id":"B9AO10293U381011",
		  "reference_bank":"799102077483101"
		}