Jump to content
Sign in to follow this  
dynamoeffects

PayPal Payflow Pro [New Version]

Recommended Posts

Hello,

I got this error message:

 

The first four digits of the number entered are: 5020<br>If that number is correct, we do not accept that type of credit card.<br>If it is wrong, please try again.

 

I have set the correct number, What might be the problem?

 

I'm sorry my English is bad

 

thank

Share this post


Link to post
Share on other sites

Brian,

 

Hats off. This is an excellent contribution. Night and day difference compared with PayPal's API system, which is the only other PayFlow mod that I've been able to get to work consistently.

 

HOWEVER, I have to echo the issue regarding the error trapping on cards. I've noticed that a transaction may be allowed by PayPal's back-end processing, yet it returns an error and then OSC does not process the order. Let's say for example you have a bad billing address.

 

I tried this on my own card. Result was that as the store customer, I see a message which reads, "MODULE_PAYMENT_PAYFLOW_PRO_TEXT_ERROR_INCORRECT_BILLING_STREET." Now aside from the text issues there, the broader problem is that my card WAS charged, even though my order was not processed by OSC (I end up back on the 1st Checkout screen). I double checked the admin tool in OSC, and sure enough - nada - no order.

 

I tested this with only the CCGV (trad) mod installed, so it was a relatively clean installation.

 

If you can improve the error trapping and clean up the handling of the text error messages a bit, I think you've got an outstanding mod! Now, I just need an Express Pay mod that plays nicely with it. :)

 

In the meantime though I'll have to stick with the behemoth API mod from PayPal, since it handles everything pretty well.

 

Regards,

Share this post


Link to post
Share on other sites

Hi David,

 

Please add the code described at the following link to your module:

http://forums.oscommerce.com/index.php?s=&...t&p=1321700

 

Then do a similar transaction you did before that would cause the error that you're describing and send me the results, minus any sensitive financial information. I mainly need to see what the response from PayPal is.


Please use the forums for support! I am happy to help you here, but I am unable to offer free technical support over instant messenger or e-mail.

Share this post


Link to post
Share on other sites

I have updated the module to fix the missing language define and sending the customer to the checkout_payment page with an error when the AVS or CSC checks fail even when the card was charged.

 

I cannot find anything in the API to allow you to reject cards based on a failed AVS or CSC check. The information is received by the module only after the card has been charged, so by that point it's too late. I will update the module when I have a solution.


Please use the forums for support! I am happy to help you here, but I am unable to offer free technical support over instant messenger or e-mail.

Share this post


Link to post
Share on other sites
I have updated the module to fix the missing language define and sending the customer to the checkout_payment page with an error when the AVS or CSC checks fail even when the card was charged.

 

I cannot find anything in the API to allow you to reject cards based on a failed AVS or CSC check. The information is received by the module only after the card has been charged, so by that point it's too late. I will update the module when I have a solution.

 

Brian,

 

It seems to me that what's happening is the card issuing bank is authorizing the charge. I believe PayPal is simply passing the info along (to the issuing bank), and then PayPal receives both the "bad address" message and the "approved" message back from the bank.

 

So, I think the risk control issue would be at the issuing bank level, and not PayPal (i.e. can't do anything about that).

 

Regardless, the problem is that PayPal is approving the charge, but your PayPal mod interprets the results string in such a way that it thinks the transaction was denied. Big question is can you differentiate between a transaction that had bad address and went through versus one with bad address that did not go through? Is the code returned from PayPal to your mod the same either way? I would think that PayPal would include some kind of yes/no flag regarding whether or not the charge went through. If not, that is a huge hole on PayPal's part and obviously you cannot do anything about it if that's the case. There is no way to accurately predict how every issuing bank will handle these type of transactions.

 

I'm going to do as you asked in a separate post and provide the info that PP spits back to your mod.

Share this post


Link to post
Share on other sites
I installed and made 2 live transactions. (I have a UK paypal merchant account)

 

Transaction1: provided a real mastercard number with right CVV2 but wrong name, address, post code, country.

Result1: Error message saying the postcode (zip) was bad. Hoever, the money was collected from the card and is listed in paypal history.

 

Transaction2: provided a real mastercard number with right CVV2 and right zip postcode but wrong name, address and country

Result2: Got to the "success" page but the transaction is not listed in the paypal history

 

LS,

 

Did you test with the same MC card # in both instances?

 

Your experience is the opposite of what I would have expected, as most issuing banks and/or processors just look at card #, exp, CVV, and zip code. Though some do look at the whole address (and that is happening more and more to attempt to reduce fraud).

 

David

Share this post


Link to post
Share on other sites

Brian,

 

Ok. here is where I hit my technical wall. I made the changes to the PHP file, to capture the output (also using your latest v0.3 files), and now my Checkout_Confirmation.php file barfs on checkout with a blank screen. Presuming this is normal, I tried to find a log on the server that would have the output you want but I cannot find it atm (and it's a Sunday, so no chance of sysadmin help today).

 

Where should I find the output? Will it be in a server side log or was it supposed to echo it to the browser?

 

David

Share this post


Link to post
Share on other sites
Regardless, the problem is that PayPal is approving the charge, but your PayPal mod interprets the results string in such a way that it thinks the transaction was denied. Big question is can you differentiate between a transaction that had bad address and went through versus one with bad address that did not go through? Is the code returned from PayPal to your mod the same either way? I would think that PayPal would include some kind of yes/no flag regarding whether or not the charge went through. If not, that is a huge hole on PayPal's part and obviously you cannot do anything about it if that's the case. There is no way to accurately predict how every issuing bank will handle these type of transactions.

 

 

Most likely it is a bank-level issue as you noted, but I'm waiting for confirmation from PayPal about that. I read through the API documentation and I cannot find any reference to a switch to decline transactions that fail AVS/CSC checks. The only time the module is able to determine if the AVS or CSC check have failed is after the card has been charged.

 

It's not necessary to add that debug code anymore, I discovered what the problem was. It was sending a response code of 0, meaning that there was no error, but because the AVS check failed it created an error message that caused the module to think the card wasn't charged. I have taken that out until I hear back from PayPal.


Please use the forums for support! I am happy to help you here, but I am unable to offer free technical support over instant messenger or e-mail.

Share this post


Link to post
Share on other sites
Most likely it is a bank-level issue as you noted, but I'm waiting for confirmation from PayPal about that. I read through the API documentation and I cannot find any reference to a switch to decline transactions that fail AVS/CSC checks. The only time the module is able to determine if the AVS or CSC check have failed is after the card has been charged.

 

It's not necessary to add that debug code anymore, I discovered what the problem was. It was sending a response code of 0, meaning that there was no error, but because the AVS check failed it created an error message that caused the module to think the card wasn't charged. I have taken that out until I hear back from PayPal.

 

Ack! Of course, I just installed 0.3 and forgot to remove the "die" code snippet... oh well. :)

 

I checked though and yes it works much better now. Thanks for the quick turn-around. I actually think the functionality is ok / good as you have it now. It should not be the merchant's decision as to whether or not the shipping address is OK. That's not the merchant's job.

 

I just tried your new code and it works like a champ! I love your code versus the PayPal sanctioned API version, because this mod is SO much cleaner... 2 files. I love it!

 

Thank you so much for sharing this mod and especially for providing timely tech support as well. :)

 

Regards,

 

David

Share this post


Link to post
Share on other sites

I heard back from PayPal and basically this is what has to happen:

 

1) If available, you can set filters in your merchant account to decline transactions with failed AVS/CSC checks.

 

2) The module will have to first authorize a $1 charge to the customer's card, void the transaction, then take action depending on the response codes received. If the AVS check is a success, charge the full amount to the card. If it fails, display the error to the customer.

 

I'm not sure when I'll have time to add that second bit, so I would first check in your merchant account's settings if you can filter out those transactions in the interim. That would be the best solution anyway.


Please use the forums for support! I am happy to help you here, but I am unable to offer free technical support over instant messenger or e-mail.

Share this post


Link to post
Share on other sites
2) The module will have to first authorize a $1 charge to the customer's card, void the transaction, then take action depending on the response codes received. If the AVS check is a success, charge the full amount to the card. If it fails, display the error to the customer.

 

Brian,

 

Sounds to me like a pain, and perhaps something that should be optional for the merchant to use that feature.

 

Question: What if you auth the full transaction amount, review response code, then send instruction to charge the auth amount. I know this can be done with PayPal's Virtual Terminal. Can it be done via the API / SOAP / etc. systems? Seems to me that would be ideal if possible, so that you are also verifying funds availability. That way you can capture all the decline possibilities in the same set of code / first transaction. If not then don't you still need to look for decline codes in the actual real charge?

 

My $0.02. :)

 

Regards,

 

David

Share this post


Link to post
Share on other sites

Because when you authorize an amount on someone's card, it reserves that money for you for up to 30 days and is completely inaccessible to the customer during that period.

 

For instance let's say the customer has a credit card with a $1,000 limit and they make a purchase for $900. That $900 that you authorized and then declined would effectively kill that customer's card for upwards of a month. By authorizing only $1, the effect on the customer's card is minimal. Also if they decide to go back and change the billing address on the order to try to make it work, their card would be declined off the bat simply for not having enough funds.

 

It's admittedly a crappy way of handling this, but there is no other method. In all honesty, I would steer people away from Payflow Pro for this reason alone as I think it's going to cause a lot of headaches for both the store owners and customers. Other payment gateways like Authorize.net give you the ability to filter this out in their control panel so that this isn't even necessary.

Edited by dynamoeffects

Please use the forums for support! I am happy to help you here, but I am unable to offer free technical support over instant messenger or e-mail.

Share this post


Link to post
Share on other sites

Hi and thank you for helping,

 

Please, tell me if your mod works with a multiple IPN set-up (allowing use of IPN on more than one URL)

I know it's possible to do with cubecart ("This enables multiple stores to use the same PayPal account, and still take advantage of IPN"), but I'd rather stick with osCommerce.

Share this post


Link to post
Share on other sites
Hi Brian,

 

I would really love to have this thing working because i'm at my wits end with the 10001 errors i've started getting recently with the paypal API 2.0 interface (i posted about this in your paypal pro uk contribution thread)

 

 

I looked at your code a bit and had some questions/comments:

 

1) is is possible to add the INVNUM in the request? it would help a lot in tax reports to have the oscommerce transaction id as the invoice number recorded with paypal history logs.

 

2) what is this mystery variable $fraud ? where is it set ?

 

3) why do you copy the credit-card number and details in $order ? where does this information end up and is that secure ?

 

4) can all the returned codes be stored in the transaction history so that I can later cancel the transaction if it was "approved" although none of the fields match ?

 

thanks for your great contributions!

 

In the meantime i managed to get the paypal API working again so i'm not using this mod any more.

but if i recall, this mod was keeping the card details in the database.

FYI:

I just received a notification from another merchant account bank that VISA is forbidding to keep any credit card details unencrypted anywhere on a server. 5000EUR penalty.

https://www.pcisecuritystandards.org/securi...ss_download.htm

The Payment Card Industry Security Standards Council (PCI SSC), a committee concerned with data
protection in the card business, already prohibited the storage of confidential authentification data in
its obligatory data security standard, the Payment Card Industry Data Security Standard (PCI DSS),
which was released in September 2006.
Visa Europe has now decided that all merchants have to implement this prohibition by 31 December
2008. This means that confidential authentification data may not be stored any more after this date –
be it in an encrypted or in a non-encrypted form.
Any merchant who stores confidential authentification data after this date will be fined EUR 5,000. Any
such fines will be passed on to the relevant merchants or partners during the clearing procedure.


*Do not advertise in your signature

Share this post


Link to post
Share on other sites

Brian!

 

I'm running my default currency in Euro. The transaction goes through smoothly to my PayPal account but the amount comes through as USD instead of EUR currency.

 

Ex. €250 item purchased ends up in the PayPal account as $250 USD.

 

Is there something in the PHP that I need to edit. or is it on the PayPal Payflow account side?

 

Please help!

Thanks,

Chris

Edited by cpannek

Share this post


Link to post
Share on other sites

Brian,

 

Hello there. :)

 

Question: Are you familiar with Package Tracking Plus 2.2? There is a mod of this mod for PayPal modules, but I'm not sure if I'd want to apply it to your PayPal Pro v0.3 contib.

 

Would you mind providing your thoughts on the proposed change outlined in the PTP contrib? I have pasted the text of the proposed PayPal file modification below. It seems harmless enough, like it's just altering slightly a confirmation email sent to the customer. I have not poked around in your code (yet) to see how this might match up with it. I recall that some emails come from PayPal as well as the store, but what I'm concerned about are the triggers of what gets emailed when.

 

Regards,

 

David

 

###########

 

**********

* STEP 9 *

**********

 

OPEN catalog/includes/modules/payment/paypal_standard.php

 

FIND this:

 

// lets start with the email confirmation

$email_order = STORE_NAME . "\n" .

 

REPLACE with this:

 

//Package Tracking Plus BEGIN

// lets start with the email confirmation

$email_order = EMAIL_TEXT_GREETING . "\n" .

EMAIL_SEPARATOR . "\n" .

STORE_NAME . EMAIL_INVOICE . "\n" .

//Package Tracking Plus END

 

 

FIND this:

 

EMAIL_TEXT_INVOICE_URL . ' ' . tep_href_link(FILENAME_ACCOUNT_HISTORY_INFO, 'order_id=' . $order_id, 'SSL', false) . "\n" .

 

REPLACE with this:

 

//Package Tracking Plus BEGIN

EMAIL_TEXT_INVOICE_URL . ' ' . "<a HREF='" . tep_href_link(FILENAME_ACCOUNT_HISTORY_INFO, 'order_id=' . $order_id, 'SSL') . "'>" . 'order_id=' . $order_id . "</a>\n" .

//Package Tracking Plus END

 

 

FIND this:

 

tep_mail($order->customer['firstname'] . ' ' . $order->customer['lastname'], $order->customer['email_address'], EMAIL_TEXT_SUBJECT, $email_order, STORE_OWNER, STORE_OWNER_EMAIL_ADDRESS);

 

REPLACE with this:

 

//Package Tracking Plus BEGIN

tep_mail($order->customer['firstname'] . ' ' . $order->customer['lastname'], $order->customer['email_address'], STORE_NAME . ' ' . EMAIL_TEXT_SUBJECT_1 . ' ' . $order_id . ' ' . EMAIL_TEXT_SUBJECT_2 , $email_order, STORE_OWNER, STORE_OWNER_EMAIL_ADDRESS);

//Package Tracking Plus END

 

 

FIND this:

 

tep_mail('', SEND_EXTRA_ORDER_EMAILS_TO, EMAIL_TEXT_SUBJECT, $email_order, STORE_OWNER, STORE_OWNER_EMAIL_ADDRESS);

 

REPLACE with this:

 

//Package Tracking Plus BEGIN

tep_mail('', SEND_EXTRA_ORDER_EMAILS_TO, STORE_NAME . ' ' . EMAIL_TEXT_SUBJECT_1 . ' ' . $order_id . ' ' .EMAIL_TEXT_SUBJECT_2, $email_order, STORE_OWNER, STORE_OWNER_EMAIL_ADDRESS);

//Package Tracking Plus END

 

 

********

* DONE *

********

Share this post


Link to post
Share on other sites

I'm having a problem with my account settings. When I log into http://manager.paypal.com. I enter "Partner", "Merchant Login" and "Password", but I don't require a "Username" for my account. I've added that information to the Payflow Pro settings in osCommerce 2.2RC1 in the "Credentials: Partner", "Credentials: Merchant/Vendor" and "Credentials: Password" fields respectively. However, when I perform a test transaction, I get the following error when I click the Continue button on the same page I enter my credit card information:

 

Account configuration issue. Please verify your login credentials.

 

Any idea why I would receive this error?

 

Thanks!

Jason Huebel

Edited by jhuebel

Share this post


Link to post
Share on other sites

So can I assume this module is no longer maintained? There doesn't appear to be activity from the developer since October. *sigh*

 

I found the API documentation and a recommendation from Payflow support personnel stating that they are moving to an HTTPS interface for interacting with the API. So I guess I either have to hack up a new version or be stuck?

Share this post


Link to post
Share on other sites
So can I assume this module is no longer maintained? There doesn't appear to be activity from the developer since October. *sigh*

 

I found the API documentation and a recommendation from Payflow support personnel stating that they are moving to an HTTPS interface for interacting with the API. So I guess I either have to hack up a new version or be stuck?

 

Seems HTTPS support is already in place and my problem may be a PayPal account configuration issue. I'll call PayPal tomorrow. But I'm still concerned about using an unsupported module. :-/

Share this post


Link to post
Share on other sites

It seems that PayPal is launching a new version of the Payflow module (version 5.0) come September and will not be accepting any transactions from the old modules after that. Will there be any upgrades through osCommerce? Right now it looks like the latest version available here is 3.0 where there's already a version 4.0 out. Thanks!

Share this post


Link to post
Share on other sites
It seems that PayPal is launching a new version of the Payflow module (version 5.0) come September and will not be accepting any transactions from the old modules after that. Will there be any upgrades through osCommerce? Right now it looks like the latest version available here is 3.0 where there's already a version 4.0 out. Thanks!

 

I'm new to this open source stuff and have been struggling to find a solution to the September Payflow change on OSC and CREloaded. I can't get anybody to respond to questions either. Is this normal or is it just that the questions are related to Payflow? I'm trying to learn how all the parts relate and teach myself how to modify the code but I'm thinking I'm gonna wind up on a hosting platform with a supported integrated platform. What's the secret to figuring all this stuff out? Sorry for the rambling.

Share this post


Link to post
Share on other sites

HI,

I just installed the Payflow module to be able to accept credit cards on our website.

I placed a test order and it was generated correctly.

When I logged into the Payflow account, I noticed the amount charged to the credit card was not the same. The difference comes from the tax charged for shipping.

 

Example:

 

Item 1: $2.00

Shipping: $8.00

5% GST: $.10

5% GST on Shipping: $.40

Total: $10.50

 

The oscommerce admin indicates the correct total of $10.50. The gateway and credit card transaction shows $10.10.

 

We are also accepting Paypal this was never an issue.

Why is this occurring? Where should I look to find the answer?

 

Any insight would be greatly appreciated.

Thanks

Share this post


Link to post
Share on other sites

My hat is off to Brian for his efforts in creating this module and receiving recommendations from Paypal to use it as is shown here http://paypaldeveloper.com/pdn/board/messa...;thread.id=6309 . It was based on this recommendation that I began installing and using it.

 

Before I begin I must state that I am NOT the original author of the module only a merchant with a few albeit limited skills with the php language and code tracing. Having stated that I also need to point out the issues I discovered with this module.

 

1. Many customers do NOT understand nor do they have a clue what CVV2 is.

2. The module will allow transactions to appear within the orders section showing them as APPROVED even though CVV2 portion failed.

 

I am using osCommerce Online Merchant v2.2 RC2 NOT RC2a

I am in the US and Paypal is my ACH (Automated Clearinghouse)

We only accept VISA and MasterCard.

 

I will now explain what I did to resolve those issues and the information I utilized to make my changes and why.

 

 

BEFORE YOU GO ANY FURTHER - this works for me it should for you IF properly incorporated. BACK UP THE FILES REFERRED TO and if possible check on a test site first.

 

REMEMBER TO BACK UP THE ORIGINAL FILES AND TEST BEFORE USING ON LIVE STORE!!!!

 

 

ISSUE #1 above

 

To resolve this you need to do a couple of things

 

#####################

Things you will need

 

PayPal Payflow Pro v1

http://addons.oscommerce.com/info/4805

You only need the csc.htm, amex.htm and the images (you may have to edit them to fit your specific site)

 

Obviously Brian's Module

PayPal Payflow Pro [New Version]

http://addons.oscommerce.com/info/6244

 

DID YOU BACK UP THE ORIGINAL FILES?????

 

#####################

 

FIRST WE ARE GOING TO CHANGE THE "CVV2" presentation text to "Card Security Code".

 

FROM Brian's Module

PayPal Payflow Pro [New Version]

 

#### OPEN ####

catalog/includes/languages/english/modules/payment/paypal_payflow_pro.php

 

#### FIND ####

define('MODULE_PAYMENT_PAYPAL_PAYFLOW_PRO_TEXT_CREDIT_CARD_CVV2', 'CVV2:');

 

#### CHANGE TO ####

define('MODULE_PAYMENT_PAYPAL_PAYFLOW_PRO_TEXT_CREDIT_CARD_CVV2', 'Card Security Code:');

 

#### FIND ####

define('MODULE_PAYMENT_PAYPAL_PAYFLOW_PRO_TEXT_ERROR_CVV2', "Your CVV2 security code does not match. Please re-enter.");

 

#### CHANGE TO ####

define('MODULE_PAYMENT_PAYPAL_PAYFLOW_PRO_TEXT_ERROR_CVV2', "Your Card Security Code did not match. Please re-enter.");

 

###### SAVE AND CLOSE ######

 

NOW WE ARE GOING TO CREATE A POP-UP WINDOW LINK TO

EXPLAIN WHAT THE HECK "Card Security Code" is and how to locate

it.

 

#### OPEN ####

catalog/checkout_payment.php

 

#### FIND ####

</head>

 

#### BEFORE IT ADD ####

 

<script language="javascript"><!--

function popupWindow(url) {

window.open(url,'popupWindow','toolbar=no,location=no,directories=no,status=no,menubar=no,scrollbars=no,res

izable=yes,copyhistory=no,width=650,height=500,screenX=150,screenY=150,top=150,l

eft=150')

}

//--></script>

 

 

#### FIND THE SECTION ####

 

<?php

} elseif (isset($selection[$i]['fields']) && is_array($selection[$i]['fields'])) {

?>

<tr>

<td width="10"><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

<td colspan="4"><table border="0" cellspacing="0" cellpadding="2">

<?php

for ($j=0, $n2=sizeof($selection[$i]['fields']); $j<$n2; $j++) {

?>

<tr>

<td width="10"><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

<td class="main"><?php echo $selection[$i]['fields'][$j]['title']; ?></td>

<td><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

<td class="main"><?php echo $selection[$i]['fields'][$j]['field']; ?></td>

<td width="10"><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

</tr>

<?php

}

?>

</table></td>

 

#### CHANGE TO READ ####

#### MAKE SURE YOU CHANGE <YOUR DOMAIN> to your url ####

 

 

} elseif (isset($selection[$i]['fields']) && is_array($selection[$i]['fields'])) {

?>

<tr>

<td width="10"><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

<td colspan="4" class="main"><img src="images/cclogos.gif" alt="Cards We Accept"><table border="0" cellspacing="0" cellpadding="2">

<?php

for ($j=0, $n2=sizeof($selection[$i]['fields']); $j<$n2; $j++) {

?>

<tr>

<td width="10"><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

<td class="main"><?php echo $selection[$i]['fields'][$j]['title']; ?></td>

<td><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

<td class="main"><?php echo $selection[$i]['fields'][$j]['field']; ?></td>

<td width="10"><?php echo tep_draw_separator('pixel_trans.gif', '10', '1'); ?></td>

</tr>

<?php

}

?>

<tr>

<td colspan="5" class="main"><a href="java script:popupWindow('http://<YOUR DOMAIN>/catalog/csc.htm')"><u><font color="0000FF">Card Security Code Explanation</font></u></a></td>

<tr>

</table></td>

 

 

#### DID YOU CHANGE <YOUR DOMAIN> to your url ####

 

#### SAVE and CLOSE ####

 

#### FINAL TOUCHES ####

 

From PayPal Payflow Pro v1

http://addons.oscommerce.com/info/4805

 

AS STATED PREVIOUSLY WE ACCEPT ONLY VISA AND MASTERCARD

SO WE DO NOT USE THE amex.htm file. THIS INCORPORATES BOTH

 

#### UPLOAD TO /catalog ####

 

csc.htm, amex.htm

 

### UPLOAD TO /catalog/images ##

 

the images (you may have to edit them to fit your specific site)

 

#### IF YOU DO NOT ACCEPT AMEX YOU NEED TO REMOVE THE

#### CONFUSION FACTOR LIKE THIS

 

#### OPEN /catalog/csc.htm ####

 

#### FIND ####

<p>

<font face="Verdana" size="2"><a href="csc_amex.htm">Using American Express?</a></font><span style="font-weight: 400"><font face="Verdana" size="2"><br>

</font></span>

<br>

 </p>

 

#### DELETE IT ####

 

######################################

######################################

 

ISSUE #2 above

 

To resolve this you need to do a couple of things

 

#####################

Things you probably need to look at

 

How to implement Automated Clearinghouse (ACH) with Payflow Pro

https://cms.paypal.com/cms_content/US/en_US...yment_Guide.pdf

 

DID YOU BACK UP THE ORIGINAL FILES?????

 

#####################

AS IDENTIFIED IN ABOVE MANUAL from Table 8-5 ON PAGE 57

How to implement Automated Clearinghouse (ACH) with Payflow Pro

 

WE ARE GOING TO ADD A CHECK FOR Code 114 - CVV2 or CID Mismatch

 

DID YOU BACK UP THE ORIGINAL FILES?????

 

 

FROM PayPal Payflow Pro [New Version]

 

#### OPEN ####

catalog/includes/modules/payment/paypal_payflow_pro.php

 

#### FIND ####

 

} else if ($result_code == 12) {

$RespMsg = MODULE_PAYMENT_PAYPAL_PAYFLOW_PRO_TEXT_ERROR_DECLINED;

 

#### BEFORE IT INSERT ####

 

} else if ($result_code == 114) {

$RespMsg = MODULE_PAYMENT_PAYPAL_PAYFLOW_PRO_TEXT_ERROR_CVV2;

 

#### THIS WILL SEND THE CUSTOMER BACK TO THE CREDIT CARD ENTRY PAGE FOR A CVV2 ERROR ####

 

#### SAVE AND CLOSE ####

 

 

That's it Folks and Good Luck.

 

REMEMBER TO BACK UP THE ORIGINAL FILES AND TEST BEFORE USING ON LIVE STORE!!!!

 

BJ

Edited by Chadduck

Share this post


Link to post
Share on other sites
Hey,

 

I upgraded to PayFlow Pro v0.3. i need to know if this is enough and is it compatible with Paypal upgrades starting September 1.

 

Any help appreciated..

 

I myself am using this and after several separate conversations with Paypal - yes it is compatible.

 

BJ

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×