MSA ADDENDUM
Additional Terms for OCI Enterprise Deployments & ISO 20022 Engine Deployments.
1. Scope of Agreement & OCI Enclave Governance
1.1 Incorporation by Reference. This Addendum is incorporated directly into the Master Services Agreement ("MSA") between Provider and Subscriber. It governs all transactions executed via OCI confidential enclaves for ISO 20022 deterministic engine processing.
1.2 Precedence. In the event of any conflict between the terms of the main MSA, Subscriber’s standard procurement guidelines, and this Addendum, the terms of this Addendum shall strictly control regarding OCI enclave billing and infrastructure provisioning.
1.3 Oracle Cloud Infrastructure Terms. Both Parties acknowledge that hardware, attestation, and regional isolation are delivered on Oracle Cloud Infrastructure confidential VMs (AMD SEV-SNP), subject to Oracle’s underlying cloud terms of service.
2. Financial Architecture & Toll Allocation
2.1 Toll Card Entitlement and Allocation Blocks. Subscriber explicitly acknowledges that the engines selected under the toll card (SHIELD, CLEANSE, TRANSLATE, HARMONIZE) constitute a pre-paid allocation of deterministic message-processing capacity.
2.2 Deduction Mechanics. Per-message tolls are metered deterministically at the point of engine invocation and billed via Stripe enterprise rails. No fee is assessed on messages rejected before processing. There are zero fixed monthly minimums.
2.3 No-Rollover and Capacity Forfeiture.
- All message-processing capacity and engine throughput are provisioned on a strict cyclical basis (monthly or annually, as defined by the executed agreement).
- Any unutilized processing capacity or compute hours at the end of a billing cycle shall not roll over to subsequent periods and shall be permanently forfeited.
- Subscriber acknowledges that no refunds, offsets, or contract modifications will be issued for unspent capacity, as the full commitment value is consumed to reserve hardware-isolated infrastructure blocks.
3. Metered Billing Reconciliation
3.1 Base Tolls via Stripe. The foundational per-message tolls are processed against Subscriber’s Stripe enterprise ledger.
3.2 Variable Compute Overages. Dynamic infrastructure overages resulting from high-volume message processing are calculated programmatically by Provider’s deterministic engines and metered through the Stripe Metered Ledger.
3.3 Stripe Contingency & Safety Valve Ledger.
- In the event that Subscriber’s committed balance is exhausted, temporarily locked, or contractually capped mid-billing cycle, all variable fees or excess infrastructure usage shall automatically fail over to the secondary Stripe Metered Ledger.
- Subscriber hereby authorizes Provider to automatically calculate, ledger, and draft any such outstanding platform fees directly via Corporate ACH or pre-authorized corporate credit card managed within the Stripe infrastructure.
4. Institutional Enclave Provisioning & Multi-Region SLA
4.1 Dedicated Hardware Isolation. For enterprise deployments, Provider agrees to provision AMD SEV-SNP confidential VMs on Oracle Cloud Infrastructure, with Intel TDX attestation available via the Phala enclave layer.
4.2 Multi-Region Geographically Split Load. To prevent operational downtime, API throttling, or regional datacenter failures, Provider shall deploy a geographically split, shard-based infrastructure across a minimum of three (3) independent OCI regions (Americas, Europe, Asia-Pacific).
4.3 Traffic Redundancy & Core System Immunity.
- Provider’s routing layer will dynamically distribute incoming API traffic to bypass localized memory constraints and hardware limitations.
- In the event of a total systemic outage of a specific OCI geographic region, traffic will automatically fail over to active parallel nodes.
- Subscriber agrees that temporary throttling or regional degradation caused directly by Oracle’s core cloud fabric shall not constitute a breach of the Provider’s Service Level Agreement (SLA), provided the multi-region failover configuration remains operational.
5. Data Security, Stateless Audits & Compliance
5.1 Stateless Processing Architecture. The platform operates on a stateless processing framework within hardware-isolated OCI confidential enclaves. Provider covenants that no message payload content is permanently stored or cached within non-volatile storage media post-processing.
5.2 Compliance Anchors. Provider warrants continuous alignment with FedRAMP High control surface parameters and Oracle SOC 2 Type II / ISO 27001 validation protocols, inherited at the hardware layer of Oracle Cloud Infrastructure.
5.3 Stateless Audit Verification. Subscriber retains the right to initiate programmatic, non-disruptive, live Stateless Audits of the active OCI enclaves to verify cryptographic isolation and compliance parameters, subject to forty-eight (48) hours electronic notice passed via API webhook.
Execution Addendum
This document is electronically linked to the executed MSA/BAA and enclave attestation record.