What SPCR knows, and what it does not

What leaves your systems is a Loan ID.

Per receivable, SPCR stores

• The Loan ID you chose.
• Which pool it belongs to.
• Its on-chain identifier and current holder.

No borrower name, no debtor, no amount, no interest rate, no due date, no documents.

On the blockchain

A 256-bit identifier and an owner address. The Loan ID is not on chain, and neither is anything listed above. There is no NFT metadata either: tokenURI returns an empty string, so a certificate carries none of the name, image or description a normal NFT would.

Your loan tape is not uploaded

When you verify, the file is parsed entirely in your browser and never leaves it.

When you register, the cell values are sent to an extraction service so the Loan ID column can be found in a file whose layout we have never seen. Only the Loan ID is ever put on the blockchain. If you would rather not send cell values at all, type the Loan IDs in by hand, or hand the file a clean single column so the deterministic in-browser parser handles it without help.

What SPCR does not disclose

Who holds a receivable. The public verification page shows the vault address holding it, which the chain publishes anyway, but never the funder's name. The mapping from address to name is shown only inside a workspace, to the party entitled to it.

Anything commercial. No amount, no rate, no debtor. SPCR does not hold those, so nobody can learn them from the registry.

What that means for the double-pledge guarantee

The guarantee works on identifiers, not on underlying assets. SPCR can tell you that the identifier ACME-2026-P1-L0044 is registered once and held by one party. It cannot tell you that ACME-2026-P1-L0044 and some other identifier are the same underlying loan. That is a commercial and contractual matter, and we would rather say so than let it be assumed.