...
Introducing BK Pay as a payment method to web/app will increase MARU by X% by the end of <date> by introducing another convenient way to of payment method in-restaurant by accommodating all users with a checking account in Germany that are not able to use Apple or Google Pay. Since the vast majority of banks don‘t support Apple Pay with Girocard (the local debit card) and almost none Google Pay, BK Pay will have an advantage over other digital payment wallets on the market.
Introducing BK Pay as a payment method to web/app will Increase an average check value for a restaurant customer by X% by <date>, assuming X% of current cash payers will transition to BK Pay, based on the fact that non-cash papers payers tend to have a higher average check by X%.
...
Introducing BK Pay as a payment method to web/app will decrease overhead cost by X% by <date> , assuming that X% of cash payers and X% of credit card payers will transition to BK Pay.
Do you have a way to track and report it?
Payers' behavior:
The SPACE 2022 results show that:
...
Increase MARU (Monthly Active Registered Users) by X% in order to collect user data.
Increase an average check value by X%. (usually higher with cc than cash) (whats the average check value for cc and whats for cash, is the split 50/50)- overall average check.
...
Reduce overhead costs by X % by decreasing in-restaurant cash and credit card payments (in selected restaurants) to X% combined, by the end of 2024, maintaining at minimum the same level of average monthly sales X EUR/ month at least, considering seasonality.
Decrease cash-handling costs by X% (From X to X )
Decrease credit card processing fees by X% (From X to X )
convenience- only Kaufland has this use case- attempt to differentiate the BK app- ties back to MARU, decrease time to place an order (difficult to measure) -
...
Any perspective on cross-store/ venue promotion?
Kaufland - do they incorporate loyalty? What was their objective?
How do we envision the cross-promo? What’d be the objective?
Follow up on the data insights from Bluecode on the current BK Pay usage:
Payment success rate =>
we had 1763 payment attempts where 45 transactions happened at other merchants!). of the transactions at BK, only twice was a token expired (user can try again), twice the payment was cancelled by the user and 41 users were blocked due to clear and proven fraud attempts.What % of users paid successfully out of the users that opened the BK Pay app =>
we had about 15.9K app openings, 10% of openings end up as payment, the rest was informational or onboarding processes.What % of users downloaded the app but ended up not inserting the bank account details =>
we had 1656 wallet installed, 803 onboarded and 513 made at least one payment, so 853/1656 = 51% did NOT onboardWhat % of users inserted their bank account details and did not pay with BK Pay =>
513 did at least one payment so, 290/803 = 36% did onboard but no paymentAverage # orders paid via BK Pay app per BK Pay app user =>
1598 payments in BK restaurants, on a contract basis (IBAN equivalent, ie unique users) it was 312 different contracts, 5.12 payments per contract!Average order value per BK Pay user =>
1598 payments had an total value of 18 218 Euro, average order value 11.40 Euro, average order value per contract 58.39 Euro.
assuming 1% of transactions done with Bk Pay,
1% of users have current Bk Pay,
page visints 5% clickable
DE market survey on demand for BK Pay
Script
Sample size and demographics
Results
✅ Action items
Magdalena Dlugolecka will follow up with the restructured objectives and metrics early next week and we can connect on that asynchronously via email.-early week of 4.9.23
Melina to provide the survey results from DE
Eduardo Javier Magdalena Dlugolecka We'll reconvene next Friday at 2:15pm to review the user test results and the design proposal. 8.9.23