How to Connect Authorize.Net to Sparkforge Order Forms

Authorize.Net connects to Sparkforge as a card payment gateway. Once integrated, it processes payments on order forms, invoices, subscriptions, and membership checkouts. You can run it as your default gateway or alongside Stripe and PayPal.

Requirements

• Available for merchants in the United States, Canada, and Australia.
• Funnels v2 required.
• Supported browsers: Chrome v80+, Edge (Chromium) v85+, Firefox v78+, Safari v12+. Internet Explorer, Edge Legacy, and Opera are not supported.

Get your API credentials

1. Log into your Authorize.Net account.
2. Go to Account Settings > API Credentials & Keys.
3. Generate your API Login ID and Transaction Key.

For sandbox testing, log into the sandbox Merchant Interface to get a separate set of keys.

Connect Authorize.Net to Sparkforge

1. In Sparkforge, open Payments > Integrations.
2. Paste your Live API keys into the Live fields and Sandbox keys into the Sandbox fields.
3. Click Save.
4. Sparkforge prompts you to set Authorize.Net as your default gateway. Confirm to make it default, or Cancel to keep your current default and run Authorize.Net alongside it.

Running multiple gateways

You don't need to disconnect Stripe to add Authorize.Net. Both can stay connected. The default gateway handles new transactions; existing Stripe subscriptions keep running through Stripe. PayPal works alongside either as a second payment method on order forms.

Test cards

Use a future expiry date and any 3 or 4-digit CVC.

• 4007000000027 — Visa
• 4012888818888 — Visa
• 4111111111111111 — Visa
• 370000000000002 — American Express
• 5424000000000015 — Mastercard
• 2223000010309703 — Mastercard
• 6011000000000012 — Discover
• 3088000000000017 — JCB
• 38000000000006 — Diners Club

Reporting

Authorize.Net transactions appear under Payments > Transactions. Subscriptions are visible under Payments > Subscriptions. Workflow triggers and attribution behave the same as with Stripe.

Subscription statuses

Failed payment retry logic

When a recurring payment fails, the subscription moves to Unpaid. Sparkforge retries twice more, 24 hours apart. If a later subsequent payment succeeds, the subscription returns to Active. If all retries on the final transaction fail, it moves to Expired.

Refunds

Refund any Authorize.Net transaction directly from Payments > Transactions.

Subscription cancellation

Cancel Authorize.Net subscriptions from the Subscriptions page using the Cancel Subscription action. The merchant portal is not used for this.

FDS filters

If you use Authorize.Net Fraud Detection Suite filters to hold transactions for review, Sparkforge respects them. Held order-form transactions show in your merchant portal and the Transactions page reflects the status when you approve or decline.

For recurring invoice and calendar appointment payments, FDS-held transactions are treated as declined, since waiting on manual approval would create scheduling complications.

What's covered

• Order forms — yes
• Invoices — yes
• Memberships — yes
• SaaS v2 — yes
• Text2Pay, calendar payments — check the latest release notes