Read the docs Request API access →
Platform

Environments & release rings

Credicorp runs a three-ring release pipeline for the public-facing estate (the marketing and content sites) — ww2 (staging) → beta (QA-gated pre-prod) → production. This page explains what each ring is for and, critically, which of them you may safely integrate against.

The API you build on — partner/v1 and the read-only public/v1 ring — has its own, separate live and sandbox environments documented on the API reference overview. The rings below are about how content and site changes are staged and promoted to the live estate; they are not additional API base URLs.

Only Production is for real integrations. ww2 and beta are pre-release mirrors: they exist so new public content can be designed and reviewed before it goes live. They may be unstable, may show unfinished work, and can change or break without notice. Do not point production traffic, monitors, or API clients at them, and do not link to them from indexed pages — they are noindexed.

The pipeline

Changes to the public estate flow strictly left-to-right. Nothing reaches production without passing through the review gate.

pipeline
  design / draft        QA + review gate        stable, indexed
  ┌──────────────┐      ┌──────────────┐      ┌──────────────┐
  │     ww2      │ ───▶ │     beta     │ ───▶ │  PRODUCTION  │
  │  (staging)   │      │ (pre-prod)   │      │   (live)     │
  └──────────────┘      └──────────────┘      └──────────────┘
   blue/green build      reviewed gate         credicorp.co.uk
   may change anytime     may still change      + the live estate

The three rings

RingHostStatusPurposeSafe to integrate?
Production credicorp.co.uk, hub.credicorp.co.uk, api.credicorp.co.uk stable The live, indexed estate and the regulated platform. Everything real happens here. Yes
beta beta.credicorp.co.uk pre-release QA / pre-production mirror. Content promoted from ww2 lands here and is reviewed before it is allowed through to production. Still subject to change. No
ww2 ww2.credicorp.co.uk pre-release Staging mirror, blue/green. Where new public content is designed and first assembled. The most volatile ring — expect unfinished work. No

ww2 — staging

ww2.credicorp.co.uk is the staging mirror of the public estate, run blue/green so a new build can be assembled and swapped in without disturbing the live site. It is where new pages, layouts and copy are first designed. Because it is a working surface, its content is unstable and may change or disappear at any moment. It is noindexed and excluded from search.

beta — QA / pre-production

beta.credicorp.co.uk is the pre-production gate. Content that has settled on ww2 is promoted here and put through a QA review before it is cleared to production. It is closer to final than ww2, but it is still pre-release: it can hold changes that are never shipped, or that ship differently. It is also noindexed.

Production — live

Production is the stable, indexed estate: the marketing site at credicorp.co.uk, the platform at hub.credicorp.co.uk, and the API at api.credicorp.co.uk. This is the only ring you should build against, link to publicly, or monitor.

Pre-release notice. ww2 and beta are provided for previewing upcoming public content only. They are not for production integration, carry no availability or stability guarantee, may break or change without notice, and are noindexed so they never compete with the live estate in search. Links to them here carry rel="nofollow" and these hosts are deliberately excluded from this site’s sitemap.

Platform status

Live platform health is published, unauthenticated, as an ops probe on the hub. Use it to confirm the production platform is up before cutting over or debugging an integration.

Platform (hub)
hub.credicorp.co.uk
Health probe
GET https://hub.credicorp.co.uk/public/v1/healthz
Status page
Developer status

The probe returns a small JSON document reporting database, migration and queue health. A representative shape (captured live):

json
{
  "status": "ok",
  "app": "hub",
  "db": { "up": true, "latencyMs": 1 },
  "migrations": { "applied": 208, "onDisk": 208, "inSync": true },
  "queue": { "reachable": true, "pending": 0 },
  "time": "2026-07-03T13:06:50Z"
}

See the Public API — health probe for field meanings.

Where to go next