Try Verify with free verifications included in your plan
You can now run Verify checks on your own real data, in production, without buying an add-on first. Eligible organizations receive a free allowance of verifications included in their plan, usable from the Yousign app and from the API with a production API key.
EligibilityAvailable on Plus, Pro and Scale plans, for organizations with the API enabled in production. An organization whose subscription is still in its own trial period receives no allowance.
The allowance is granted automatically when your organization becomes eligible. Start by visiting the Application to check the experience and to check the amount of credits available.
Each verification type carries its own allowance, counted separately:
| Verification | Included |
|---|---|
| Image Identity Verification | 5 |
| Company Registry Verification (France) | 2 |
| Company Registry Verification (Germany) | 2 |
| Company Registry Verification (Italy) | 2 |
| Bank Account IBAN Verification | 2 |
The allowance is granted once per organization. It has no expiry date and is never topped up. It is shared across all your workspaces and all your users, whoever creates the verification and wherever they create it from.
Verifications created with a sandbox API key never draw on it.
How units are counted
A unit is reserved when the verification is created, then settled when the verification reaches a terminal status. A verification that ends on a status Yousign does not bill gives its unit back.
| Verification | Consumes a unit | Gives the unit back |
|---|---|---|
| Image Identity Verification | verified, failed | inconclusive |
| Bank Account IBAN Verification | verified, failed | inconclusive |
| Company Registry Verification | verified | failed, inconclusive |
A retry is a new verification, so it draws a new unit.
When your allowance is used up
Creating another verification of that type answers 400 with the error type included_quota.limit_reached.
This is a new error type. An organization that never had access to a verification type keeps receiving configuration.not_enabled, unchanged. The two are deliberately distinct, so you can tell an allowance that is spent from an entitlement you never had.
Only creation is refused. Verifications you already created stay readable, and each verification type runs out on its own.
Remaining counts are not exposed on the API. Read them in the app under Verify > Verifications, or handle the 400.
When you buy the add-on
Buying the matching Verify add-on ends the free allowance for that verification type. Any unspent units are dropped and your organization switches to the metered add-on. Verifications still running when the purchase lands settle on the free allowance and are never invoiced. Your other verification types are unaffected.
Start with : Initiate a new Identity Document Verification, Initiate a new Company Verification or Initiate a new Bank Account Lookup Verification.

