Page MenuHomePhabricator

Ingenico/Worldline addition of Initial Scheme Transaction ID to avoid recurring declines
Closed, ResolvedPublic

Description

Ingenico/Worldline have advised of the best practice of sending the Initial Scheme Transaction ID only for MIT/recurring transactions in order to avoid potential declines by issuers on our recurring transactions. We should comply with this even as a US merchant according to Ingenico.

From Ingenico:
You’re correct that this shouldn’t apply as you’re a US entity. However, we’re being told that even though this is the case we have seen that EU issuers soft decline transaction and challenge requesting for 3DS SCA. It’s not a scenario that happens often, but in theory is possible. In those cases, Wikimedia would need to authenticate the first transaction and link it to the subsequent transaction, MIT linking is a global practice. Therefore this is more a cautionary suggestion should there be a 3DS SCA challenge and dependent on your routing logic given the 3DS flow through us has ceased since December.

The mandate:

The PSD2 SCA was introduced by Visa and Mastercard on 1 January 2021. From this date on, you are required to keep an identifier linked to the proof of the first authorized transaction. That proof is called as the Initial Scheme Transaction ID and it is provided in each authorization response for Merchant Initiated Transactions (MITs) under the parameter Scheme Transaction ID

Your immediate action is needed to protect your online business
The schemes are mandating that you use only the Initial Scheme Transaction ID only for MIT/recurring transactions. If you are initiating an MIT without an Initial Scheme Transaction ID or by using a fixed Interim Scheme Transaction ID value provided by Visa and Mastercard then you need to make changes on your end.
We will stop supporting the Interim/Dummy Scheme Transaction ID from 1st May 2023. If you have not yet switched to the real Initial Scheme Transaction ID, this would result in all MIT transactions being rejected by issuers/schemes.

We strongly recommend you to start using the a real Initial Scheme Transaction ID immediately.

Your imminent action:

• Make sure that you start sending us the Initial Scheme Transaction ID with every MIT. Issuers/schemes will decline all transactions where the proof provided is incorrect.
• You need to keep storing it on your end and share the Initial Scheme Transaction Id with the next MIT request you send us.
• In case you don’t have the Initial Scheme Transaction Id stored on your end then please send us the Scheme Transaction ID received from the most recent MIT.

What are we doing to help your business?

We care for your business we have developed a temporary solution. This is a safety net for a limited part of your transactions if you are not compliant after 1st of May.
Impact - is that when you are not sharing the initial scheme Transaction ID (a part of) your transactions will be declined by the schemes.

Quick Summary :

• Start sharing the real Initial Scheme Transaction ID before the 1st May 2023 to avoid any declines on MIT and recurring transactions.

• If you are using a partner platform or a third party to connect to us, then speak with your partner and make sure they comply with this mandate on your behalf.

An FAQ added for your reference before you contact the Customer Experience Team.

If you still have query’s please reach out to our Customer Experience Center. Please use the reference 02032023

Best regards,
Customer Experience Center

FAQs
What is the business impact if you do not send the Initial Scheme Transaction Id ?
Issuer and Schemes will decline your MIT / Recurring transaction if the Initial Scheme Transaction Id is missing or if a
dummy / interim Scheme Transaction Id is passed.
Where can I find the Initial Scheme Transaction Id ?
We have been passing you the Initial Scheme Transaction Id and shall continue to do so under the parameter
Scheme_Transaction_ID. If you are unable to map the Initial Scheme Transaction Id from the initial / first transaction
(Customer Initiated Transaction) then start using the Scheme Transaction ID received from the most recent MIT.
What is the deadline for this requirement ?
We will stop accepting the Interim/Dummy Scheme Transaction ID from 1st May 2023. Please note some of the
acquirers might stop supporting Interim/Dummy Scheme Transaction ID even earlier.
What is Worldline doing to protect our business ?
We are developing an interim solution to find and map the associated Initial Scheme Transaction ID with the
received MIT only for the cases where you are unable to send the Initial Scheme Transaction ID. This is not a
permanent solution , there shall still be a portion of your MIT volume that will get declined by the issuers / schemes
if the Initial Scheme Transaction Id is missing.
Which schemes are mandating the Initial Scheme Transaction Id as of today ?
Currently its Visa, MasterCard & Carte Bancaire as part of the PSD2 SCA compliance, however other Schemes could
follow this precedence soon.

Event Timeline

Aklapper removed a subscriber: Fundraising-Backlog.

@EMartin: Please add project tags as project tags - thanks!

Ejegg triaged this task as High priority.
Ejegg moved this task from Backlog to Doing on the Fundraising Sprint Fish HEAD^ board.

Change 901316 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/SmashPig@master] Handle initial scheme transaction ID

https://gerrit.wikimedia.org/r/901316

Change 904385 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Add new custom field for initial scheme txn ID

https://gerrit.wikimedia.org/r/904385

Change 905752 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Use API4 for inserting ContributionRecur records

https://gerrit.wikimedia.org/r/905752

Change 905768 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Add initial scheme id when present in message

https://gerrit.wikimedia.org/r/905768

Change 905772 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Use API4 to get payments to charge

https://gerrit.wikimedia.org/r/905772

Change 905773 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] WIP send initial scheme transaction id with recur charge

https://gerrit.wikimedia.org/r/905773

Change 901316 merged by jenkins-bot:

[wikimedia/fundraising/SmashPig@master] Handle initial scheme transaction ID

https://gerrit.wikimedia.org/r/901316

Change 906673 had a related patch set uploaded (by Ejegg; author: Ejegg):

[mediawiki/extensions/DonationInterface@master] WIP send initial scheme txn ID to Civi

https://gerrit.wikimedia.org/r/906673

Change 904385 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add new custom field for initial scheme txn ID

https://gerrit.wikimedia.org/r/904385

Change 905752 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Use API4 for inserting ContributionRecur records

https://gerrit.wikimedia.org/r/905752

Change 905768 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add initial scheme id when present in message

https://gerrit.wikimedia.org/r/905768

Change 905772 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Use API4 to get payments to charge

https://gerrit.wikimedia.org/r/905772

Change 905773 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Send initial scheme transaction id with recur charge

https://gerrit.wikimedia.org/r/905773

Change 906673 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Send initial scheme txn ID to Civi

https://gerrit.wikimedia.org/r/906673

Change 910577 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Fill scheme ID for ingenico recurrings

https://gerrit.wikimedia.org/r/910577

Change 910577 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Fill scheme ID for ingenico recurrings

https://gerrit.wikimedia.org/r/910577

Change 911428 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Add debug info to FillSchemeId

https://gerrit.wikimedia.org/r/911428

Change 911429 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Limit scheme fill query to last 45 days

https://gerrit.wikimedia.org/r/911429

Change 911428 merged by Ejegg:

[wikimedia/fundraising/crm@master] Add debug info to FillSchemeId

https://gerrit.wikimedia.org/r/911428

Change 911429 merged by Ejegg:

[wikimedia/fundraising/crm@master] Limit scheme fill query to last 45 days

https://gerrit.wikimedia.org/r/911429

Change 911431 had a related patch set uploaded (by Ejegg; author: Ejegg):

[wikimedia/fundraising/crm@master] Fix typo in scheme lookup

https://gerrit.wikimedia.org/r/911431

Change 911431 merged by Ejegg:

[wikimedia/fundraising/crm@master] Fix typo in scheme lookup

https://gerrit.wikimedia.org/r/911431

Hey @Ejegg is this task actually done? I wasn't at the sprint review this week.

Nevermind, just closing! Let me know if that's wrong :)

Hi @greg, we did all the work on it and I've verified that we're storing it, I was just trying to verify that we were sending the new ID on API requests for recurring charges and I was having a heck of a time actually getting that outbound data in the log, even though we have a pretty standard setting that should make it show up.