How to Send a Bulla Invoice NFT on RSK

Before connecting a wallet, confirm that Bulla currently offers invoice creation on Rootstock (RSK). Bulla is a crypto project, but its current RSK workflow, supported wallets, and invoice-NFT features are not confirmed here. Do not assume a feature exists just because the topic refers to it.

Check Bulla’s own app and documentation for these points:

• Does the app explicitly list Rootstock or RSK as a supported network?
• Can you create an invoice as an NFT, rather than only send a payment request?
• Which wallet and invoice currency does it support?
• Does the NFT contain invoice data, or only a reference to data stored elsewhere?
• What happens if the recipient does not have a compatible wallet?

If the app does not clearly support RSK, stop. Do not connect your wallet to a similarly named site or approve a transaction that claims to enable support. A wrong-network transaction may not be recoverable, and an NFT sent to an incompatible destination may be difficult to use. Treat Bulla’s stated support and the wallet’s transaction details as prerequisites, not steps to work around.

Rootstock, often called RSK, is an EVM-compatible blockchain network. A compatible wallet still needs the correct Rootstock network configuration and the asset used to pay transaction fees. On Rootstock, the native gas asset is RBTC; this is separate from the amount or token you might put on an invoice.

Prepare your wallet only after confirming that Bulla supports your wallet and Rootstock. Use Rootstock’s official network details or Bulla’s own instructions to add or select the network. Check the network name shown in your wallet before connecting; do not copy settings from an unknown post or message.

Before you proceed:

1. Back up your wallet recovery phrase offline. Never enter it into Bulla or share it with support staff.
2. Check that the wallet is on the Rootstock network Bulla specifies, not Ethereum or another EVM chain.
3. Keep enough of the required gas asset for the transaction. The precise amount varies with network conditions and the operation.
4. Verify the app’s domain independently before connecting.

Connecting a wallet does not by itself send funds, but approving a transaction or granting permissions can have consequences. Read each wallet prompt and reject anything that does not match the action you intend to take.

If Bulla provides an invoice-NFT flow for Rootstock, use the app’s own invoice form and check every field before minting or sending. The exact button names and available fields may change, so follow the current interface rather than assuming a particular sequence.

A careful workflow is:

1. Choose Rootstock in Bulla and confirm the same network appears in your wallet.
2. Enter the invoice recipient, amount, currency or token, due date, and payment instructions that the app supports.
3. Add an invoice number and a clear description for your records.
4. Preview the invoice and confirm that the recipient can access or receive the NFT.
5. Check what will be stored publicly, including any metadata or linked file.
6. Continue only if the wallet shows an expected transaction on Rootstock.

Do not put private customer information, bank details, or confidential commercial terms in public NFT fields. If you need to include a detailed document, find out whether Bulla stores it on-chain, off-chain, or as a public link; those choices have different privacy and availability risks. If Bulla does not identify the data-storage method, avoid adding sensitive material and consider using a conventional invoice instead.

An NFT transaction may make invoice data or its metadata publicly visible and persistent. Even if the invoice document is stored outside the blockchain, the NFT may expose a wallet address, transaction history, token identifier, or link that can be viewed by others. Treat the invoice as public unless Bulla clearly explains a privacy control and what it protects.

Review the preview with the same care you would give a public business record. Check the recipient’s wallet address character by character using a trusted channel, and verify the invoice amount, token, due date, and payment destination. A familiar name or profile image is not proof that the address belongs to your customer.

Before you mint or send, ask:

• Will the NFT go to the customer’s wallet, or will Bulla send a claim or viewing link?
• Can the recipient access it without using Bulla?
• Can the invoice details be edited, revoked, or corrected after minting?
• Does the NFT contain the full invoice, a summary, or only a pointer?
• Is the customer expecting an NFT invoice and able to use it?

If a material field is wrong, do not sign and hope to fix it later. Correct the draft first. If an already-issued NFT cannot be edited or revoked, you may need to issue a corrected invoice and explain which record supersedes the earlier one.

The wallet’s confirmation screen is your last chance to catch a wrong network, recipient, or unexpected contract call. Check that the transaction is on Rootstock, that the recipient and contract details match what Bulla’s workflow requires, and that the fee is acceptable. Network fees fluctuate; Bulla’s current fee schedule and a fixed price for minting an invoice NFT are not confirmed here.

If the transaction is correct, approve it in your wallet. Never share your recovery phrase or private key to complete a transaction. If Bulla asks for an approval or permission beyond the invoice action, stop and understand what the permission allows before signing.

After signing, wait for the transaction to confirm in the wallet or Bulla. Save the transaction hash, invoice number, NFT identifier if shown, and a copy of the invoice. A pending transaction is not the same as a confirmed one. If it fails, check the wallet’s status and Bulla’s instructions before retrying; repeated attempts may create extra fees or duplicate records.

Send the invoice to the customer through the delivery method Bulla provides, then confirm they can view it and understand how to pay. Do not tell them it is paid merely because the NFT was created or transferred. Issuing the invoice and receiving payment are separate events.

When the customer pays, verify the payment separately from the NFT. Check the transaction on Rootstock using a trusted block explorer or Bulla’s verified payment-status feature, if it provides one. Confirm the receiving address, token, amount, and transaction status. A screenshot or message from the customer is not enough on its own.

Compare the confirmed payment with the invoice. Make sure it covers the amount due in the correct asset, and account for any agreed partial payment or adjustment. If the payment is short, sent in another token, or sent to the wrong address, contact the customer and resolve the difference using your normal accounting process. Do not assume that transferring the invoice NFT automatically settles the debt.

Keep a record of the invoice itself and the associated transaction details. This can include the invoice number, date, customer, amount, payment asset, transaction hash, and any correction or credit note. Reconcile these records with your accounting system and check local tax and invoice-retention rules.

An NFT does not automatically make an invoice legally compliant or guarantee that its contents remain accessible. If you need a formal tax invoice, use a format that meets your jurisdiction’s requirements and treat the NFT as an additional tracking or delivery mechanism—not a replacement—unless a qualified adviser confirms otherwise.

A few avoidable errors can turn a simple invoice into a costly or confusing record. Use this checklist before you finish:

• Wrong network: Confirm both Bulla and your wallet are set to Rootstock, not another EVM network.
• Wrong recipient: Verify the customer’s address through a trusted channel; do not rely on a pasted address alone.
• Wrong asset or amount: Make sure the invoice specifies the intended payment token and exact amount.
• Unexpected signing request: Reject transactions or permissions that do not match the invoice action.
• Sensitive data in metadata: Keep personal and confidential information out of public fields.
• No gas balance: Check that you have the required Rootstock gas asset before starting; the exact fee depends on the transaction and network conditions.
• Assuming the NFT is payment: Wait for confirmed payment and reconcile it separately.
• Treating the NFT as a legal invoice: Keep a compliant invoice and accounting record where required.

If Bulla does not clearly confirm Rootstock support, explain what the NFT stores, or show a transaction that matches your intended action, pause instead of guessing. A regular invoice sent by email or another established billing tool may be the safer option until those details are clear. Never use a VPN or another workaround to bypass geographic, identity, or platform restrictions.