One of:
End-user geographic coordinates captured at the moment of the withdrawal
request. Consumed by BlockingRuleMethod.GEOLOCATION enforcement.
Replay-of-different-coords bypass is prevented server-side: the first resolved {country, state} for a given (merchant, user) pair is pinned in Redis, and subsequent requests are evaluated against that pinned value regardless of the lat/lng they submit.
The transactions to be signed by the user and sent to the blockchain.
Solana - Transactions are base58 encoded. You can reconstruct them by calling Transaction.from(base58.decode(transaction))
Evm - Transactions are JSON stringified. You can reconstruct them by calling JSON.parse(transaction)
The web3 wallet of the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
The blockchain associated with the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
The session key generated for the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key