Data Panda brings your QuickBooks Payments data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
QuickBooks Payments is Intuit's merchant-services arm for QuickBooks Online and QuickBooks Desktop. Customers pay an invoice with credit card, debit card, ACH bank transfer, Apple Pay, PayPal or Venmo from the Pay Now link, the customer portal or a card-on-file profile, and the matching payment, sales receipt and deposit record land back on the QuickBooks invoice without a re-key. In the field there is the GoPayment mobile app with a Bluetooth chip-and-tap card reader, and the Merchant Service Center for virtual-terminal entries.
Under the hood the API exposes six resources: charges, refunds, tokens, cards, bank-accounts and echecks. Each card or ACH transaction lives as a charge with a status (authorised, captured, refunded, failed) before it is rolled into the end-of-day batch, settled the next business day, and deposited as one lump on the bank feed with the per-charge processing fees and any chargeback fees taken out. The QuickBooks ledger itself only ever sees the net deposit and the linked invoices. We pull the charge-level feed, the refund and dispute records, the deposit batches and the fee detail into your warehouse, so the controller can answer "what did we net on this invoice, after card and ACH fees" without opening the Merchant Service Center.
Charge, fee and refund detail joined back to the QuickBooks invoice and customer.
Stop hand-splitting weekly deposit lumps and chasing disputes by email.
Train models on real charge history, not survey data.
Internal tools for the controller, the billing clerk and the founder.
A list of concrete reports, automations and AI features we have built on QuickBooks Payments data. Pick the one that matches your situation.
How much did we net on each invoice after fees and refunds?
Each QuickBooks Payments charge is joined to its invoice in the warehouse, with the per-transaction processing fee and any partial or full refund subtracted. The controller sees gross invoice, gross collected, fee, refund and net cash on one row per invoice, instead of guessing at it from a monthly Merchant Service Center summary.
Which customers cost us money to take payment from?
Card and ACH have very different fee profiles, and Apple Pay or PayPal route through their own surcharge bands. Net margin per customer drops the processing-fee load on top of the line items, so the sales lead can spot the customer who pays on a corporate card every month and is quietly eating the margin on a thin-spread product.
Where in the dispute pipeline are we losing?
Every chargeback is tracked from the customer's bank notice through to the final outcome. Win-rate, average time-to-resolution, the chargeback-fee total and the loss exposure are visible per reason code and per customer, so the billing clerk knows whether the bigger fix is in the invoice description, the refund policy or the cardholder dispute response.
Net cash per invoice and per customer after card, ACH and chargeback fees, alongside the deposit batch reconciliation. Month-end stops being a wrestling match between the bank feed, the QuickBooks invoice list and the Merchant Service Center.
Customer payment-method history visible at the deal: who pays card, who pays ACH, who has had a card-on-file fail this quarter. The next quote can route to ACH for the customer who keeps bouncing on an expired card.
GoPayment terminal volume by location, ACH retry queues and card-on-file expiries on one operations board. The team works the renewal of expiring cards before the recurring invoice fails, not after.
Each HubSpot contact and company carries the QuickBooks Payments history of charges, refunds, ACH bounces and open disputes. The account executive sees on the deal screen which customer paid by card last month, which one had a chargeback open and which one is still on an expiring card-on-file, before sending the renewal quote.
Salesforce accounts and opportunities carry the live charge, refund and dispute feed from QuickBooks Payments. The sales lead sees net realised revenue per account after refunds and chargebacks, and the customer-success team knows when a card-on-file is about to expire on a renewing contract.
Failed ACH attempts, opened chargebacks, expiring cards-on-file and unusually large authorisations land in the right Slack channel with the customer name, the amount and a deep link to the charge in the Merchant Service Center. The billing clerk and the controller act the same day, instead of finding it in next week's deposit summary.
Open chargebacks become cards on a monday.com board with the original invoice, the customer history and the evidence-deadline date. Failed ACH retries and expiring card-on-file profiles get their own swimlanes, so the billing team works one queue instead of jumping between QuickBooks, the Merchant Service Center and an inbox.
A failed ACH, a declined card-on-file or a card-expiring-soon flag triggers the matching Mailchimp journey, with the customer name, the open invoice and a one-click update-payment-method link. Marketing carries the dunning lift instead of finance writing one-off emails per failed charge.
For groups running QuickBooks Payments on a US entity and Exact Online on a Belgian or Dutch entity, the daily deposit batch and its per-charge fee detail are mirrored into the Exact ledger with the right matching customer and FX rate. Group consolidation sees one net-cash view across both bookkeeping engines, instead of a manual export from the Merchant Service Center each month.
You keep the reporting tool you already have. We connect it to the warehouse where your QuickBooks Payments data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
The QuickBooks connector pulls the accounting ledger: invoices, customers, vendors, items, the chart of accounts. The QuickBooks Payments connector pulls the merchant feed underneath it: per-charge card and ACH transactions, refunds, disputes, deposit batches and processing fees. Most groups want both: the invoice from one, the cents-of-fee detail behind it from the other, joined on invoice id in the warehouse.
Yes. The deposit batch lands in QuickBooks as a single net amount on the bank feed, but the warehouse holds the underlying charge, fee, refund and chargeback rows. The controller sees per-invoice net cash and a clean breakdown of what made up each daily deposit, without recomputing it by hand.
QuickBooks Desktop reached its end-of-sale milestone for new US subscribers in 2024 and the supported Desktop versions are on a published end-of-life ladder. For merchants still on a supported Desktop release with QuickBooks Payments active, the same merchant feed (charges, refunds, disputes, deposits) is available. Most new groups land on QuickBooks Online plus QuickBooks Payments, and the connector's modelling is identical on top.
We review your QuickBooks Payments setup and the systems around it. Together we pick the first thing worth building.