From your first connection
to your first receipt.

01. Create your business account

Sign in with Google, or create an email and password account. Signing in to InboxPay does not yet give it access to your mail. That connection is a separate step.

Your business has its own wallet, vendors, payment settings, and records. Check the business name and active network before setting up payments.

02. Connect the right inbox

In Invoices, choose Connect Gmail and authorize the Google account that receives your business invoices. After connecting, refresh the inbox to see the invoices the agent found.

Supported sources include email text and text-based PDF invoices. Image-only or scanned PDFs are not supported as a reliable extraction source. An empty queue does not mean a payment was made.

If the connection expires or access is revoked, InboxPay asks you to reconnect. Start a new connection rather than reusing an expired Google sign-in link.

03. Set up payments

1. Choose your environment. Start on Arc Testnet for testing. Mainnet uses real funds and has a separate setup.
2. Create and fund your business wallet. Follow the setup checklist. The full address is available in your business account; copy it instead of retyping it.
3. Add and verify your vendor. Check the recipient address and invoice sender. Saving a vendor is not the same as verifying them for payment.
4. Configure payment settings. Review your limits, cash floor, vendor registration, and USDC access before authorizing them. Deployment and authorizations are explicit actions.
5. Review an invoice. Open it from the queue. Read the amount, due date, agent explanation, and live payment checks. Only an eligible invoice offers payment.

Automatic payments are optional and require explicit activation in Payment settings. Enabling them lets the agent execute eligible invoices within your active settings. Turning them off does not undo an already submitted payment.

What “Needs review” means

The agent hasn’t been able to proceed. Open the invoice to see why: a vendor may need verification, a required field may be missing, a payment limit may be reached, or a live check may be unavailable.

Do not work around a failed check by changing a wallet address or duplicating the invoice. Correct the underlying issue, refresh, and review the current result.

A queued review is not a submitted payment. A future invoice can wait for its due date; payment still depends on the current vendor, balance, and payment checks.

Know when a payment is complete

Submitted means the payment has been sent for execution. It does not mean the recipient has received confirmed funds. Confirmed and reconciled means InboxPay has matched the Arc transaction and recorded its receipt.

Open Payments for the transaction hash and reconciliation record. If a payment is still processing, let InboxPay recover the original submission; don’t send it again manually. Activity shows the recorded actions for your business.

Keep up in Telegram

Open Notifications, select Connect Telegram, and start the InboxPay bot using the generated connection link. Return to InboxPay and refresh the connection status. Send a connection test to check the destination.

Connected businesses can receive recorded payment and review alerts. A connection test proves the destination works; it is not a payment receipt. No bot code or API token is needed from your business.

Test money and real money stay separate

Arc Testnet is for testing with test USDC. Arc Mainnet uses real USDC. Switching environments changes the active business wallet, vendor registration, and payment setup. Check the environment before funding or authorizing anything.

The end-to-end autonomous payment flow has been demonstrated on Arc Testnet. A genuine third-party Mainnet business invoice settlement is not yet claimed as verified usage.