Help Center

Overview

This guide provides a quick reference for which payment providers and methods are compatible with different areas of the CRM. Use it during client onboarding, for troubleshooting payment issues, and when designing your checkout flows.

Payment Support Matrix

The following table shows which payment providers and methods are supported (marked with Y) or not supported (marked with N) in each product area. Please note that some payment methods only support one-time payments and are not available for recurring subscriptions.

Payment Providers / Methods

Order Forms: Y
Form Payments: Y
Survey Payments: Y
Email Direct Checkout: Y
Ecommerce Store: Y
Invoices: Y
Invoices (Recurring): Y
Payment Links: Y
Courses: Y
Communities: Y
Contact page (charge a card): Y
SaaS Mode: Y
Calendar / Services: Y
Service Menu: Y
POS: Y

This pattern continues for each provider and method listed in the source, mapping the Y/N values accordingly for Stripe (and its various methods like Apple Pay/Google Pay, ACH, etc.), PayPal, AuthorizeDotNet, NMI, Square, Razorpay, and 3rd Party Integrations.

Product Area Definitions

Understanding the different areas where payments can be collected is key to using this guide effectively.

Order Forms: Forms built within funnels or websites specifically for selling products or offers.
Form Payments: Standard forms that have been upgraded with a payment element to collect one-time payments or donations.
Survey Payments: Surveys that include a payment element, allowing you to accept a payment when the survey is submitted.
Email Direct Checkout: A checkout process started directly from an email using a payment link.
Ecommerce Store: A full storefront with a product catalog and integrated checkout system.
Invoices: System for creating and sending one-time invoices to contacts.
Invoices (Recurring): System for setting up and managing automated, recurring billing cycles.
Payment Links: Shareable links that lead to a hosted checkout page for one or multiple products.
Courses: Payments associated with purchasing or gaining access to a course.
Communities: Payments for membership to a community or group.
Contact page (charge a card): Functionality to charge a saved card or a new card directly from a contact's record.
SaaS Mode: Billing for software plans and subscriptions offered by an agency to its sub-accounts.
Calendar / Services: Collecting payments in conjunction with booking a service or calendar appointment.
Service Menu: A menu-driven interface for ordering and paying for services.
POS: Accepting in-person payments using a mobile device or a compatible card reader.

Frequently Asked Questions

Why is a wallet payment button (like Apple Pay or Google Pay) not showing even though the table says it's supported?

Wallet buttons have specific technical requirements. Apple Pay will only appear on Apple devices (like iPhones, iPads, and Macs), and Google Pay will only appear on Android devices. Ensure the payment method is activated with your provider and that the customer's digital wallet is properly set up.

If the table shows a provider is supported, does that mean it works for subscriptions?

Not always. Some payment methods are designed for one-time payments only and cannot be used for recurring billing. Please review the note at the top of the table and thoroughly test any recurring payment scenario before making it available to customers.

Can I display both Stripe and PayPal options on the same checkout page?

Yes, in most product areas, you can offer multiple payment options if you have connected and enabled both providers. The checkout page will automatically display the available payment buttons to the customer.

Do physical card readers work with Order Forms or Invoices?

No. Card readers are exclusively for use with the POS (Point of Sale) product area for accepting in-person payments.