Authorize.Net x Virto Commerce
B2B enterprises that need a reliable, established payment gateway with support for cards, eChecks, and B2B-specific tools like invoicing and net terms can use Authorize.Net, and Virto Commerce connects to it through APIs to handle checkout, payment processing, and settlement.
About Authorize.Net
Authorize.Net is a payment gateway, owned by Visa, that connects merchants, payment processors, and banks to process credit cards, eChecks, and digital wallet payments. It serves a large base of small-to-mid-sized businesses, with specific tools for B2B payment scenarios like terms invoicing and recurring billing. It includes built-in fraud detection, customer information storage for repeat transactions, and digital invoicing that lets businesses email invoices customers can pay through a secure link.
How Virto Integrates with Authorize.Net
Virto Commerce connects to Authorize.Net through its API to process payments during checkout, keeping payment processing and compliance with Authorize.Net while Virto handles the buyer-facing commerce experience. Order and payment data flow from Virto’s checkout to Authorize.Net, which authorizes the transaction and returns the result back to Virto.
The integration approach generally covers:
- Routing checkout payments through Authorize.Net’s API for authorization and settlement
- Supporting the payment methods Authorize.Net makes available, including cards, eChecks, and digital wallets
- Handling payment confirmation, failure, and refund flows between Virto and Authorize.Net
- Keeping sensitive payment data within Authorize.Net’s compliant infrastructure rather than passing it through commerce
Note: For system-specific integration patterns, available accelerators, and the right approach for your payment setup, speak with a solution partner.
Implementation Approach
Virto Commerce integrates with enterprise systems through a combination of APIs, middleware, and integration accelerators — designed to reduce implementation effort while preserving the flexibility that enterprise-specific workflows require.
Key considerations: which payment methods need to be supported, whether B2B-specific flows like terms invoicing are required, existing Authorize.Net account setup, and whether the business needs online payments only or a broader multi-channel setup including phone or in-person.
Use Cases
Offering eCheck payments alongside cards for B2B orders
B2B buyers often prefer eChecks over cards for larger orders since they typically carry lower processing fees. When Virto’s checkout connects to Authorize.Net, buyers can choose eCheck or card at checkout, with both payment types flowing through the same integration.
Buyers get a lower-cost payment option for larger orders, and Virto’s checkout handles both payment types without separate logic for each.
Supporting B2B terms invoicing alongside standard checkout
Some B2B buyers need to pay via invoice with payment terms rather than at the time of order. Authorize.Net’s invoicing tools can email a payable invoice tied to an order that originated through Virto’s checkout, giving buyers a terms-based path alongside immediate payment.
Buyers who need payment terms get an invoicing path, while buyers who want to pay immediately still go through standard checkout — both connected to the same order in Virto.
Keeping payment data out of the commerce platform
Sensitive card data should never sit inside a commerce platform if it can be avoided. Virto’s checkout passes payment details straight to Authorize.Net, so card numbers are processed and stored within Authorize.Net’s compliant infrastructure, not within Virto.
PCI compliance scope stays with Authorize.Net’s certified infrastructure, keeping the commerce implementation simpler and lower-risk by design, not as a workaround.