Brenneck Pay / BB-Demo – Kickoff
Callcompleted
Brenneck Pay: documents · 2026-02-09 08:30
Kickoff for Brenneck Pay's Growth implementation. Goal is one page per merchant with sourced answers. EU residency was a condition of signature. The merchant identifier mapping is not clean and security evidence is awaited.
What was said
What this says
Current to 11 Oct 26Kickoff for Brenneck Pay's Growth implementation. Goal is one page per merchant with sourced answers. EU residency was a condition of signature. The merchant identifier mapping is not clean and security evidence is awaited.
What happened: Hamza Akhtar and Elena Novak ran the kickoff with Katrin Vogelsang, Jonas Albrecht and Sabine Kranz on 9 Feb 2026. Seven written actions were agreed, with dates marked fixed or expected.
Customer view: Katrin wants account management and merchant risk to work from one view, with every answer linked to its source. Sabine said EU data residency was a condition of signature and will not accept verbal assurances.
Commercial: The order form is signed at £50k a year, running to 2 Feb 2027 with renewal on 3 Feb 2027. Growth has no SSO with SCIM, which makes leaver removal a manual step.
Watch: The merchant mapping table is not clean and go-live is expected, not fixed. Jonas is the admin who owns the Snowflake account.
Themes
Current to 9 Oct 26Theme
Growth implementation kickoff
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Jonas Albrecht to create the read-only role and send Hamza Akhtar the grant statement.
- Hamza Akhtar to review the masked mapping sample and send the mismatch list to Katrin Vogelsang and Jonas Albrecht.
- Elena Novak to send the sub-processor list and confirm the date and the implementation invoice date with finance.
Risks
Current to 9 Oct 26- The merchant identifier mapping between CRM and alert data is not clean, so a wrong join would give confident answers on the wrong merchant.
- Security evidence on processing region and sub-processors is outstanding, and Sabine Kranz will not accept verbal assurances.
- Without SSO and SCIM on Growth, leavers must be removed from the brain by hand.
Opportunities
Current to 9 Oct 26- The manual access review gap could open an Enterprise conversation about SSO and SCIM.
- The 40 users and eight connectors under Growth leave room to add connectors once the first three are live.
Transcript
Elena Novak NoneGood morning, everyone. Can you all hear me? I see Katrin and Jonas. Sabine, I think you are just joining.
Sabine Kranz NoneGood morning. Yes, I can hear you. My camera is slow, one moment.
Katrin Vogelsang NoneGood morning, Elena, good morning, Hamza. It is very grey here in Frankfurt today, so I hope Amsterdam is better.- Elena Novak NoneAlso grey, I am afraid. Rain since the weekend. But we are indoors, so it is fine.
Hamza Akhtar NoneMorning all. Hamza here, from London, so I can confirm it is raining on this side of the water as well.
Jonas Albrecht NoneGood. Then nobody has the advantage. Morning.- Elena Novak NoneThank you all for making the time. To confirm, I sent the agenda last week, and I will restate it briefly. First, introductions and what success looks like for Brenneck Pay. Second, the connectors and who owns each one. Third, the Snowflake account and EU data residency. Fourth, the security evidence. Fifth, the plan for the weeks ahead and who sends what. I will make sure that we leave with written actions.
- Katrin Vogelsang NoneThat matches my agenda, so good. May I add one point under the plan? I would like the minutes to say clearly which dates are fixed and which are only expected.
- Elena Novak NoneOf course, as agreed. I will mark each one as fixed or expected.
- Katrin Vogelsang NoneThank you. Then let me say why we are here, to be precise. We are a payment institution, we are supervised by BaFin, and at the moment our merchant account managers and our merchant risk team each look at a different picture of the same merchant. Account management sees the relationship, risk sees the transactions and the alerts, and when they disagree we spend a day finding out who has the newer information.
- Hamza Akhtar NoneRight, and that is exactly the case the Growth tier is built around, several teams on one view. So the target is one page per merchant, and both teams ask their questions against the same data.
- Katrin Vogelsang NoneYes. And for me success is simple. A merchant manager can ask why a merchant is flagged, and the answer comes with a source. What is the source? That is always my question.
- Hamza Akhtar NoneUnderstood. Every answer in the brain links back to the record it came from, so you can click through. I will show you that on your own data once the first connector is live, not on a demo set.
- Katrin Vogelsang NoneGood. Then I am satisfied for now.
- Elena Novak NoneJonas, would you like to introduce yourself and your role? You are the admin for the brain on your side.
- Jonas Albrecht NoneJonas, data engineering lead. I own the Snowflake account. Which means I own whatever you put in it. So, yes, I am the admin, and nothing gets loaded without me knowing about it.
- Hamza Akhtar NoneThat is the right way round, honestly. It is your account, we run inside it. We do not hold a copy somewhere else.
- Jonas Albrecht NoneMm. I read that in the documents. I would still like to see it in the role grants.
- Sabine Kranz NoneMay I introduce myself as well. Sabine Kranz, information security officer. I ran the security review, and I should say plainly that EU data residency was a condition of signature. This is a requirement, not a preference.
- Elena Novak NoneUnderstood, Sabine, and thank you. We have that noted, and it is why I asked for the security part to have its own slot. Before that, let us do the connectors, so that Jonas has what he needs.
- Hamza Akhtar NoneRight. So under Growth you have up to eight connectors, and forty users, which is the number on the order form. I would not start with eight. I would start with the ones that give risk and account management the shared view, and add the rest as we go.
- Katrin Vogelsang NoneWhich would those be, in your view?
- Hamza Akhtar NoneWell, it depends on where the merchant record actually lives. You told us the CRM holds the relationship, and the helpdesk holds the merchant questions. Is that still right, Katrin, or has something moved?
- Katrin Vogelsang NoneThat is still right. The relationship notes are in the CRM, the merchant tickets are in the helpdesk. Transaction alerts come from the risk engine, and that one is already in Snowflake. Jonas, correct me.
- Jonas Albrecht NoneCorrect. Alerts land in a schema that my team maintains, loaded nightly. I checked the load history this morning, no gaps in the last few weeks.
- Hamza Akhtar NoneThat is helpful, thank you. So the alerts are already where the brain lives, which saves us a connector and some time. Then I would suggest the CRM first, the helpdesk second, and the alert schema read directly.
- Jonas Albrecht NoneRead directly, through which role?
- Hamza Akhtar NoneA dedicated role that you create, read only, scoped to that schema. We do not ask for broader access than that.
- Jonas Albrecht NoneGood. Then I will define the role myself, and I will send you its name and grants in writing. I do not grant access by email, so I will do it in the account and send you the statement afterwards.
- Elena Novak NoneAs agreed. I will note that as action one: Jonas creates the read-only role and sends the grant statement to Hamza.
- Katrin Vogelsang NoneAnd who owns the CRM connection on our side? Somebody must be able to approve the application.
- Jonas Albrecht NoneMe, for the technical part. The CRM administrator sits in Katrin's team, so the approval comes from there.
- Katrin Vogelsang NoneYes. Let me be exact. I will ask the CRM administrator to approve it, and the owner of that connector on the business side is me. Jonas owns it technically. Please write both names.
- Elena Novak NoneI will write both. Thank you, Katrin.
- Hamza Akhtar NoneWhile we are on owners, what about the helpdesk? Who approves that one?
- Katrin Vogelsang NoneAlso my team, the merchant support lead. I will confirm her availability and come back to you.
- Hamza Akhtar NoneFine. And a question about the merchant identifier. Is it the same key in the CRM, the helpdesk and the alert schema? Because that is what makes one page per merchant possible.
- Jonas Albrecht NoneNot exactly. That is a schema change waiting to happen, to be honest. The CRM uses its own account reference, and the alert schema uses the internal merchant number. There is a mapping table, but I would not call it clean.
- Katrin Vogelsang NoneIt is not clean, no. Two merchants have been merged in the CRM and not in the alert data. This is one of the reasons we are here.
- Hamza Akhtar NoneRight, that is useful to know early. I would like to look at the mapping table with Jonas before we load anything. If the join is wrong, the brain will give a confident answer on the wrong merchant, and that is worse than no answer.
- Jonas Albrecht NoneAgreed. I can share a sample, with the merchant names masked. I would not send the full table.
- Hamza Akhtar NoneA masked sample is enough for me to see the pattern.
- Elena Novak NoneAction two, then. Jonas sends a masked sample of the mapping table, Hamza reviews it and reports the mismatches in writing.
- Katrin Vogelsang NoneAnd I would like to see the mismatches too, please, because risk and account management must agree which record is right. Let us agree the next step: Hamza sends the list to me and Jonas together.
- Hamza Akhtar NoneYes, both of you, same message.
- Elena Novak NoneNow item three, the Snowflake account and the EU region. Jonas, can you tell us how the account is set up today?
- Jonas Albrecht NoneIt is in an EU region, in Frankfurt. We chose that when the account was created, because the regulator expects it. Warehouses are separated per team. There is a warehouse for data engineering, one for analytics, and I would want a separate one for the brain so that I can see its cost and its queries.
- Hamza Akhtar NoneThat is how we would suggest it too. A dedicated warehouse, a dedicated database or schema for the brain's own tables, and the read-only role for the source schemas. Then you can audit everything the brain does through the normal query history.
- Jonas Albrecht NoneGood. That I can show an auditor.
- Sabine Kranz NoneMay I ask my questions here? Question one. Where exactly is the data processed? Not stored, processed. Including any model calls that answer a chat question.
- Hamza Akhtar NoneFair question. The brain runs inside your Snowflake account, so processing happens in that account and in its region. For the chat, I need to be careful not to give you a verbal assurance, because I know you will not accept one. I will get the written statement from our security team that covers the model processing, and send it with the architecture note.
- Sabine Kranz NoneCorrect, I will not accept it verbally. Please provide evidence. A statement is acceptable if it names the region and the processing steps.
- Elena Novak NoneTo confirm, I will make sure that the statement names the region and each processing step. I will chase it myself if it is late.
- Sabine Kranz NoneQuestion two. Access logs. Who can see which merchant data through the brain, and where is that recorded? DORA and the BaFin outsourcing requirements ask us to show this, on paper and in practice.
- Hamza Akhtar NoneThe brain respects the roles in your account, and the queries it makes are visible in your query history. For the user side, the sign-in logs are the other part. Growth does not include single sign-on with SCIM, so users sign in with the brain's own accounts, and I would want to be honest about what that means for your access review.
- Sabine Kranz NoneSay more. Is that a gap?
- Hamza Akhtar NoneIt is a difference rather than a gap, but you should decide that, not me. It means your leavers process has to include removing brain users by hand. Jonas as admin can do it, but it is a manual step.
- Jonas Albrecht NoneWhich I can live with for forty users. I would put it in the leaver checklist.
- Sabine Kranz NoneI would like that written into the procedure, not only agreed here. And I will want the user list reviewed on a fixed schedule. I will propose one.
- Elena Novak NoneThank you, Sabine. I will record it as action three: Sabine proposes the review schedule, Jonas updates the leaver checklist, Hamza provides the sign-in log description.
- Sabine Kranz NoneQuestion three. Sub-processors. I need the list, with locations, and I need to be told if it changes.
- Elena Novak NoneI will send the current list from our side, with locations, and a note on how changes are notified. I will not promise the date in this meeting, because it depends on our security team. I will confirm it in the minutes.
- Sabine Kranz NoneThat is acceptable. A date in the minutes is a commitment, so please be sure.
- Elena Novak NoneI understand. I will check first.
- Katrin Vogelsang NoneSabine, if I may, one thing for the auditor. Can we also have a one page description of how the brain is used by merchant operations? Then the audit file shows purpose, data, and owner in one place.
- Sabine Kranz NoneYes, I support that. Purpose, data categories, owner, retention.
- Hamza Akhtar NoneRetention is a good point. The brain indexes what is in the source systems, so retention follows your source rules. If a record is deleted at source, it should drop out of the index at the next refresh. I will test that on the first connector and show you the result, so you have evidence rather than a claim.
- Sabine Kranz NoneThat is exactly the sort of evidence I mean. Thank you.
- Jonas Albrecht NoneI would add one test. Delete a record in a test copy on a weekday morning, check the next night's load. Not on a Friday.
- Hamza Akhtar NoneNoted, no Friday changes. We will plan around it.
- Elena Novak NoneNow item five, the plan. Hamza, could you walk us through the implementation weeks?
- Hamza Akhtar NoneYes. Growth has an eight week implementation. Roughly, the first two weeks are access and the Snowflake setup, the next weeks are the first connectors and the merchant mapping, and then the remaining connectors, the pages for each team, and training for the forty users. The go-live depends on the mapping being right, so I would rather say expected than fixed.
- Katrin Vogelsang NoneExpected, then. Please write exactly that in the minutes.
- Elena Novak NoneAs agreed. Katrin, there is also the commercial side. The order form is signed, the contract runs to 2 Feb 2027, and the renewal date is 3 Feb 2027. I mention it only so that the minutes hold the dates, and our CSM role will come back to you well ahead of it.
- Katrin Vogelsang NoneUnderstood. Sabine, you do not need to listen to this part, but I want it in my file. The annual amount is fifty thousand pounds, as in the order form, and we signed on 3 Feb 2026.
- Elena Novak NoneThat is right. £50,000 a year, and the invoice matches the order form.
- Sabine Kranz NoneI will mute myself for the commercial items. I do not discuss them.
- Katrin Vogelsang NoneOf course. One more thing for finance, they asked me when the invoice for the implementation will arrive. I do not know.
- Elena Novak NoneI do not want to give you a date for that without checking with our finance team. I will ask them today and put the answer in the minutes.
- Katrin Vogelsang NoneGood, thank you. That is the right way.
- Jonas Albrecht NoneCan I ask something practical? When Hamza's team connects, who do I call if a load fails at night? I am the one who gets the alert.
- Hamza Akhtar NoneDuring implementation, me directly, and I will send you my contact details in the follow-up. After go-live you raise a ticket through the helpdesk, and Elena is your named contact for anything that needs escalating.
- Elena Novak NoneI will make sure that the escalation route is in the written plan, with the response times for the Growth tier.
- Katrin Vogelsang NoneLast item from me. Which dates are fixed, as I asked at the beginning? Let me repeat what I heard, and please correct me.
- Katrin Vogelsang NoneFixed: the signature date, the contract end and the renewal date. Expected: go-live, and the invoice date, which Elena will confirm. Everything else has an owner but no date yet. Is that complete?
- Elena Novak NoneThat is complete. I would only add that the first working session between Hamza and Jonas should be booked this week, and I will send the invitation myself.
- Jonas Albrecht NoneThis week is fine, as long as it is not Friday.
- Hamza Akhtar NoneWednesday or Thursday, then. Early in the day, so that a load can be checked the following morning.
- Elena Novak NoneI will propose Wednesday. To summarise the actions. One, Jonas creates the read-only role and sends the grant statement. Two, Jonas sends the masked mapping sample and Hamza reports the mismatches to Katrin and Jonas. Three, Sabine proposes the access review schedule, Jonas updates the leaver checklist. Four, Hamza sends the architecture note and the processing statement. Five, Elena sends the sub-processor list and confirms the date, and checks the invoice date with finance. Six, Katrin confirms the helpdesk approver. Anything missing?
- Sabine Kranz NoneThe one page purpose description for the audit file. Katrin owns the draft, I will review it.
- Elena Novak NoneThank you, that is seven. Written minutes will be with you today.
- Katrin Vogelsang NoneThen we have a clear next step. Thank you, everyone. It was a good start, and I am glad it was careful.
- Jonas Albrecht NoneThanks. Talk on Wednesday.
- Hamza Akhtar NoneThanks all. Speak soon.
- Sabine Kranz NoneThank you. I will wait for the evidence.
- Elena Novak NoneThank you, goodbye, everyone.
Callsmade from