What it does
resolveTinRoute creates a confirmed Solana connection through the supplied RPC URL and delegates TIN resolution to resolveTIN. It returns the identity route data used by an application to build a payment authorization; it does not submit a payment.
How the flow works
1
Caller invokes the function
The caller supplies a ten-digit TIN, an RPC URL, and optionally the TIN program ID.
2
Validation
The underlying resolver reads the TIN registry and rejects malformed, missing, legacy, or unavailable identity state.
3
Main work
The SDK derives the registry address, fetches the account, decodes it, and exposes the current route commitments.
4
Result
The caller receives
TinResolvedIdentity and can bind its route commitment and version into a signed payment intent.Signature
bigint | number | string
required
Ten-digit TIN lookup value.
string
required
Solana RPC endpoint used for the account read.
PublicKey | string | null
TIN program override. Defaults to the SDK program ID.
Result and errors
The result includes the resolved registry identity and route fields such astcapRouteVersion, tcapRelationshipCommitment, and tcapPolicyCommitment. Errors from the connection, account lookup, decoding, or legacy-route checks are propagated.
tins.ts:1687-1696