By Eric Kuvykin. Reviewed October 17, 2026. This practical guide replaces an earlier general commentary article at the same address.
A sign that says “cards accepted” is a customer promise. A merchant should be able to explain which payment methods work in each channel and what staff do when they fail. Build an acceptance matrix before changing a policy or making claims based on a litigation headline. This is an operational inventory, not permission to discriminate among card categories or override the merchant agreement.
Map channels separately
Create rows for the staffed counter, mobile terminal, online checkout, telephone order, invoice link and any third-party platform. For each, record the accepted brands and supported methods exactly as the provider documents them. Identify whether recurring payments, refunds or order adjustments use a different system. Leave an unknown field blank and assign someone to obtain the answer.
Add columns for customer-facing signs, website text, booking confirmations and staff instructions. Compare the promise with the actual supported configuration. A payment icon copied into a website footer does not prove the method is enabled, and a working terminal does not establish that an unrelated online plugin supports the same behavior.
Separate current rules from proposed changes
Before narrowing acceptance or introducing a fee, obtain current written guidance from the processor and review the relevant agreement. Visa’s rules and policy resources provide a primary network reference. Record the effective date and scope of any instruction. A proposal, preliminary court development or news summary should not become a terminal setting without an account-specific implementation review.
Ask who will approve the decision, configure the system and check the customer communications. If multiple locations use different merchant accounts, review them individually. Do not assume that a test in one store validates every account or that a cash register label accurately identifies every underlying card product. Questions about legal obligations belong with a qualified adviser.
Test an ordinary purchase and the exception path
Use the provider’s approved testing method to check a supported transaction, a refund, a failed attempt and the resulting receipt. Record the expected outcome before the test. Confirm that staff know the approved alternative if a method is temporarily unavailable. They should be able to explain the limitation respectfully without requesting sensitive details through an improvised channel.
Keep the matrix beside the digital-wallet counter checklist and the tap-to-phone equipment review. For a business with different operating locations, the New Jersey guide supplies a local planning starting point rather than an acceptance-rule opinion. Review the matrix when software, signage or the merchant agreement changes. The benefit is a consistent customer promise backed by configuration and records that an owner can actually verify.
