# Broadgate Financial

Here's the onboarding plan I'm working to: **Onboarding Stages:** - Compliance & KYC: this week (days 1–5) - Sandbox provisioning: this week in parallel - Technical integration: weeks 2–3 - UAT: weeks 3–4 - Go-live target: end of April (day 30) James is keen to move quickly — his team has Q2 budget allocated and wants transactions flowing by May. Sam, are you good to kick off CDD today? Lena, how soon can you get sandbox access sorted?

I'll get sandbox access set up tomorrow. Do we have their technical contact details yet? Need a name and email to send API credentials to.

Yes — their integration lead is Priya Mehta, senior engineer on their payments team. She's apparently very hands-on and already familiar with REST payment APIs. I'll DM you her contact details.

CDD checklist sent to James's team. Standard UK corporate pack: company registration, beneficial ownership register, director IDs, source of funds declaration. Should be straightforward for a firm of their size.

Also adding this channel to the onboarding tracker. James has a call with his board at the end of this week so CDD sign-off before Thursday would be ideal if possible.

CDD documents received from Broadgate — they came back quickly, less than 24 hours. Company docs, full beneficial ownership structure, director IDs — everything we asked for. They were well-prepared. Starting Onfido verification now.

That's a fast turnaround on the docs — good sign on the client. Thanks Sam.

Sandbox environment is being provisioned. Should be ready end of day tomorrow.

Heads up — Onfido verification for Broadgate is queued. We're hitting rate limits. 15 verification requests are sitting in the queue. Not urgent yet but flagging early.

All 15 queued verifications processed. Onfido rate limit cleared at 12:10, batch ran through cleanly. Broadgate KYC is clean — no flags on any of the directors or beneficial owners. Sam, over to you for formal sign-off.

Compliance sign-off confirmed. KYC passed, sanctions screening clean across all entities. Broadgate Financial is cleared to proceed.

Sandbox provisioned. API credentials generated and sent to their engineer via secure link. Integration docs shared — Payments API reference, FPS/BACS/CHAPS flow guides, webhook setup. They should be able to start testing early next week.

Brilliant start this week. Small blip with Onfido yesterday but handled well and resolved same day. KYC complete, sandbox ready. We're ahead of schedule going into week 2. Nice work Sam and Lena.

Morning — Broadgate's engineer apparently started sandbox testing over the weekend. James mentioned she came in Saturday to get a head start. Any early signals from our side?

Yes, I can see their test traffic in the sandbox logs. They've got basic FPS payments working already — integration looks clean. Seeing a handful of 400 errors on BACS batch submissions though. Looking into whether it's their payload or something on our end.

Found the issue — our batch endpoint has a bug with deduplication key generation when the `external_reference` field is null. Broadgate's scheduled payment system doesn't always populate that field for certain payment types. @tom-brennan this is in the batch processing service. The dedup logic assumes `external_ref` is always present and fails ungracefully when it isn't. Can you take a look?

yeah looking at it now. you're right — dedup logic doesn't handle null `external_ref`. it should fall back to our internal transaction ID. easy fix, give me a couple hours

fix deployed to sandbox. lena can you ask their team to re-run the batch test?

Confirmed — batch submissions processing cleanly now. Ran a 50-payment test batch, all good. Nice one Tom.

np 👍

Their test traffic is looking healthy today. They're now testing edge cases — large batch sizes, duplicate submission detection, error handling on malformed payloads. Their engineer clearly knows what she's doing.

Quick update — I had a call with James this morning to check in on integration progress. He's pleased with how quickly they've got FPS working. His engineer Priya Mehta mentioned the API docs are well-structured. James's words: 'your team is responsive.' Good sign.

I've shared the CHAPS test guide with their engineer — she hadn't started CHAPS testing yet. Wanted to make sure she has everything she needs before the security brief call this week.

James has come back with a question ahead of his next board meeting — he wants a security overview to share with his board before committing to full go-live. Specifically: data encryption at rest and in transit, recent pen test, FCA authorisation status. Can someone help me put together a brief one-pager?

Security brief sent to James. His feedback: 'thorough and professional' — his exact words. His board is satisfied. Well done Lena and Sam.

Their engineer is now running full end-to-end payment flows in sandbox. I've been watching the test traffic over the past couple of days — volume and patterns are sensible, error rate from their side is very low. They're testing edge cases too. Their engineer knows what she's doing — clean API usage, good error handling on their side.

FYI — I've documented the Onfido rate limiting action items from last week in the compliance tracker. We need to negotiate higher rate limits with Onfido and implement proper request queuing with retry logic on our side. Both still pending. I'll follow up with engineering to make sure they don't drop off the list.

Morning — catching up after the weekend. Sandbox traffic shows they ran tests on Saturday morning too. Their engineer has really been pushing through the test scenarios. CHAPS is looking solid.

Broadgate sandbox testing summary as of this morning: ✅ FPS: all test scenarios passing ✅ BACS batch: clean after Tom's fix ✅ CHAPS: tested successfully including high-value payment scenarios ✅ Webhook delivery: confirmed, they've integrated the status callbacks correctly We're in good shape to move to UAT planning. Worth getting a call in with James and his team this week, Alex?

This is really solid. I'll get a UAT planning call booked with James and his team. Can we do a quick prep chat beforehand Lena — just to align on scope?

UAT test matrix drafted — 47 scenarios across FPS, BACS, CHAPS, webhooks, error handling, and idempotency. Covers the edge cases their engineer has already been probing in sandbox. Sharing with Alex now.

Had the UAT planning call with James and his team this morning — went well. Their engineer has her own internal test matrix that lines up nicely with Lena's. One thing James raised though: Broadgate has two European subsidiaries in Germany and Netherlands, and he's asking whether they'd be able to route EUR payments through us eventually. Can someone give me a clear picture of where we stand on SEPA before I respond?

Spoke to James — he's fine with SEPA being a future conversation. Happy to proceed with GBP rails for now and revisit EUR in H2 once we have something concrete. No drama.

One thing worth confirming for the record — Broadgate's legal team have signed the data processing agreement. That's the last contractual item outstanding from the compliance side. We're clean.

UAT officially underway. Broadgate's engineer has started running through the test matrix — she has a detailed internal checklist on top of ours. James is keeping a close eye on progress.

Quick heads up — I'm being pulled onto a Vertex API issue for a day or two. There are response time problems that need diagnosing. I've got Broadgate's UAT test scripts fully documented so their team can run scenarios independently. I'll be back on this by Monday.

While it's quiet — I've flagged the Onfido action items to the engineering backlog: higher rate limits negotiation with Onfido, and request queuing with retry logic. Both pending. Nothing blocking Broadgate but worth it being tracked.

Broadgate's team have been running UAT independently while Lena was away. James mentioned they got through about 60% of the test matrix. Good progress.

I'm back from the Vertex thing. Monitoring Broadgate's UAT traffic — looking clean so far. They made good progress while I was away.

Good UAT progress today — they've completed all FPS scenarios and most of the BACS matrix. Zero failures so far.

One thing their engineer flagged — our webhook retry logic on failed deliveries isn't documented anywhere in the integration guide. She's asking how many retries we do and what the backoff schedule is. Valid gap. I'll update the docs today.

Their engineer replied to the webhook doc update — she said 'exactly what I needed, thank you.' Nice when clients are easy to work with.

Alex tagged me in about settlement setup. What's the configuration for Broadgate — standard next-day?

Updated the webhook docs — 3 attempts with exponential backoff (1 min, 5 min, 30 min), then dead-letter queue with manual review alert. Also added a section on idempotency key handling for retry-safe payment submission — their engineer had a follow-up question about that too.

UAT is going well — Broadgate's team found an edge case: a CHAPS payment with a future-dated value date returns a 500 instead of a proper validation error. Lena, is that on our side?

Fix deployed to sandbox. Future-dated CHAPS payments now return a clean 422 with a clear message. Their engineer confirmed it's working correctly.

Settlement profile configured. Broadgate on next-day cycle, end-of-day reporting by 08:00. Tested the reconciliation flow with dummy data — clean match.

Production credentials generated and sent to their engineer via secure channel. Also setting up monitoring dashboards today — alerts for error rate above 1%, p99 latency spikes, and settlement exceptions. Will have everything live by end of day.

Broadgate UAT is wrapping up. Their engineer ran through all 47 scenarios — only two findings both of which are now fixed. UAT sign-off from James expected this week.

Tom — just a heads up, you might get a question from Broadgate's engineer about the batch dedup fix you deployed a couple of weeks ago. She's asking whether there's a corresponding fix in the production environment. Can you confirm it's there?

Monitoring dashboards are live. Alerts configured and tested: error rate >1%, p99 latency >400ms, settlement exceptions, failed webhook deliveries. I'll watch closely for the first few days in production.

Settlement profile double-checked in production. Broadgate confirmed for next-day settlement, reporting by 08:00. Reconciliation flow tested with dummy data — matched cleanly.

Quick compliance note — Broadgate's transaction monitoring profile is configured in ComplyAdvantage. Standard screening thresholds for a UK corporate at their projected volume. Worth noting: if they ramp above £20M/month we'd need to review the thresholds upward. I'll flag that at their first QBR.

James signed off on UAT this morning. One more thing before he confirms go-live — he wants to understand the incident response process for customers. Specifically: how would Broadgate hear about service disruptions? His board flagged this as a due diligence requirement.

I've sent James the clause from the Tier 2 service schedule on incident notification — 4-hour SLA for SEV1/SEV2. He came back quickly saying that's acceptable.

Monitoring dashboards are fully configured. Also ran a production readiness check — all payment rails active, API responding, settlement profile live. We're good to go for Monday.

James has formally signed off. We're confirmed for go-live on Monday May 5. Sending the formal go-live confirmation email to him today. I want to say — this has been one of the smoothest onboardings I've been part of. Real credit to everyone in this channel. Well done.

Production environment fully ready. Credentials active, monitoring live, settlement profile confirmed. Good to go Monday morning.

It's go-live day for Broadgate Financial! Production environment is ready, credentials are active, monitoring is on. Let's have a clean first day.

And we're live! First real transaction through Acme for Broadgate Financial. Great work everyone.

They've been running steadily through the morning. Mix of FPS and a couple of BACS. Monitoring is quiet — all green.

End of day 1: 14 transactions processed — mix of FPS and BACS. All successful. Latency well within SLA, error rate zero. Monitoring shows no anomalies. Good start.

Minor thing to flag — Broadgate's batch BACS submission this morning had 3 payments rejected by Modulr for invalid sort codes. Not a bug on our side — the sort codes are genuinely invalid (closed branches in their data). I've let their engineer know and she's looking into it.

heard broadgate went live monday — nice one. anything on the batch processing side to watch?

Update from James — he's happy with how the first two days have gone. Explained the rejected sort codes as a data quality issue on their side, he was fine with it. His team is already correcting the reference data. He also asked about uptime over the past 24 hours — pointed him to the monitoring dashboard.

First settlement file generated for Broadgate: 23 transactions, net £184k. Reconciliation matched cleanly, no exceptions.

Clean settlement on day 2. Brilliant.

Broadgate volume picking up — they processed £1.2M yesterday. Payment mix is roughly 60% FPS, 35% BACS, 5% CHAPS. All within expected patterns.

Second settlement file processed. 31 transactions, net £287k. Reconciliation clean again.

ComplyAdvantage handling the volume cleanly — no false positives so far, all transactions screening without issue. Good to have the calibration right from the start.

End of week 1 in production: 💰 £4.3M processed ✅ Zero failed transactions (excluding the sort code data issue on their side) ✅ Settlement reconciling cleanly every day ✅ Error rate: 0.02% ✅ Monitoring: all green James is very pleased. I'm scheduling their 30-day health check for early June.

Morning all — Broadgate volume update. They're at £6.8M total through the first 8 production days. James says they're shifting more of their payment flows over to us this week. Should track toward their projected £15M/month run rate by end of May.

Good to see the ramp. Monitoring is healthy — error rate 0.02%, p99 latency at 180ms. Well inside SLA. Nothing to flag.

Settlement running cleanly into the second week. No exceptions, reconciliation matching every day. Broadgate's finance team are organised — no queries on the reporting.

Broadgate's finance team is asking about settlement reporting format — they want a CSV export as well as the standard PDF statement. Is that something we do for Tier 2?

Mid-week monitoring check for Broadgate: volume continuing to ramp, latency stable at around 175-185ms p99, error rate unchanged at 0.02%. Settlement exceptions: zero. Everything is nominal.

Heads up — I'm being pulled onto the PayBridge EU reconciliation issue for a couple of days. There's a EUR rounding discrepancy that needs investigating. Broadgate is stable so it shouldn't cause any issues here, but flagging in case anything comes up.

CSV settlement export configured for Broadgate. Their finance team will get both PDF and CSV from the next settlement run. Let me know if the format looks right when it comes through.

James is asking about setting up a regular business review cadence. He's thinking quarterly but wants to know what's typical. I'm proposing monthly for the first quarter while they're ramping, then shift to quarterly once at steady state. Does that align with what we do for other accounts?

FYI — Broadgate's transaction monitoring flagged a handful of payments for enhanced screening over the past couple of days. All cleared automatically, nothing concerning. But the volume is now slightly above the threshold I calibrated at onboarding. Adjusting the monitoring profile to reflect real throughput — better to tune it now than have false positives cause friction.

Back from PayBridge — Broadgate monitoring all green while I was away. No issues.

James's team confirmed the new CSV report format looks exactly right. They've already integrated it into their internal reconciliation workflow. Happy client.

James sent a note this morning — he said his team are happy with the onboarding experience and wants to make sure he has a named contact if his engineer has technical questions going forward. I've said Lena is the technical lead and he can always reach me for anything account-related.

End of second production week — error rate held at 0.02% all week, no incidents, no escalations. Monitoring is quiet. This is what a clean integration looks like.

Morning all — Broadgate weekly update. They processed £11.2M in their first two full weeks of production. Volume is tracking to hit £14–15M this month, right on their original projection. James is happy, his team is happy, settlement is clean every day. This is a good one.

Monitoring is showing the volume ramp clearly in the dashboards. p99 latency holding steady at 182ms even with the increased load. No headroom concerns at current trajectory.

Transaction monitoring recalibration is holding well with the new volume. All payments screening cleanly. No enhanced review flags this week.