Try the full loop
Play both sides: register a business as an MSME, get it verified, then switch to Financier and request that business's verified credential, both before and after consent is granted. Every action here is a real call through the gateway, appended to the same hash-chained ledger the API docs describe.
Identity verification (Fayda eSignet) is still a stub in this MVP: the button below always verifies with a fixed dummy id, no real Fayda flow yet. Business verification (eTrade) is real: it needs an identifier that actually exists in the connected eTrade registry.
Step 1 of 6
Register
livePOST /ledger/msme: self-registration, the only ledger write that doesn't need an existing MSME id.
Verify identity (Fayda eSignet)
stubPOST /connectors/fayda/verify: not a real Fayda flow yet; always verifies with the dummy id 123. Optional, but one click.
Verify business (eTrade)
livePOST /connectors/etrade/verify: a real lookup against the connected eTrade registry (via tsverse), not simulated. Optional: skip if you don't have a real identifier on hand.
Grant consent
livePOST /consent/grant: give a financier scoped access to this MSME's verified data.
Revoke consent
livePOST /consent/revoke. Optional: take a scope back from a grantee.
View my full credential
liveGET /credentials/:msmeId: no grantee, so this is the MSME's own unfiltered copy.
That's the whole MSME side. Switch to the Financier tab to request this same credential and see disclosure change with consent.
Step 1 of 2
Request the verified credential
liveGET /credentials/:msmeId?grantee=<you>: what you get back depends entirely on what's currently been granted to your id.
Whatever id the MSME granted access to on the other tab.
Verify the credential's signature
livePOST /credentials/verify: the one route that never needs the platform API key. An independent signature check, the same one a bank's own code could run without this API at all.