Skip to main content

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 TypeExample
Security"Multiple failed PIN attempts"
Fraud"Suspected fraudulent activity"
KYC"KYC documents not verified"
Compliance"AML screening flag"
Request"Customer requested block"

Errors

StatusCodeDescription
400MISSING_REASONReason is required
401UNAUTHORIZEDInvalid or missing API key
403FORBIDDENInsufficient permissions
404NOT_FOUNDSubscriber not found
409ALREADY_BLOCKEDSubscriber already blocked
500INTERNAL_ERRORServer error

Unblock Subscriber

Restore access to a blocked subscriber account