Verifying Account Status for an ISV Payment Aggregator Architecture using Locations API

Questions
1

Hello everyone,

I am building a B2B payment platform called PayServ, functioning as an integrated software platform (ISV). We have recently completed our production merchant KYC verification process and successfully run our live live testing cycles.

Architecturally, we are deploying a Payment Aggregator / Merchant of Record (MoR) model. Instead of using third-party merchant OAuth handshakes, all transactional volume from our downstream sub-merchants will route directly through our central master production keys.

We plan to programmatically utilize the Locations API to partition distinct sub-merchant storefronts, dynamic credit card statement descriptors, and isolated reporting balances, while our backend infrastructure handles downstream payouts.

Since this is a centralized aggregation layout rather than a decentralized OAuth layout, we want to proactively ensure our production merchant account is correctly flagged or whitelisted for this specific platform aggregation use case so it doesn’t trigger automated fraud velocity rules.

Could a Square Developer Advocate point me in the right direction to ensure our merchant compliance profile is properly aligned with this architecture? (I can provide our Application ID privately via DM).

Thank you!

2

The architecture you’re describing is not a supported use case on the Square platform. Square’s platform model requires each merchant to have their own Square account with direct onboarding (via OAuth for platform integrations). This ensures each business undergoes proper identity verification and receives settlement directly.

Processing payments on behalf of others through your own credentials, is not permitted under our Developer Terms of Service and Acceptable Use Policy.

If you’re building a platform that connects multiple merchants to Square, the supported path is our OAuth-based platform integration, where each merchant authorizes your application and maintains their own Square account. You can learn more here: OAuth API