Configure Settings in Global Admin
Configure Settings in the Event Portal
Authorize.net Configurations
In order to be able to reuse or refund an existing credit card, Customer Information Manager (CIM) service will need to be activated in the Authorize.Net portal. Please see the following help article, and/or contact your Authorize.net representative for additional information: https://www.gatewaysetup.com/customer-information-manager
Please ensure that once you activated the portal you have reviewed its settings.
Additionally, please determine whether you are using Advanced Fraud Detection Suite and ensure that no transactions that may go through the portal are placed in either the Authorized/Pending Review or Pending Review states.
Configure Settings in Global Admin
First Time Setup
- Navigate to Event > Event Configuration > Preczn Payment Gateway Configuration
- In the Add Merchant section, enter a unique name (such as your Event Type - Processor Name), and click Provision Merchant Account.
- Select 'AuthorizeNet' and complete all fields, click Connect
- 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.
- Navigate to Event > Event Configuration > Preczn Payment Gateway Configuration
- 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.
- Navigate to Event > Event Configuration > Preczn Payment Gateway Configuration
- 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.
- 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
- Navigate to your Event Portal > Admin Panel > Payments > Payments Manager > Merchant
- Configure the Merchant section:
- Set the Gateway ID field to "Use config from Global Admin." Click Save.
- Set the Gateway Environment field to Production. Click Save.
- Update the Comment 1 field to mirror the text from Global Admin > Event Configuration > Payment Gateway Comment 1 field
- Update the Comment 2 field to mirror text from Global Admin > Event Configuration >Payment Gateway Comment 2 field
- 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.
- Navigate to your Event Portal > Admin Panel > Payments > Payments Manager > Invoice Configuration
- Select settings
- Under Invoice Type, select CompanyId + EventId
- Bill-to-Address Contact Type: This will pull the address of a specific contact type (such as the invoice contact) for all invoices.
- 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
- Additional Content: Add any specific payment information here
- 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
- Grant Exhibitor Access to view the My Account Invoice site page and statement report
- Navigate to Admin > Organizations Manager > Configuration > Contact Types
- 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')
- Navigate to Admin > Page Editor > /exhibitorhub to add My Account access directly from the exhibitor hub page
- Add HTML custom button that links directly to the /organizations/myaccount page
- 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)
Testing & Troubleshooting
- Create a $1 order for a test company in Global Admin
- Tip: When adding yourself as a contact to your test company, do not use your same email connected to your Event Portal Admin account.
- Login to your Event Portal and process a real $1 cc payment
- Use Global Admin to refund (Note: Authorize.net requires a 24-hour waiting period for refunds)
- Check all links
Common Errors in the Credit Card Log:
- This transaction cannot be accepted. - The error indicates they have not selected the check box to Disable Old Transaction Key(s). The client can either wait 24 hours for the old transaction key to become inactive or they can rest the API Login and check the box.
- This account has not been given the permissions required for this request. - This error most likely means the credentials were not put in the correct place in Event Configuration.
- User authentication failed due to invalid authentication values. - verify the credentials entered into Event Configuration.
- The merchant login ID or password is invalid or the account is inactive. - This error most likely means Transaction Key has been changed in Authorize.net, and must be updated in a2z. Or, Authorize.net representative should be contacted for further questions.
- The referenced transaction does not meet the criteria for issuing a credit. - ensure that Customer Information Manager (CIM) service is configured and there are no rules in place to prevent reusing the token from previous transactions.