v2
latestSwagger 2.02026-08-0610101.9 MBBank account restrictions
Apply bank account restriction
Applies a restriction to a bank account.
Reason codes
| Code | Description |
|---|---|
| customer-request | Account holder requested temporary restriction pending further instruction. |
| deceased | Account holder confirmed deceased. Restricted pending estate administration. |
| dormant | Account inactive for 2+ years (no customer-initiated transactions). |
| fraud-1st-party | Account holder is suspected perpetrator committing fraud against Griffin or third parties. |
| fraud-3rd-party | Account holder is victim of account takeover by unauthorised party. |
| fraud-app-perpetrator | Account holder is perpetrator receiving fraudulent payments from victims. |
| fraud-app-victim | Account holder is victim tricked into authorising payments to a fraudulent recipient. |
| law-enforcement | Restricted following law enforcement request, court order, or legal obligation. |
| money-laundering | Suspected money laundering detected. Restricted pending investigation. |
| other | Restriction applied for reasons not covered by standard categories. |
| risk-appetite | Account activity exceeds risk appetite thresholds. Restricted pending review. |
| sanctions | Account holder or associated party identified on a sanctions list. Restricted pending investigation. |
| terrorist-financing | Suspected terrorist financing. Restricted pending investigation. |
Legal status
| Code | Description |
|---|---|
| suspected | Restriction due to suspicion of offence. No formal charges filed. |
| formal-charge-filed | Customer formally charged with an offence. Legal proceedings active. |
| conviction-confirmed | Customer convicted. Deposits connected with the conviction are ineligible for FSCS compensation. |
| not-applicable | Legal status not relevant (e.g. customer requests, dormant accounts). |
post/v0/bank/accounts/{bank-account-id}/restrictions
Path parameters
bank-account-idstring required
Request body
Response
Created
Example response
{
"restriction-applied-by": {
"user-url": "/v0/users/ur.ICAgICAgICAgdXNlci1pZA",
"user-username": "user@example.com"
}
}