ASCEND ECO™ connection contracts
What BetweenPay consumes, and what's still pending.
BetweenPay uses shared ASCEND ECO services rather than building its own. Anything not yet connected is shown as pending — never as complete.
Dependencies
Each entry declares its owner, purpose and the scope BetweenPay is allowed.
- Identity & AuthenticationPending shared coreASCEND ECO Shared Core
Server-side session and authentication for every ASCEND ECO product.
ABS scope: Consume session claims only. ABS never mints or stores credentials.
- Canonical PersonPending shared coreASCEND ECO Global
The single authoritative record of a person across ASCEND ECO.
ABS scope: Read-only. Corrections are raised as governed requests.
- People & AuthorityGlobal-governedASCEND ECO Global
Canonical identity governance, merges, transfers, org assignment.
ABS scope: No ABS controls. Request-only pathway.
- EntitlementsPending shared coreASCEND ECO Shared Core
Authoritative record of what a person may access.
ABS scope: Read entitlement decisions server-side. Never grant locally.
- Commerce (Stripe → reconciliation → entitlement)Pending shared coreASCEND ECO Shared Core
Authoritative payment capture, reconciliation and provisioning.
ABS scope: Display plans and initiate checkout intent only. No ABS payment authority.
- Requests & Governed DecisionsPending shared coreASCEND ECO Shared Core
Request → review → decision → provisioning → validation → audit.
ABS scope: Create requests. Never self-approve protected access.
- NotificationsPending shared coreASCEND ECO Shared Core
Delivery, acknowledgment and retry for product notices.
ABS scope: Publish ABS-classified notifications with privacy classification.
- Audit & EvidencePending shared coreASCEND ECO Shared Core
Tamper-evident record of governed actions.
ABS scope: Append-only writes. ABS cannot edit or delete evidence.
- Product SwitcherPending shared coreASCEND ECO Shared Core
Authorized product surface across the ecosystem.
ABS scope: Render entitled products. The switcher never creates access.
- Search TechnologyPending shared coreASCEND ECO Shared Core
Shared, permission-aware search infrastructure.
ABS scope: ABS-private scope only. No cross-product traversal.
- JOY GovernancePending shared coreASCEND ECO Shared Core
Guardrails for assistant behaviour, disclosure and confirmation.
ABS scope: Private JOY runs under ABS privacy scope with confirmation gates.
- Human SupportPending shared coreASCEND ECO Shared Core
Entitled human assistance and contextual handoff.
ABS scope: Handoff with minimum necessary information.
- IntegrationsPending shared coreASCEND ECO Shared Core
Governed external data connections and freshness.
ABS scope: Consume connection state. Secrets stay server-side.
- Environment Awareness & Maintenance StatePending shared coreASCEND ECO Global
Environment isolation and maintenance windows.
ABS scope: Read-only consumption. ABS owns no maintenance administration.
- Connection & Health StatusPending shared coreASCEND ECO Shared Core
Service reachability and data freshness signals.
ABS scope: Display user-safe status. No internal operational detail.
Maintenance execution and scheduling belong to restricted ASCEND ECO Controlled Admin. BetweenPay only consumes maintenance state.