Providers to assess for payments and point of sale
StripeConnect your own account
SquareLimited release
CloverNeeds assessment
PayPalNeeds assessment
Check the actual connection before changing your process.
On Pro, the QuickBooks Online connection imports customers and invoices from your own company and does not write back. It still needs checking with your company. Other provider names and the information flows below describe requirements to assess, not ready-to-use connections. Confirm the provider, plan, permissions, direction and any setup cost before work begins.
What these systems normally control
Requirements for assessment; confirm supported actions before relying on this workflow.
Card processing, ACH, terminals, refunds, chargebacks, tipping, tender types, and — for POS — sales, product catalogs, and register-close reporting.
Why the specialized system usually stays
Requirements for assessment; confirm supported actions before relying on this workflow.
Payment processing is regulated and priced by the processor. POS systems handle terminals, receipts, tender types, and end-of-day close in ways The Forge is not designed to. The Forge sits above the processor to connect payments back to the customer, invoice, or job they belong to.
Information to review for import
Requirements for assessment; confirm supported actions before relying on this workflow.
Payments, refunds, and chargebacks
Payment methods on file (tokenized only)
Sales transactions from POS with line items
Register or shift close summaries
Product and service catalogs where relevant
Information to review for export
Requirements for assessment; confirm supported actions before relying on this workflow.
Requests to charge a saved payment method against an invoice
Refund requests for approved invoices
Customer and invoice metadata attached to the payment intent
Payment-related communication to the customer
Events to consider during setup
Requirements for assessment; confirm supported actions before relying on this workflow.
Payment succeeded
Payment failed or was refunded
POS sale closed
Chargeback received
Saved payment method expired
Manual work the proposed connection may reduce
Requirements for assessment; confirm supported actions before relying on this workflow.
Matching Stripe deposits to customer accounts by hand
Applying POS sales to the right customer record after the fact
Reconciling refunds against the sale or job they belong to
Copying receipts between systems for follow-up
Whose work improves
Requirements for assessment; confirm supported actions before relying on this workflow.
Owner / executive
Finance and accounting
Operations manager
Office administrator
Reports that become possible
Requirements for assessment; confirm supported actions before relying on this workflow.
Revenue by acquisition source, job, or campaign
Failed-payment rate by customer segment
Average time from work completion to payment
Chargeback rate by service type
Access and permission notes
Requirements for assessment; confirm supported actions before relying on this workflow.
Card data is never stored on The Forge — only processor-issued tokens.
Processor OAuth or scoped API tokens are used.
Refund actions can be gated on human approval for accounts that require it.
Common category-wide limitations
Requirements for assessment; confirm supported actions before relying on this workflow.
POS providers vary widely in API depth; some require managed exports.
Historical payments may not be importable beyond a provider-set window.
Real-time reconciliation depends on the processor's webhook reliability.
What might be replaced after review
Requirements for assessment; confirm supported actions before relying on this workflow.
The Forge does not replace the processor or the POS. It removes the reconciliation work that lives between them and your connected business record.