Link payments to account work
Connect
SPIRITT
HitPayHitPay
Payment data drives the next move
Build HitPay payment, balance, recurring-billing, and commerce views with accountable follow-up. Bring charges, payment requests, and currency-specific balances into a working merchant console.
What you can do with HitPay.
Money states made visible
Bring charges, payment requests, and currency-specific balances into a working merchant console.
Customer follow-through
Connect observed invoice and recurring-billing states to CRM and support work without changing payment records.
Commerce in context
Use products, categories, locations, and orders to coordinate the operations around your store.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace to build a merchant payment console. Bring the operating rules and source records you want it to use.
02
Connect HitPay
Connect your HitPay account with access to the records and actions your mission needs. Connect the companion apps you want involved in the handoff.
03
Delegate an outcome
Start with: Build a merchant payment console. Define the account scope, approval rules, and destination for the result. SPIRITT runs the work and verifies the outcome.
Hand over a mission.
Choose a mission. Make it yours.
Put HitPay to work.
Payment data drives the next move
Questions
HitPay, with SPIRITT.
01Can it build a merchant payment view?+
Bring charges, payment requests, and currency-specific balances into a working merchant console. Preserve currency and source IDs in Supabase, follow supported charge pagination, and show the retrieval window so merchant teams can act on actual payment states.
02Can payment data drive customer follow-up?+
Connect observed invoice and recurring-billing states to CRM and support work without changing payment records. Update the authorized HubSpot handoff field, create a Zendesk case for unresolved payment issues, and keep request status distinct from assumed fulfillment.
03Can it support store operations?+
Use products, categories, locations, and orders to coordinate the operations around your store. Build a searchable internal directory and create Asana tasks for missing owner assignments.
04What do I connect to get started with HitPay?+
Connect your HitPay account, identify the records or project scope for the mission, and provide the operating rules. For build a merchant payment console, start with the source inputs described in that mission and authorize the companion apps used for its handoffs.
05Can it charge customers, refund payments, or retrieve unlimited history?+
This connection reads HitPay data; it does not create payments or refunds. Charges and locations support continuation, while customer, invoice, and order lists return a single available page without verified continuation. SPIRITT keeps those coverage limits explicit in operational reports.
06Can pending balances be counted as available cash?+
No. HitPay returns separate available, pending, deposit, and reserve balances by currency and wallet provider. SPIRITT preserves those distinctions in the merchant view and avoids combining different currencies without a supplied conversion policy.