# Verifia by AnybanQ

> Identity verification, screening, bills and bank payments for Sri Lanka, on one API.
> Merchants issue bills and collect from a customer's bank account through HNB JustPay,
> verify identities and bank accounts, screen against sanctions lists, and run their
> loyalty and voucher programmes. Customers see everything in AnybanQPay at
> https://pay.anybanq.lk.

## What it does

- Bills and payments: register an invoice, issue a pay-link, take payment from a
  linked bank account, reconcile settlement, refund. Instalments (2-3 months) are
  available per merchant.
- Payment links and a pay button, with no code written at all: a merchant makes a
  link in the dashboard at [payment links](https://verifia.anybanq.lk/payment-links) and sends it, or mints a
  signed product code and pastes one tag on its own website —
  `<script src="https://verifia.anybanq.lk/sdk/v1/pay-button.js" data-verifia-pay="CODE"></script>`.
  The price lives inside the signed code, on our side, so there is no API key on
  the page and editing the page cannot change what is charged.
- Verification: bank account ownership, NIC format and structure, mobile ownership
  by OTP, liveness and face match.
- Screening and monitoring: OFAC, EU, UN, UK OFSI and Sri Lanka designated persons,
  with ongoing re-screening when a list changes, and a customer risk register with
  PEP handling and periodic review.
- Regulatory reporting: STR and CTR drafts exported in goAML XML for FIU-CBSL.
- Loyalty and vouchers: points programmes, merchant gift vouchers, and voucher swaps
  settled in LKR. No stored value or e-money is held.
- E-signature: signing requests with multiple signers. Electronic signatures are
  legally recognised in Sri Lanka under the Electronic Transactions Act No. 19 of
  2006 (amended 2017); wills, powers of attorney, trusts, bills of exchange and
  land sale or transfer are excluded.
- API hub: a merchant's own commerce API is reached through one hub contract, so
  products, orders, voucher validation, voucher redemption and points balances can be
  read from systems the merchant already runs.

## How integration works

- Authentication: an API key as `Authorization: Bearer divp_live_...`. The legacy
  `x-api-key` header is still accepted.
- Environments: a `divp_test_` key runs in the sandbox — no bank, registry or SMS
  gateway is contacted and nothing is metered. A `divp_live_` key reaches the real
  thing. A sandbox key is issued with the account at signup, before any review;
  live keys come after approval.
- Sandbox outcomes are deterministic: the last four digits of an NIC or account
  number choose the result (0000 verifies, 1111 not found, 2222 times out, 3333 is
  malformed), and an amount of 999.99 is always declined. The same rules, with
  worked examples, are published for humans at [the developer guide](https://verifia.anybanq.lk/developers).
- Driving it from an assistant: an MCP server wraps bills, pay links, verifications
  and the account's own price list as tools for Claude or any other MCP client. It
  is not published to a package registry yet — ask us for it.
- Money: amounts carry an explicit currency and are never assumed to be LKR. Fields
  documented as minor units are in minor units.
- Webhooks: subscribe to events, with replay of failed deliveries.
- Write operations are idempotent where a repeat would move money twice.

## Pricing

Prices are not published. Plans carry a monthly fee with an included verification
quota, and further checks are charged per use; plan and volume discounts apply. There
is no setup fee, and nothing is charged for sandbox usage. A merchant sees its own
effective rate for every feature in the dashboard, and [we will quote you](mailto:hello@clobe.lk)
for your volumes.

## Getting started

- [Integration guide, sandbox rules and key handling](https://verifia.anybanq.lk/developers)
- [Sign up](https://verifia.anybanq.lk/register) — the response hands back a sandbox key you can call
  with immediately; it is shown once and only its hash is kept.
- Onboarding needs: business registration number and certificate, at least one director
  with NIC, and a settlement bank account. A platform officer reviews every application
  and approves, returns it for changes, or declines with a reason.
- API reference: the OpenAPI document is served to authenticated merchants in the
  dashboard rather than published openly.
- [Security and data protection](https://verifia.anybanq.lk/trust)

## Limits and honesty

- Sri Lanka has no national NIC registry API, so NIC checks validate format and
  structure; identity is further evidenced by mobile OTP and bank account linking.
- Card acceptance is not offered. Payments settle from bank accounts through HNB
  JustPay.
- AnybanQ holds no customer balances and issues no e-money.

## Contact

- [AnyBanQ — support and integration](https://anybanq.lk)
- [Verifia](https://verifia.anybanq.lk)