For the complete documentation index, see llms.txt. This page is also available as Markdown.

Customer Top Up Status

This is one of the services providing user e-money transaction history in list format, where partners are able to query the date range for transaction history information. Response may vary depending on the transaction history owned by the user, where partners need to maintain its UI and UX in paginating.

Technical Specification

Service Code: 39

Body Request

No
Name
Type
Mandatory
Min Length
Max Length
Description

1

originalPartnerReferenceNo

String

M

1

64

Transaction identifier on service consumer system

2

originalReferenceNo

String

M

1

64

Transaction identifier on service provider system. Must be filled upon successful transaction

3

serviceCode

String

M

1

2

To identify which transaction that needs to be checked, must filled with 38

Sample Request

{
  "originalPartnerReferenceNo": "78912343452347893",
  "originalReferenceNo": "2211150005490937",
  "serviceCode": "38"
}

Body Response

No
Name
Type
Mandatory
Min Length
Max Length
Description

1

responseCode

M

1

7

BI SNAP Response Code.

2

responseMessage

String

M

1

150

BI SNAP Response Message.

3

originalReferenceNo

String

O

1

64

Transaction identifier/reference generated by PJP AIS Selain Bank.

4

originalPartnerReferenceNo

String

O

1

64

Transaction identifier on service consumer system

5

serviceCode

String

M

1

2

To identify which transaction that needs to be checked, filled with 38

6

amount

O

1

2

Detail of amount transaction

7

latestTransactionStatus

String

M

1

2

Latest transaction status labelled with constants.

8

transactionStatusDesc

String

O

1

50

Transaction status description

Sample Response

Response Code & Message

The table below lists response codes and messages for the Customer Top Up Status API.

No
HTTP Code
Code
Message (Indonesian)

1

200

2003900

Successful

2

400

4003900

Bad request

3

400

4003901

Invalid field format {field}

4

400

4003902

Invalid mandatory field {field}

5

401

4013901

Invalid token (B2B)

6

401

4013900

Unauthorised. [Reason]

7

403

4033901

Feature not allowed

8

403

4033904

Activity count limit exceeded

9

404

4043908

Invalid merchant

10

500

5003900

General error

11

504

5043900

Timeout

Last updated