Project

General

Profile

Actions

Feature proposal #8535

closed

Paypal gateway: Workaround for a bug at Paypal.com side to display Thank you page after purchase instead of "INVALID" (when Paypal returns with PDT without POST despite rm=2 asking for it)

Added by beat over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
25 May 2021
Due date:
% Done:

100%

Estimated time:

Description

Around mid-May, Paypal started subitely ignoring the rm=2 parameter (behaving like rm=0) for payments requiring a secure return by POST and not just GET with long URL potentially disclosing private information.

This undocumented change is a bug on Paypal.com side.

The Paypal.com documentation still states that rm=2 should return to site with a POST and not a GET:
https://developer.paypal.com/docs/paypal-payments-standard/integration-guide/Appx-websitestandard-htmlvariables/

This breaks the return page, that displays "INVALID" instead of the Thank you message, as it is not treated as a valid PDT return, because it is lacking the POST part and returning private information that a PDT with rm=2 should not return.

Actions #1

Updated by beat over 1 year ago

  • Subject changed from Paypal gateway: Add support for displaying Thank you page after purchase, despite the bug of Paypal.com for a PDT without POST despite rm=2 asking for it to Paypal gateway: Workaround for a bug at Paypal.com side to display Thank you page after purchase instead of "INVALID" (when Paypal returns with PDT without POST despite rm=2 asking for it)
Actions #2

Updated by beat over 1 year ago

Bug report sent to Paypal to merchanttechsupport at paypal.com with Case Number:08827840 through their form at https://www.paypal-support.com/s/contactsupport

Actions #3

Updated by beat over 1 year ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Implemented in commit 329658dc53dd610cb73f7be1d0728dd1069c46fa

(also now using Guzzle for verification HTTPS calls to Paypal)

Actions #4

Updated by beat over 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF