BANK INTEGRATION · API v1.0

FLEXCUBE integration
for credit evaluation

An evaluation API for bank IT heads, administrators and integrators. Explore the contract with synthetic records, then configure approved REST services for your FLEXCUBE sandbox.

Evaluation service: synthetic data only. No live bank connection, core transaction changes, credit decisions or disbursements. FLEXCUBE product, release and enabled services must be confirmed with your bank.

Download OpenAPI 3.0 Administrator guide Download connector & tests

How the connection works

Credit officerAuthorized customer and branch scope

Regence AIEvidence-backed assistance; human approval

Controlled adapterAuthentication, mappings and scope validation

Bank gateway + FLEXCUBEApproved inquiry services; system of record

Production target: bank-approved private connectivity and hosting boundary. Policy RAG remains separate from authoritative account balances. This public demo does not represent in-country production hosting.

Open the agent evaluation workspace ↗ to execute these synthetic inquiries as agent tools, inspect calculations and record a review disposition.

API endpoints

Evaluation base URL: https://regenceai.com/integration-api

Method	Path	Capability
GET	`/v1/customers/{customerId}/credit-context`	Customer credit context
GET	`/v1/customers/{customerId}/accounts`	Customer accounts
GET	`/v1/customers/{customerId}/loans`	Existing customer loans
GET	`/v1/loans/{loanId}/repayment-schedule`	Loan repayment schedule
GET	`/v1/loans/{loanId}/security`	Loan security

These are Regence API paths, not native Oracle operation names. Every inquiry needs a scoped bearer token, X-Bank-Branch and X-Bank-Entity.

Synthetic inquiry example

Evaluation tokens are issued by the administrator. Credentials are never embedded in this documentation. Demo identifiers: DEMO-C001 (customer), DEMO-L001 (loan), branch 001, entity DEMO.

curl https://regenceai.com/integration-api/v1/customers/DEMO-C001/loans \
  -H "Authorization: Bearer $POC_TOKEN" \
  -H 'X-Bank-Branch: 001' \
  -H 'X-Bank-Entity: DEMO'

Example response, abbreviated:

{
  "data": [{
    "loanId": "DEMO-L001",
    "customerId": "DEMO-C001",
    "currency": "NGN",
    "principalOutstanding": "45000000.00",
    "status": "ACTIVE"
  }],
  "meta": {
    "mode": "mock",
    "synthetic": true,
    "source": {"system": "SYNTHETIC_FIXTURES", "completeness": "fixture-only"}
  }
}

The complete response also includes request ID, retrieval time, branch and entity. Amounts are decimal strings. A customer profile is not a complete exposure calculation.

For the bank administrator

Confirm FLEXCUBE product, release, patchset and enabled modules.
Provide approved sandbox paths, response schemas and gateway authentication requirements.
Issue a read-only service identity and restrict pilot customers, loans, branches and entities.
Confirm network routing, bank CA certificates and any mTLS requirements.
Validate data accuracy, authorization isolation and operational behavior.

For the integrator

Import the OpenAPI document into Postman or your API tooling.
Run the supplied connector in mock mode and execute the tests.
Map approved bank REST paths and fields in a version-specific profile.
Verify ownership and completeness against bank reference records.
Agree pilot acceptance criteria before enabling bank access.

Expected responses

400 missing bank context · 401 invalid token · 403 scope denied · 404 record not found · 429 rate limit · 501 operation not mapped · 502 upstream/schema error · 503 bank unavailable.

Writes return 405. The POC allows 60 inquiries/minute/client, uses a 10-second upstream timeout and marks synthetic results explicitly. No automatic core write-back, SOAP adapter, OAuth renewal or live inference is included.

Oracle references

FLEXCUBE Universal Banking web services library ↗
Oracle REST API Services User Guide ↗

Bank-deployed documentation governs the final mapping. This evaluation connector is not Oracle-certified.

FLEXCUBE integrationfor credit evaluation