Fraud Awareness Week is here! Discover your hidden fraud risks with Dojah’s free assessments.Review Your Defences
arrow
Skip to content
back

Go back to Blog

Jennifer Edidiong

Marketing

11 min read

Share to

What to Look for in a KYC API SLA Before Signing a Contract

A vendor's sales deck says "99.9% uptime." You sign. Three months later, the verification API stalls for an hour on a Monday morning, your sign-up flow stops, and the contract covers neither the hour nor the customers you lost.

The gap between what a vendor says and what the contract promises is exactly what an SLA decides. A service level agreement is the part of the contract that turns the sales pitch into obligations: how much downtime is acceptable, how fast the vendor responds when something breaks, and what you get if it fails. For a KYC API this matters more than for most, because every outage stops customers from signing up, and part of the service depends on government databases the vendor does not control.

This guide is for product, compliance and engineering teams about to sign with a KYC provider. It covers how to read an uptime promise, what to ask about government data sources, which support and remedy terms matter and what Nigerian law and the CBN expect of your vendor contract.

Read the Uptime Number Properly

A percentage means little until you turn it into time. Over a year, 99.9% allows about 8.76 hours of downtime, roughly 43 minutes a month, and 99.99% allows about 53 minutes a year. Each extra nine is a different promise, and the figure only means something once you know how it was produced. Check four things in the contract:

  • How it is measured: The contract should say whose monitoring is used and how often it checks. A vendor that measures only from its own servers can report "up" while your customers cannot get through.
  • The time window: A yearly average can hide a bad month. A single eight-hour outage fits inside a 99.9% yearly figure, but measured monthly, that month would come in at about 98.9%.
  • Which services count: A platform-wide average can hide one failing check, such as BVN lookups, so look for a figure for each API.
  • What is excluded: Planned maintenance, third-party outages and "force majeure" can swallow a lot. Get each exclusion in writing, along with how much notice maintenance requires.

 

Look at Upstream Data Sources

A KYC check often depends on a government or identity database that the vendor does not control. Dojah's documentation, for example, has a status code for when a dependent source such as a government or identity provider fails or does not respond. Many SLAs exclude these sources, and a vendor that says so openly is more useful than one that promises everything.

Two practical points belong in the contract. Get written confirmation of whether calls that fail because a source is down are billed, and whether retries are. And check what you can do while a source is down: retry guidance, and a way to hold a customer in a pending state. In EasyOnboard, for example, a session can be retried when a government check was temporarily unavailable.

 

Look at Speed and Success, Not Only Availability

An API that is "up" but slow still breaks onboarding, so availability is only part of the picture. Ask for response-time targets for each endpoint, ideally the median and the slowest few percent, and check where they are measured. A figure taken at the vendor's edge says little about what your customers on Nigerian networks experience.

Ask for a success rate for each check type too, with a written definition of success, and decide in advance whether "no record found" and timeouts count towards it. Confirm the rate limits and whether there is room for bursts, such as a campaign launch or salary-day traffic. And keep your own log of calls, response codes and response times. It lets you check the vendor's reports and gives you evidence if you need to claim a credit.

 

Check Support Terms

Support terms decide how long an outage lasts once it starts. Look for these in the contract:

  • Severity levels: The contract should define what counts as critical, with response and resolution targets for each level. An incident where production is down or most checks are failing deserves a far faster response than a how-to question.
  • Hours and channels: Confirm whether support covers nights and weekends in your time zone, and whether it comes by phone, chat or email.
  • Escalation: Know who you contact when something breaks and who they escalate to if it is not fixed.
  • Which channel starts the clock: An incident raised in chat or a community channel may not count, while a ticket or email does, so check which one the SLA recognises.

 

Look at Remedies

An SLA without consequences is a brochure. Check what you get when the vendor misses a target:

  • How credits are applied: Service credits should be applied automatically. If you have to claim them, check the deadline, because a short one means most credits go unclaimed.
  • What a credit is worth: Check what it is calculated on. If it is a share of your monthly fee, compare it with what an hour of lost signups costs you, and see whether a cap makes it meaningless. As an example, 120 signup attempts an hour, one hour of downtime and a 60% completion rate means 72 customers not onboarded. Use your own numbers.
  • Repeat failures: Look for a right to terminate after repeated breaches, and for credits that increase when targets are missed more than once.
  • Other remedies: Check whether credits are your only remedy, and read the liability limits that sit beside the SLA.

 

Expect Clear Incident Communication

During an outage, silence costs you almost as much as the outage does. The contract should say how and how fast the vendor tells you about an incident, and whether there is a public status page you can subscribe to. After a serious incident, expect a written report with a timeline, the cause, the customers affected and the fix, and look for advance notice of planned maintenance and the hours it runs.

 

Check Data Protection and Security Terms

A KYC vendor handles your customers' identity data, so your duties under the Nigeria Data Protection Act reach into the contract. Section 29 requires a controller that engages a processor to ensure the processor complies with the Act, assists with compliance and operates under a written agreement. Section 40 requires a processor to notify the controller on becoming aware of a breach, and the controller then has 72 hours to notify the Commission where the breach poses a risk. Write a notice deadline into the contract that leaves you most of that window.

Confirm where data and backups are stored, which subprocessors touch them and how long images and records are kept. Dojah's docs, for example, say file links for selfies and documents expire within about an hour, so you copy them to your own storage. Know what you must keep yourself.

 

Plan Your Exit Before You Enter

If you are a CBN-regulated entity, the Baseline Standards for Automated AML Solutions list customer identification and verification among an AML solution's functions, so a KYC vendor typically falls under them. They expect:

  • A vendor management policy: It should cover procurement, implementation, support, change management, incident handling and exit strategies, so the contract should support each of those.
  • Heightened due diligence: You should assess the vendor's ability to support your own configuration, give you access to audit and validation data, and meet the Standards' governance requirements.
  • Resilience and data location: The solution must stay available, with disaster recovery arrangements so monitoring and screening do not degrade during outages or migrations, and processing and storage must comply with Nigerian data sovereignty and privacy laws.
  • Telling the CBN: You must tell your supervisory department which AML solutions you use, and about any material change, so switching vendors is a regulatory event.

That makes the exit terms worth negotiating before you sign. The contract should say in what format and how quickly you get your data, and what help the vendor gives. Make sure you can keep verification records and audit trails after you leave, for as long as the law requires you to retain them, and get written confirmation that the vendor has deleted your data. Check the notice period, any exit fees, and whether service continues on the same terms until you have moved.

 

How Dojah Supports Your SLA Review

Dojah's documentation covers the points that sit in your hands, so you can check a lot before you sign and keep checking after you go live.

  • Error handling: The errors guide lists each status code and says which to retry. Timeouts, a dependent source failing and server errors are worth retrying with a delay, while bad requests, wrong keys, an empty wallet and "no record found" are not worth retrying unchanged.
  • Testing before launch: The sandbox uses the same requests and response shapes as production, returns mock data and never charges your wallet, so you can test your integration before launch. It cannot show how upstream sources behave in production.
  • Service health: The dashboard includes an API Status page showing the real-time health of each service, with a status, a strip of recent uptime and incident banners. It reflects Dojah's own services, so if a check fails only for you while the service shows online, the cause is more likely your request or balance. Dojah also keeps a public status page with live uptime and incident history, where you can subscribe to updates during incidents.
  • Your own records: The Usage page logs every API call with its cost, service, status code and outcome. You can filter by service or status code and export the data, which helps you check failure rates, reconcile billing and back up a claim.
  • Support channels: Dojah lists four ways to get help: the Help Centre for pricing, billing and account questions, technical support for failing calls and production incidents, Slack for questions about how Dojah works, and live chat in the dashboard. Keep customer data out of the public Slack community.
  • Billing and change: Each production call draws from a prepaid wallet, and a call your balance cannot cover returns a 402 and is not processed. You can set a low-balance alert and turn on auto top-up so an empty wallet does not stop production. Dojah also publishes a changelog of API changes, so ask the team what notice you get for breaking changes.

For SLA terms such as uptime targets, support response times and credits, ask the Dojah team for the current terms in writing, as you would with any vendor. As with any vendor, confirm in writing how failed and upstream-failed calls are billed.

Treat the SLA as part of the product. A clear one, agreed before you sign, is cheaper than a dispute after an outage.

Comparing KYC APIs? Fintechs and banks can see how Dojah's identity verification products fit their onboarding flow, then take the SLA points above to the team.

 

Frequently Asked Questions

1. What is a good uptime SLA for a KYC API?
There is no single right number, but know what it means in time. 99.9% allows about 8.76 hours of downtime a year, and 99.99% about 53 minutes. Compare how each vendor measures it and what it excludes.

2. Do KYC API SLAs cover government data sources?
Often they do not, because those sources sit outside the vendor's control. Check whether upstream failures are covered and how the vendor reports them.

3. What should I check besides uptime?
Response times, success rates, support severity levels, service credits, incident communication, data protection terms, and your rights to export and delete data when the contract ends.

4. Are service credits enough?
Credits reduce your bill after a missed target. They are based on your fees, not necessarily your losses, so also check termination rights and liability limits.

5. What does the CBN expect when I use a third-party KYC vendor?
The Baseline Standards expect a vendor management policy covering procurement, support, change management, incident handling and exit, plus heightened due diligence on the vendor and data handling that follows Nigerian law.

6. What should happen to my data if I leave a KYC vendor?
You should be able to export your records, keep the audit evidence the law requires you to retain, and get written confirmation that the vendor has deleted your data.

Start using Dojah for all your business needs

Explore more

Subscribe to our newsletter

Get notified when we publish new stories, announcements, products and more. Subscribe to receive updates.