> ## 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. # Show Detail > Retrieves full details of a single cardless withdrawal including status, OTP, fee breakdown, and balance impact. The `{id}` parameter is the `transaction_id`, not the numeric ID. ## OpenAPI ````yaml https://payment-b2b.singapay.id/api/docs/merchant-api.json get /api/v1.0/cardless-withdrawals/{account_id}/show/{id} 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/v1.0/cardless-withdrawals/{account_id}/show/{id}: get: tags: - Cardless Withdrawal summary: Show Detail description: >- Retrieves full details of a single cardless withdrawal including status, OTP, fee breakdown, and balance impact. The `{id}` parameter is the `transaction_id`, not the numeric ID. operationId: cardlessWithdrawalShow parameters: - name: account_id in: path description: >- Unique identifier (ULID) of the merchant account. Must belong to the authenticated merchant. required: true schema: type: string example: 01K946KF851RK7FX075GJHBVKF - name: id in: path description: >- The `transaction_id` of the cardless withdrawal to retrieve. This is the platform-assigned business identifier returned when the withdrawal was created. required: true schema: type: string example: CW-20251024-0001 responses: '200': description: >- Success. Returns the cardless withdrawal transaction detail with the associated account information. content: application/json: schema: $ref: '#/components/schemas/ResponderSuccessCardlessWithdrawal' '403': description: >- Forbidden. The authenticated merchant does not have access to the specified account. content: application/json: schema: $ref: '#/components/schemas/ResponderErrorEnvelope403' '404': description: >- Not found. The account or the specified withdrawal transaction does not exist. content: application/json: schema: $ref: '#/components/schemas/ResponderErrorEnvelope404' '503': description: >- Service unavailable. The Cardless Withdrawal feature is not available yet in the current environment. content: application/json: schema: $ref: '#/components/schemas/ResponderErrorEnvelope503' security: - BearerAuth: [] PartnerId: [] components: schemas: ResponderSuccessCardlessWithdrawal: description: >- Success response envelope for cardless withdrawal endpoints returning a single transaction record. required: - status - success - data properties: status: description: HTTP status code echoed in the response body. type: integer example: 200 success: description: Indicates whether the request completed successfully. type: boolean example: true data: $ref: '#/components/schemas/CardlessWithdrawalResource' description: The cardless withdrawal transaction record. type: object ResponderErrorEnvelope403: required: - status - success - error properties: status: type: integer example: 403 success: type: boolean example: false error: $ref: '#/components/schemas/ResponderErrorBody403' type: object ResponderErrorEnvelope404: required: - status - success - error properties: status: type: integer example: 404 success: type: boolean example: false error: $ref: '#/components/schemas/ResponderErrorBody404' type: object ResponderErrorEnvelope503: required: - status - success - error properties: status: type: integer example: 503 success: type: boolean example: false error: $ref: '#/components/schemas/ResponderErrorBody503' type: object CardlessWithdrawalResource: description: >- Cardless withdrawal transaction record returned by list, show, create, and cancel endpoints. properties: id: description: Internal record identifier. type: integer example: 1001 transaction_id: description: >- Unique transaction identifier assigned by the platform. Use this value when calling the show, cancel, or delete endpoints. type: string example: CW-20251024-0001 status: description: >- Current transaction lifecycle status. `pending` — awaiting OTP redemption at ATM; `success` — funds withdrawn; `expired` — OTP expired before redemption; `failed` — withdrawal failed; `refunded` — funds returned to merchant; `canceled` — merchant canceled the withdrawal. type: string enum: - pending - success - expired - failed - refunded - canceled example: pending otp_number: description: >- One-time password (OTP) that the end customer enters at the ATM to complete the cardless withdrawal. Only present while the transaction is in `pending` status. type: - string - 'null' example: '847291' otp_expired_at: description: >- ISO 8601 timestamp indicating when the OTP expires. The customer must complete the ATM withdrawal before this time. type: - string - 'null' format: date-time example: '2025-10-24T14:00:00+07:00' amount: description: >- Net withdrawal amount in IDR (the denomination selected by the merchant, excluding fees). type: number example: 500000 vendor_fee: description: >- Fee charged by the bank or payment channel for processing the withdrawal, in IDR. type: - number - 'null' example: 6500 our_margin: description: Platform service fee applied to the transaction, in IDR. type: - number - 'null' example: 1500 total_paid: description: >- Total amount debited from the merchant account in IDR. Calculated as `amount` + `vendor_fee` + `our_margin`. type: number example: 508000 transaction_type: description: Type classification of the transaction. type: - string - 'null' example: withdrawal balance_before: description: >- Merchant account balance (in IDR) immediately before this withdrawal was processed. type: - number - 'null' example: 1500000 balance_after: description: >- Merchant account balance (in IDR) immediately after this withdrawal was processed. type: - number - 'null' example: 992000 created_at: description: ISO 8601 timestamp when the withdrawal was created. type: - string - 'null' format: date-time example: '2025-10-24T13:44:39+07:00' updated_at: description: ISO 8601 timestamp when the withdrawal record was last updated. type: - string - 'null' format: date-time example: '2025-10-24T13:45:07+07:00' type: object ResponderErrorBody403: properties: code: type: integer example: 403 message: type: string example: Access denied. type: object ResponderErrorBody404: properties: code: type: integer example: 404 message: type: string example: Account not found. type: object ResponderErrorBody503: properties: code: type: integer example: 503 message: type: string example: Service temporarily unavailable. 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 ````