Skip to content
ABS BetweenPay, part of ASCEND ECO by Nelson & FieldsBetweenPay
Sign in
ABS BetweenPay, part of ASCEND ECO by Nelson & FieldsBetweenPayABS · Part of ASCEND ECO™ by Nelson & Fields

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.

Loading

Dependencies

Each entry declares its owner, purpose and the scope BetweenPay is allowed.

  • Identity & Authentication
    Pending shared core
    ASCEND 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 Person
    Pending shared core
    ASCEND ECO Global

    The single authoritative record of a person across ASCEND ECO.

    ABS scope: Read-only. Corrections are raised as governed requests.

  • People & Authority
    Global-governed
    ASCEND ECO Global

    Canonical identity governance, merges, transfers, org assignment.

    ABS scope: No ABS controls. Request-only pathway.

  • Entitlements
    Pending shared core
    ASCEND 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 core
    ASCEND ECO Shared Core

    Authoritative payment capture, reconciliation and provisioning.

    ABS scope: Display plans and initiate checkout intent only. No ABS payment authority.

  • Requests & Governed Decisions
    Pending shared core
    ASCEND ECO Shared Core

    Request → review → decision → provisioning → validation → audit.

    ABS scope: Create requests. Never self-approve protected access.

  • Notifications
    Pending shared core
    ASCEND ECO Shared Core

    Delivery, acknowledgment and retry for product notices.

    ABS scope: Publish ABS-classified notifications with privacy classification.

  • Audit & Evidence
    Pending shared core
    ASCEND ECO Shared Core

    Tamper-evident record of governed actions.

    ABS scope: Append-only writes. ABS cannot edit or delete evidence.

  • Product Switcher
    Pending shared core
    ASCEND ECO Shared Core

    Authorized product surface across the ecosystem.

    ABS scope: Render entitled products. The switcher never creates access.

  • Search Technology
    Pending shared core
    ASCEND ECO Shared Core

    Shared, permission-aware search infrastructure.

    ABS scope: ABS-private scope only. No cross-product traversal.

  • JOY Governance
    Pending shared core
    ASCEND ECO Shared Core

    Guardrails for assistant behaviour, disclosure and confirmation.

    ABS scope: Private JOY runs under ABS privacy scope with confirmation gates.

  • Human Support
    Pending shared core
    ASCEND ECO Shared Core

    Entitled human assistance and contextual handoff.

    ABS scope: Handoff with minimum necessary information.

  • Integrations
    Pending shared core
    ASCEND ECO Shared Core

    Governed external data connections and freshness.

    ABS scope: Consume connection state. Secrets stay server-side.

  • Environment Awareness & Maintenance State
    Pending shared core
    ASCEND ECO Global

    Environment isolation and maintenance windows.

    ABS scope: Read-only consumption. ABS owns no maintenance administration.

  • Connection & Health Status
    Pending shared core
    ASCEND 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.

Part of ASCEND ECO™ by Nelson & Fields. ABS financial information is private to you.