Build for Business Services
Power partners serving professional and personal services businesses — from consulting firms to home services — with recurring billing, invoicing, and flexible payment collection.
Get sandbox →Build with AI →VERTICAL Business Services · INTEGRATION MODEL Embedded · CHANNELS CNP, CP, Omni-Channel
01 / SOLUTIONS
Where this recipe fits
Three common partner implementation patterns.
01
Partner offers SaaS platform for home services (plumbing, HVAC, cleaning) with embedded scheduling and payment collection.
02
Professional services platform enabling consultants to invoice clients with card-on-file auto-charge.
03
Field service management tool with mobile payment acceptance for on-site job completion.
02 / CAPABILITIES
The payment stack
Products in the current recipe source. The API reference below shows each capability’s status.
01 · Product
Accept Payments
02 · Product
Unified Checkout
03 · Product
Recurring Billing
04 · Product
Digital Invoicing
05 · Product
Pay by Link
06 · Product
Customer Info Manager
03 / BUILD
API reference
Capabilities and documentation links from the current recipe source.
Common APIs
Required · Core Payments
Payment Authorization
Authorizes transactions across supported channels and payment types.
Required · Core Payments
Refund and Void
Processes refunds, voids pending authorizations, and handles payment reversals.
Primary Payment Acceptance
These are the recommended ways for merchants to accept card payments in your platform:
Recommended · Digital Acceptance
Unified Checkout
Full-featured hosted payment UI handling card capture, digital wallets, and 3DS — recommended for simplicity and reduced PCI scope (SAQ-A eligible). Documentation
Alternative · Digital Acceptance
Flex Microform v2
Secure card field tokenization with full UI control — ISV manages all subsequent transactions (authorization, capture, refunds). Documentation
Secondary Payment Channels
Additional payment collection methods — invoices, payment links, and other non-checkout flows:
Required · Billing
Digital Invoicing
Generate and send payment-enabled invoices with embedded pay links. Documentation
Required · Digital Acceptance
Pay by Link
Send secure payment links through email, SMS, or messaging for remote collection. Documentation
Services APIs
Required · Subscription
Recurring Billing
Automated billing cycles with flexible scheduling and retry logic. Documentation
Required · Security
Tokenization Service
Secure card-on-file storage for recurring and repeat clients. Documentation
Optional · Integration
Webhook Notifications
Real-time alerts for successful payments, failures, and subscription events.
04 / CONSIDERATIONS
Regional insights
Consider these market differences as you design the integration.
Europe
SCA exemptions for merchant-initiated transactions (MIT) critical for subscription billing. SEPA Direct Debit widely expected for recurring B2B services. VAT handling on invoices varies by country.
Asia-Pacific
Diverse recurring payment rules — Japan and Korea have specific card-on-file consent regulations. UPI AutoPay in India for recurring. High mobile penetration means SMS-based pay links are primary collection method.
Latin America
Boleto bancário (Brazil) and OXXO (Mexico) still significant for non-card payers. Recurring billing on credit cards limited in some markets — pre-authorization models needed. Currency volatility impacts pricing.
Middle East and Africa
Growing gig economy drives demand for instant settlement to service providers. Salary card payments common in UAE and Saudi Arabia. Arabic language invoicing support needed.
Regulatory notes
Recurring billing requires clear consumer consent and easy cancellation mechanisms (EU Consumer Rights Directive). PCI DSS tokenization required for card-on-file. Digital invoice archival requirements vary by jurisdiction.
Merchant segment variance
SMB services need simple recurring billing with templated invoices. Enterprise service providers need custom billing workflows, multi-entity invoicing, and integration with their existing ERP and accounting systems.
05 / LAUNCH
From sandbox to go live
Five steps from testing to partner launch.
Step 1
Sandbox Access
Register on developer portal, obtain sandbox API credentials, and configure test merchant profiles.
Step 2
Develop
Build your payment integration using Visa Acceptance Solutions SDKs and APIs for your chosen channels.
Step 3
Testing and Validation
Execute test scenarios, validate payment flows, and confirm compliance requirements.
Step 4
Go Live and Scale
Launch with pilot merchants, monitor performance, and scale across your portfolio.
Step 5
Merchant Onboarding
Onboard merchants with KYC, bank verification, and product activation.
BUILD WITH AI
Build faster with Developer MCP
Use natural language to explore APIs, generate integration code, and debug your implementation with the Visa Acceptance Developer MCP.
Explore Developer MCP →Explore another market: View all recipes →