| krobinson | |
| Jul 3 2025, 3:42 PM |
| F62822204: Boleto donation attempt.png | |
| Jul 3 2025, 3:42 PM |
| F62822197: PIX donation attempt.png | |
| Jul 3 2025, 3:42 PM |
Brazilian donors are hitting a wall in the PIX and boleto donation flow via Gravy. They are successfully taken to the payments wiki PIX / boleto page, fill in their details and after hitting continue see an error message.
Adriana on our team is able to recreate the issue:
PIX donation attempt:
Boleto donation attempt:
These donation attempts cannot be found in Gravy or DLocal.
Change #1166231 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[wikimedia/fundraising/SmashPig@master] Truncate description field to match gravy requirement and add phone number where necessary
Change #1166231 merged by jenkins-bot:
[wikimedia/fundraising/SmashPig@master] Truncate description field to match gravy requirement and add phone number where necessary
From Rakhi via a slack channel (not sure which one, I don't have access):
"Hello everyone! I hope everyone had a great weekend. I wanted to share this ticket and added it to the BR error triage tab. I encountered the same error as the donor: unable to generate the page for PIX and Boleto. This case is similar to this Phab task. Please let me know if you can guide other necessary steps. TY"
She replicated the issue and got error: 233215691.2
Looks like the descriptor is too long again:
SmashPig-Gravy: gravy::233215691:233215691.1 | (RawData) Create payment response {"type":"error","code":"bad_request","status":400,"message":"Request failed validation","details":[{"location":"body","pointer":"\/statement_descriptor\/description","message":"String should have at most 22 characters","type":"string_too_long"}]} | |
I'll make sure we're actually truncating in code and not just relying on a translated string that potentially could get updated automatically from translatewiki
Just an update on timing: there is a campaign scheduled to go out tomorrow afternoon UTC that would use this payment method.
This is fixed!
Somehow during a deploy last Thursday I seem to have removed @Damilare's earlier fix for this issue. I've deployed an update just now to re-apply that fix, and I can now submit the page without that descriptor error.