💳Card States

• issuing - an initial state for a Card. This state is immediately assigned to an entity created via POST /accounts/{accountId}/cards endpoint. At this stage we perform request validations (checking whether a Customer and an Account are active) and submit an issuing request to our banking partner. If our validations or partner request failed, an entity is transitioned to issue_failed state
• issue_failed - a Card issuance request did not pass validations or was rejected by our banking partner. A new request must be submitted. This is a final state

• active - a Card is successfully issued and can be used to make payments. An entity can be temporarily deactivated in case of any issues. In this case an entity is transitioned to inactive state. You can also deactivate Card yourself using PATCH /cards/{cardId}/deactivate endpoint. If we suspect any illicit activity, a Card is transitioned to suspended state. If we have evidence of any illicit activity received through our constant monitoring workflows, an entity is transitioned to blocked state. Finally, if card termination was requested via DELETE /cards/{cardId} endpoint, it is transitioned to terminated
• inactive - a Card is temporarily deactivated. It can be re-activated using PATCH /cards/{cardId}/activate endpoint
• blocked - we have evidence of illicit activity by the cardholder. This is a final state

• suspended - a Card has been suspended as we suspect illicit activity by the cardholder. If suspicions are not confirmed, a Card is transitioned back to active, otherwise - to blocked

• terminated - a Card termination has been requested. This is a final state. Please, note, that while this card is no longer available for new payments and authorisations, we have to respect all fund capture requests for pending authorisation within 30 days from termination date