Block Subscriber
POST
/subscribers/{id}/blockOpen in the API playground →
Warning
Blocking a subscriber prevents all transactions on their account and any linked cards.
Request
Authorizationstringheaderrequired
Bearer olive_live_xxx or Bearer eyJ... (JWT)
Path Parameters
idstringpathrequired
Subscriber UUID (e.g., sub_abc123)
Body Parameters
reasonstringbodyrequired
Reason for blocking the account. This is logged for audit.
Response
successboolean
Whether block succeeded
messagestring
Result message
Examples
Request
cURL
curl -X POST "https://demo.api.vultlocal.com/api/v1/subscribers/sub_abc123/block" \
-H "Authorization: Bearer olive_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"reason": "Suspicious activity detected - multiple failed PIN attempts"
}'
Response
200 OK
{
"success": true,
"message": "Subscriber blocked successfully",
"blocked_at": "2025-01-20T14:45:00Z",
"blocked_by": "admin@smartpay.sl"
}
404 Not Found
{
"error": "Subscriber not found",
"code": "NOT_FOUND"
}
What Gets Blocked
Account Actions
- All wallet transactions
- P2P transfers
- Cash-in/cash-out
- PIN changes
Card Actions
- All linked cards blocked
- POS payments rejected
- NFC tap disabled
Common Reasons
| Reason Type | Example |
|---|---|
| Security | "Multiple failed PIN attempts" |
| Fraud | "Suspected fraudulent activity" |
| KYC | "KYC documents not verified" |
| Compliance | "AML screening flag" |
| Request | "Customer requested block" |
Errors
| Status | Code | Description |
|---|---|---|
| 400 | MISSING_REASON | Reason is required |
| 401 | UNAUTHORIZED | Invalid or missing API key |
| 403 | FORBIDDEN | Insufficient permissions |
| 404 | NOT_FOUND | Subscriber not found |
| 409 | ALREADY_BLOCKED | Subscriber already blocked |
| 500 | INTERNAL_ERROR | Server error |
Related
Unblock Subscriber
Restore access to a blocked subscriber account