Looking at #2, 3 and 8 here
This is probably related to T131401 we need to know if we can make any changes here or if this is just on dlocal.
Do we want to discuss this with Dlocal further? They are happy to talk to us about a workaround but as of today they cannot send back two codes to enable us to send the donor back to the payments page. Do we want to discuss a work around or leave as is? Notes from discussions:
7/30/2019
2
ICancel/Continue redirect
https://phabricator.wikimedia.org/T229336
From slide screen captures: #8, #2 ‘Cancel’ and ‘Continue’ buttons takes to the Thank You Page. Should take donor back to payments page (link above)
Looks like for credit cards, back when fixing T131401, they changed something on their end to kick back a failure code on cancel, so that we at least send donors to the fail page rather than the thank you page. That behavior is still present on the cc forms. One would assume they could do the same for the BT forms. It doesn't look like we ever got them redirecting back to the payments page, but it's been a while so we can ask if that's possible.
8.14 under investigation as turned around to DLocal only on 8.12
Notes from 8.16 When cancel we do not want user returned to TY page. We want two different return codes, error codes, no TY page redirection when canceled.
9.12 Wikimedia needs to brainstorm a work around with Dlocal because we can’t provide two codes without effecting your entire customer base.
11 b.
7/30/2019
2
Cancel redirect
From slide screen captures #3 CANCEL button takes to the Thank You Page. Should take donor back to payments page (link above)
Looks like for credit cards, back when fixing T131401, they changed something on their end to kick back a failure code on cancel, so that we at least send donors to the fail page rather than the thank you page. That behavior is still present on the cc forms. One would assume they could do the same for the BT forms. It doesn't look like we ever got them redirecting back to the payments page, but it's been a while so we can ask if that's possible.
8.1`4 under investigation as turned around to Dlocal only on 8.12
8.21.2019 DLocal to consider a way to send
8.28.2019 If we change the code we are sending it will change every merchant on the current version of API. Dlocal can only provide only one notification type. Should we have Elliott speak to Seba again on a one-off workaround.