KreedX — Banking API and Payments Platformby DigiPulse Solutions
Now live — Verification (PAN, Aadhaar, GSTIN, CIN), Recharge and Flight & Bus Booking APIs, plus the Recharge & Travel Portal.Now live — Verification (PAN, Aadhaar, GSTIN, CIN), Recharge and Flight & Bus Booking APIs, plus the Recharge & Travel Portal.Now live — Verification (PAN, Aadhaar, GSTIN, CIN), Recharge and Flight & Bus Booking APIs, plus the Recharge & Travel Portal.
KYC & KYB Verification

KYC & KYB Verification APICheck who you are onboarding, before you onboard them.

Verify a person or a business from inside your own onboarding flow — PAN, Aadhaar through DigiLocker, GSTIN, CIN, bank account and IFSC, each answered from the source record.

Book a demo Talk to our team

What's available

  • PANLive
  • Aadhaar (DigiLocker)Live
  • GSTINLive
  • CIN / companyLive
  • Bank accountLive
  • IFSCLive
PAN, Aadhaar, GSTIN, CIN, bank
Live
Checked against the issuing record
Source
Answer back in the request
Same call
Integration for KYC and KYB
One
How it worksWhat's includedWho it's forDay one vs paperworkSpecsFAQ
How it works

Where the money actually goes.

Not a sign-up checklist — the real path one transaction takes, and which part of it is ours to run.

Verification is live on the KreedX Verification APIs. One integration checks a person or a business against the source record — PAN, Aadhaar through DigiLocker, GSTIN, CIN, bank account and IFSC — and answers in the same call, so your onboarding screen can decide without sending the customer away.

  1. Step 01

    Send the identifier

    Your onboarding form posts the number the customer typed — PAN, GSTIN, CIN, an account number with IFSC, or an Aadhaar consent flow through DigiLocker.

  2. Step 02

    We check the source

    The request goes to the issuing record rather than a copied dataset, so what comes back is what the authority itself holds right now.

  3. Step 03

    Get the answer back

    The response says whether it is valid and returns the details on record — registered name, status and the fields your check needs — so your screen can accept or reject without a person reading a document.

  4. Step 04

    Keep the trail

    Every check carries a reference ID, so a review months later can show what was verified, when, and what the source said at that moment.

What's included

What you get with the integration.

Every line here is something that exists today, not a roadmap item.

  • PAN & Aadhaar (DigiLocker) — live
  • GSTIN, CIN & company checks — live
  • Bank account & IFSC — live
  • One integration for KYC and KYB
Who it's for

Teams who ask for this first.

Each one is buying the same rails for a different reason.

Fintechs and lenders onboarding customers or merchants
Marketplaces checking the businesses that sell on them
Banks and NBFCs running KYC and KYB at scale
Any team replacing document uploads with a real-time check
Before you plan your timeline

What is live on day one, and what needs paperwork.

Most product pages only show the fast half. Here is both, so your launch date is built on the real one.

Live on day oneSame day

  • Sandbox credentials and full API documentation, up front
  • Every check callable from the first day, with test identifiers
  • A reference ID on each response for your audit trail
  • A named integration contact, not a ticket queue

Needs paperwork firstAllow time

  • Production keys — issued once commercials and documentation are in place
  • Compliance checks, which run in parallel with your build
  • A go-live review of how your side handles a failed or inconclusive check
Specifications

The facts, without the prose.

The things a technical evaluator scrolls straight down to find.

Individual (KYC)PAN basic and detailed, Aadhaar via DigiLocker, bank account
Business (KYB)GSTIN, GSTIN checked against PAN, CIN basic and advanced company checks
BankingBank account verification and IFSC lookup
SourceChecked against the issuing record, not a cached dataset
ResponseValidity plus the details on record, returned in the same call
AuditA reference ID per check, so a later review can show what was seen and when
IntegrationREST API · sandbox and production environments
SupportIntegration team through sandbox, testing and go-live
Questions

Asked before every integration.

What can I verify today?+

PAN (basic and detailed), Aadhaar through DigiLocker, GSTIN including GSTIN checked against a PAN, CIN with basic and advanced company checks, bank account and IFSC — all live, through the same integration and the same credentials.

Is this checking a real record or a copied database?+

The check goes to the source record, not a cached copy. That is the point: a name or status that changed last week comes back changed, instead of however some dataset looked when it was last refreshed.

Can I use it for both KYC and KYB?+

Yes. PAN, Aadhaar and bank account cover individual KYC; GSTIN, CIN and the company checks cover business KYB. One integration serves both, so onboarding a customer and onboarding a merchant do not need two different vendors.

How fast does a check come back?+

Each call answers within the same request, so your screen does not have to park the customer and come back later. The exact timing depends on the source being queried — we walk you through what to expect for each check during integration.

Also on the same rails

What teams usually add next.

See it running on your own use case.

A 30-minute call where we walk one live transaction end to end, against the flow you actually need.

Book a demo info@digipulse.co