Skip to main content
POST
/
api
/
v2.0
/
ewallet
/
account-inquiry
Inquiry Account
curl --request POST \
  --url https://sandbox-payment-b2b.singapay.id/api/v2.0/ewallet/account-inquiry \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-PARTNER-ID: <api-key>' \
  --data '
{
  "account_id": "01K5G4FZZ18DMK0M5QTR8Y9QY9",
  "ewallet_code": "DANA",
  "customer_number": "085733347341",
  "amount": {
    "value": "10000.00",
    "currency": "IDR"
  }
}
'
{
  "response_code": "SP000",
  "response_message": "Successful",
  "data": {
    "ewallet_code": "DANA",
    "customer_number": "085733347341",
    "customer_name": "John Doe",
    "min_amount": {
      "value": "10000.00",
      "currency": "IDR"
    },
    "max_amount": {
      "value": "10000.00",
      "currency": "IDR"
    },
    "amount": {
      "value": "10000.00",
      "currency": "IDR"
    },
    "fee_amount": {
      "value": "10000.00",
      "currency": "IDR"
    },
    "gross_amount": {
      "value": "10000.00",
      "currency": "IDR"
    }
  }
}

Authorizations

​
Authorization
string
header
required

JWT issued by POST /api/v1.1/access-token/b2b. Send Authorization: Bearer <token>.

​
X-PARTNER-ID
string
header
required

Merchant API key (Credential.api_key). Required on every request.

Body

application/json

Request payload for validating e-wallet beneficiary and retrieving transfer limits and fee information.

​
account_id
string
required

Unique identifier (ULID) of the merchant account from which funds will be transferred.

Maximum string length: 64
Example:

"01K5G4FZZ18DMK0M5QTR8Y9QY9"

​
ewallet_code
string
required

E-wallet provider code. Supported providers: DANA, OVO, GOPAY, SHOPEEPAY. Must be a valid code from the provider list.

Example:

"DANA"

​
customer_number
string
required

Beneficiary phone number or e-wallet account identifier. Format and validation rules are specific to the selected e-wallet provider.

Required string length: 10 - 15
Example:

"085733347341"

​
amount
object
required

Transfer amount to be validated against provider limits and available balance.

Response

Success — data matches EwalletAccountInquirySuccessData (SP000)

Success response data from account inquiry endpoint (HTTP 200). Includes beneficiary details, transfer limits, and fee calculation.

​
response_code
string

Standardized response code (e.g., SP000 for success)

Example:

"SP000"

​
response_message
string

Human-readable response message

Example:

"Successful"

​
data
object

Detailed data about the e-wallet account inquiry result