The image shows the architecture for monetizing data by setting up a payment framework on OCI. It comprises three elements:

• An on-premises location
• An OCI implementation
• The internet

The on-premises location shares an ERP service and a CRM service with the OCI implementation.

The OCI location contains

• instances of the data products autonomouse data warehouse and Oracle Machine Learning
• Two instances of Oracle Functions
• An API gateway
• An instance of Oracle's Identity and Access Management service.

The components are interconnected by numbered arrows that describe this dataflow:

1. The customer authenticates with identity provider.
2. The customer access data product API through API Gateway, which will later apply its own policies (eg. throttling) after authorising the request.
3. The API Gateway invokes a function to authorise request.
4. The function validates provided customer tokens with identity provider
5. The function checks customer’s access rights to data product in CRM or other system, and also checks whether subscription or per-use payment applies. If a subscription applies, the functions checks whether that subscription is valid.
6. Once authorised, the API Gateway forwards the request to a proxy function.
7. On a per-request basis, the proxy function charges for the access to the data product. Note that this charging can also be done after a successful access to the data product, avoiding the situation that customers are charged if the access fails. Charging is done by either:
   1. Recording use in a ledger; and/or
   2. Executing an online payment through a payment provider.
8. The proxy function accesses the monetized data on behalf of the customer.