> ## 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. # Unbind Card > Revokes an active binding. After this completes the binding can no longer be charged. Some banks require OTP; in that case the response is **HTTP 202** with `data.otp_required=true` and an `otp_handoff` block, and the merchant must follow up with `POST /verify-otp`. Other banks use a fire-and-forget flow; the binding remains in its current `status` until the `direct-debit.unbinding.succeeded` webhook confirms the final state. No request body is required. ## OpenAPI ````yaml https://payment-b2b.singapay.id/api/docs/merchant-api.json post /api/v2.0/direct-debit/bindings/{binding_id}/unbind 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/direct-debit/bindings/{binding_id}/unbind: post: tags: - Direct Debit summary: Unbind Card description: >- Revokes an active binding. After this completes the binding can no longer be charged. Some banks require OTP; in that case the response is **HTTP 202** with `data.otp_required=true` and an `otp_handoff` block, and the merchant must follow up with `POST /verify-otp`. Other banks use a fire-and-forget flow; the binding remains in its current `status` until the `direct-debit.unbinding.succeeded` webhook confirms the final state. No request body is required. operationId: directDebitBindingsUnbind parameters: - name: binding_id in: path description: UUID of a `DirectDebitBinding` owned by the authenticated merchant. required: true schema: type: string format: uuid responses: '200': description: >- **SP000** Unbinding initiated (fire-and-forget). `data` matches `DirectDebitBindingData`; `status` flips to `UNBOUND` only after the `direct-debit.unbinding.succeeded` callback lands. content: application/json: schema: $ref: '#/components/schemas/MerchantV2ApiEnvelope' example: response_code: SP000 response_message: Unbinding initiated data: binding_id: 9a1c5b3e-2d4f-4d8c-93cf-9a1c5b3e2d4f customer_ref: cust-9001 bank_code: '008' masked_card: 888xxxxxxxxx1234 status: ACTIVE payment_otp_mode: WITH_OTP created_at: '2026-06-04T07:25:01+07:00' updated_at: '2026-06-04T08:10:01+07:00' failure_reason: null '202': description: >- **SP000** OTP required — `data` matches `DirectDebitUnbindOtpRequiredData`. Persist `otp_handoff` and submit it back through `POST /verify-otp` along with the OTP the customer received. content: application/json: schema: $ref: '#/components/schemas/MerchantV2ApiEnvelope' example: response_code: SP000 response_message: OTP required to complete unbinding data: binding_id: 9a1c5b3e-2d4f-4d8c-93cf-9a1c5b3e2d4f status: PENDING_OTP otp_required: true otp_handoff: flow: UNBINDING external_id: 9a1c5b3e2d4f4d8c93cf9a1c5b3e2d4f partner_reference_no: DD-UNBIND-1717476601 reference_no: GW-REF-2026060400123 otp_token: TKN-9f3c7b9e1a2d8e6f '401': description: Unauthorized. content: application/json: schema: $ref: '#/components/schemas/MerchantV2ApiEnvelope' example: response_code: '4010000' response_message: Unauthorized data: null '404': description: '**SP_DD_NOT_FOUND** — binding not found for this merchant.' content: application/json: schema: $ref: '#/components/schemas/MerchantV2ApiEnvelope' example: response_code: SP_DD_NOT_FOUND response_message: Binding not found data: null '502': description: >- **SP_DD_UNBIND_FAILED** — the gateway rejected the unbind request before we could persist a state. content: application/json: schema: $ref: '#/components/schemas/MerchantV2ApiEnvelope' example: response_code: SP_DD_UNBIND_FAILED response_message: Failed to unbind. Please retry. data: null security: - BearerAuth: [] PartnerId: [] components: schemas: MerchantV2ApiEnvelope: description: >- SingaPay Merchant API v2 custom response envelope (`ApiResponderHelper::responseJson`, `ApiResponseTrait`). Business outcome is determined by `response_code` (SP000–SP020), not by HTTP status alone. On success (`SP000`), `data` holds the operation payload. On errors, `data` often includes a `message` and may echo request fields. required: - response_code - response_message properties: response_code: $ref: '#/components/schemas/MerchantV2ResponseCode' response_message: $ref: '#/components/schemas/MerchantV2ResponseMessage' data: description: >- Endpoint-specific payload on success, or error context (validation message, inquiry result with `status` invalid, etc.). type: - object - 'null' additionalProperties: true type: object example: response_code: SP000 response_message: Successfully data: [] MerchantV2ResponseCode: description: SingaPay custom business response code. type: string example: SP000 MerchantV2ResponseMessage: description: Human-readable label paired with `response_code`. type: string example: Successfully 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 ````