How Didit routes an exchange
When a Didit customer sends a transfer, Didit tries these rails in strict priority order and uses the first one that can reach you:
The table above covers transfers a Didit customer sends.
When you send a transfer to a Didit customer, Didit can take it only as a
TRP transfer inquiry, once Didit’s public TRP host is live (it does not answer yet, see TRP endpoints), or, after settlement, as a sunrise registration: today no network rail and no email channel delivers an inbound transfer to a Didit customer.
The network rails (GTR, TRUST, VERIFYVASP, SYGNA) run over a membership on the sending side.
Today that has to be the Didit customer’s own connected membership: Didit holds no platform membership on any of these networks yet and is onboarding as a provider.
GTR is not included by default, and the same membership requirement applies to all four networks.
The sender should check the networks object in Get Travel Rule Settings: didit means Didit’s membership carries that application as its own participant on the network, own means a connected customer membership, off means platform routing is disabled, and unavailable means nothing can send on that network for the application yet.
Until Didit holds a platform membership, no network reports didit.
Enabling Travel Rule does not activate a network membership.
See Travel Rule networks for what each network reaches today.
If you are on one of those networks and the Didit customer holds its own membership there, share your network identifier with them and the transfer reaches you over the network you already operate.
Over SYGNA, your permission answer completes or declines the transfer: Didit polls the transfer’s status every 5 minutes, and also registers https://trp.didit.me/sygna/callbacks/permission/{token}/ as the callback of each permission request, with a token minted for that transfer.
That callback is on Didit’s public TRP host, which does not serve requests yet.
A permission_status of ACCEPTED moves the sender’s transfer to COMPLETED, and REJECTED moves it to COUNTERPARTY_VASP_GENERAL_DECLINE, or to COUNTERPARTY_MISMATCHED_DATA when the reject_code is BVRC007 (the beneficiary name does not match).
The callback needs your signature: it answers 401 with {"status": "INVALID_SIGNATURE"} without a valid one, 404 for an unknown token, and 200 again for a decision it already applied.
With zero shared memberships, TRP is the path to plan for: share your travel address with the Didit customer, and their transfers reach your TRP endpoint. An answer you give in your inquiry response completes or declines the transfer at once; an answer you post later to Didit’s callback needs Didit’s public TRP host, which is not live yet.
When none of the rails can identify you, Didit runs one more resolution step: blockchain analytics attribution.
The destination wallet is resolved against blockchain analytics data, and when it is attributed to your exchange or custody service, Didit records your name in its VASP directory and retries the rails with it.
This means you can be identified even when the sender supplied nothing but a wallet address.
Attributed transfers route to you automatically only once your directory entry carries a route: a verified TRP endpoint, a network listing, or a compliance contact (see Getting into the Didit VASP directory).
The full resolution chain is therefore: a Didit customer that proved control of the wallet (INTERNAL) and the travel address the sender stored for it, then the protocol and network rails, then blockchain analytics.
Travel addresses
Every Didit VASP with Travel Rule enabled has a travel address - a compact string starting withta that encodes the URL of its personal TRP transfer-inquiry endpoint.
Didit customers read theirs from their Travel Rule settings and share it with counterparties; when a Didit customer gives you theirs, you hold everything needed to reach them over TRP.
The encoding follows the TRP travel address convention:
- Strip the
taprefix. - Base58Check-decode the remainder (Bitcoin alphabet, double-SHA256 checksum).
- The decoded bytes are the inquiry URL without its scheme; prepend
https://. - The URL always carries the query pair
t=i(type: inquiry).
{profile_uuid} identifies the hosted VASP profile - POST your transfer inquiries to that URL, and query the matching identity endpoint to verify who you are talking to first.
The second shape is a per-wallet travel address: it names one wallet of the Didit customer (receiving_travel_address on its address book), so your inquiry reaches that wallet without the customer having to match it by account number or holder name. It answers 404 once the wallet is deleted or recorded as another VASP’s.
TRP endpoints
Didit speaks TRP API version3.2.1 at the base URL https://trp.didit.me.
All endpoints exchange JSON over HTTPS.
Two TRP headers matter:
api-version- the TRP protocol version you speak, for example3.2.1. Required on inquiries and on both callbacks.request-identifier- your unique id for the request, echoed back in the response headers. Required on inquiries and on both callbacks.
400.
Every response from Didit carries api-version: 3.2.1 and echoes your request-identifier.
GET /identity
Returns the platform operator’s identity. No headers are required.GET /trp/identity//
Returns the identity of the specific VASP you are about to exchange with - use it to verify the name and LEI before sending PII. Didit performs the same check in reverse when it initiates: if the identity your endpoint reports does not match the expected LEI or name, the exchange is aborted.404 when the profile does not exist or its Travel Rule setup is disabled.
POST /trp/inquiries//
Submit a transfer inquiry - you are the originator VASP, the Didit customer is the beneficiary VASP.
Assets are identified by DTI on this rail, and a DTI identifies a token on a single blockchain.
Didit maps
BTC (4H95J0R2X), ETH (X9J9K872S), and USDC on nine networks today, with further assets added over time.
See TRP asset identifiers for the full list.
An inquiry whose DTI Didit does not recognize is still accepted and surfaced to the beneficiary VASP with the DTI as the asset code.
A 200 response means the inquiry was accepted for processing; 400 means missing TRP headers or an invalid body, 404 means the profile (or the wallet of a per-wallet address) is unknown or disabled, and 422 means the request uses a TRP extension: Didit supports none, so an api-extensions header or an extensions key in the body is refused.
Re-sending the same request-identifier is idempotent - the original inquiry is reused instead of duplicated.
Didit then creates the inbound transfer on the customer’s application and resolves it against the customer’s wallet address book and policy.
It matches the beneficiary by the wallet a per-wallet travel address names, else by the first wallet address in IVMS101.beneficiary.accountNumber, or, without one, by the beneficiaryPersons[0].naturalPerson name against the customer’s verified wallet entries.
The 200 response carries the answer when Didit can give it at once:
{"approved": {"address": "...", "callback": "..."}}when the inquiry was approved automatically. Didit does not post that approval to yourcallbackas well.{"rejected": "NOT_ENOUGH_COUNTERPARTY_DATA: inquiry carries no beneficiary identification"}when the inquiry names neither the beneficiary nor a wallet address, so always include both.{"version": "3.2.1"}when the decision waits for the Didit customer. The resolution then arrives later as a POST to yourcallbackURL, with one of the two bodies below.
originatingVASP is what the Didit customer sees as the transfer’s originator VASP.
Didit sets no deadline on an inquiry you send, and a Didit customer that cancels it sends you no rejection, so apply your own timeout.
After you receive an approval and broadcast the transfer on-chain, close the exchange out by POSTing to the approved.callback URL you were given:
{ "canceled": "reason" } to the same URL instead if you abort the transfer.
txid moves the beneficiary-side transfer to FINISHED; canceled moves it to CANCELLED.
Both callbacks answer 204 once handled, 404 for an unknown token or a transfer that is no longer waiting for that callback, and 400 for a body that carries neither of the callback’s two fields.
Resolving inquiries Didit sends you
When a Didit customer originates a transfer to you over TRP, Didit:- Fetches
/identityat the root of your inquiry URL’s host (https://{your-host}/identity) and verifies the reported name and LEI against what the customer expects. When the route came from Didit’s directory, your/identitymust report that directory entry’s LEI. - POSTs a transfer inquiry to your inquiry URL with the same body shape as above -
asset.dti, a base-unitamountas a JSON number, acallback, and theIVMS101payload.
2xx answer counts as delivered. A 3xx is refused, because redirects are not followed, and any other answer is recorded on the customer’s transfer timeline with your status code, for example refused by counterparty (HTTP 403): ....
Both calls carry the two TRP headers, and Didit does not follow HTTP redirects on them, so serve /identity and the inquiry URL directly.
If /identity is unreachable, reports no LEI or a different LEI when the customer supplied one, or reports a name that does not match, Didit stops before sending the inquiry and the customer’s transfer moves to COUNTERPARTY_VASP_NOT_REACHABLE.
If the inquiry POST then fails or your endpoint answers it with a 4xx or 5xx status, the transfer also moves to COUNTERPARTY_VASP_NOT_REACHABLE.
The callback in that inquiry points at Didit’s resolution endpoint (/trp/callbacks/resolution/{token}/).
Respond by POSTing the same resolution bodies Didit uses: { "approved": { "address": "...", "callback": "..." } } to approve (your callback is where Didit will post the on-chain confirmation), or { "rejected": "reason" } to decline.
Send both TRP headers with it.
Didit answers 204 once handled, 404 when the transfer is no longer waiting for a resolution, and 400 for an approval without an address or whose callback is not a public http(s) URL Didit will call.
On approval the Didit side moves to COMPLETED; once the customer reports the on-chain hash, Didit POSTs { "txid": "..." } to the confirmation callback you supplied (or { "canceled": "reason" } if the transfer is cancelled first).
Callback tokens are single-purpose, unguessable secrets minted per transfer - treat the full callback URLs as confidential, and note that a resolution is only accepted while the transfer is still awaiting one.
Email pickup
If no protocol channel reaches you and the Didit customer supplied your compliance email, Didit falls back to email: your compliance contact receives a message naming the originator VASP with a one-time secure pickup link. No account, API key, or integration is needed - the link token is the authentication. Opening the link shows the pending exchange; the underlying API (which the hosted page drives for you) is public:amount is the stored decimal verbatim, so it carries the full 18 decimal places.
decision is accept or decline; on accept, supply the beneficiary’s name as your records hold it so the originator side can run its name match, or send your full IVMS 101 response as ivms_response, whose beneficiary name then wins.
On decline you can give a decline_reason (data_mismatch, not_our_customer, wallet_not_hosted, sanctions, risk_appetite, jurisdiction, insufficient_data or other) and a decline_detail of up to 512 characters, required for other.
An accept without beneficiary_name is recorded as a mismatch when the sender supplied a beneficiary name, unless the sender has name matching turned off.
The response is the resulting {"status": "..."}: COMPLETED when the names match, COUNTERPARTY_MISMATCHED_DATA when they do not, or COUNTERPARTY_VASP_GENERAL_DECLINE after a decline.
You can respond once, while the transfer is waiting for you: after you respond, after the transfer is cancelled, or after its confirmation deadline, both endpoints return 410, and an unknown token returns 404.
The request shows the originator fields the sender shares and an IVMS 101 ivms_request, in the language of your jurisdiction, and you are reminded 72, 24 and 6 hours before the deadline while you have not answered.
Invitation details and the free workspace
The join invitation API returns sender_name and, for an eligible linked pickup transfer, request_id, amount (decimal string), currency and sent_at. Unavailable request details are null. portal_url returns the original pickup link only while it is valid and the invitation recipient was addressed on that request; it never renews the link.
The invitation’s outbound_price is a public list quote or null. After joining, the workspace API returns your own account quote, the VASP licence and the claim’s rejection_reason. You can submit an optional licence when claiming the directory entry, then read or update the granted profile licence through Travel Rule settings.
An expired join link returns 410 with reason: "expired" and sender_name. It includes sender_contact_email only when the linked sender has a currently public, confirmed compliance mailbox. Already-used or withdrawn join links return a generic 410; unknown tokens return 404. These responses reveal no recipient address, request summary or pickup URL.
Sunrise: transfers that settled before the exchange
When a transfer reaches a Didit customer’s wallet before any Travel Rule exchange took place - because no shared rail existed at the time - the data can still be delivered after settlement. Send the Didit customer (your beneficiary counterparty) the Travel Rule payload through your normal channel and ask them to register it; they callPOST /v3/travel-rule/inbound/ with the deposit’s chain, txid, wallet address, amount, currency, and your originator data.
Include your VASP identity - name, LEI, and travel address - as originating_vasp in that payload, so the Didit customer’s transfer records who sent the deposit.
It stays on that transfer and never creates or changes your directory entry.
The LEI must be a valid 20-character LEI and the travel address a valid one, or the registration is rejected.
Getting into the Didit VASP directory
Didit maintains a VASP directory that its customers’ outbound routing consults. Entries come from these sources:- The ESMA interim MiCA register of crypto-asset service providers, read every week: your name, LEI, and home member state if you are listed there.
- The public TRISA directory, read every week: who you are, your country, and your TRISA listing.
- The global LEI register, which fills in your LEI, other legal names, and country.
- Blockchain analytics attribution, when a destination wallet is resolved to your exchange or custody service: Didit adds or matches your entry and keeps the attributed name as an alias.
- Didit staff, who curate entries: routing identifiers and network listings they verified, compliance contacts, aliases, and brands with their entities.
originating_vasp on a sunrise registration or a travel address on a transfer, stays on that customer’s transfer and never changes your entry.
Transfer inquiries you send to a Didit customer do not create or update your entry either.
Your entry routes a transfer to you when it carries a verified TRP endpoint, a network listing the sender can use, or a compliance contact for the email fallback.
A compliance address at one of your own domains that answers a request through its response link becomes a contact every Didit customer can use.
Until your entry carries a route, a Didit customer reaches you only with the fields it passes on each transfer: your travel address, your network identifier (counterparty_gtr_vasp_code, counterparty_trust_membership_id, counterparty_verifyvasp_id, or counterparty_sygna_vasp_code), or your compliance email (counterparty_vasp_email).
To be reachable today, share your travel address, network identifier, or compliance email with the Didit customers you work with.
Checklist for counterparty VASPs
- You run TRP already: share your travel address and LEI with the Didit customer - their
BTC,ETHandUSDCtransfers arrive as standard TRP inquiries at your endpoint. Answer in your inquiry response: a later answer needs Didit’s public TRP host, which is not live yet. - You are on GTR, TRUST, or VerifyVASP: share your network identifier; transfers arrive over that network when the Didit customer holds its own membership there. Didit reads your GTR or VerifyVASP answer from the network, but not a TRUST one, so publish a TRP endpoint as well when an exchange over TRUST has to conclude. Travel Rule networks says when that changes.
- You are on Sygna Bridge: share your Sygna VASP code; when the Didit customer holds its own Sygna membership, your permission answer completes or declines the transfer once Didit reads it by polling.
- You have no protocol channel yet: give the Didit customer a monitored compliance email - you will receive pickup links and can respond from the hosted page with zero integration.
- A transfer already settled: deliver the data via sunrise registration through the Didit customer.
- You also want to originate to Didit VASPs: ask your counterparty for their travel address from their Didit Travel Rule settings, then follow POST /trp/inquiries once Didit’s public TRP host is live.
Next steps
Travel Rule
The customer-facing product: lifecycle, settings, rails, and the /v3/ API.
Wallet ownership widget
How beneficiary-side ownership proofs are collected when a wallet is self-hosted.
Sunrise registration
Registering Travel Rule data for deposits that already settled on-chain.
Webhooks
How Didit customers observe every exchange transition on their side.