Databases
StackOverflow2013
Postsdbo
POPayPal CUSTREF Not Appearing in PayFlow Pro Transactions with Secure Token (Transparent Redirect)
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPayPal CUSTREF Not Appearing in PayFlow Pro Transactions with Secure Token (Transparent Redirect)
    text
    copied!<p>I'm using PayPal PayFlow Pro to process transactions. We've opted to use the secure token with transparent redirects to try and address PCI-Compliance issues.</p> <p>In my token request, I am specifying the CUSTREF parameter like so:</p> <pre><code>&amp;CUSTREF=461 </code></pre> <p>I have also created a hidden field for this in the transaction form. I have the HTTPS proxy enabled for Fiddler and I can see these values coming through in both the secure token and transaction requests. The transactions complete successfully on the live PayFlow gateway.</p> <p>However, when I view the transactions under <a href="https://manager.paypal.com/" rel="nofollow">https://manager.paypal.com/</a> > Reports > Daily Activity, the <em>Cust Ref #:</em> field on the detail page is empty.</p> <p>The parameter is discussed for use in inquiry transactions on page 71 of this document: <a href="https://www.paypalobjects.com/webstatic/en_US/developer/docs/pdf/payflowgateway_guide.pdf" rel="nofollow">https://www.paypalobjects.com/webstatic/en_US/developer/docs/pdf/payflowgateway_guide.pdf</a></p> <p>I couldn't find much documentation on this field other than this. I had a look at some code samples, and it looks like the CUSTREF parameter should be passed in the transaction request (which was the first thing I tried), e.g.</p> <p><a href="https://github.com/angelleye/paypal/blob/master/PayFlowTransaction.php" rel="nofollow">https://github.com/angelleye/paypal/blob/master/PayFlowTransaction.php</a></p> <p>Has anyone encountered this before? I have a ticket open with PayPal.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload