> ## Documentation Index > Fetch the complete documentation index at: https://docs.singapay.id/llms.txt > Use this file to discover all available pages before exploring further. # Inquiry Status > Retrieves the current status of a previously initiated e-wallet transfer. This endpoint looks up the transaction by reference number and returns detailed status information. For transactions still in Pending status, the endpoint may query the e-wallet provider for updated status information. Status codes include 00 (Success), 03 (Pending), and 06 (Failed). Network timeouts during provider status checks will result in error code SP005. ## OpenAPI ````yaml https://payment-b2b.singapay.id/api/docs/merchant-api.json post /api/v2.0/ewallet/{account_id}/inquiry-status openapi: 3.1.0 info: title: Singa Merchant API description: >- OpenAPI specification for the merchant/partner HTTP API. All routes below are additionally protected by `ip.whitelisted.merchant` — the caller IP must be registered for the credential or merchant. Obtain a JWT using `POST /api/v1.0/access-token/b2b` (Basic auth) or `POST /api/v1.1/access-token/b2b` (X-Signature) before calling secured endpoints. version: 1.0.0 servers: - url: https://sandbox-payment-b2b.singapay.id description: >- API host. Paths include `/api` prefix (see `RouteServiceProvider`). Replace scheme/host with your environment. security: [] tags: - name: Security description: >- Merchant authentication (`OauthMerchantTokenController`). **v1.1** B2B token uses `X-CLIENT-ID`, `X-PARTNER-ID`, and `X-Signature` (no Basic auth). Secured routes also require the issued Bearer JWT plus `X-PARTNER-ID`. - name: Accounts description: >- Account management (`routes/merchantApiRoute.php`, `v1.0`). Path parameter `{id}` is always the account ULID. - name: Balance Inquiry description: >- Merchant and per-account balance inquiry (`BalanceController`, `v1.0`). Path `account_id` is the account ULID. - name: Statements description: >- Per-account statement list and detail (`AccountController::accountStatements`, `accountStatementDetail`, prefix `v1.0/statements`). Flugger responses; detail path param `{statement_id}` maps to `statements.transaction_id`. - name: Payment Link description: >- Payment link CRUD and payment-method catalog (`PaymentLinkApiController`, prefix `v1.0/payment-link-manage`). `account_id` is ULID; `payment_link_id` is numeric `payment_links.id`. - name: Payment Link History description: >- Payment link transaction/history listing and detail (`PaymentLinkApiController`, prefix `v1.0/payment-link-histories`). `history_id` is numeric `payment_link_histories.id`. - name: Virtual Account description: >- Native VA CRUD (`VirtualAccountController`, prefix `v1.0/virtual-accounts`). `account_id` and `virtual_account_id` are ULIDs. - name: VA Transaction description: >- VA money-in transaction listing and detail (`VirtualAccountController`, prefix `v1.0/va-transactions`). - name: QRIS (Money In) description: >- MPM dynamic QRIS list, show, and generate (`QrisMpmDynamicApiController`, prefix `v1.0/qris-dynamic`). - name: QRIS (Money Out) description: >- Issuer MPM decode/inquiry, payment credit (money out), and transaction status (`QrisIssuerMpmController`, `QrisApiV2Controller::checkStatus`, prefix `v2.0/qris`). Related list/detail: `GET /api/v2.0/qris/transaction/...`. - name: E-Wallet (Money In) description: >- E-Wallet Native checkout and transactions (`EwalletNativeApiController`, `EwalletNativeTransactionApiController`, `EwalletNativeV2ApiController`). Paths include `v1.0/ewallet-native`, `v1.0/ewallet-native-transactions`, and `v2.0/ewallet-native`. - name: E-Wallet (Money Out) description: >- E-wallet disbursement / top-up to beneficiary wallets (`EWalletTopUpController`, prefix `v2.0/ewallet`). Responses use the custom **`MerchantV2ApiEnvelope`** with **`MerchantV2ResponseCode`** (SP000–SP020). - name: Card (Money In) description: >- One-time card payment, cancel, and inquiry (`CardPaymentMerchantApiController`, prefix `v2.0/card`). - name: Subscription (Recurring) description: >- Credit-card recurring subscription plans (`SubscriptionPlanApiController`, prefix `v2.0/recurring`). Plan `{id}` is UUID (`sub_plans.id`). - name: Direct Debit description: >- Direct Debit — bind a customer bank account once via hosted webview, then charge it host-to-host (`DirectDebitMerchantController`, prefix `v2.0/direct-debit`). Binding `{binding_id}` and transaction `{transaction_id}` are UUIDs. Responses use the **`MerchantV2ApiEnvelope`** with both standard SP000–SP020 codes and Direct-Debit-specific codes (`SP_DD_*`). The `/charge` endpoint is additionally protected by **`X-Signature`** + **`X-Timestamp`** (`verify.signature-internal`); see operation parameters for the signing scheme. - name: Account Transfer description: >- Move funds between sub-accounts within the same merchant (`AnotherAccountApiController`, prefix `v1.0/account-transfer`). The transfer endpoint requires request signature headers (`verify.signature-internal`). Both accounts must belong to the authenticated merchant and be accessible to the credential. - name: Disbursement (Money Out) description: >- Bank disbursement (`DisbursementController` **v1.0**, `DisbursementV2Controller` **v2.0**). **v1.0** list/show/fee/beneficiary/transfer use Flugg envelopes; v1 inquiry-status uses the **custom v2 envelope** (`MerchantV2ApiEnvelope`, codes **SP000–SP020**). **v2.0** check-beneficiary, transfer, and inquiry-status use the same custom envelope — see component schema **`MerchantV2ResponseCode`** for the full response code table. - name: Cardless Withdrawal description: >- Cardless withdrawal API for initiating ATM cash withdrawals without a physical card. Supports creating withdrawals with OTP generation, listing transaction history, viewing transaction details, canceling pending withdrawals, and deleting canceled records. All endpoints use the `v1.0/cardless-withdrawals` route prefix and the standard success/error response envelope. Path parameter `{id}` refers to the `transaction_id` (platform-assigned business identifier). paths: /api/v2.0/ewallet/{account_id}/inquiry-status: post: tags: - E-Wallet (Money Out) summary: Inquiry Status description: >- Retrieves the current status of a previously initiated e-wallet transfer. This endpoint looks up the transaction by reference number and returns detailed status information. For transactions still in Pending status, the endpoint may query the e-wallet provider for updated status information. Status codes include 00 (Success), 03 (Pending), and 06 (Failed). Network timeouts during provider status checks will result in error code SP005. operationId: ewalletTopUpInquiryStatus parameters: - name: account_id in: path required: true schema: description: Account ULID type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/EwalletTopUpInquiryStatusRequest' responses: '200': description: Success — `data` matches `EwalletInquiryStatusSuccessData` content: application/json: schema: $ref: >- #/components/schemas/EwalletMoneyOutInquiryStatusSuccessResponse '404': description: '**SP020** account not found' content: application/json: schema: $ref: >- #/components/schemas/EwalletMoneyOutBeneficiaryInfoNotFoundResponse '504': description: '**SP009** vendor status refresh timeout' content: application/json: schema: $ref: '#/components/schemas/EwalletMoneyOutTimeoutResponse' security: - BearerAuth: [] PartnerId: [] components: schemas: EwalletTopUpInquiryStatusRequest: description: >- Request payload to retrieve the current status of a previously initiated e-wallet transfer. required: - reference_number properties: reference_number: description: Reference identifier of the transaction to check type: string maxLength: 64 example: REF-001 type: object EwalletMoneyOutInquiryStatusSuccessResponse: description: >- Success response data from inquiry status endpoint (HTTP 200). Contains current transaction status and financial details. May trigger vendor status refresh if transaction is still pending. properties: response_code: description: Standardized response code (e.g., SP000 for success) type: string example: SP000 response_message: description: Human-readable response message type: string example: Successful data: $ref: '#/components/schemas/EwalletInquiryStatusSuccessData' description: Detailed data about the transaction status inquiry result type: object EwalletMoneyOutBeneficiaryInfoNotFoundResponse: description: >- Response when beneficiary information is not found during account inquiry. properties: response_code: description: Standardized response code (e.g., SP117 for beneficiary not found) type: string example: SP117 response_message: description: Human-readable response message type: string example: Beneficiary not found data: description: Additional data or null when beneficiary is not found properties: ewallet_code: description: E-wallet provider code that was queried type: string example: DANA customer_number: description: Beneficiary account identifier that was queried type: string example: '085733347341' type: object type: object EwalletMoneyOutTimeoutResponse: description: Response when a timeout occurs during account inquiry or status refresh. properties: response_code: description: Standardized response code (e.g., SP009 for timeout) type: string example: SP009 response_message: description: Human-readable response message type: string example: Upstream timeout data: description: Additional data or null when a timeout occurs properties: reference_number: description: Reference number of the transaction that experienced a timeout type: string example: '176458254538481' type: object type: object EwalletInquiryStatusSuccessData: description: >- Success response data from inquiry status endpoint (HTTP 200). Contains current transaction status and financial details. May trigger vendor status refresh if transaction is still pending. properties: transaction_id: description: Unique system-generated transaction identifier type: string example: EWT-20260402-0001 transaction_status: $ref: '#/components/schemas/EwalletTopUpTransactionStatus' description: >- Current transaction processing status (may be refreshed from provider) reference_number: description: Your reference identifier for tracking this transaction type: string example: REF-001 notes: description: Optional notes associated with the transaction type: - string - 'null' example: Top up DANA ewallet: description: Beneficiary e-wallet information properties: code: description: E-wallet provider code type: string example: DANA customer_number: description: Beneficiary account identifier type: string example: '085733347341' customer_name: description: Beneficiary name type: - string - 'null' example: John Doe type: object post_timestamp: description: ISO 8601 timestamp when transaction was initiated type: string example: '2026-04-02T10:30:00+07:00' processed_timestamp: description: ISO 8601 timestamp when transaction was completed or failed type: string example: '2026-04-02T10:30:05+07:00' balance_after: $ref: '#/components/schemas/EwalletMoneyOutMoneyAmount' description: Merchant account balance after transaction amount: $ref: '#/components/schemas/EwalletMoneyOutMoneyAmount' description: Net amount received by beneficiary fee_amount: $ref: '#/components/schemas/EwalletMoneyOutMoneyAmount' description: Platform or provider fee for this transaction gross_amount: $ref: '#/components/schemas/EwalletMoneyOutMoneyAmount' description: Total deducted amount (net + fee) type: object EwalletTopUpTransactionStatus: description: Transaction status information with provider-specific status codes. properties: code: description: >- Standardized transaction status code: `00` (Success), `03` (Pending), `06` (Failed), or other provider-specific codes type: string example: '03' desc: description: Human-readable status description type: string example: Pending type: object EwalletMoneyOutMoneyAmount: description: >- Monetary amount with currency information. All amounts are displayed with exactly 2 decimal places. required: - value - currency properties: value: description: Numeric amount with exactly 2 decimal places (e.g., 10000.50) type: string pattern: ^\d+\.\d{2}$ example: '10000.00' currency: description: Currency code (ISO 4217) type: string enum: - IDR example: IDR type: object securitySchemes: BearerAuth: type: http description: >- JWT issued by `POST /api/v1.1/access-token/b2b`. Send `Authorization: Bearer `. bearerFormat: JWT scheme: bearer PartnerId: type: apiKey description: Merchant API key (`Credential.api_key`). Required on every request. name: X-PARTNER-ID in: header ````