With some verbiage about how we don't store it and if they leave it blank they will see a randomly generated one.
Description
Details
Event Timeline
Change 905255 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/SmashPig@master] Map phone number to payer when sent
Change 905290 had a related patch set uploaded (by Ejegg; author: Ejegg):
[mediawiki/extensions/DonationInterface@master] Add handling for phone number to generic form
Change 905291 had a related patch set uploaded (by Ejegg; author: Ejegg):
[mediawiki/extensions/DonationInterface@master] Add optional phone to dlocal UPI non-recurring
Change 905255 merged by jenkins-bot:
[wikimedia/fundraising/SmashPig@master] Map phone number to payer when sent
Change 905290 merged by jenkins-bot:
[mediawiki/extensions/DonationInterface@master] Add handling for phone number to generic form
Change 905291 merged by jenkins-bot:
[mediawiki/extensions/DonationInterface@master] Add optional phone to dlocal UPI non-recurring
@EMartin @RKumar_WMF this is now deployed - the phone input on our form is sent to DLocal (but not to CiviCRM). DLocal should pass it along to the one-time UPI donation form.
@Ejegg. Great news! What is the narrative on the form around this? @RKumar_WMF Can you check this out and ensure user clarity? thanks
All looks good on the clarity part of the message however now on the next screen the field to enter phone number is not appearing. So this is not relevant anymore I guess.
Message appears with Phone Number field. "This is optional and we do not store it. If left blank our payment processor will generate a random placeholder on the next screen." I left the phone number field blank. Next screen is of PayTM UPI, there is no screen now asking to enter the phone number.
dLocal is now saying on today's call they've got a new provider for the UPI one-time, which does not require a phone number.
@jgleeson @Ejegg Please note that they are testing the alternate provider (Razorpay) today. If they find moving to Razorpay works ok, moving to Razor pay (vs Cashfree) will not require the phone number and we can remove the text. Until they come back to us to confirm the Razorpay option, we should keep the phone number narrative/field as we may need to go ahead with Cashfree. I will update here further once I've heard back from Dlocal on their findings.
@AKanji-WMF @jgleeson @Ejegg 6April. We had a call with Dlocal again today. We learned that the donor will only be prompted for the phone number for ONE TIME donations. We are prompting for the phone number in our form for recurring as well. We need to change our logic to only ask for the phone number (implemented above) for one time donations. Can this change be made and timely given this will go to the fundraising team next week? many thanks. @RKumar_WMF @MBeat33
@EMartin We already have logic to exclude it from the recurring UPI form, and I don't see it at this link: https://payments.wikimedia.org/index.php?title=Special:DlocalGateway&appeal=JimmyQuote&payment_method=bt&recurring=1&uselang=en&language=en¤cy=INR&amount=500&country=IN&utm_campaign=internal_test&payment_submethod=upi
Can you please paste a link where you're seeing it on a recurring form?
@Ejegg I have gone back to Dlocal about this. After further input, Rakhi confirms that we are not prompting for phone on recurring despite what Dlocal told me. The ball is back in their court to explain why we are prompting for phone on one time transactions and yet we no longer see the phone number presented down stream in the checkout flow. I'll share their follow up here.
@Ejegg Dlocal came back to us today to explain that Cashfree was not setup in the sandbox/production account which is why we were not seeing the phone number prompts. It has now been enabled and we see the phone number fields for one time transactions and no fields for recurring as expected. Resolving this task.