The exchange, embedded · For Platforms & Marketplaces

Duty credit, as a feature of your product. One API, one key.

You already serve Indian exporters and importers. Embed scrip trading through one REST API and one API key. Onboard your firms, and credit by credit take a firm quote at a firm price, one all-in number landing in the seller's bank. Scriphouse makes the price, matches the trade, and settles it end to end.

One key, five firms or five hundredFirm quotes per scrip, held 60 secondsSandbox by default
The exchange, embedded

You bring the firms. Scriphouse makes the market.

Scriphouse is the duty-credit scrip exchange, an Eximfiles product. If your platform already serves Indian exporters and importers, scrip trading becomes a feature of your product through one REST API and one API key. You keep the relationship. Scriphouse prices, matches, and settles the trade underneath it.

The priceA firm quote per scrip

Credit by credit, take a direct firm quote for each client's scrip, produced for that specific credit at the moment you ask and held for sixty seconds. One all-in number lands in the seller's bank. No indicative figures dressed up as offers.

Both sidesSell scrips, or fund duty

Onboard exporters to sell matured scrips at a firm price, or one all-in number. Onboard importers to fund customs duty below face the same way. Sell side and buy side, one API key.

The railsPriced, matched, settled

Scriphouse makes the price, matches the trade, and settles it end to end, atomic delivery-versus-payment on ICEGATE in minutes, same day (T+0), with a UTR, whether you bring five firms or five hundred.

How the model works

Onboard, quote, settle.
Paid in minutes.

Four steps from a firm on your platform to money in its bank, credit by credit, through your own product.

01

Onboard your firms

Create each firm under your account. Each one connects its own ICEGATE operation under a signed, revocable mandate and trades as itself, scoped by your API key.

POST /v1/firms
02

Quote each scrip on its own merits

Credit by credit, request a firm quote priced for that specific credit. Show it while it holds for sixty seconds. One all-in number, the reasons alongside it.

quote holds 60s
03

Match and settle atomically

Place the order against the quote. Scriphouse matches it and settles atomic delivery-versus-payment on ICEGATE, the buyer's money locked before the scrip moves.

atomic DvP
04

Get paid, in minutes

On a sale, one all-in number lands in the seller's bank in minutes, same day (T+0) with a UTR. On a duty payment, the scrip covers the assessed bill below face. A webhook confirms each milestone.

T+0 with a UTR
The API lifecycle

Onboard, snapshot, quote, place, settle. Over REST.

Embed the trade in your own product. Onboard a firm, read a live market snapshot, take a firm quote locked for sixty seconds, place the order, watch positions, and pull an audit pack per trade. Webhooks push the order and settlement milestones as they happen. One header, JSON in, JSON out.

  The lifecycle · REST, JSON, x-scriphouse-key
POST/v1/firmsonboard a firm under your account
GET/v1/market/{scheme}a live snapshot for one scheme
POST/v1/quotefirm quote, held for 60s
POST/v1/ordersplace the trade against a quote
GET/v1/positionsopen positions, firm by firm
POST{your webhook}order + settlement milestones
GET/v1/audit/exportpull the audit pack for a period
200 OKrequestId req_8f3a21quote holds for 60s
One key, many firms

The account is multi-tenant by design. One API key onboards five firms or five hundred, each connecting its own ICEGATE operation and trading as itself. Quotes, ledgers, and audit packs stay scoped and separate, firm by firm.

Sandbox by default, live on agreement

Every key starts in the sandbox. Run the whole flow, onboard to quote to order to audit pack, with nothing binding and no scrip moving. Live access follows a signed partner agreement, and every response records the environment that produced it.

You are never in the chain of title

The instrument never sits on your books and you never stand between two firms. Settlement is delivery versus payment: the buyer's funds are secured before the transfer is initiated, or neither moves, and released to the seller only once the transfer is confirmed, in minutes, the same business day.

Webhooks, and a request ID

Webhooks push order and settlement milestones with retries and replay, so a missed delivery is never a lost event. Every response carries a request ID, success or error, so a support conversation starts with a fact. Per-endpoint rate limits are published in the docs.

Straight answers

What runs under your product.

Settlement is atomic delivery-versus-payment. The buyer's money locks before the transfer executes seller to buyer on ICEGATE, and payout fires on confirmation with a UTR, in minutes, same day (T+0). A failed settlement unwinds and refunds in full the same day.

The shipping-bill chain, seller IEC history, KYC, and live ledger status are screened before a scrip is listed, so a firm on your platform is never buying someone else's problem.

Every trade ships a GST invoice, a net-realisation statement, and an audit pack. The scrip sale is GST-exempt under HSN 4907, so the paperwork is legible to your firms and to their auditors.

Each firm connects its ICEGATE operation under a signed, revocable Power of Attorney. Nothing is submitted without approval, and a firm can revoke at any time.

Every trade belongs to the firm that made it. Firms are scoped by API key, and their quotes, orders, ledgers, and audit packs stay separate, firm by firm, whether you bring five or five hundred.

Pull a hash-chained, tamper-evident audit pack for any settled trade, with the GST invoice and net-realisation statement alongside it, and a full ledger export, CSV or Tally-ready vouchers, whenever your own reporting needs the numbers.

Every event we send is signed so you can prove it came from us, and carries a stable delivery id so a redelivery is easy to discard. A failed delivery is retried, and one we still cannot get to you is kept rather than dropped, so you can list what failed and replay it yourself.

Send an idempotency key with a write and a repeat is a repeat, not a second trade. A timeout on your side is the case every integration gets wrong, so retrying is the correct response here rather than a dangerous one.

What you have earned is read from the same double-entry record the money posted to, not from a separate tally kept for the dashboard. There is no second set of numbers to drift out of agreement with the first, which is the usual reason a partner statement and a bank statement disagree.

An integrator never holds the instrument. Title moves on ICEGATE and the seller payout is released against confirmation of that transfer. See how Scriphouse handles compliance and trust.

Questions

Asked, answered.

The sell side, where an exporter turns a matured credit into cash, is generally available. The buy side, where an importer funds customs duty with credits bought below face, is in preview and enabled per partner on request. Both run through the same key and the same settlement, but if your case rests on the buy side, say so in the first conversation rather than after a design review.

Each firm you onboard operates under its own signed Power of Attorney for its ICEGATE operation, scoped to that firm. Nothing is submitted without approval, and a firm can revoke its mandate at any time.

Two modes, and you choose per trade. Where your exporters and importers trade at prices Scriphouse makes, they pay the standard self-serve rates published on the pricing page, first trade on each IEC free included, exactly as if they traded here directly, and the platform earns a share of the Scriphouse fee on the trades it originates. Where the platform instead settles a cross of its own, one of its exporters' scrips against one of its importers' duty covers, at prices the platform set, the platform pays: the flat 0.50% desk rate on the value that settles plus GST, charged to the platform and to neither client, once per settled trade. A trade is charged on one basis only, never both. The revenue-share split sits on the agreement settled when you connect, so there is no percentage for us to publish here, and it is agreed there rather than discovered on an invoice. Earnings and charges are reported per client and per trade, read from the same ledger the money posted to.

A sandbox key is bound to a test IEC: onboard test firms, take quotes, place orders and pull an audit export end to end, with nothing legally binding and no scrip ever moving. Live access follows a signed partner agreement. The two kinds of key carry different prefixes, so a rehearsal is never mistaken for a settled trade.

Whether you bring five firms or five hundred, each connects its own ICEGATE operation under its own mandate and trades as itself. Quotes, orders, ledgers and audit exports stay separate firm by firm, and a call that reaches past the firms your key holds a mandate for is refused rather than answered.

On a sale, the firm is paid one all-in number into its own bank on the same business day, with a UTR. On a duty payment, the credit lands in the firm's own ledger, ready to apply when the Bill of Entry is filed. A settlement that fails unwinds and refunds in full the same day, and your platform is party to none of it.

Contact

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@scriphouse.com

Used only to reply to you. No newsletters, no sharing.

Get started

Duty credit, as a feature of your product.

Build against the sandbox today. Go live on a signed partner agreement.

One REST API, one key. Onboard five firms or five hundred, priced per scrip and settled in minutes, same day (T+0).