Payment acceptance fundamentals
Getting Started & Merchant Accounts
Starting payment acceptance means connecting a business, checkout method, provider, transaction flow, settlement path, and support process. This hub explains the roles merchants commonly encounter and the records to verify before choosing or changing a setup.
Build the map
Identify each organization and system involved
A merchant account can describe the account relationship used to accept and settle electronic payments. A processor carries transaction messages among payment participants. A gateway securely passes payment information from a digital checkout. Some providers combine these functions, while other setups involve separate organizations and agreements.
Business account
Confirm the legal business name, tax information, owners or authorized contacts, deposit account, operating model, and locations used during onboarding.
Acceptance channels
List storefront, mobile, ecommerce, invoicing, recurring, keyed, and other workflows so the solution matches how customers actually pay.
Service ownership
Document who provides the account, gateway, software, equipment, deposits, statements, dispute tools, security guidance, and support.
Evaluation sequence
Compare the complete operating relationship
Before applying
- Verify the provider's legal identity and official contact information.
- Read the agreement, renewal, cancellation, equipment, and support terms.
- Confirm supported payment channels using current written documentation.
- Ask what business records and ownership information are required.
Before going live
- Test the approved checkout and receipt workflow.
- Confirm user permissions and administrator access.
- Locate transaction, batch, transfer, statement, and dispute reports.
- Save escalation contacts without sharing secret credentials.
Useful starting points
Answer the foundational questions first
Common questions
Merchant account FAQ
Does every provider use a separate merchant account?
No. Some payment services combine account, processing, and gateway functions, while other arrangements separate them. Confirm the actual legal and operating structure.
Is a merchant ID the same as a bank account number?
No. A merchant identifier is used within a payment relationship. Keep it protected and follow the provider's instructions when referencing it.
Can equipment be moved between providers?
Do not assume so. Hardware ownership, software, encryption, configuration, certifications, and provider policies can affect use. Obtain written confirmation first.
What records should a merchant retain?
Keep signed agreements, approved applications, support contacts, equipment records, statements, transaction reports, and account-change confirmations according to business and legal requirements.
Last editorial review: August 13, 2026. Product structures and onboarding requirements vary; verify current details with the organization responsible for the account.
Next step
Define the checkout before comparing providers
Document where customers pay, which systems need to connect, who needs access, and how deposits and support should work.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US