Hand a customer an address that names us, not a wallet.
Today a customer being paid reads out a wallet address, and the payer's VASP
has to work out who owns it. A Travel Address is a string that names
this deployment: the payer's VASP decodes it, asks us who we are,
and sends the compliance inquiry here. The wallet address never leaves a
VASP-to-VASP exchange — we supply it in the resolution, after we know who is
asking.
Addresses are long-lived, like an IBAN: one customer can hand the same one out repeatedly, or hold several — one per counterparty — and withdraw the one that leaks. Withdrawal is soft, so an inquiry arriving on a retired address is answered
Addresses are long-lived, like an IBAN: one customer can hand the same one out repeatedly, or hold several — one per counterparty — and withdraw the one that leaks. Withdrawal is soft, so an inquiry arriving on a retired address is answered
404 invalid or expired Travel Address rather than
quietly creating a case.
Your own identifier for this customer, not their name. It is stamped
onto any case an inquiry on this address creates
(
host_beneficiary_user_ref).