Account holder APIPayout and vendor operations
Verify account holders, including fixed-amount virtual accounts.
Not every account you need to check is an ordinary bank account. Verify account holders using bank and account details, including virtual accounts that require a designated amount.
Ordinary accounts. Amount-verified virtual accounts.
Choose the lookup that matches the account type. For an amount-verified virtual account, you must already know the designated amount.
Ordinary accounts
Check the account holder using the bank and account number.
Amount-verified virtual accounts
Provide the bank, account number, and designated amount to check the account holder.
Amount-verified virtual account lookups require the correct designated amount.
Start checking before payouts, without a certificate.
No issuer registration or joint certificate is needed. Add checks at account registration or before a payout, and pay only for accounts whose holder is returned.
No joint certificateNo issuer registration is needed either.
Pay for successful lookupsNo deduction when no account holder is found.
Pricing and requirements
Before you get started.
Account holder lookup
50 points per successful account lookup
Only accounts that returned a holder are charged. Misses, failures, and quota rejections cost nothing, and test keys are always free.
No charge for accounts whose holder cannot be found or whose lookup fails. No subscription plan restriction applies.
- Amount-verified virtual accounts require the correct designated amount.
- See the official documentation for supported banks.
Duplicate billing exclusions apply only within one request. Ordinary accounts are charged once per bank and account number, virtual accounts per unique amount. Separate requests are charged again.
See how point top-ups work (opens in a new tab)Build with your AI tool
Start with the AI tool you already use.
Copy a prompt with official documentation, prerequisites, and test goals into the AI tool you use for your project.
Read the prompt
Integrate this Bolta API into the current project. Verify account holders, including fixed-amount virtual accounts. Read the official documentation first and propose an implementation that fits the project's language and structure. https://docs.bolta.io/llms.txt https://docs.bolta.io/docs/api-introduction/quickstart https://docs.bolta.io/docs/api-introduction/bank-account-holder https://docs.bolta.io/docs/api-introduction/pricing Prerequisites and scope: - Amount-verified virtual accounts require the correct designated amount. - See the official documentation for supported banks. Account holder lookup: 50 points per successful account lookup No charge for accounts whose holder cannot be found or whose lookup fails. No subscription plan restriction applies. Read the API key from a server environment variable. Do not ask for secrets in chat. Start with the documented test key and test inputs. Test goals: Test ordinary and amount-verified virtual account success, amount mismatch, and lookup failure. Distinguish duplicate entries within one request from separately billed repeat requests. Do not invent undocumented features or responses. Identify open questions and summarize test results and production-readiness steps.
Questions before you integrate
Are repeat lookups charged again?
Yes. A new request is charged again. Within a single request, duplicate ordinary accounts with the same bank and account number are charged once. Amount-verified virtual accounts are charged for each unique amount.
What if we do not know the designated amount?
You need the correct designated amount for an amount-verified virtual account.