Skip to main content
POST

Authorizations

Authorization
string
header
required

JWT Bearer token obtained from /api/v1.0/access-token/b2b

Headers

X-PARTNER-ID
string
required

Your unique partner API key

Accept
string
default:application/json
required
Content-Type
string
default:application/json
required

Body

application/json
command
enum<string>
required

Biller command, mapped 1:1 to a flat category (pulsa→PULSA, data→DATA, plntok→PLNTOK, topupg→TOPUPG, vouchg→VOUCHG, strmg→STRMG, emoney→EMONEY, ewallet→EWALLET, cashwd→CASHWD)

Available options:
pulsa,
data,
plntok,
topupg,
vouchg,
strmg,
emoney,
ewallet,
cashwd
Example:

"pulsa"

data
object
required

Response

Payment accepted (00 success / 01 pending)

V3 prepaid payment response (direct and inquiry-based). response_code 00 = success at vendor, 01 = pending (final status arrives via callback). Extra vendor fields (customer_name, token, serial_number, ...) depend on the command template.

command
string
Example:

"pulsa"

response_code
enum<string>
Available options:
00,
01
Example:

"01"

response_text
string
Example:

"Payment pending"

data
object