PayPal payments do not work

From Kolmisoft Wiki
Jump to navigationJump to search

Troubleshooting

  • Check /home/mor/config/environment.rb file and make sure variable Web_URL matches the IP or Hostname to which your user comes to your site.

Example:

If your site is http://www.mycompany.com and your IP is 22.33.44.55, then in Web_URL you should put http://www.mycompany.com, not the IP!

You need to restart Apache after you made changes to environment.rb file. 

/etc/init.d/httpd restart



Payment options are not shown for users

Disable option "Hide payment options for postpaid users" in SETTINGS > Setup > Settings > Visual.

User sees payment option but not authorized to view this page

Please make sure that Payments permission is enabled for the user.
https://wiki.kolmisoft.com/index.php/User_Permissions



No (Unnotified payment)

This value is assigned before the transaction to PayPal. When the transaction is completed this value is changed accordingly to the response got from PayPal

Reasons for this might be:

  • MOR does not get a response from PayPal - this might be if:
    • you are using unsupported type of PayPal gateway. MOR supports: Website Payments Pro (in Payment Gateway Addon) and Personal
    • your IPN is disabled by PayPal. PayPal sends an email with warning. Links to check IPN: Setting Up IPN Notifications on PayPal, Check the IPN History
    • IPN Troubleshooting Tips
      • IPN failures fall into three categories: not receiving any IPN messages from PayPal, receiving some but not all IPN messages, and receiving INVALID messages from PayPal after responding to a message.
      • If you do not receive any IPN messages from PayPal:
        • Check the IPN History page on PayPal. It tells you whether PayPal sent the IPN message and whether your listener responded to it. It may also provide information about the status of the server on which your listener is running. If necessary, from this page you can also request that PayPal resend the IPN message.
        • Check that the path to your IPN listener is correct and you are using that path correctly in your IPN notification URL; for example, the file path is often similar to, but not the same as, the URL. (Example: http://your_domain/billing/payments/paypal_ipn)
        • Verify that your firewall settings are not blocking HTTP POST messages from PayPal.
        • If the logs for your web server are available, check the logs to confirm that messages are being sent to your web server and check for any errors that may have occurred. (Logs are in /tmp/mor_debug)
      • If you receive some messages but not others:
        • Verify that your IPN listener is responding to all messages, even those you do not intend to process.
        • Check that the account is valid and confirmed; for example, if you send money to an unconfimred account, PayPal does not send an IPN message.
      • If you receive an INVALID message
        • Check that your are posting your response to the correct URL, which is https://www.sandbox.paypal.com/cgi-bin/webscr or https://www.paypal.com/cgi-bin/webscr, depending on whether you are testing in the Sandbox or you are live, respectively.
        • Verify that your response contains exactly the same IPN variables and values in the same order, preceded with cmd=_notify-validate.
        • Ensure that you are encoding your response string and are using the same character encoding as the original message.
      • Note:
        • If you receive multiple IPN messages for the same transaction or if messages appear to be out of order, this is not necessarily an indication that your listener is malfunctioning. For example, if you do not respond in time, PayPal resends the message. You should investigate these situations; however, because they could be caused by a logic errors or performance problems as wel
  • Server has no route to paypal - this means either a DNS problem or a network issue. Connect from console to server to check if paypal page is reachable. For example by using Lynx
  • User did not completed the payment



Payment was unsuccessful, details from Gateway: Security header is not valid

As Satish points out, if you want to test in the Sandbox, you *MUST* generate a new set of API credentials from within the Sandbox account. The Security Header Not valid error means you are using a set of credentials that are not valid for the chosen environment. You cannot use your Live credentials with the Sandbox - they are completely separate environments.

To get a PayPal Live certificate.

1. log in to https://www.paypal.com.

2. click on "My Account" then "Profile".

3. click the API Certificate Request link.

4. enter API Username(from paypal page) in Login field in MOR PayPal payments PRO gateway

5. enter API Password(from paypal page) in Password field in MOR PayPal payments PRO gateway

6. enter Signature in(from paypal page) in Signature field in MOR PayPal payments PRO gateway

Payment was unsuccessful, details from gateway: This transaction cannot be processed due to an invalid merchant configuration.

1. login to your Paypal

2. then go to Merchant Services

3. Choose Website Payments Pro

4. Choose Accept Billing Agreement

  • You are using an unsupported PayPal account in MOR



We are not able to process this transaction because of a problem with the PayPal email address supplied by the seller.

Email used to pay money does not match email in User's MOR account.

You don't have permission to access "/cgi-bin/webscr" on this server.

Paypal security issue. Please contact paypal support.

See also

Retrieved from "https://wiki.kolmisoft.com/index.php?title=PayPal_payments_do_not_work&oldid=27114"