Add a Customer Card From the Membership Workflow

The maintenance plan is ready, the customer is ready, and the payment method should not be hiding in a different corner of the office. Authorized Local Business Pro users can add a customer card from the contact's Memberships workflow using a Stripe-hosted form. Contact-level card setup is Stripe only. It requires configured Stripe credentials, an active connected Stripe account that can accept charges, and the appropriate Service Agreements & Memberships access. Saving the card does not charge the customer, enroll the membership, or activate recurring billing. It prepares an eligible payment method for a separate, reviewed enrollment decision.

Add the card where the recurring plan is being reviewed

The contact record brings the customer, service address, memberships, agreements, and saved payment methods into one working context. The Memberships area gives an authorized operator an Add payment method action there, instead of sending the office into a separate payment workflow.

After Stripe verifies the setup, the saved method can appear with practical details such as card brand, last four digits, expiration, primary status, and any reason it is unavailable.

That readback matters. “Card on file somewhere” is not a billing policy. The team still needs to know whether this card belongs to the right customer and connected account, remains usable, and matches the plan being considered.

The person completing the work needs Service Agreements & Memberships permission. The card remains scoped to its customer and business context.

Stripe collects and verifies the card details

Card entry takes place in Stripe's hosted payment form. Stripe collects and verifies the sensitive card details; Local Business Pro receives the verified payment-method reference and saves the card summary needed for the contact workflow. The application does not ask the operator to submit or store the raw card number or security code.

Before that form is available, the business needs its Stripe configuration in place and an active connected Stripe account with charges enabled. If the connection is missing, inactive, or not ready to accept charges, the setup should stop for review. Completed setup does not prove a future charge will succeed or that every recurring plan can use the card.

This update does not add contact-level card setup for Deluxe, Authorize.Net, Dejavoo, or every other processor. It also does not introduce a universal ACH setup path from this action. Those are different processor and method workflows with their own requirements.

A saved card still has to fit the selected plan

Saving a card creates an option. Enrollment decides whether that option is eligible.

The processor and connected account must match

The saved card must belong to the active processor and connected Stripe account resolved for enrollment. A card saved under another provider or connected account cannot be borrowed for the plan.

The card must still be usable

An expired, hidden, invalidated, or otherwise unavailable card is not eligible. Its summary and availability reason distinguish “this card exists” from “this card is ready for this plan.”

The plan must accept cards

A card-only or card-accepting plan may use an eligible saved card. An ACH-only plan may not. Adding a card does not rewrite the plan's accepted payment methods, and it does not make every payment type interchangeable because they all live under the general heading of money.

The billing rule decides whether a card is required

Not every membership needs a saved card at enrollment. An automatically billed plan with a charge due may require one. A manually billed plan can proceed without forcing card setup when its rules allow it. A configured zero-dollar automatic start may also proceed without a payment method under the supported first-cycle rules.

A zero-dollar opening cycle does not promise that later billing requirements disappear. The operator should review the billing trigger, first-cycle amount, accepted method types, and plan configuration before enrollment.

Saving a card and enrolling a membership are separate decisions

Card setup does not skip the recurring-service review. The contact and business must be in scope; the plan must be active and eligible; and the service address, agreement, accepted method, and first charge must be ready. The operator then selects an eligible saved method when required and completes enrollment separately.

That separation protects the customer decision. A saved card does not automatically start the membership, sign an agreement, schedule visits, collect the first payment, or promise that a later charge will succeed. It is one guarded part of the wider agreement-to-payment handoff.

For the surrounding customer and payment context, review the contact workspace and transaction tools. Recording an invoice payment is also a separate workflow; use the guide to record payments on invoices when the work is invoice collection rather than membership card setup.

Four recurring-service workflows

HVAC maintenance with automatic billing

An office manager opens the customer contact, adds a Stripe card, and confirms the displayed brand, last four digits, and expiration. Before enrollment, the operator verifies that the connected Stripe account is active and charges-enabled, the HVAC maintenance plan accepts cards, automatic billing requires a payment method, and any required agreement is signed. Saving the card alone completes none of those other steps.

Pest control with a zero-dollar first cycle

A recurring pest plan may have a zero-dollar automatic start. That opening cycle can proceed without a payment method when properly configured. Later billing still follows the plan and its accepted methods.

Plumbing membership with manual billing

A plumbing company enrolls a customer in a manually billed membership. If the plan does not require a card, the operator can complete enrollment without manufacturing a card requirement.

Electrical plan that accepts ACH only

The contact already has a saved Stripe card, but the selected electrical service plan accepts ACH only. The card may remain visible on the contact while being unavailable for that enrollment. The operator uses the supported method and workflow for the plan rather than bypassing the accepted-method rule.

What this update does not add

This focused card-setup workflow does not promise:

• card setup for every payment processor;
• universal ACH setup from the contact action;
• automatic membership activation, renewal, or billing;
• automatic fallback to a backup card;
• arbitrary card updates, deletion, or migration between processors;
• universal off-session charging or payment recovery; or
• successful charges merely because setup completed.

It also does not remove agreement, address, permission, first-cycle, processor, or enrollment review. Those are not ceremonial hoops. They are the facts that determine whether this saved card belongs in this recurring plan.

Frequently asked questions

How do I add a saved card from a customer membership record?

Open the contact's Memberships workspace and use Add payment method. An authorized user completes the card entry in Stripe's hosted form, then reviews the verified saved-card summary on the contact.

Which processor supports contact-level card setup?

Stripe only in the current workflow. The business also needs configured Stripe credentials and an active, charges-enabled connected Stripe account.

Does saving a card automatically enroll the membership?

No. Card setup and enrollment are separate actions. The operator must still review the plan, agreement, service address, billing rule, accepted method, first-cycle amount, and any required payment-method selection.

Does every recurring plan require a card?

No. Manual-billing plans and some configured zero-dollar starts may not require one. A plan that accepts only ACH cannot use the newly saved card.

Why is a saved card unavailable for a membership plan?

The card may be expired, hidden, invalidated, tied to the wrong provider or connected account, incompatible with the plan's accepted methods, or associated with an inactive payment connection.

Confirm the whole enrollment before the final click

Choose one recurring plan your team actually sells and review it from the contact record. Confirm staff permission, the connected Stripe account, accepted payment methods, agreement status, billing trigger, first-cycle amount, card availability, and service address. Then make the enrollment decision as its own step.

The feature keeps card setup close to the membership conversation. The operator still keeps the decision honest—which is exactly where that responsibility belongs.