Skip to main content
POST
/
user
/
block
Block a user
curl --request POST \
  --url https://api.sdev.banking.ingopayments.tech/api/v4/user/block \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '
{
  "api_key": "YOUR_API_KEY",
  "user_id": "user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef"
}
'
{
  "status": "success",
  "message": "operation completed",
  "data": {
    "items": [
      {
        "id": "user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef",
        "uuid": "<string>",
        "first_name": "Jane",
        "middle_name": "<string>",
        "last_name": "Doe",
        "email": "jane.doe@example.com",
        "phone_number": "+12125551234",
        "date_of_birth": "1990-04-15",
        "address_one": "<string>",
        "address_two": "<string>",
        "city": "<string>",
        "state": "<string>",
        "country": "<string>",
        "postal_code": "<string>",
        "ssn_last_4": "6789",
        "status": "active",
        "kyc_status": "verified",
        "created_at": "2026-04-16T12:34:56.000Z",
        "updated_at": "2026-04-16T12:34:56.000Z"
      }
    ],
    "pagination": {
      "page": 1,
      "per_page": 25,
      "total": 100,
      "sort": "created_at:desc",
      "search": "jane"
    }
  }
}

Documentation Index

Fetch the complete documentation index at: https://developers.ingopayments.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
api_key
string
header
required

Program API key identifying your integration. Pass as the api_key HTTP header (preferred) or as an api_key field in the JSON request body. Required on every request in addition to the HMAC Authorization header.

Body

application/json
​
user_id
string
required

Identifier of the target user. Required when the endpoint operates on a specific user.

Example:

"user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef"

​
api_key
string

Program API key. Accepted either in the api_key HTTP header or as this body field.

​
reason
string

Free-form reason describing why the state change occurred.

Response

Success.

​
status
enum<string>
required
Available options:
success
​
message
string
required
Example:

"operation completed"

​
data
object

Endpoint-specific payload; shape varies per operation.