All Collections
Crypto Payment Solutions
Invoices
Pay Gilded Invoices With Confidence
Pay Gilded Invoices With Confidence

Make sure that you're sending funds to the correct address on the proper blockchain

Gil Hildebrand avatar
Written by Gil Hildebrand
Updated over a week ago

Attention to detail is crucial when it comes to paying people in crypto. One wrong move and you could send your hard-earned coins to the wrong crypto address, resulting in an irreversible loss of funds. It's important to know what NOT to do as much as what to do.

While we support other blockchains for accounting purposes (like Polygon, BNB, and Ronin), you can only pay and send invoices on BTC and ETH blockchains.

Read below as we walk through each step of paying a Gilded Invoice, as well as pointing out best practices for varying blockchains. Click here to read about Gilded's Security and Privacy Promise.

Paying A Gilded Invoice

When receiving a Gilded Invoice via email or a shared link, you can pay and view the pertinent details: current status, sender/recipient, due date, description, quantity, unit price, and total amount due. Invoices can also be downloaded as a PDF for record keeping purposes. After reviewing the Invoice details, click on the “Pay Invoice” button at the bottom of the page.

The recipient of the Invoice will be asked how they would like to pay the amount listed. They will be prompted to choose the blockchain/token in which to pay.

Important Note: You cannot send BEP20, ADA, XRP, or any tokens/blockchains not listed above via a Gilded Invoice. Any attempt to pay with a token from an improper and unsupported address/blockchain could result in a loss of funds.

Paying Gilded Invoices With Bitcoin

Depending on whether the payer chooses Bitcoin or Ethereum, the steps to make the payment in Gilded will differ.

For Bitcoin payments, Gilded will provide the address, QR code, and amount of BTC to send. A warning will appear instructing that only BTC can be sent to BTC addresses. Once the payment has been confirmed on the blockchain, you can enter the transaction hash/ID in the provided space. Click “Confirm Payment” after the payment has been recorded on the blockchain.

Note: Confirming a BTC payment without providing the transaction hash/ID will result in an “Unverified Payment” invoice status.

Paying Gilded Invoices With Ethereum

For Etherum payments, users will have the option to pay by connecting their non-custodial wallet (MetaMask, Ledger, etc.) or by address/QR code. When choosing a non-custodial wallet, Gilded will prompt the user to connect their wallet and initiate payment from within said wallet.

For payments via address/QR code, Gilded will provide the corresponding QR code, address, and payment amount in ETH. A warning will appear instructing that only ETH can be sent to another ETH address. Just as with Bitcoin payments, the payer must wait for the transaction to confirm on the blockchain and then enter the transaction hash/ID in the space provided. Click on “Confirm Payment” to verify the transaction.

Gilded Invoice Status

Once payment for an invoice has been sent, Gilded will update the status in real time as the transaction is confirmed on the blockchain. Upon confirmation, invoice status will reflect as "Paid" and the transaction ID and link will automatically generate to document the payment. Gilded Invoices awaiting payment will reflect as “Unpaid” and/or “Awaiting Payment.”

For BTC and ETH payments executed through address/QR code, the transaction hash must be entered in order for the invoice to reflect as “Paid.” If a payment is manually confirmed as paid but no transaction hash/ID is provided, the Invoice will reflect as an “Unverified Payment.”

When sending crypto to another address in Gilded (or anywhere else in the crypto-sphere) always be sure to double check that both the corresponding blockchain and address are correct. Otherwise, it will likely result in a loss of funds.


Got a question? Contact our Customer Success team via the in-app chat at the bottom-right of your screen, or email [email protected]

Did this answer your question?