Author Topic: When CC charge fails, Civi should NOT complete Profile / CMS ID Creation (Read 1164 times)

mdlueck · April 26, 2011, 06:49:40 am

We just recreated our four site Membership Join Contribution pages last evening, and I am working through testing them now.

The Contribution page for site yearly memberships receives a PayJunction error, thus the charge is not completed.

Code: [Select]

Yearly Membership using Credit Card
 Registration successful. You are now logged in.
  Payment Processor Error message: FE:dc_schedule_periodic_type is required.

However the Profile attached to the Contribution Page, which that creates a Drupal account, does succeed.

aaaakkkk!!! Process should be that unless the CiviContribute charge is successful, should not go off saving the profile nor creating a Drupal account.

Is there a logical reason why the code is doing what it is doing, or can this be turned into a bug report to get fixed?

And I need to check with the application people... I seem to remember that site yearly memberships were only suppose to send a reminder email when the year is coming due, not auto renew. In that case, it would be incorrect to set up a PayJunction auto recurring transaction in this case. I believe we only auto recur for monthly memberships.

mdlueck · April 26, 2011, 08:46:27 am

I checked with the application team. Seems for our purposes, we have no need for reminder emails for monthly memberships, only the yearly ones.

For yearly: A reminder email goes out N days before renewal to notify the member that their card is going to be charged for another year's site membership.

For monthly: No reminder emails are suppose to go out.

So, seems there is a legit problem with Civi / PJ and yearly recurring transactions.

Donald Lobo · April 26, 2011, 09:38:58 am

this is due to the asynchronous nature of IPN. We have no idea if the transaction will succeed or fail and when the IPN will come back

If this is an issue, you might want to consider using something like PayPal Pro or Authorize.net (but then u'll need to ensure u meet the PCI DSS standards etc)

this is unlikely to change in the near future and if/when it does it will be a fairly significant change

lobo

mdlueck · April 26, 2011, 10:27:09 am

I had no idea what Civi is sending PJ for the yearly transaction, here is an Rx from PayJunction tech support:

Quote

Hi,

"yearly" is not a valid option.

Rather than "yearly", you should use the following:

dc_schedule_periodic_number=12
dc_schedule_periodic_type="monthly"

In other words, "every 12 months".

With Kindest Regards,
Alex Estrada

Senior Tech Support Rep
PayJunction, Inc.

We adjusted our CiviMember membership for yearly to be "for 12 months" instead of "yearly". Now new join processes successfully charge with PayJunction and we are no longer getting the "dc_schedule_periodic_type" error.

Lobo, I will send your response back to Alex to get his take on it. Supposidely there is no async IPN with PayJunction. "All that PJ is going to say about the transaction it says as the return code when transactions are sent to PJ."

Straight up plain donation transactions consistently get to "Completed" state through PayJunction. Only site memberships are the ones getting stuck in "pending" state.

However, this specific situation was worse than getting stuck in "pending" state... member's CC's were never getting charged the way we had it first configured.

CiviCRM Community Forums (archive)

News:

Author Topic: When CC charge fails, Civi should NOT complete Profile / CMS ID Creation (Read 1164 times)

mdlueck

When CC charge fails, Civi should NOT complete Profile / CMS ID Creation

mdlueck

Re: When CC charge fails, Civi should NOT complete Profile / CMS ID Creation

Donald Lobo

Re: When CC charge fails, Civi should NOT complete Profile / CMS ID Creation

mdlueck

Re: When CC charge fails, Civi should NOT complete Profile / CMS ID Creation