Masking https referer to gateway

Hey Mad Hatters,

Anyone know how to mask, rewrite, or cloak the http referer that a website communicates to a merchant gateway when processing a transaction?

Apparently merchant processors don't like when you send through transactions from websites they haven't previously approved. From my understanding, risk departments look at http referer URL's to make sure merchants are sending transactions from websites that correspond to the account. Accounts tend to get shut down when this happens.

Not sure what your setup is, or what you exactly try to do, but you can manually set the referrer value for a request. With CURL for example you can set the 'CURLOPT_REFERER' option to your desired value.

cloakcoder said:

Not sure what your setup is, or what you exactly try to do, but you can manually set the referrer value for a request. With CURL for example you can set the 'CURLOPT_REFERER' option to your desired value.

Click to expand...

Perfect. This is what I was wanting to know.

It's my understanding that a merchant gateway logs the http referer that banks will look at to identify the URL referring a transaction. Basically just trying to see if it's possible pass an http referer value for a different URL than the URL of the page accepting payment.

or just get a chrome extension that does the job