Page MenuHomePhabricator

Epic: Distinguish PayPal legacy vs. Express Checkout transactions
Open, Needs TriagePublic


Use case: we need to be able to ship something in the return url that we can use to differentiate between Paypal Legacy and Express Checkout in the listener. We need this to not explode everything that pays attention to order_id. That is going to require some subtasks.

Event Timeline

Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptJun 16 2016, 8:37 PM
awight renamed this task from Epic: Add semantic prefix to order_id to Epic: Distinguish PayPal legacy vs. Express Checkout transactions.Dec 5 2016, 10:22 PM
awight added subscribers: Ppena, awight.EditedDec 7 2016, 8:27 PM

The biggest question mark here is actually for you. It seems that the easiest way to implement Express Checkout is as an entirely new gateway. This means that CiviCRM transaction IDs would look like "PAYPAL_EC 01234..." and the totals would be grouped separately from legacy transactions in various reports. Does this ring any alarm bells for you, or should I go ahead with that plan?

It makes me uncomfortable that the payments will all be going to the same PP account but will reconcile separately.

Change 325818 had a related patch set uploaded (by Awight):
[WIP] Change gateway for Express Checkout

mmodell removed a subscriber: awight.Jun 22 2017, 9:33 PM