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
Payment integration
Connect Authorize.Net without treating checkout as proof
Use tokenized Authorize.Net invoice capture in Invoice Crowd with exact transaction verification and disclosed subscription limitations.
- Status: Active tokenized capture
- Verified against application docs
- Provider terms still apply
Last updated:
Configuration to settlement
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
Credentials and mode stay tied to the selected business.
Confirm provider eligibility before rollout
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
Availability is evaluated before a customer enters checkout.
Use the supported one-time flow
Tokenized one-time capture is active and requires a settled or captured provider result before the invoice changes.
- Server-owned amount
- Bound invoice allocation
- Provider-controlled payment step
Read the recurring-payment boundary separately
Existing marker-bound renewals and lifecycle handling are supported; new Authorize.Net subscription creation is retired.
- One-time and recurring differ
- Existing bindings may be compatibility-only
- Retired creators stay unavailable
Verify before recording money
The final local state follows provider evidence, not the browser.
Match the commercial record exactly
Authenticated transaction result, merchant account/mode, invoice allocation, amount, currency and stable transaction identity.
- Merchant account and mode
- Allocation, amount and currency
- Successful provider state
Keep the current limitation visible
Do not plan a new subscription workflow around the retired creator. Existing bindings remain a compatibility path.
- No inferred settlement
- Pending stays pending
- Mismatch fails closed
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; new Authorize.Net subscription creation is retired.
-
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 boundary
Do not plan a new subscription workflow around the retired creator. Existing bindings remain a compatibility path.
-
Invoice data
Amount, currency and allocation are derived from the current server-side invoice state.
-
Customer result
A provider screen or browser return is a locator, not sufficient settlement proof.
-
Retries
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
-
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?
Current status: Active tokenized capture. Tokenized one-time capture is active and requires a settled or captured provider result before the invoice changes.
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.
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; new Authorize.Net subscription creation is retired.
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.
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.
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.
- No browser-only settlement
- Provider terms apply
- Current status is visible