Support using an existing wallet address for disbursements as an alternative to receiver registration.
What problem does your feature solve?
Currently, the SDP requires receiver registration through SEP-24 before disbursing funds. This process can be redundant when the organizations disbursing funds already have access to the receiver's wallet address, leading to unnecessary steps and delays.
What would you like to see?
We propose adding support for Known Wallet Address in the disbursement process. Specifically, we should:
Add a new column named wallet_address to the CSV file containing the disbursement instructions.
Upon initiating the disbursement and creating the receiver and receiver_wallet, we automatically set the receiver wallet status to REGISTERED.
When a wallet_address is provided, bypass the SEP-24 registration process and directly disburse the funds to the receiver's wallet if the wallet is valid (i.e. it exists on the network, has the appropriate trustlines, etc.)
Support using an existing wallet address for disbursements as an alternative to receiver registration.
What problem does your feature solve?
Currently, the SDP requires receiver registration through SEP-24 before disbursing funds. This process can be redundant when the organizations disbursing funds already have access to the receiver's wallet address, leading to unnecessary steps and delays.
What would you like to see?
We propose adding support for
Known Wallet Address
in the disbursement process. Specifically, we should:wallet_address
to the CSV file containing the disbursement instructions.REGISTERED
.wallet_address
is provided, bypass the SEP-24 registration process and directly disburse the funds to the receiver's wallet if the wallet is valid (i.e. it exists on the network, has the appropriate trustlines, etc.)