Add Store metrics (reserve, payout, NOF, etc) to API
No description
Streamline onboarding
Extend the branding available on hosted payment links beyond a per-store logo — full color theming and custom domain support, so the link reads as the merchant's own checkout rather than a generic SwipeAras page.
Not a new integration — a static reference page or document listing every integration Forge already supports (QuickBooks, NetSuite, Sage Intacct, etc.) plus ones in progress, so sales agents have something to check or point a prospect to before a call. Distinct from any single integration request; this is about discoverability of what already exists.
Sales agents and agency principals need to see their own book of merchants, margin, and commission/renewal projections across all processors — not just the merchants they happen to be viewing one at a time. Raised by 1PriceSwipes as they bring on more agents writing deals across multiple banks.
Payouts batch, so individual payments don't map one-to-one to bank deposits — an unnoticed chargeback or ACH return in a batch makes a merchant think they were shorted. Requested: a close-out report that maps individual payment IDs to their batch-out, netting chargebacks and returns, so merchants (especially on the QuickBooks integration) can reconcile without a support call.
1PriceSwipes' existing book runs on Square, Clover, and Valor/Suede outside Forge. Until Square transaction and reporting data appears in Forge, the "one platform across processors" promise doesn't cover their actual business. Requested as part of the broader multi-processor backbone unification (Adyen + Stripe today, Square next).
Top-level dashboard metrics are currently partly locked to a 14-day window. Agencies and merchants need to set their own start and end dates to answer questions like month-end close or a specific promo period, without switching to the transaction-level table to get a custom range.
Add risk metrics that roll up from the stores up (NOF, Chargebacks, etc)