Standalone Card Unbinding
Market: ZA South Africa
Unbinds a previously bound cardToken, making it permanently unavailable for future payments. Once unbound, the card can no longer be used in cardPayerInfo when calling [CreateOrder]. To pay with the same card again, the cardholder must complete [Bind Card] again to obtain a new cardToken.
⚠️ Precondition: this endpoint only succeeds when the target
cardTokenis currently incardStatus = 1(Linked). Calling it on a token that is not in this state (e.g. never completed binding, already unbound, or in any other status) returnsAC000006. Always confirm the token's current status via [Token Query] before calling this endpoint if you are not certain.
Typical use cases: cardholder removes a saved card from their wallet, merchant offboards a stored payment method on customer request, compliance-driven token cleanup.
Request Parameters
Yes = required · No = optional
Response Fields
Example — Success
Request / Response
Example — Failure
Unbinding fails if the cardToken is not currently in cardStatus = 1 (Linked) — for example, if it was already unbound, never completed binding, or is otherwise invalid.
Idempotency Note
Calling this endpoint again with a cardToken that has already been unbound does not return a success response. Since the token is no longer in cardStatus = 1, the request fails with AC000006. Merchants should treat AC000006 on a retry as confirmation that the token is already unbound, rather than as an unexpected error.
Card Status Requirement
Error Codes
Additional error codes may apply for common platform-level errors (signature errors, IP allowlist, etc.) — refer to the [Open Platform error code reference].