By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.
Treat activation as an operating handoff
A software account showing a payment button does not tell the business whether every onboarding step is complete. Before the first public sale, verify the merchant entity, receiving account, support route and reporting access. Assign a person to own the handoff from application to live operations.
Make a checklist from the provider’s actual requirements. Mark what has been submitted, what has been accepted and what still needs review. Avoid describing a pending account as fully ready simply because staff can enter products or view a dashboard.
Verify the records that connect the relationship
Compare the legal entity and trading name across the software subscription, merchant agreement and provider records. Ask how the customer-facing descriptor will appear. Confirm the approved method for verifying the payout destination without sharing banking information through an untrusted channel.
Record which company handles payment support and how to identify the account when contacting it. If the software vendor and processor use different account references, keep the relationship between them in the internal support guide.
Run a complete approved test
Ask the provider how to perform a permitted test of a purchase, void and refund. Trace the resulting entries into the order report and payout record. The test is incomplete if the employee sees a successful checkout but the bookkeeper cannot explain the financial entries.
Confirm how staff should respond if an order appears unsuccessful after the customer submitted payment. They need a status-check process before trying again. Document which provider owns the investigation when the application and payment screens disagree.
Check permissions and the first statement
Review who can change payment settings, issue refunds and export financial reports. Use the PCI Security Standards Council’s merchant resources to frame the security discussion with the provider. Ask what responsibilities apply to this specific integration.
For a New Jersey service business replacing a booking platform, identify who will handle deposits and refunds from the previous system. Keep old transaction references accessible for legitimate service needs. Do not assume opening the new account automatically transfers earlier obligations or saved credentials.
After the first complete statement, compare actual charges and deposits with the agreement and tests. Keep unanswered questions on an exception list. Onboarding is finished when the business can operate and supervise the payment workflow, not just when a sign-up form has been submitted.
References and related reading
Primary resource checked for this review: PCI Security Standards Council’s merchant resources. Confirm the current requirements and implementation with the responsible provider or appropriate adviser.
Continue with Embedded Payments: Map the Support and Exit Responsibilities and How to Read a Merchant Processing Statement Without Losing the Detail.
For state and local business resources alongside this operating checklist, use the New Jersey business operations guide on All State Merchants.
