Skip to main content
POST
Force a verification result
Provider sandbox on this deployment. Our backend targets the bank provider’s sandbox: bank details are test details, no real transfer settles, and settlement lands on a testnet (read network from GET /v1/config). Known limits: only the EUR/IBAN rail is wired for the simulated pay-in, and identity checks run on test-mode applicants. Every response says which environment answered in its environment field.

Authorizations

Authorization
string
header
required

Your API key, issued by us and shown once at creation.

Body

application/json
applicantId
string
required

A test-mode applicant at the identity provider.

Minimum string length: 1
reviewAnswer
enum<string>
required

The provider's own vocabulary: GREEN approves, RED rejects.

Available options:
GREEN,
RED

Response

The provider's simulation answer.

environment
enum<string>
required

Which environment answered. sandbox: at least one money upstream is the provider's sandbox - no real money moves there, and the card corridor is the sandbox's asset (read GET /v1/config), not the documented production one. production: every configured upstream is real. Derived from the configured upstream hosts at boot, never a flag.

Available options:
sandbox,
production
Example:

"sandbox"

testEnvironment
boolean
required

Always true: nothing recorded off these endpoints is a real event.

result
any
required

The provider's own simulation answer, verbatim.