Articles in this section

PayPal Configuration

Avatar
John Mackenzie
Updated
Follow

Configure Settings in Global Admin

Configure Settings in the Event Portal

Testing

 

Configure Settings in Global Admin

First Time Setup

  1. Navigate to Event > Event Configuration > Preczn Payment Gateway Configuration
  1. In the Add Merchant section, enter a unique name (such as your Event Type - Processor Name), and click Provision Merchant Account.
  1. Select 'PayflowPro' and complete all fields, click Connect (Credentials to enter into the system are the same ones that must be entered into manager.paypal.com)
  1. In Event Configurations, complete the following fields:
  • Payment Gateway Comment1 prefix in Comment 1 which will appear along with the company identification.
  • Payment Gateway Comment2 an additional comment field if desired.

Additional Event, Same Merchant Setup

This is for events that have the same merchant and credentials as the other events in the system are already configured. 

  1. Navigate to Event > Event Configuration > Preczn Payment Gateway Configuration
  1. Select the existing merchant from the Connect Existing Merchant to Event dropdown

 

Note: If password has been updated since the last event, updating in one event will sync it across ALL connections for that merchant.

Additional Event, New Merchant Setup

This is for additional events that have the same merchant with different credentials or a completely different merchant account.

  1. Navigate to Event > Event Configuration > Preczn Payment Gateway Configuration
  1. Complete Add Merchant section, enter a unique name for the merchant connection (such as Event Type_Processor Name) and click Provision Merchant Account to pull the client's connected account credentials.

  2. Continue with credential entry. If different merchant (Authorize.net, 8am) please see setup article for those specific merchant accounts if you'd like to see screenshots for specific fields. Setup steps will be the same as above.

Configure Settings in the Event Portal

Portal Connection & Environment

  1. Navigate to your Event Portal > Admin Panel > Payments > Payments Manager > Merchant
  2. Configure the Merchant section:
    1. Set the Gateway ID field to "Use config from Global Admin." Click Save.
    2. Set the Gateway Environment field to Production. Click Save.
  3. Update the Comment 1 field to mirror the text from Global Admin > Event Configuration > Payment Gateway Comment 1 field
  4. Update the Comment 2 field to mirror text from Global Admin > Event Configuration >Payment Gateway Comment 2 field
  5. Ensure the Required Payment Fields mirror those set in your payment processor 

 

Invoice Configuration

Please work with your project manager to ensure changes here are consistent with your invoices in Global Admin.

  1. Navigate to your Event Portal > Admin Panel > Payments > Payments Manager > Invoice Configuration
  2. Select settings
    1. Under Invoice Type, select CompanyId + EventId
    2. Bill-to-Address Contact Type: This will pull the address of a specific contact type (such as the invoice contact) for all invoices. 
    3. Hide Payment Schedule: Select this box if you would like to hide the payment schedule on both the invoice screen and the PDF download from Event Portal
    4. Additional Content: Add any specific payment information here
    5. Invoice Logo: If you would like the system to pull a specific logo you may utilize this field, otherwise the system will use the Large Logo from the site header

 

My Account Access

  1. Grant Exhibitor Access to view the My Account Invoice site page and statement report
  2. Navigate to Admin > Organizations Manager > Configuration > Contact Types
  3. Select the Invoice Access radio button for all contact types you wish to have access to the invoice and make payments (note: these contact types much also be set as 'allowed')
  1. Navigate to Admin > Page Editor > /exhibitorhub to add My Account access directly from the exhibitor hub page
    1. Add HTML custom button that links directly to the /organizations/myaccount page
    2. Be sure to remove any old exhibitor console link blocks that may direct exhibitor to a different site (if you previously used any legacy account pages, your project manager has placed a redirect on those pages that will take exhibitors back to the event portal to avoid any confusion)
SS10-Setup Exhibitor Hub Buttons.png

 

Testing

  1. Create a $1 order for a test company in Global Admin
    1. Tip: When adding yourself as a contact to your test company, do not use your same email connected to your Event Portal Admin account.
  2. Login to your Event Portal and process a real $1 cc payment 
    1. Use Global Admin to refund (Note: Authorize.net requires a 24-hour waiting period for refunds)
  3. Check all links

 

Suggested Payment Configurations within PayPal

 

PayPal Support (How to obtain the Account and Credentials) : Click Here

  1. User Predefined Role = FULL_API_ACCESS​ (API_FULL_TRANSACTIONS)
     

  2. Block Accidental Payments = No, allow multiple payments per invoice IDA2Z only stores one Invoice ID per company/per event, and if an exhibitor wants to make more than one payment against the Invoice ID, this setting will allow them to do so.

    To update the block accidental payments setting, follow these instructions below:

    • Log in to your PayPal account
    • Hover over your Name on the top right
    • Click on Account Settings
    • Click on Payment preferences then update next to Block payments

    There will be the setting "Block accidental payments" as the second setting.

    PayPal.png

  3. Allow Reference Transactions = Yes

    When you perform a transaction, you generate a Transaction ID. You can use this ID, or token, to initiate subsequent transactions, even when you're not storing the credit card information in your local database. This can save you from

    Having to ask the buyer for their credit card ID again.
    The burden of complying with PCI requirements for storing credit card information.

    For Reference Transactions only PayPal's customer service team has access to the tool to request reference transactions. It requires a back end team to review your account, and they will perform a credit check. If your account qualifies for reference transactions after being reviewed by a back end team, then it will be enabled on your account. 
     

    To enable reference transactions on your account, please work with the customer support team.

    • Log in to your account at www.paypal.com.
    • Click Help at the top of the page.
    • Click Help Center at the bottom of the page.
    • Scroll to the bottom and click "Contact Us"
    • Choose "Message Us" at the bottom.
       

Troubleshooting

Error Codes

  • 15005: Processor Decline - This transaction cannot be processed.
  • 15006: Processor Decline - This transaction cannot be processed. Please enter a valid credit card number and type.
  • 15007: Processor Decline - This transaction cannot be processed. Please use a valid credit card.


Cause
Error codes 15005, 15006 and 15007 all indicate a processor decline. Processor declines result directly from the financial information entered and aren't under PayPal's control.

Solution
The merchant must request that the buyer either use a different funding source for the payment, or contact their issuing bank (call the customer service number on the back of the credit card being declined).

Note: PayPal doesn't give merchants specific reasons for payment declines. If more information is required, have the buyer contact PayPal Business Support.

In general:

  • 15005 errors result from an AVS decline, usually caused by the billing address not matching the card issuer's information on file. The card-issuing bank may also have declined the transaction due to lack of funds.
  • 15006 errors occur when a hold exists on the card or the card-issuing bank's system has flagged it.

Field format error: 91537-Purchase order number is too long.Purchase order number must be 17 characters or shorter and can only contain printable ASCII characters.

  • a2z Event Name is passed to Purchase Order Number in Paypal. This field is only 17 characters long on PayPal side, and if the event name is longer than that, they send a code that refuses the transaction.  Please shorten the name of the event to be 17 characters or fewer.

Generic processor error: 10001-Internal Error

  • This is an internal error on PayPal side and must be diagnosed by them.  No further information is available to us.

User Authentication Failed

See full support article here: https://www.paypal.com/us/smarthelp/article/why-did-i-get-the-error-user-authentication-failed-or-merchant-identification-error-ts1223 

The most common issues are:

- The account credentials are incorrect

- In some instances, special characters in the Password field can cause issues

- The client has restricted PayFlow Pro to specific IP addresses:

 

A2Z PayPal IP (as of 5/15/2026)

  • 3.215.93.31 
  • 3.212.249.119
  • 204.236.228.163
  • 50.16.48.23
  • 52.27.132.25
  • 100.21.136.206

    mceclip0.png

Related articles

Powered by Zendesk