The image shows the architecture for monetizing data by setting up a payment framework on OCI. It comprises three elements: The on-premises location shares an ERP service and a CRM service with the OCI implementation.
The OCI location contains

A client application and a payment processor (for example, Stripe) reside on the internet.

The components are interconnected by numbered arrows that describe this dataflow:
  1. The customer authenticates with identity provider.
  2. The customer accesses the data product API through an API Gateway, which will later apply its own policies (for example, throttling) after authorizing the request.
  3. The API Gateway invokes a function to authorize the request.
  4. The function validates provided customer tokens with the identity provider.
  5. The function then checks the customer’s access rights to data product in the CRM or other system and also checks whether subscription or per-use payment applies. If a subscription applies, the function checks whether it is valid.
  6. The function records data product use for payment:
    1. Recording use in a ledger; and/or
    2. Executing an online payment through a payment provider.
  7. Once authorized and monetized, the API Gateway provides access to data product.