Skip to main content
Use a blockchain_deposit_address to create an inbound-only address and bind it to an account number. The address accepts stablecoins and automatically off-ramps them to USD in the bound account number. Blockchain Deposit Address 1 When stablecoins are received to a blockchain_deposit_address, a blockchain_payment is created and the object moves through the blockchain_payment life cycle.  Blockchain Deposit Address Life Cycle The resulting blockchain_payment object will contain the debtor’s wallet address, the token, the blockchain used and the id of the blockchain_deposit_address the funds were sent to. The tracking identifier will be a transaction_hash.  A blockchain_deposit_address is bound to only one account_number_id. An account_number_id can have many blockchain_deposit_addresses pointing to it.  The blockchain_deposit_address is for a single network & token pair, however, the address can repeat across networks. Blockchain Deposit Address Account Number
Stablecoins will be lost if they are sent to the wrong network or in a token that is not configured

​
Requirements

​
Statuses & webhooks

A blockchain_deposit_address is created with a status of active. Only Lead can move it to closed. When a blockchain_deposit_address is closed, payments sent to it are not posted.
Status**Definition **
activeIn use and can receive payments
closedDeposit addresses can no longer accept incoming funds; no blockchain_payment object will be created. Terminal state. Only Lead can move a blockchain_deposit_address to this state.
There are no independent webhooks. A blockchain_payment webhook is created after stablecoins are received. 
When funds arrive at a blockchain_deposit_address, Lead creates a blockchain_payment and screens the sending wallet. If the screen passes, the payment moves to submitted. If it fails, the payment moves to rejected and the funds are held.