Know the Cost
Look at the complete processing structure instead of comparing only the headline transaction percentage.
Merchant Services + Payment Processing
Accept payments. Understand what you are paying for.
Payment processing involves more than the percentage printed on a rate sheet.
Fawkes can help connect websites and eCommerce checkout with supported payment providers while helping businesses understand the difference between the storefront, payment gateway, processor, merchant relationship, fees, settlement, risk, and operational workflow behind every transaction.
Checkout
Gateways
Processing
PCI Awareness
Payments Without the Confusion
The checkout button is only the visible part.
Behind an online or in-person payment can be a merchant account, payment gateway, processor, acquiring relationship, card network, bank, fraud controls, settlement process, fees, compliance requirements, and customer refund or chargeback process.
Understanding how those pieces connect makes it easier to compare providers, evaluate costs, plan integrations, and avoid making an important business decision based on one advertised percentage.
Know the Provider
Understand which company provides the merchant relationship, gateway, processing services, equipment, software, or other payment components.
Know the Integration
Confirm how the payment system connects with the website, eCommerce platform, point of sale, accounting, CRM, or other business systems.
Know the Payout
Understand expected settlement timing, deposit schedules, holds, reserve requirements, and circumstances that may delay funds.
Know the Risk
Industry type, transaction method, chargebacks, refunds, average ticket, processing history, and other factors can affect the merchant relationship.
Know the Responsibility
Accepting payment cards creates security, operational, provider, and PCI-related responsibilities that should be understood before launch.
How the Pieces Fit Together
Storefront. Checkout. Gateway. Processing.
These terms are often used as if they mean the same thing. They do not.
Storefront
The website, product page, invoice, point of sale, or other customer-facing experience where the purchase begins.
Checkout
The customer-facing process used to review the transaction, provide required information, select payment options, and submit the purchase.
Payment Gateway
The technology layer that securely connects payment information from the checkout experience into the processing environment.
Processor
The processing infrastructure helps route the transaction through the appropriate financial and card-network systems for authorization and settlement.
Merchant Relationship
The merchant agreement establishes important terms surrounding processing, pricing, settlement, risk, reserves, disputes, and account responsibilities.
Settlement
After successful processing, funds move through the settlement process and are deposited according to the provider relationship and applicable timing.
Payment Processing Review
The lowest advertised rate may not be the lowest total cost.
Processing can include percentage-based fees, per-transaction charges, gateway fees, monthly charges, equipment, PCI-related fees, chargeback costs, specialty transaction pricing, and other provider-specific expenses.
The more useful question is often not “what is the rate?” but “what does accepting payments actually cost this business?”
Processing Rate
Understand the percentage-based portion of transaction pricing and how it applies to the transactions your business accepts.
Transaction Fees
Review per-transaction charges that can become especially important for businesses with many smaller purchases.
Monthly Costs
Consider gateway, software, statement, platform, equipment, account, or other recurring charges associated with the relationship.
Chargeback Costs
Understand provider policies and potential costs surrounding disputes, chargebacks, evidence requirements, and transaction reversals.
Settlement Timing
Review how quickly processed funds are normally deposited and what conditions may create holds, reserves, or delayed availability.
Effective Cost
Evaluate the complete processing expense against actual transaction volume rather than comparing one number in isolation.
Business Fit Matters
The right payment setup depends on how you actually get paid.
A restaurant, professional office, contractor, online retailer, subscription business, nonprofit, and high-ticket service provider can have very different transaction patterns and payment requirements.
The processing environment should be evaluated around the business model instead of assuming one merchant setup works equally well for everyone.
- Monthly processing volume
- Average transaction amount
- In-person versus online payments
- Card-present versus card-not-present transactions
- Recurring payments
- Refund patterns
- Chargeback exposure
- Industry classification
- Settlement requirements
- Software and integration needs
One Rate Does Not Tell the Story
A payment model that works for one business may be expensive or impractical for another.
Transaction size, volume, payment channel, industry, refund behavior, chargebacks, hardware, software integrations, and settlement needs can all change what “good payment processing” looks like.
Payment Channels
Customers may pay in more than one place.
The payment strategy should account for the places and processes through which the business actually accepts money.
Website Checkout
Accept payment through supported eCommerce and online checkout experiences connected to the selected provider.
Point of Sale
Support in-person transactions through compatible POS hardware, software, processors, and business workflows.
Invoices
Allow customers to pay invoices or payment requests through supported payment links and connected systems where available.
Recurring Payments
Subscriptions, memberships, retainers, and recurring services may require tokenized or provider-managed recurring-payment workflows.
Mobile Payments
Field-service and mobile businesses may need payment options that work outside a traditional storefront.
Multiple Channels
Businesses accepting payments online, in person, by invoice, and through recurring billing should consider how those channels connect operationally.
Payment Security + PCI
Payment information deserves a smaller attack surface.
Businesses accepting payment cards have security and PCI responsibilities that depend on how payments are accepted, transmitted, processed, and stored.
A practical payment architecture should minimize unnecessary exposure to card data and rely on supported payment-provider controls wherever appropriate.
- Use supported payment providers
- Limit unnecessary card-data exposure
- Use secure hosted or tokenized workflows where appropriate
- Protect administrative access
- Maintain secure website infrastructure
- Keep payment integrations current
- Understand PCI responsibilities
- Document operational payment procedures
Important Distinction
A secure website does not automatically make the entire business PCI compliant.
Compliance depends on the complete payment environment, processing method, provider relationship, systems, procedures, employee practices, and applicable requirements.
Refunds
Plan the customer-service side of payments.
Refund policies, cancellation terms, receipts, fulfillment expectations, customer communication, and support processes can all influence how smoothly payment issues are resolved.
Chargebacks
A payment dispute becomes an operational issue too.
Businesses should understand how disputes are communicated, what documentation may be required, applicable response deadlines, provider policies, and how excessive chargebacks may affect the merchant relationship.
Where Fawkes Fits
Build the customer experience. Connect it to the payment system.
Fawkes focuses on the digital experience surrounding the payment rather than pretending the website itself is the merchant processor.
eCommerce Websites
Build customer-facing product, cart, checkout, and purchase experiences using supported commerce platforms.
Gateway Integration
Connect supported payment gateways and provider integrations available through the selected website or commerce platform.
Checkout UX
Make the path from product or service to checkout clear, mobile friendly, trustworthy, and easy for customers to understand.
Performance
Build the surrounding website with performance, mobile usability, security, and customer experience in mind.
Customer Trust
Use professional design, clear policies, accurate information, contact details, and purchase expectations to reduce uncertainty.
Technical Direction
Help identify how the website, payment gateway, processor, and broader business systems need to connect.
Payments + Business Operations
The payment is one transaction. The business process continues.
After a payment is accepted, the business may still need to update the customer record, account for the transaction, manage products or inventory, fulfill an order, send communications, create documents, or trigger additional workflows.
Fawkes Digital Marketing
Customer-facing commerce.
Fawkes focuses on websites, eCommerce storefronts, checkout experiences, supported gateway integrations, search visibility, and the digital customer journey surrounding the transaction.
- eCommerce websites
- Product pages
- Cart and checkout
- Gateway connections
- Mobile experience
- Customer-facing trust
Brilliance One
Operational workflows behind the transaction.
Brilliance One provides a broader business environment for organizations that need payment-related activity connected with POS, accounting, products, inventory, CRM, customer records, automation, and other operational workflows.
- Point of sale
- Accounting
- Products and inventory
- CRM
- Customer records
- Automation
- Communications
- Operational workflows
eCommerce + Payments
The storefront and processor need to work together.
Choosing an eCommerce platform without considering payment requirements can create limitations later. Choosing a processor without considering the storefront and operational systems can create the same problem in reverse.
Payment compatibility should be considered while the commerce architecture is being planned rather than after the store is already built.
Storefront
Cart
Checkout
Gateway
Processor
Settlement
Accounting
Inventory
Payment Review
Understand. Compare. Connect.
Start with what the business needs rather than beginning with whichever payment provider is being promoted.
-
Understand
Review how the business accepts payments, transaction volume, average ticket, sales channels, eCommerce requirements, settlement expectations, and software needs.
-
Compare
Evaluate pricing structure, provider requirements, gateway compatibility, settlement terms, contracts, risk considerations, and operational fit.
-
Connect
Connect the selected payment approach with the website, eCommerce checkout, point of sale, accounting, CRM, or other business systems as appropriate.
Merchant Services FAQ
Payment processing in plain language.
What are merchant services?
Merchant services is a broad term for the financial and technical services businesses use to accept and process customer payments. Depending on the provider and setup, that can include merchant processing, gateways, terminals, online payments, settlement, reporting, fraud tools, and related services.
Is a payment gateway the same as a payment processor?
Not necessarily. A gateway generally provides the technical connection for securely transmitting transaction information, while processing involves routing and handling the financial transaction. Some providers bundle these functions into one service, which is why the terminology can appear interchangeable.
Does Fawkes provide payment processing?
Fawkes focuses on the website, eCommerce, checkout, and supported payment integration around the transaction. Merchant processing itself depends on the selected payment provider and merchant-services relationship.
Can Fawkes connect a payment provider to my website?
Yes, when the selected provider is supported by the website or eCommerce platform. Integration requirements vary by platform, provider, gateway, and business use case.
What should I compare when choosing a processor?
Useful considerations can include total processing cost, transaction fees, monthly charges, settlement timing, gateway compatibility, hardware or software requirements, contract terms, chargeback policies, reserve requirements, customer support, integrations, and business fit.
What is PCI compliance?
PCI DSS is a set of security requirements related to payment-card data. A business's responsibilities depend on how card information is accepted, transmitted, processed, stored, and which providers and systems are involved.
Does using a payment provider automatically make my business PCI compliant?
No. Using a provider can reduce the amount of payment-card data your systems handle directly, but the business can still have PCI responsibilities based on the complete payment environment, configuration, procedures, and transaction methods.
Can Brilliance One connect payments with other business operations?
Brilliance One provides a broader operational environment that can connect payment-related business activity with areas such as point of sale, accounting, products, inventory, CRM, communications, and workflow automation depending on the implementation.
Web. Hosting. Search.
Ready for a better online presence?
Fawkes helps businesses build a professional digital foundation through website design, hosting, business email, search visibility, and reputation support.
Website Design
Professional websites built around your business, services, customers, usability, and lead generation.
Web + Email Hosting
Reliable website hosting, SSL, backups, monitoring, and professional business email.
SEO + Reputation
Strengthen search visibility, local discovery, reviews, and the trust customers see when they find your business.
Payment Processing Review
Know where the money goes before you sign the agreement.
Tell us how your business accepts payments, what systems need to connect, and where the current process is creating questions. We can help separate the storefront, checkout, gateway, processing, and operational requirements so the next decision is clearer.
eCommerce · Checkout · Payment Gateways · Processing Review · PCI Awareness · Business Operations