Skip to content

PayJunction Configuration

Setting up a Test Account

PayJunction has a sandbox account that is open to the public to use. To use it follow these steps:

  • Set up your CiviCRM payment processor by going to Administer CiviCRM >> Global Settings >> Payment Processors >> New Payment Processor
  • Select "PayJunction" as the payment processor type
  • Enter the following details under Test Payment

Running a Test Charge

Test your payment processor by following these steps:

  • Set up contribution page in CiviContribute (see documentation)
  • Select your PayJunction payment processor as that contribution page's processor
  • Run your contribution page in Test mode
  • For the financial information enter the following:
    • Card Type: Visa
    • Card Number: 4444333322221111
    • Code: 999
    • Expiration Date: Any date in the future
  • Make sure your charge is not huge - suggest something like $10.77, so it is easy to identify among the thousands of other test charges in PayJunction

Repetitive charges

PayJunction will not allow you to charge the same amount to the same card within a 10 minute period, so keep this in mind when testing

View Your Test Charges

After submitting a charge via CiviContribution or other Civi module, you can view your charges by following these steps:

  • Go to PayJunction Demo site
  • Click on "Merchant Login"
  • Login to the test account with Username: payjunctiondemo, Password: demo123
  • In the top menu, go to "Batches/History", then click on "View Current Batch".
  • Recurring transactions can be found by going to "Recurring", then "Recurring Overview".

Setting up a Live Account

Follow the same steps above, but you'll need to get an account at PayJunction.

Recurring Contributions

The PayJunction payment processor will handle recurring contributions, but currently it will only create a single initial contribution in the CiviCRM database. PayJunction will keep processing recurring payments based on the schedule requested by the donor, but there is no call-back procedure to CiviCRM to let it know that follow on contributions or charges have been processed. Phase2 Technology, contact Michael Morris at mmorris at phase2technology dot com) has developed a Drupal module that performs automatic processing of subsequent recurring contributions in the CiviCRM database, but the process is prone to getting out of synch if the actual charge from PayJunction fails, e.g., due to expired card, etc. So, the module assists in managing your recurring contributions, but there is still some manual effort involved.

Future handling of recurring contributions

Future versions of CiviCRM may have a better solution for handling recurring contributions from payment processors that don't have a charge call back feature, like PayJunction.

Because of the situation described, the version of the PayJunction processor that shipped with CiviCRM1.9 is not enabled for recurring contributions right out of the box. This was done in order to reduce confusion and to not lead users on that the PayJunction payment processor is a fully fledged, front to back, recurring contribution solution. However, if you are willing to accept the limitations described above, the processor is able to submit recurring contributions to PayJunction. To activate that functionality, a small change needs to be made to the CiviCRM database.

Enabling the PayJunction processor to handle recurring contributions

Run the following query on your CiviCRM database:

update civicrm_payment_processor set is_recur=1 where name='PayJunction';

Once this is done, a checkbox will appear on your Contribution Amount set up page that allows you to enable Recurring contributions for that Contribution page.