Follow-up from today's demo: next steps for Brenneck Pay
Email thread Brenneck Pay: documents · sales
After the demo, Matteo Ricci confirmed requirements and a decision by 20 Jan 2026. Jonas Albrecht replied that the brain needs a least-privilege role, EU-only storage in writing and review of schema names, and that he will grant nothing by email.
What was said
What this says
Current to 11 Oct 26After the demo, Matteo Ricci confirmed requirements and a decision by 20 Jan 2026. Jonas Albrecht replied that the brain needs a least-privilege role, EU-only storage in writing and review of schema names, and that he will grant nothing by email.
Ask: Matteo summarised four needs: one merchant view, EU region, Snowflake-resident, and auditable sources. He asked what the regulator needs to see before go-live.
Customer view: Jonas called the summary accurate, then set conditions. He wants a dedicated least-privilege role, a written statement that indexed copies and embeddings stay in the same EU account, and a review of schema names before deployment.
Next: Hannah Lowe owes Jonas an architecture note listing grants object by object. Jonas named the payments platform exports and the merchant CRM as first sources, with support tickets later.
The thread
Updated 9 Oct 26Messages
Matteo Ricci 4 Nov 2025 13:39Dear Katrin, Jonas, Aylin, Thank you for your time this morning. I would rather start with the timeline, so we all hold the same picture: you told me you would like a decision by 20 Jan 2026, and everything below is arranged to make that realistic without anyone rushing a security or regulatory step. What I took from the session, let me confirm that in writing: - Merchant account managers and merchant risk should work from one view of each merchant, rather than reconciling two sets of notes by hand. - The data must stay in an EU region, and the brain must run inside your own Snowflake account. - Jonas wants to see exactly which roles the brain needs, and what it writes into the account. - Katrin needs evidence she can show an auditor, with a source for every answer. What I would suggest next: Hannah, copied here, will send Jonas a short architecture note on how the brain sits in your Snowflake account, which objects it creates and which role it uses. If Jonas can tell us which source systems you would connect first, she can be specific rather than general. One question for all of you: what does your regulator need to see from us before a go-live? I would rather we knew now than discovered it in January. Best regards, Matteo Matteo Ricci Account Executive, BB-Demo
Jonas Albrecht 5 Nov 2025 15:04Matteo, Thanks for the summary. It is accurate. A few points from my side, so Hannah can answer them in the note: - Which role has access? I want the brain to run under a dedicated role with least privilege, not under anything that can see the whole account. Please list the grants it needs, object by object. - Where do the indexed copies and embeddings live? Same account, same EU region, no exceptions. I need that stated in writing. - Any schema it creates is a schema change on our side. I will want to review the names before anything is deployed, and nothing goes into production on a Friday. - First sources: the payments platform exports and the merchant CRM. Support tickets could come later. I will not grant anything by email. Once we are agreed on the design, we do it through our normal change process. I checked our load history for the merchant tables and the nightly loads are stable, so I do not expect surprises there. Jonas