Skip to content
Register

Payment integration

Accept invoice payments with Authorize.net

The Authorize.net integration lets customers pay your Invoice Crowd invoices through Authorize.net. Invoice Crowd verifies the transaction before recording the payment, and can send refunds back through Authorize.net.

Review the flow All integrations
  • Status: Active tokenized capture
  • Checked against the app
  • Provider terms still apply
Invoice Crowd Payment Methods with Authorize.net selected and a Authorize.net account set to Live, a paid invoice recorded after Authorize.net confirmed it, and the Refund window sending money back via Authorize.net.

From setup to paid

How Authorize.net fits the Invoice Crowd payment boundary

Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.

Connect the merchant account

Each business profile has its own account and live or test mode.

Invoice Crowd Authorize.net account form with Live and Sandbox modes and a fictional nickname, the business's Authorize.net accounts, and the Transaction Key kept write-only when editing.

Enter only the fields the provider requires

API login ID, client key, write-only transaction and signature keys, plus Live/Sandbox mode.

  • Selected business profile
  • Explicit live or test mode
  • Write-only secret editing

Check the provider accepts your business first

Authorize.net controls merchant eligibility, supported currencies, fees and settlement services.

  • Merchant country and account
  • Invoice and settlement currency
  • Provider fees and review

Understand the customer path

The payment option only shows when it can be used for that invoice.

Invoice Crowd invoice INV-2050 for Oakridge Dental Group in USD, the customer's Select a Payment Method sheet with Pay Using Authorize.net, and what Authorize.net asks for next.

Use the one-time payment flow

Tokenized one-time capture is active and requires a settled or captured provider result before the invoice changes.

  • The amount comes from the invoice
  • The payment is applied to that invoice
  • The customer pays on the provider's own page

Recurring payments work differently

Existing marker-bound renewals and lifecycle handling are supported. Invoice Crowd does not create new Authorize.net subscriptions.

  • One-time and recurring differ
  • Some existing setups only keep running
  • New ones aren't offered where unsupported

Checked before the payment is recorded

An invoice is marked paid only when the provider confirms it.

Invoice Crowd Payments Needing Review holding a Authorize.net payment for INV-2050 that arrived after the invoice was paid, with the checks Authorize.net payments must pass before they are recorded.

The payment must match the invoice

Authenticated transaction result, merchant account/mode, invoice allocation, amount, currency and stable transaction identity.

  • Merchant account and mode
  • Same invoice, amount and currency
  • The provider reports it as paid

Know the current limits

Do not plan a new subscription workflow around this integration. Existing bindings remain a compatibility path.

  • Nothing is assumed paid
  • Pending stays pending
  • Mismatches are refused

Integration facts

What to verify before using Authorize.net

The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.

  • Availability

    Active tokenized capture

  • One-time payment

    Tokenized one-time capture is active and requires a settled or captured provider result before the invoice changes.

  • Recurring payments

    Existing marker-bound renewals and lifecycle handling are supported. Invoice Crowd does not create new Authorize.net subscriptions.

  • Merchant setup

    API login ID, client key, write-only transaction and signature keys, plus Live/Sandbox mode.

  • Settlement evidence

    Authenticated transaction result, merchant account/mode, invoice allocation, amount, currency and stable transaction identity.

  • Regional fit

    Authorize.net controls merchant eligibility, supported currencies, fees and settlement services.

  • Current limits

    Do not plan a new subscription workflow around this integration. Existing bindings remain a compatibility path.

  • Invoice data

    Amount, currency and allocation are derived from the current server-side invoice state.

  • Unmatched payments

    If a confirmed Authorize.net payment can't be applied to its invoice, for example because the balance changed after checkout started, Invoice Crowd holds it in Payments Needing Review. You then apply it to the invoice, keep it as customer credit, or refund it.

  • Refunds

    Choose Refund on the invoice in Invoice Crowd and the money goes back to the customer through Authorize.net. The refund is booked only after Authorize.net confirms it. This covers online payments made on the invoice page.

  • Provider fees

    Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.

  • Alternative gateways

    Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.

Questions

Authorize.net and Invoice Crowd, answered

Is the Authorize.net integration currently available in Invoice Crowd?

Yes. Authorize.net is active in Invoice Crowd for one-time payments. The payment is tokenized and captured, and the invoice changes only after Authorize.net returns a settled or captured result.

What do I need to connect Authorize.net?

API login ID, client key, write-only transaction and signature keys, plus Live/Sandbox mode. Authorize.net controls merchant eligibility, supported currencies, fees and settlement services. Authorize.net needs a paid Invoice Crowd plan; the free plan includes PayPal.

How does Authorize.net one-time checkout work?

Tokenized one-time capture is active and requires a settled or captured provider result before the invoice changes.

Does Authorize.net support recurring payments in Invoice Crowd?

Existing marker-bound renewals and lifecycle handling are supported. Invoice Crowd does not create new Authorize.net subscriptions.

How does Invoice Crowd decide that a payment succeeded?

Authenticated transaction result, merchant account/mode, invoice allocation, amount, currency and stable transaction identity. A browser return or posted status alone cannot settle the invoice. A confirmed payment that can't be applied to its invoice is held in Payments Needing Review until you decide what to do with it.

Are gateway fees included in Invoice Crowd pricing?

No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.

Can I refund a Authorize.net payment from Invoice Crowd?

Yes. Choose Refund on the invoice (from the invoice list, the editor or Manage Payments), then pick "Refund it to the customer via Authorize.net". Invoice Crowd sends the refund through Authorize.net and books it only after Authorize.net confirms it. This works for online payments made on the invoice page, not for recurring, subscription or payment-link invoices.

Test Authorize.net with a representative invoice

Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.

  • Never marked paid from the browser alone
  • Provider terms apply
  • Current status is visible
Start free Payment gateway overview