Onboarding API now supports multiple applications per organization
The Onboarding API can now create multiple applications under a single orgID, so an organization can be provisioned with more than one merchant account through the API — for example a separate account per program, season, division, or location.
This is not enabled by default. SportsPay configures it on the back end for the Registration Platform; there is no request parameter for it. Until it is enabled, an orgID that already exists in the SportsPay database will be rejected when creating a new application.
Before enabling
Where an organization holds more than one merchant account, SportsPay will push more than one termID and password for that orgID. Credentials are delivered one termID and password per callback — they are never batched.
Registration Platforms must confirm their Merchant Provisioning integration stores each new credential pair as a new record, keyed on termID. A system that keys stored credentials on orgID will silently overwrite the organization's existing terminal when the next one arrives.
orgIDis not unique per merchant accountThe Merchant Provisioning documentation previously stated that each merchant account provisioned through the API must have its own unique
orgID. That is no longer the case. Gateway credentials must be stored againsttermID.
New and updated response codes
| Code | Description |
|---|---|
1004 | OrgID already has a application or merchant account |
1009 | OrgID already has active application in progress |
1010 | Application cannot be modified |
1010 is returned when an application exists but can no longer be edited — it has been submitted, merged, or moved to a final state.
Only one application per orgID may be in progress at a time, even where multiple applications are enabled. 1009 is returned if a second is attempted.
See Onboarding and Merchant Provisioning.