Following up on the demo
Email thread Veenendrecht Payments · sales
Matteo recaps the demo and asks for technical answers. Ruben replies on sources and asks who can see what inside the brain, as Daan wants risk data kept apart. A Growth proposal is targeted for decision on 22 Jan 2026.
What was said
What this says
Current to 14 Oct 26Matteo recaps the demo and asks for technical answers. Ruben replies on sources and asks who can see what inside the brain, as Daan wants risk data kept apart. A Growth proposal is targeted for decision on 22 Jan 2026.
Ask: Matteo wanted answers on data sources and input to the proposal from Daan Visser and Eline Bakker. Ruben Dekker confirmed payments data is already in Snowflake, helpdesk API access is unconfirmed and the dispute source refresh is unknown.
Customer view: Ruben raised permissions, because Daan will want risk data separated from some merchant success views. No reply from Daan or Eline appears in the thread.
Next: Hannah Lowe is to put the permissions model in writing and check the dispute source refresh. Matteo is working to a Growth proposal and the 22 Jan 2026 decision date.
The thread
Updated 9 Oct 26Messages
Matteo Ricci 25 Nov 2025 09:31Dear all, Thank you for the time at the demo. It was useful to see how Daan's team and Eline's team look at the same merchant, and I would rather you heard from me directly what we took away. What we saw: disputes, tickets and volumes brought together for a merchant, running inside your own Snowflake account. What remains open: which of your systems you want connected first, and what your regulator would need to see about how the data is handled. Ruben, Hannah has a short list of technical questions about your sources. Could you reply with the answers when you have a moment? Daan and Eline, please add anything you want covered in the proposal. Best regards, Matteo
Ruben Dekker 27 Nov 2025 12:58Hi Matteo, Thanks for the summary. Answers to Hannah's questions below, as far as I know them today. - Our payments data is already in Snowflake, so that part should be simple. - The ticketing data sits in our helpdesk. I need to check who can grant API access. - Dispute data comes from a separate source. I am not sure yet how often it refreshes. One question from our side: who is able to see what inside the brain? Daan will want risk data kept apart from some of the merchant success views. Regards, Ruben- Matteo Ricci 28 Nov 2025 17:45Dear all, Thank you, Ruben, that is very clear. On access, Hannah will put in writing how permissions work inside your Snowflake account, so Daan can judge whether the separation he needs is possible. She will also check the dispute source refresh with you, because that decides how current the merchant view can be. We are working towards a proposal for Growth, with a target of 22 Jan 2026 for the decision. If anything in the timeline is wrong on your side, please tell me early. Best regards, Matteo