Developers · Grid Protocol

Build on the
protocol.

GrydFi is infrastructure, not a product you resell. Everything the network does — consent, matching, disclosure, lifecycle — is a typed message you can send and receive. Embed the widget, integrate the API, or implement the protocol yourself.

Get sandbox access→Integration reference ↓

Three ways in.

All three reach the same network and the same institutions. Pick the one that matches how much of the surface you want to own.

M—01One line

Widget embed

A script tag renders the whole consent-and-offer flow inside your product, on its own origin. Your servers never see a name, a phone number or a PAN.

Marketplaces, payroll apps, POS, checkout

M—0250–200 lines

Server-to-server API

Publish your credit criteria, receive matches as they happen, confirm terms, and report the loan lifecycle back. You keep your own interface end to end.

Banks, NBFCs, HFCs, SFBs with their own stack

M—03Your codebase

Implement the protocol

The Grid protocol is a set of typed messages. Any institution can implement it directly with the open-source protocol SDK and speak to the network as a peer.

Institutions building their own rails

The one-line version

The widget is served from its own origin, validates every message against your registered domains, never reads your DOM and never writes to browser storage. Set the locale and it renders in your user's language.

BundleSmall — it will not slow your page down

First renderunder 1 second on 3G

Languagesen · hi · bn · mr · ta · te · kn · gu

Storagenone — stateless per session

embed.jssandbox

<script src="https://widget.gridfy.in/v1/embed.js"
  data-channel-id="ch_yourapp_prod"
  data-product="personal_loan"
  data-locale="fr"
  data-container="#credit-slot">
</script>

No PII crosses your serverCSP-safe

Consent is the API.

Consent is granted a step at a time and can be withdrawn the same way. Withdraw one and the network cascades it for you — that is behaviour you inherit, not behaviour you implement.

On device

Nothing identifying reaches your servers. The widget mints a profile token in the browser and works from that.

Scoped

Every grant carries a purpose and an expiry, and is recorded in a ledger the borrower and their regulator can both read.

Reversible

A withdrawal propagates to every participant that relied on it. You get a signed event; you do not maintain the graph.

The tier model, the scopes each step unlocks and the event names are in the integration reference below.

Start in the sandbox.

An isolated instance with mock providers and synthetic profiles. Sign-up is self-serve and free; no call, no contract.

To first API call

5 min

third-party developer

Channel to first capsule

1 hr

widget embed

Lender to first appetite

4 hrs

API integration

Synthetic profiles

10,000

in the sandbox

Onboarding figures are current targets from the product spec, not measured medians — we will publish measured numbers once there is a production series worth quoting.

Accès contrôlé

La référence d'intégration est partagée avec les partenaires.

Les capacités du protocole sont publiques — chaque type de message, endpoint et charge utile d'événement ne l'est pas. Saisissez votre phrase d'accès partenaire pour ouvrir la référence, ou demandez un accès et nous vous en enverrons une.

Pourquoi un accès contrôlé ? Publier l'intégralité de la surface de messages revient à remettre à n'importe qui une carte du protocole. Les partenaires l'obtiennent sur demande ; la description des capacités ci-dessous est publique et le restera toujours.

Inside the reference

Endpoint reference

Protocol message catalogue

Authentication and key rotation

SLA targets

Consent tier model

Client libraries

Developers

Sandbox access is instant.

Production access follows one call. Bring your use case; we'll bring the phrase for the reference.

Get sandbox access→