Veenendrecht Payments / BB-Demo – Onboarding
Callcompleted
Veenendrecht Payments · 2026-02-18 15:00
Onboarding call with Eline Bakker and data engineer Ruben Dekker. The Snowflake role request is the next blocker. First sources are helpdesk, disputes and volumes, with no user invitations until data has loaded.
What was said
What this says
Current to 13 Oct 26Onboarding call with Eline Bakker and data engineer Ruben Dekker. The Snowflake role request is the next blocker. First sources are helpdesk, disputes and volumes, with no user invitations until data has loaded.
What happened: Ruben owns the Snowflake role request, raised through the customer's IT request process. Eline will get a helpdesk service credential from the support lead.
Customer view: Eline described merchant success and risk as two worlds that cannot answer a merchant's story quickly. She prefers a few sources working properly to many half working.
Commercial: Only Ruben and Eline have access so far, with forty users licensed. Eline wants a first group from merchant success and two from risk, but not before data is loaded.
Watch: Compliance matters because the customer is supervised by De Nederlandsche Bank. Risk may want faster than nightly refresh later, but Eline would not promise that now.
Themes
Current to 9 Oct 26Theme
Onboarding sources and access
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- Ruben Dekker raises the Snowflake role request on the day of the call.
- Eline Bakker obtains the helpdesk API credential from the support lead.
- Laura Penhaligon sends the one-page compliance note by the end of the week and sets up the schema once the role exists.
Risks
Current to 9 Oct 26- The Snowflake role depends on the customer's internal IT request process.
- Users who log in before data has loaded may not return.
- Risk may later want faster than nightly refresh, which Growth does not promise.
Opportunities
Current to 9 Oct 26- A rollout to merchant success and two risk users can follow the first load.
- A one-page data location note for compliance can build trust with the regulator-facing team.
Transcript
Laura Penhaligon NoneHello, can you both hear me all right?
Eline Bakker NoneYes, I hear you. Ruben is just joining, one moment.
Ruben Dekker NoneHi, sorry. My headset was on the wrong output. Can you hear me now?- Laura Penhaligon NoneLoud and clear. Good afternoon, both. Thanks for making the time, I know it's a busy week for you.
- Eline Bakker NoneGood afternoon. Let's make it practical. First, last time's actions. I said I would send the list of merchant segments. I sent it on Monday. Did you get it?
- Laura Penhaligon NoneI did, thank you, that was really useful. And mine was the access checklist for Ruben, which I sent over on Tuesday. Ruben, have you had a chance to look?
- Ruben Dekker NoneYes, I went through it. Most of it is fine. The part about the role in Snowflake, I need to ask a colleague in IT, because we create roles through a request process.
- Laura Penhaligon NoneRight, that's quite common. The brain runs inside your Snowflake account, so we need a role that can create a schema and read the source tables you choose. Nothing more than that.
- Ruben Dekker NoneOkay. Read only on the sources, and write only on the schema for the brain.
- Laura Penhaligon NoneExactly that. And no access to anything you don't point us at.
- Eline Bakker NoneWho owns the next step on this? I want one name.
- Ruben Dekker NoneMe. I raise the request today. I think it is quick, maybe a couple of days.
- Eline Bakker NoneGood. Then it is Ruben.
- Laura Penhaligon NoneLovely. Shall we talk about the sources? Eline, in the kickoff you said the point is that merchant success and merchant risk look at the same merchant together.
- Eline Bakker NoneYes. Now it is two worlds. Merchant success sees the tickets and the relationship. Risk sees disputes and volumes. When a merchant grows fast, or when disputes go up, the two teams do not see the same picture. What is the merchant's story? Nobody can answer quickly.
- Laura Penhaligon NoneThat's very clear. So for the first phase, I'd suggest we start with the ones that give you that story fastest. Your Growth plan covers eight connectors, so there's room, but I'd rather we get two or three working properly than eight half working.
- Eline Bakker NoneAgreed. I do not like half working.
- Ruben Dekker NoneWhich ones do you suggest first?
- Laura Penhaligon NoneWell, tickets from the helpdesk, because that's the easiest and it shows value early. Then the dispute data. And then the volume data, which I think is the one you'll care about most, Ruben, since it probably sits in your own tables.
- Ruben Dekker NoneYes. Volumes and disputes are in our warehouse already. The helpdesk is a separate system, so that needs credentials from the support team.
- Eline Bakker NoneSupport is in my area. I can arrange that. I will ask the team lead for an API credential, not a personal login.
- Laura Penhaligon NonePerfect, a service credential is exactly right. One more thing, Ruben. You raised a ticket with us last week. I saw it was marked high priority.
- Ruben Dekker NoneYes. That was the sign in. I could not get into the admin page, I thought something was wrong with my invitation. It was my mistake, I used the old link.
- Laura Penhaligon NoneNo problem at all, that happens a lot. I've seen it's resolved, so you're in now?
- Ruben Dekker NoneYes, I am in. Only me and Eline so far.
- Laura Penhaligon NoneThat's about what I'd expect at this stage. You have forty users licensed, so nobody's short of room. The question is more who comes in and when.
- Eline Bakker NoneI would like a first group from merchant success and two from risk. But not before the data is there. If people log in and see nothing, they do not come back.
- Laura Penhaligon NoneCompletely agree. So, no invitations until the first two sources have loaded and you've looked at them yourselves. Does that work?
- Eline Bakker NoneYes. And one more thing. The regulator. We are supervised by De Nederlandsche Bank. Anything with merchant data, I need to be able to explain where it lives.
- Laura Penhaligon NoneSure. It lives in your Snowflake account, in a schema you control, and we work inside it. I can write that down in one page for your compliance colleagues if that helps.
- Eline Bakker NoneYes please. One page, short.
- Laura Penhaligon NoneShort it is. I'll send it by the end of the week.
- Ruben Dekker NoneCan I ask something about refresh? When does the data update?
- Laura Penhaligon NoneNightly. It's complete by 07:00 your time on business days. So when Eline opens it in the morning, it's yesterday's picture.
- Ruben Dekker NoneOkay, that is fine for merchant success. Risk may want faster later, but we start there.
- Eline Bakker NoneLet's not promise later things now. Start with what we have.
- Laura Penhaligon NoneFair. So, let me recap. Ruben raises the role request today. Eline gets the helpdesk credential from the support lead. I send the one page for compliance by the end of the week, and I'll set up the schema the moment the role exists. Then we meet again next week and look at the first load together.
- Eline Bakker NoneYes. That is the list. I will check it at the start of the next call.
- Laura Penhaligon NoneI'd expect nothing less. Thanks, both.
- Ruben Dekker NoneThanks. Speak soon.
- Eline Bakker NoneGroetjes, Eline. Bye.
Callsmade from