Be careful how we want to distinguish these transactions. How do they show up in reconciliation reports? How are transaction IDs stored?
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T87621 [epic] PayPal upgrade | |||
Resolved | None | T131815 Paypay Express checkout internal test | |||
Invalid | None | T130852 Debug gateway account name handling | |||
Resolved | awight | T134452 Spike: Decide whether PayPal Express Checkout is a new gateway, payment method, or account name. |
Event Timeline
Comment Actions
@Ppena
What do you think about PayPal legacy and express checkout being reconciled separately? Would that be helpful, or a pain?
Comment Actions
Change 294123 had a related patch set uploaded (by Awight):
Express Checkout is recorded as PayPal
Comment Actions
Change 294181 had a related patch set uploaded (by Awight):
Express Checkout is recorded as PayPal
Comment Actions
Back on the table... I've reverted the crm patch because it was causing duplicate contributions (and TY letters). The listener and audit processors are a blocker, they would need to be able to distinguish paypal from paypal_ec in order to send a message with the right gateway, and to dedupe before sending.