Swedish donations stuck at status 600
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	• DStrine
	Mar 2 2020, 8:23 PM

Project Tags

Referenced Files

	Restricted File
	Dec 5 2022, 8:03 PM

	Restricted File
	Dec 5 2022, 8:03 PM

	Restricted File
	Dec 5 2022, 7:44 PM

	Restricted File
	Dec 5 2022, 7:44 PM

	F34690230: noname1
	Oct 15 2021, 4:34 PM

	F34690231: invite.ics
	Oct 15 2021, 4:34 PM

	F34690229: invite.ics
	Oct 15 2021, 4:33 PM

	F34690228: noname1
	Oct 15 2021, 4:33 PM

Subscribers

View All 12 Subscribers

Description

Hi all,
I am seeing a number of orphan's NOT rectified during the Sweden campaign. This is ala the Big English trend I spotted above. I am reopenning this as I suggest it's worth revisiting this before BE2020 as this problem scales with volume and impacts valid donors. Recent examples from Sweden in the last few days:

79388584.2 SE SEK 50 3/1/20 16:53 y past 79388584.2
79388254.1 SE SEK 208 3/1/20 13:51 y past 79388254.1
79388173.1 SE SEK 500 3/1/20 12:59 y past 79388173.1
79384824.1 SE SEK 104 2/29/20 17:50 y past 79384824.1
79380244.1 SE SEK 53 2/28/20 16:01 y past 79380244.1
79380154.1 SE SEK 208 2/28/20 15:35 y past 79380154.1
79378894.1 SE SEK 100 2/28/20 12:51 y past 79378894.1
79372835.1 SEK SEK 53 2/27/20 20:29 y 79372835.1
79372483.1 SEK SEK 312 2/27/20 19:42 y past 79372483.1
79372070.1 SEK SEK 53 2/27/20 19:04 y past 79372070.1
79370727.1 SEK SEK 200 2/27/20 17:20 y past 79370727.1
79370675.1 SEK SEK 200 2/27/20 17:12 y past 79370675.1
79370188.1 SEK SEK 100 2/27/20 16:41 y past 79370188.1
79367543.1 SEK SEK 104 2/27/20 15:49 y past 79367543.1
79368612.1 SEK SEK 53 2/27/20 14:56 y past 79368612.1
79367944.1 SEK SEK 104 2/27/20 14:14 y past 79367944.1
79367028.1 SEK SEK 520 2/27/20 13:27 y past 79367028.1
79366901.1 SEK SEK 30 2/27/20 13:20 y past 79366901.1
79366634.1 SEK SEK 104 2/27/20 13:09 y past 79366634.1

Related Objects

Mentioned In: T257707: Q1 FY 20/21 epic for Q2 readiness
T239769: Ingenico transactions stuck at 600 without fraud scores
Mentioned Here: T290923: Adyen Checkout: Show validation errors and allow resubmit for appropriate API error codes
T292475: Figure out what to do with OFFER_CLOSED Adyen ipn messages

Event Timeline

• DStrine created this task.Mar 2 2020, 8:23 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 2 2020, 8:23 PM

• DStrine mentioned this in T239769: Ingenico transactions stuck at 600 without fraud scores.Mar 2 2020, 8:24 PM

• DStrine moved this task from Triage to Next on the Fundraising-Backlog board.Mar 3 2020, 4:43 PM

• DStrine moved this task from Next to Sprint +1 on the Fundraising-Backlog board.Mar 17 2020, 5:32 PM

• DStrine moved this task from Sprint +1 to Q3 2021-2022 on the Fundraising-Backlog board.Jun 18 2020, 5:17 PM

• DStrine mentioned this in T257707: Q1 FY 20/21 epic for Q2 readiness .Jul 10 2020, 8:56 PM

• DStrine added a project: FR-Q2-FY2020-21-cleanup-list.Jul 20 2020, 10:36 PM

• DStrine moved this task from Q3 2021-2022 to Next on the Fundraising-Backlog board.Jul 21 2020, 3:01 PM

• DStrine moved this task from Next to Q3 2021-2022 on the Fundraising-Backlog board.Jan 3 2021, 8:34 PM

Further to this issue, we are seeing an inordinate amount of transactions in the JP campaign that are not scored but are awaiting settlement at 600 each day. Orphan Rectifier is not either scoring or settling transaction timely adding to and extensive manual review process much like we've seen above. What is contributing to the delay and can this be addressed? We don't want to delay the review process because the authorization will expire so how can we improve the work of Orphan Rectifier?

Examples:

likely plausible 7/19/21 15:31 102767507.2 0 JP JPY 335
likely plausible 7/19/21 15:10 102767194.1 0 JP JPY 1040
likely plausible 7/19/21 14:28 102766077.1 0 JP JPY 300
likely plausible 7/19/21 11:16 102758817.1 0 JP JPY 1040
y y past 7/19/21 8:26 102753790.1 0 JP JPY 2080
likely plausible 7/19/21 6:41 102750602.1 0 JP JPY 335
likely plausible 7/19/21 6:15 102749805.1 0 JP JPY 335
likely plausible 7/19/21 1:31 102740747.1 0 JP JPY 335
likely plausible 7/19/21 1:07 102739792.2 0 JP JPY 1040
y y past 7/19/21 0:24 102738554.1 0 JP JPY 335
y y past 7/19/21 0:06 102738033.1 0 JP JPY 335
y y past 7/18/21 22:04 102735145.2 0 JP JPY 335

~~Hi @EMartin could you provide some examples please so we can take a look?~~

~~Thanks!~~

Ah nevermind you posted them as I wrote the above :)

Hi @EMartin

I've looked at a few more and added their status below.

likely plausible 7/19/21 15:31 102767507.2 0 JP JPY 335 (Error code 430285: Not authorised.)
likely plausible 7/19/21 15:10 102767194.1 0 JP JPY 1040 (Error code 430306: Card expired.)
likely plausible 7/19/21 14:28 102766077.1 0 JP JPY 300 (Error code 430330: Not authorised.)
likely plausible 7/19/21 11:16 102758817.1 0 JP JPY 1040 (Error code 430306: Card expired.)
y y past 7/19/21 8:26 102753790.1 0 JP JPY 2080 (Error code 430306: Card expired.)
likely plausible 7/19/21 6:41 102750602.1 0 JP JPY 335 (Error code 430306: Card expired.)
likely plausible 7/19/21 6:15 102749805.1 0 JP JPY 335 (Error code 430285: Not authorised.)

likely plausible 7/19/21 1:31 102740747.1 0 JP JPY 335
likely plausible 7/19/21 1:07 102739792.2 0 JP JPY 1040
y y past 7/19/21 0:24 102738554.1 0 JP JPY 335
y y past 7/19/21 0:06 102738033.1 0 JP JPY 335
y y past 7/18/21 22:04 102735145.2 0 JP JPY 335

Hi Jack,

Here are more examples from today. Why the delay in either scoring or
settling these transactions that show up on our Fredge report? Thanks

*Payment attempt date*

*Order ID*

*Risk Score*

*Country*

*Form amount*

*AVS*

*CVV*

*ScoreCountryMap*

*ScoreName*

*ScoreEmailDomainMap*

*ScoreUtmCampaignMap*

*initial*

*IPVelocity*

*minfraud*

*SessionVelocity*

*donationInterfaceEmailPattern*

*IPBlacklist*

2021-07-20 16:22:39

102829462.1

JPY 335

2021-07-20 16:18:50

102829407.1

JPY 3120

2021-07-20 16:14:18

102829327.1

JPY 1560

2021-07-20 15:19:00

102828216.1

JPY 2600

2021-07-20 14:11:26

102826079.1

JPY 3120

2021-07-20 13:38:50

102824675.1

JPY 10400

2021-07-20 13:30:16

102821746.1

JPY 335

2021-07-20 13:17:03

102823655.1

JPY 1040

2021-07-20 11:34:25

102817946.1

JPY 535

2021-07-20 10:19:30

102814338.1

110.05

JPY 570

0.05

2021-07-20 08:38:35

102810015.2

JPY 1040

2021-07-20 08:25:49

102809510.1

JPY 2600

2021-07-20 08:07:40

102808653.1

JPY 370

2021-07-20 07:39:05

102807392.1

JPY 1500

2021-07-20 07:26:55

102806759.1

JPY 335

2021-07-20 06:34:52

102804176.1

JPY 10000

2021-07-20 06:12:53

102802994.1

JPY 300

2021-07-20 04:37:56

102798170.1

JPY 1622

2021-07-20 04:37:29

102798009.1

JPY 370

2021-07-20 04:29:47

102797693.1

JPY 1040

2021-07-20 04:23:15

102797347.1

JPY 1000

2021-07-20 04:00:54

102795885.1

JPY 500

2021-07-20 03:29:12

102793348.1

JPY 3120

@jgleeson Jack - your findings are interesting. When I look up one of the transactions you state is "Not Authorized", I clearly see an auth code in the Ingenico console telling me it is authorized. In fact, status 600 denotes authorized and what the Fredge report is reporting each day. Wondering if there is something about the statuses you are seeing vs those on the report that has some disconnect. Example below:

This is odd. The authorization time is 2 hours after the failed attempt I see in our payment logs.

Lemme see if @Ejegg has any ideas.

@EMartin there's some more work needed here to figure out what's happened. Our usual cursory log scanning isn't showing up any obvious answers.

I'll let @DStrine prioritise accordingly.

Thanks so much for all the helpful examples!

EMartin added subscribers: • AndyRussG, Cstone, XenoRyet, Jgreen.Aug 12 2021, 8:03 PM

This comment was removed by greg.

Works for me! see you then

hmmm how did the email reply to Adyen end up on this ticket

Manavi, Mark, Carmen,

We are rolling along preparing to deploy our integration over the next few
days. We don't need a call tomorrow, but let's please keep the standing
meeting for next week and beyond until we are on the other side of the
deployment. Thanks again for the great support during this period.

Evelyn

EMartin added a comment.Aug 26 2021, 8:31 PM

This comment was removed by greg.

EMartin added a comment.Sep 2 2021, 5:16 PM

This comment was removed by greg.

EMartin added a comment.Sep 16 2021, 4:53 PM

This comment was removed by greg.

Hi Adyen folks!

We're going to skip tomorrows call if that's ok?

This week we've been working towards setting up a new internet-facing
development server to help with our Apple Pay development, with the
proposal for that being approved yesterday. Now we need to complete the
work to provision it, and once up and running, we should be able to jump
back into the Apple Pay own-cert set-up process. Due to this, we don't have
any questions for Adyen just yet! :)

Thanks

jgleeson added a comment.Oct 8 2021, 1:05 PM

This comment was removed by greg.

Hi Manavi and Carmen,

Our team would like to keep the standing call tomorrow to discuss some
integration topics. We have a couple of folks on PT that want to
participate and we were wondering if we could meet a bit later. Please let
us know what is possible. We look forward to speaking with you.

Evelyn

Carmen, Manavi,

Here is some insight into questions for our call tomorrow, hope you can
make a bit later as requested below. Thank you!

OFFER_CLOSED IPNs https://phabricator.wikimedia.org/T292475

Confirm that the OFFER_CLOSED IPNs are due to iDEAL trxns being cancelled
at the users/bank side

Adyen createPayment Validation errors

https://phabricator.wikimedia.org/T290923
Is it possible to call some function on the Card component to indicate that
a field is in error? specifically either encryptedSecurityCode or
encryptedCardNumber for errorCodes 101, 102, 103 and 138

Apple Pay - Elliott's dev machine quit responding to the donate button

(not handing off to the OS Apple Pay flow when clicked) and he couldn't
figure out why until he went back to the wallet app and it said 'apple pay
has been disabled because the security settings of this mac have been
modified'
The component.isAvailable() had still been responding true though, so we
were mounting the component and the page just looked broken. Is there
anything else we can do in our JS to detect this and show an appropriate
error?

Evelyn

Hi Carmen,

That time slot works well for our side, thanks for accommodating us. I'll
get the invite adjusted.

XenoRyet added a comment.Oct 14 2021, 6:49 PM

This comment was removed by greg.

XenoRyet added a comment.Oct 14 2021, 6:49 PM

This comment was removed by greg.

XenoRyet added a comment.Oct 14 2021, 6:49 PM

This comment was removed by greg.

XenoRyet added a comment.Oct 15 2021, 4:32 PM

This comment was removed by greg.

XenoRyet added a comment.Oct 15 2021, 4:32 PM