Platform Overview
MemberPay · All clients · 28 March 2026
Total AUC (All Clients)
—
Loading…
Active Clients
—
Loading…
Payments MTD
—
Loading…
Month-to-date
Flags & Alerts
—
Not yet wired
Review →
Platform Activity
View all →
Loading platform activity…
Client Breakdown
Total clients
—
With accounts
—
Onboarding queue
—
Restricted accounts
— (not yet wired)
Total accounts (Griffin)
—
Griffin API Health
API status
— Loading
Base URL
—
Org ID
—
Webhook delivery
— (not yet wired)
FPS rail
— (not yet wired)
All Clients
Loading…
| Client | Type | Griffin Account | KYC Status | Account Status | Balance | Pmts (MTD) | Last Activity | |
|---|---|---|---|---|---|---|---|---|
| Loading clients from Griffin… | ||||||||
—
Select a client
Click a row on All Clients to load live detail.
Available Balance
—
Payments MTD
—
Out
—
—
In
—
Member Accounts
—
Accounts & money
Operating Account
▾
Bank accounts
Select a client to load
Recent Transactions
GET /v0/bank/accounts/ba_.../transactions
▸
| Date | Account | Description | Reference | Type | Amount | Balance After |
|---|---|---|---|---|---|---|
| Select a client to load transactions. | ||||||
Configuration
Portal Features
GET /api/features/{lp_id}
▸
Which pages this client sees in the MemberPay partner portal. Locked items (e.g. Dashboard) are always on. Save writes through to the proxy; the partner portal reads on next page load.
Select a client to load features.
People & access
Governing Body & Senior Managers
▸
People responsible for this society — senior-manager-function-holders and governing-body-members. Each is a Griffin legal-person (individual) linked to this society via role-association claims.
Select a client to load officers.
GET /v0/legal-persons/{lp_id}/claims
Onboarding Queue
Loading…
Griffin Verify model. OnePay creates a legal person in Griffin and submits onboarding claims. Griffin's automated checks run in real time. A
decision-created webhook fires when a decision is made (accepted / declined / requires-attention).Loading onboarding queue…
All Payments
Loading…
| Time | Client | Recipient | Reference | Rail | Status | Amount | |
|---|---|---|---|---|---|---|---|
| Loading payments from Griffin… | |||||||
Flags & Alerts
Preview — not yet wired to a rules engine
Preview data. OnePay's flagging rules (large-payment thresholds, CoP mismatches, returned FPS, KYC requires-attention) need a rules engine in front of the Griffin webhook stream before this page can show live alerts.
Large single payment — Example Client A
High Priority
£85,000 FPS outbound submitted at 08:55 today. Exceeds this client's typical single-payment pattern (avg £12,400). Griffin payment pending submission.
ClientExample Client A
Amount£85,000
RecipientVarious (batch)
CoP resultMatch
Payment held — not yet submitted to Griffin FPS rail
Payment returned — Example Client B
Medium
FPS payment PAY-EX-0337 (£3,200) was returned by the recipient bank. Reason: account-closed. Funds credited back to the client's account. Client notification not yet confirmed.
event: payment-submission-updated · status: payment-returned · pmt_example
KYC requires-attention — Example Client C
Medium
Griffin returned decision: requires-attention. Manual review needed before the embedded account can be activated. Likely cause: director address history mismatch.
event: decision-created · outcome: requires-attention · lp_example
Griffin API
Platform integration status · api.griffin.com · v0
API Requests Today
2,847
Across all endpoints
Webhook Events (24h)
341
100% delivered
Concurrent Requests
12 / 50
Within Griffin limit
Endpoint Usage (Today)
| Endpoint | Calls | Errors |
|---|---|---|
| GET /v0/bank/accounts/{id}/transactions | 1,204 | 0 |
| GET /v0/bank/accounts/{id} | 892 | 0 |
| POST /v0/bank/accounts/{id}/payments | 147 | 0 |
| POST /v0/payments/{id}/submission | 144 | 3 |
| POST /v0/organizations/{id}/cop-request | 203 | 0 |
| POST /v0/organizations/{id}/legal-persons | 2 | 0 |
Webhook Events
payment-submission-updated
● Active
transaction-created
● Active
decision-created
● Active
Delivery rate (24h)
100%
Events delivered (24h)
341
API Keys
Live key
live_key_****8f2a
Sandbox key
sandbox_key_****3c1d
Environment
● Live
Platform Settings
OnePay · MemberPay configuration
Default Client Settings
Onepay Griffin Organisation
Organisation ref
— (from /health)
Griffin relationship
Controller
Client role
Account owner
Onboarding model
Verify
Max legal persons
Unlimited
FPS capability
● Enabled
GET /v0/organizations/{org-id}
API Key Management
Griffin organisation keys, client API keys, webhooks and access logs
Active Keys
23
2 Griffin · 21 client
0 expiring soon
API Calls Today
4,812
Across all clients
↑ 12% vs yesterday
Webhook Delivery
99.6%
Last 24 hours
3 retries queued
Last Key Rotation
12 days ago
Griffin live key · 16 Mar
View →
These are OnePay's organisation-level API keys for the Griffin Bank API. They are used server-side only and should never be exposed to clients. Rotate every 90 days minimum.
GK-LIVE-••••••••••••••••••••••••••••••••
Show key
Copy
Scopes
payments:write
accounts:write
accounts:read
legal-persons:read
legal-persons:write
webhooks:read
webhooks:write
org:admin
GK-SAND-••••••••••••••••••••••••••••••••
Show key
Copy
GK-LIVE-████████████████████████████████
Revoked 16 Mar 2026
21 active keys across 18 clients — issued for direct API integration with MemberPay
CA
MP-••••-••••-••••-••••-ClientA
Show key
Copy
Scopes
payments:read
payments:write
accounts:read
transactions:read
payees:read
payees:write
CB
MP-••••-••••-••••-••••-ClientB
Show key
Copy
payments:read
accounts:read
transactions:read
CC
This key expires in 4 days. Renew it now to avoid service disruption for Example Client C. An email reminder has been sent to their account admin.
CD
Preview — not wired to live key management
Griffin delivers webhook events to your platform endpoint first. MemberPay then fans them out to each client's configured endpoint. All deliveries are signed with HMAC-SHA256.
OnePay Platform Endpoint (Griffin → OnePay)
Healthy
https://api.onepay.co.uk/webhooks/griffin
Copy URL
99.6%
Delivery rate (24h)
1,847
Events received (24h)
3
Retries queued
142ms
Avg response time
Subscribed events
payment-submission-updated
transaction-created
decision-created
verification-updated
account-status-updated
Client Webhook Endpoints (OnePay → Clients)
CA
Example Client A
https://api.example-client-a.example/hooks/memberpay
100%
Delivery (24h)
312
Events sent
0
Failures
88ms
Avg response
payment-submission-updated
transaction-created
decision-created
CB
Example Client B
https://api.example-client-b.example/payments/webhook
94.1%
Delivery (24h)
187
Events sent
11
Failures
3,420ms
Avg response
11 failed deliveries in the last 24h. Retrying with exponential backoff (next attempt in 4 min). View retry queue →
CC
Example Client C
No endpoint configured
Method
Endpoint
Status
Client
Time
POST/v0/bank/accounts/{id}/payments201Example Client A10:47:32
GET/v0/bank/accounts/{id}/transactions200Example Client A10:47:28
POST/v0/payments/{id}/submission200Example Client A10:47:15
GET/v0/bank/accounts/{id}200Example Client B10:46:54
POST/v0/organizations/{id}/cop-request201Example Client B10:46:41
POST/v0/bank/accounts/{id}/payments422Example Client B10:46:38
GET/v0/legal-persons/{id}/decisions200Example Client C10:45:59
PATCH/v0/bank/accounts/{id}/restrictions200OnePay Internal10:44:12
GET/v0/bank/accounts/{id}/transactions200Example Client A10:43:07
POST/v0/legal-persons/{id}/verifications201OnePay Internal10:41:55
POST/v0/organizations/{id}/legal-persons201OnePay Internal10:31:02
GET/v0/bank/accounts/{id}401Unknown (revoked key)10:28:44
Showing 12 of 4,812 calls today