Full API reference, system architecture, and integration guides for the Olympus Pay neobank platform.
External providers used by Olympus Pay edge functions
Download the Olympus Pay Core collection and Environment from the cards above. In Postman: File → Import and select both files. Set the Olympus Pay environment as active.
Run 01 · Auth → Login. The test script auto-saves USER_ACCESS_TOKEN and USER_ID to the environment. All subsequent requests inherit the Bearer token from the collection level.
POST https://hzxxenidupmnrpatbniq.supabase.co/auth/v1/token?grant_type=password
apikey: <SUPABASE_ANON_KEY>
{ "email": "you@example.com", "password": "your-password" }
{ "access_token": "eyJ...", "refresh_token": "...", "user": { "id": "uuid" } }
Every request needs both Authorization and apikey. The Postman collection handles this at the collection level automatically.
Authorization: Bearer <USER_ACCESS_TOKEN> apikey: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
Payments, cards, and bulk transfers all require KYC approval. Start a session, redirect the user to the returned URL, then poll for the decision.
POST /functions/v1/didit-session
{ "entity_type": "individual", "country": "BW" }
→ { "session_id": "did_sess_...", "session_url": "https://..." }
POST /functions/v1/didit-decision
{ "session_id": "did_sess_..." }
→ { "status": "success", "liveness_score": 0.98 }
Auth → https://hzxxenidupmnrpatbniq.supabase.co/auth/v1/ Database → https://hzxxenidupmnrpatbniq.supabase.co/rest/v1/ Functions → https://hzxxenidupmnrpatbniq.supabase.co/functions/v1/