Authorization
Example:
Authorization | Bearer Paste-Your-API-Key-HereResponse
Successful ResponseMain Structure (Root)
Status code returned by the API.
Status message that describes the status code.
The payment-channel configuration object for the merchant.
data Structure (Object)
Unique identifier of the payment-channel configuration record.
Identifier of the merchant that owns this configuration.
Whether the Akulaku (paylater) channel is approved for this merchant. May be
null when not yet reviewed.Whether the credit/debit card channel is approved for this merchant. May be
null when not yet reviewed.Whether the static QRIS channel is approved for this merchant. May be
null when not yet reviewed.Whether the admin fee is charged to the customer rather than the merchant.
Whether the per-channel fee is charged to the customer rather than the merchant.
Whether rate limiting is currently active for this merchant’s channels.
List of available payment channels and their enabled state.
Human-readable channel name (e.g.
Bank Transfer Mandiri).Whether the channel is enabled for this merchant.
Relative path to the channel’s logo image.
Channel type. One of
qris, va, ewallet, card, retail, paylater, qris_static.Channel code (e.g.
MANDIRI, OVO, ALFAMART). May be null for some channels.Creation timestamp (Unix epoch, in milliseconds).
Last-update timestamp (Unix epoch, in milliseconds).
Errors
Returned when the channel configuration cannot be read:
{ "statusCode": 500, "messages": "<error>" }.