The one thing you can put beside a working capital line that is not a loan.
Invoice discounting, factoring, anchor-led programmes, early-payment: every product on your platform is an advance against something that has not been paid yet, and every one of them carries underwriting, tenor, first-loss and recovery. A duty credit scrip is not that. It is an asset your exporter already owns and is already permitted to transfer. Selling one is a disposal, so none of that machinery applies, and the fee lands on a relationship you already have.
Idle credit, turned into cash, without a limit being used.
Your exporters accumulate RoDTEP and RoSCTL credits against shipments they have already made. Those credits sit in a government ledger, expire on a fixed clock, and until they are sold they finance nothing. This is what changes for the firm inside your product.
The firm is not drawing on a line, so the sale does not compete with the exposure you already extended and does not need to be underwritten again. A firm that liquidates a matured credit draws less on your facility, not more.
One all-in number, priced for that specific credit and firm for sixty seconds. The number is produced per credit and held firm, by scheme with its methodology and its history, so the number your product shows is one the firm can go and check.
An anchor-led programme reaches the suppliers an anchor will vouch for. A scrip sale needs no anchor, no limit and no rating: the exporter either holds the credit or it does not. That is a materially wider slice of your registered base than your credit products can serve.
Six calls for a working sell flow. One for a rate panel.
REST, JSON, one header. Money is integer paise, price is basis points of face value, time is ISO IST. There is no SDK you are obliged to adopt and no widget you have to host. The smallest honest integration is a read-only rate panel that needs no key and no agreement at all.
The reference rate endpoints are public and unauthenticated, with the methodology and per-scheme history alongside them. A rate panel in your dashboard is a day of work, tells you whether your users care, and commits you to nothing.
A sandbox key is bound to a test IEC and returns simulated inventory in exactly the production shape, so screens, empty states and the connect flow can all be finished and demoed internally before a live agreement exists.
Orders take an idempotency key, so a timeout on your side is a repeat rather than a second trade. Events are signed so you can prove they came from us, retried with backoff, and dead-lettered rather than dropped, with endpoints to list what failed and replay it yourself.
Positions and orders read back per firm. The event export returns your own log in sequence with a running SHA-256 chain and a final digest you can recompute independently, so a dispute starts from a record rather than from two spreadsheets.
The question your legal team asks first.
Before scrip liquidity is a roadmap item it is a risk review, and the review is short. Title, customer money, credentials, KYC, and what happens when a trade fails. Here is each one, stated so it can be checked rather than trusted.
ScripX trades as principal. It buys the credit into its own name and sells it on, so it is the counterparty on both legs. That is two transfers and two sets of documents, and your platform is party to neither. Nothing lands on your balance sheet, there is no chain of title running through you, and you are not an intermediary facilitating a trade between two other people.
Settlement is delivery versus payment. The buyer's funds are secured before the transfer is initiated and released to the seller only once the transfer is confirmed. If a leg fails, the settlement unwinds and the secured funds go back. Every rupee of that runs between ScripX and the firm, so you are not a payment intermediary and you hold no float.
Registering a firm on the API rejects any credential-shaped field outright and tells you to use the separate verification call instead. Verification and authorisation are their own steps, and the firm completes them with a one-time code sent to its own registered contacts. A credential your product never receives is one it can never be asked to have leaked.
Because ScripX is the counterparty to each leg, the seller is verified by ScripX and the buyer is verified by ScripX. Your users are not relying on each other and they are not relying on you to have checked. Provenance on a credit is screened before it is offered, so nobody in your product is vouching for a stranger's instrument.
A key is bound to one engagement and one firm. A party identifier sent in a request body is ignored and forced to the key's own firm, so a key cannot act for a firm it is not mandated on even by mistake. Another desk's resource answers 404 rather than 403, so an id cannot be probed for existence. Child keys inherit the same tenant with a strict subset of scopes.
The credit itself is an exempt supply, and the documents for both legs are ScripX's to issue because both legs are ScripX's supply. What we will not do is tell you how your own revenue share should be treated. That belongs on your partner agreement and in front of your own advisers, and a marketing page that answered it confidently would be doing you a disservice.
The full position, including how failed settlements unwind and how provenance is screened, is on compliance and trust.
Fee income, on the same books the money posted to.
Commercial terms sit on the partner agreement, so there are no numbers for us to invent on a marketing page. What we can tell you is the shape of the revenue and how you will be able to audit it, which is the part that usually turns out to matter more.
Your economics are a spread on trades that actually settled. Nothing accrues on a quote, a listing or an order that did not complete, so there is no revenue line that has to be reversed later.
An earnings read returns spread captured gross and net, volume, a per-client breakdown, and the balance still withdrawable. It is read from the same double-entry ledger the money posted to, so there is no second tally to drift out of agreement with the first.
You already know which of your firms export, and a credit arrives against shipments they have already made. This is one of the few attach opportunities where the trigger is visible in data you hold rather than inferred from intent.
Four things worth knowing early rather than late.
- The sell side is the generally available side. An exporter turning a matured credit into cash is live. The buy side, where an importer funds customs duty below face, is in preview and is enabled per desk on request. If your roadmap depends on the buy side, say so at the first conversation.
- Credits do not divide. A scrip transfers for its whole amount. Lot sizes are whatever the exporter happened to generate, so a firm cannot sell part of one to raise a particular figure, and any interface that implies otherwise will be wrong.
- The clock is sixty seconds and the same business day. A quote is firm for sixty seconds. Settlement completes the same business day, with the buyer's funds secured before the transfer is initiated and released only once it is confirmed. We do not promise faster than that, because part of the transfer is a human approval on a government system and nobody honest can.
- One role per firm, for now. A firm registers as an exporter or an importer. A firm that genuinely does both is not yet supported as a single registration.
Asked, answered.
No, and that is the point. Everything else on a trade-finance platform is an advance against something that has not been paid yet. A duty credit scrip is an asset the exporter already owns and can already transfer. Selling one is a disposal, not a borrowing, so there is no tenor, no underwriting, no collection, no first-loss guarantee and no recovery workflow attached to it.
It runs the other way. A firm that converts a matured scrip into cash draws less on the line you gave it, so the exposure you are already carrying is serviced by an asset that was previously idle. The credit does not compete with your book; it reduces the demand on it while earning you a fee on the same relationship.
It should not, and the reason is structural rather than a matter of drafting. You never take title to the credit and you never take custody of your customer's money, so there is no advance, no first-loss and no float on your side. Your own counsel has to reach that conclusion themselves, which is why the page above states exactly what does and does not pass through you rather than asking you to take our word for it.
The sell side, which is the side that matters here: an exporter turning a matured scrip into cash. The buy side, where an importer funds customs duty with credits bought below face, is in preview and is enabled per desk on request. We would rather say that plainly than let you build against something and discover it later.
Every quote is priced for the specific scrip and held firm for sixty seconds, by scheme with its methodology alongside it and with history. The rate endpoints need no API key at all, so you can render the market inside your product before a single firm has signed anything, and your users can check a quote against the same number you are showing them.
The smallest useful version is a read-only rate panel, which needs no key and no agreement. A working sell flow is a register call, a two-step connect, an inventory read, a quote, an order and a webhook. Sandbox keys are bound to a test IEC and return simulated inventory in the production shape, so the whole interface can be built and demoed before anything is live.
Not quite your product?
Exporter and importer marketplaces
A first revenue line that is not a subscription, off the exporter base you already have, with no licence to obtain and no balance sheet to put behind it.
See the seat →Broker softwareCHA and broker software
Your users already work every client IEC in your product. Scrips are the one thing in that workflow they still have to leave it for.
See the seat →ERPs and neobanksERPs and neobanks for EXIM
You already hold the ledgers and the accounts. A scrip balance is an asset your users own that your product does not currently show them.
See the seat →Background reading: what building this yourself actually involves, and what a duty credit scrip is.
Talk to a human.
A question about a quote, a settlement, or the API: write to us and a real person replies, usually within a day.
- Exporters: offers, payouts, Autopilot guard-rails.
- Importers and brokers: duty cover, the desk, API access and sandbox keys.
- Anything else: we read everything that arrives.
Prefer email? amin@eximfiles.io
A fee line with no tenor, no first loss and no title.
Build the rate panel with no key. Build the sell flow against the sandbox. Go live on a partner agreement.