For originators
Your workspace is at your own subdomain, for example yourco.spcr.io. Four
screens do the work.
Before you register anything, check your receivables documentation ties the certificate to the claim. A certificate has to be unable to move without the receivable it represents, and the receivable unable to move without it. If they can move independently, the registry record and legal title drift apart and the registry stops proving anything. See How to begin.
Dashboard
Your pools, and how many receivables in each are available versus sold.
Register receivables
- Choose a pool first. The rest of the form stays hidden until you do. Registration cannot be undone and receivables in the wrong pool are not fixable, so the choice is made explicitly rather than defaulted.
- Upload a loan tape (
.xlsx,.xls,.csv,.tsvor text) or type Loan IDs by hand. Up to 5,000 rows per submission. - Review the rows, then submit.
Every row is judged on its own, so one bad row never blocks the good ones. Each comes back with its own verdict:
| Verdict | What to do |
|---|---|
| Registered | Nothing. It is on chain, with a transaction link. |
| Rejected, invalid format | Fix the Loan ID and resubmit that row. See Loan ID rules. |
| Rejected, already registered | Stop and look into it. That Loan ID exists somewhere in the registry already. |
That third verdict is the double-pledge guard doing its job. If you did not expect it, something is wrong with your tape: check for duplicates inside the file, or whether you already registered that batch.
Accepted rows are minted immediately into custody. There is no STOKR approval step. Large batches are split across several transactions automatically.
If a row ever reports that it registered on chain but the record failed to save, the screen tells you explicitly not to retry. The certificate already exists. Contact STOKR; there is a tool that re-links it without minting anything again.
Creating a pool
From Register receivables, use + New pool:
- Code. 3 to 41 characters, letters, digits and
-_/.(e.g.YOURCO-2026-P1) - Name. Free text, whatever helps you identify it
- Passkey. See Pools and passkeys
- Pool represents. A whole asset, or a tranche
Tranches
A tranche is expressed entirely inside the Loan ID, as a prefix:
JUNIOR-YOURCO-2026-P1-L0001. No other part of the system changes: the
identifier is a hash of the Loan ID, so JUNIOR-X, SENIOR-X and plain X are
three different receivables to the chain and to the uniqueness index.
Each tranche is its own pool, created separately, because a pool is the unit that gets sold to one funder. Your loan tape does not need the prefix: it is added for you and the rows are rewritten visibly on screen before submission, so you see the exact identifier about to be registered.
Give each tranche a different passkey. Nothing stops you reusing one, but a funder who bought only the junior tranche would then hold the credential that also verifies the senior tranche.
After registering into a tranche pool, download the loan tape the result panel offers and send that to the funder. It carries the prefixed identifiers and the passkey, so they can verify the whole tranche in one upload without editing anything. It also contains the passkey, so it goes to the intended funder and nowhere else.
Transfer
Sell a whole pool to a funder, as one block.
- This is irreversible. Once a batch confirms on chain it cannot be undone.
- You may be asked to re-enter your password if you have not signed in recently.
- Large pools are processed in resumable batches, and the screen reports exactly how many receivables actually moved. On a partial failure it tells you the real number rather than claiming all-or-nothing.
Once sold, a pool locks. Receivables registered into an already-sold pool go straight to that funder's vault rather than into custody, keeping the pool consistently owned. That is the roll-over case and it is intentional.
Receivables
Everything you have registered, pool by pool, with custody status and a link to each on-chain transaction.