Skip to main content
Yativo refuses some requests before the endpoint runs: a suspended account, a banned customer, a key used from the wrong IP, or a KYC payload that looks like test data. This page lists what can trigger a block, the exact error you receive, and what to do next. Related guides: Authentication, IP whitelisting, KYC / KYB, API responses and errors.

What can restrict access

A block is not a validation error you can retry with the same payload. Fix the cause, or contact support if the account, key, IP or customer is locked.

Your account

These apply to the business that owns the API key, not to an end customer.

API keys and IPs

Production keys must have at least one allowed IP. Sandbox keys may omit a whitelist; if you set one, it is still enforced. See IP whitelisting.
Calling production from an IP that isn’t on the key’s allow list does more than return 403. After two such attempts the key is revoked and later calls return 401 Invalid or revoked API credentials. Add the new IP in Developers → API Keys before you deploy, or mint a new key after a revoke.
The customer’s browser does not need to be on the IP allow list. Only the server that sends X-Api-Key / X-Api-Secret does — including when you mint a KYC session.

Customers

These checks look at customer_id on the request (JSON body or query). A banned customer is refused even if the rest of the payload is valid. On the KYC platform the same customer can also be refused with:

Placeholder and test KYC data

KYC and KYB submissions must be the customer’s real identity. A payload that looks like test or placeholder data is rejected and the customer_id is permanently flagged. Corrected data on the same id will not go through. This is separate from the older 403 Access denied. rule for names that contain test, yativo or admin. Don’t submit documentation samples. These patterns are refused (and flag the customer) if they appear anywhere in the POST body:
  • Placeholder people: Jane Doe, John Doe, John Smith
  • Placeholder companies: Acme, “my company”, “company name”
  • Marker words: test, demo, sample, dummy, sandbox, fake, lorem
  • Emails on example.com / example.net / example.org
  • Addresses such as 123 Main Street
  • Form labels submitted as values (first name, your name, n/a, unknown)
Use the customer’s legal name, a mailbox they own, and their real address. Sandbox still blocks placeholder names — it only substitutes Nigerian identity numbers. See Sandbox KYC.

KYC sessions and hosted pages

Hosted KYC/KYB URLs and the KYC platform submit/update APIs require a signed session (or your API key pair from a server). Lookup endpoints stay public. See Mint a KYC session.

File uploads

Every KYC file must be PDF, JPG, JPEG, PNG, HEIC or TIF (ID images: PDF, JPG, JPEG, PNG only), and between 5 KB and 30 MB. Every file is scanned.

Emails Yativo won’t accept

customer_email values with a + alias are also rejected on POST /customer.

Employees

Corporate-card employees have their own status. See Corporate cards.

How to recover

1

Read the exact data.error or message

Match it to the tables above. A 422 on one field is usually a payload fix. A 403/401 about banned, blocked, suspended or revoked is not.
2

Stop retrying locks

Don’t loop on a banned customer, a revoked key, or a blocked IP. Retries can extend an IP throttle into a block.
3

Fix what you control

Add the server IP before you deploy. Mint a fresh KYC session when the hosted page returns 401. Submit real identity data, not documentation samples.
4

Contact support for locks you can't clear

Suspended accounts, revoked keys you didn’t revoke, blocked IPs, platform-banned customers, and malware blocks need support. Include the customer_id, the request_id from error_details if you have one, and the exact error string.