Notify Payment
These notify payment are to executed by our system once transaction from ATMBersama transfer for payment are successful. Merchant will need to provide callback URL to receive notify Payment. Merchant will be provided an assistant from us when they need to test this feature. This message will use POST method with XML format message as below.
Request Message Format
No | Name | Type | Status | Length | Description |
---|---|---|---|---|---|
1. | type | String | M | 10 | Filled in accordance with the type of ongoing transactions: Value:reqnotification |
2. | bookingid | int | M | 25 | Booking ID (Received From Merchant, Unique) |
3. | clientid | String | M | 50 | Client ID that use by Merchant for identified each customer (Receive From Merchant, Unique) |
customer_name | String | M | 25 | Customer name in which bookingid is attached to (Alphabet) | |
4. | issuer_bank | String | M | 50 | Name of issuer bank |
5. | issuer_name | String | M | 30 | Name of issuer bank account name of ATM Bersama |
6. | amount | Int | M | 12 | Amount that customer should pay (should numeric, excluding decimal point) For example: IDR 1.892.221 will be denoted as 1892221 |
7. | productid | String | M | 20 | Product id from Merchant (must unique on Merchant’s side) |
8. | trxid | String | M | 34 | Combination of ATM Bersama transaction ID for transaction tracing. |
9. | trx_date | String | M | 19 | Date and time of the ATM Bersama transaction. Format: YYYY-MM-dd hh:mm:ss |
10. | username | String | M | 20 | Given Merchant user name provided by Artajasa |
11. | notification_datetime | String | M | 19 | Transmission local date and time of the transaction. (GMT+7) Format: YYYY-MM-dd hh:mm:ss |
12. | signature | String | M | 32 | Signature will use MD5 with the component below : MD5(username+password+bookingID) |
Response Message Format
No | Name | Type | Status | Length | Description |
---|---|---|---|---|---|
1 | type | String | M | 10 | Filled in accordance with the type of ongoing transactions: Value: resnotification |
2 | ack | String | M | 2 | Response code of notification “00” for success, “78” for re try notification if already arrived before. |
3 | bookingid | int | M | 25 | Booking ID (Received From Merchant, Unique) |
4 | signature | String | M | 32 | Signature will use MD5 with the component below: MD5(username+password+bookingID) |
Here is the example of Notify Payment message:
Request XML :
<?xml version="1.0" ?>
<notification>
<type>reqnotification</type>
<bookingid>123456789</bookingid>
<clientid>1</clientid>
<customer_name>Faisal</customer_name>
<issuer_bank>Bank Rakyat Indonesia</issuer_bank>
<issuer_name>NAMA BIN NAMA</issuer_name>
<amount>100000</amount>
<productid>01</productid>
<trxid>0000021805410607000014000000000000</trxid>
<trx_date>2011-11-08 22:20:33</trx_date>
<username>partner</username>
<notification_datetime>2011-11-08 22:30:43</notification_datetime>
<signature>9bb575179ef43032d7dee3e57bbb5575</signature>
</notification>
Response XML :
<?xml version="1.0" ?>
<return>
<type>resnotification</type>
<ack>00</ack>
<bookingid>123456789</bookingid>
<signature>9bb575179ef43032d7dee3e57bbb5575</signature>
</return>
Sometimes notifications are having problems, such as notification response is not received from the merchant. If this happens, then the notification will be sent again. Merchant should receive the notification and reply with "ack" 78 if previous notification has been deemed responded. And our system will repeat up to 3 times after the first data packet requested.