[microtune]

I installed the file and it works great. Thank you for your help!

[microtune]

Thank you! It worked. I appreciate your help.

[microtune]

Thank you for your reply.

I would like to clarify my issue. The {shipping_info} tag does work in the sense that it displays the shipping address. However, it does not show the shipping NAME. My problem is that when the billing NAME and the shipping NAME are different, only the billing NAME is available in the form of the {first_name} and {last_name} tags.

I need to receive both the billing and shipping NAMES for my records. Ideally, I would like the shipping first name and shipping last name to be part of the {shipping_info} tag.

In the reply above by Key Master said:

“Thank you for the details. I hae made small modification to the plugin to include the name in the {shipping_info} email tag for authorize.net checkout.”

Could this be done for Stripe, as well?

Thank you again!

[microtune]

Hello,

I have the same exact problem as above, but with the Stripe payment gateway. When I use the {shipping_info} tag, it does not show the shipping name.

Could you please help me with this?

Thank you!

[microtune]

Yes, please see the thread above. I did explain that to my client, but that option was too expensive.

[microtune]

It is best explained by the chosen answer at this forum:

http://stackoverflow.com/questions/22855642/paypal-dprp-is-disable-for-live-account-error

New PayPal Pro accounts are Payments Pro 2.0 which works on the PayFlow gateway instead of DoDirectPayment and CreateRecurringPaymentsProfile.

[microtune]

Hello, thank you for your effort but this issue has been resolved. We have concluded that the issue was that the type of PayPal Pro account my client had was not compatible with the DoDirectPayment API the plugin uses.

My client has since switched to Stripe which is now working OK. We do not have a PayPal account anymore to test.

If you were referring to the Stripe issue I had, that was caused by an accidentally enabled incompatible plugin. I have addressed that in the other thread.

Thank you again.

[microtune]

I wish I knew that! I think it is too late for my client now. She already closed her PP account and set up Stripe. Assuming I can get that to work, she will probably stay with that solution.

Thank you for your kind help.

Do you plan to write an integration for Payflow Pro in the foreseeable future?

[microtune]

Thank you,

Yes, my client was using PayPal’s Payflow Pro. Upon further research I advised her to try to switch to PayPal Website Payments Pro 3.0 with the DoDirectPayment API, but she declined to pay the extra cost.

I am trying to set up the membership payment now with Stripe. Unfortunately, I am having trouble with that one, as well. I just posted on the forum about it. I hope you can help me with that.

I think as a resolution to the original problem for future visitors, the conclusion is that one needs PayPal Website Payments Pro 3.0 with the DoDirectPayment API as opposed to PayPal PayFlow Pro (which is the default PayPal setting for new “Pro” accounts). One has to phone PayPal customer support to request that service, it cannot be set up online. Please correct me if I am wrong.

[microtune]

Hello,

Was a solution ever found for this problem?

I have the same situation as described above. I would like to set up a subscription, and get the same message when attempting to process:

Error Type: paypal

Error Code: 11586

DPRP is disabled.

DPRP is disabled for this merchant.

API settings are correct.

It seems that PayPal has changed the workflow since this plugin was written.

I talked to PayPal, they said that I should use the following credentials:

Partner: PayPal

Merchant Login

Password

Please let me know if anyone has been able to use this plugin with PayPal subscriptions recently, and if yes, what they needed for the correct setup.

Thank you!

[Author]

Posts