E-commerce Account Details

This article is for Administrators managing e-commerce accounts in Certain.

Processing Account Information

Processing Account Information is shown when configuring an e-commerce account. Most fields display regardless of the chosen online processor. Some fields display only under processor-specific headings.

• Descriptive Name for Processing Account — The name that appears in Certain for this processing account.
• Online Processor — The available online payment-processing gateways are: PayPal PayFlow Pro; Cybersource; Authorize.net; Pay.gov; Chase Orbital; Stripe; Shift4.
• Note: Shift4 is specific to the Accommodation section to generate payment tokens to be stored for room guarantee, and cannot be used in forms to process online payments.
• Currency — The currency selection uses the ISO Code and the currency name (for example, USD: US Dollar; EUR: Euro). Recommendation: set up separate sub-accounts for each currency group, and avoid mixing currencies for events in the same account.
• Exact Business Name on Merchant Account — The DBA ("Doing Business As") name listed with the bank on the merchant account; this is also the name that will appear on the payee’s credit card statement.
• This is the primary processing account — Select this to indicate that this is the default or primary payment processor for all events in this account.
• Enable this e-commerce account for events and forms in sub-accounts — If selected, the same e-commerce account will be available for use in events and their forms in sub-accounts. Note: If you have multiple levels of sub-accounts, this selection cascades down to all of them.
• Single transaction limit — The maximum amount on a single transaction to be allowed through the processing account. Most processors enable up to $25,000 per transaction; however, you may wish to reduce this limit if you know that your transactions will never exceed a certain amount. Default value: $1000. Warning: Never set the single transaction limit to blank or zero ($0.00). If it is blank or zero, then a registrant would see the message “The transaction amount exceeds the limit for this event.”
• The single transaction limit can be set on the following two pages in Certain: Account > Account Settings > Registration > Financial Data > E-commerce; Event > Plan > Event Setup > Payments.
• Available Payment Methods — Select only those payment methods that have been actually configured by your bank for this merchant account. Certain currently support the following credit card payment methods: Visa; MasterCard; Amex; Diners; DiscoverCard; IPAC; JCB. The list of card types available for selection is determined by the Online Processor selected.
• Collect Billing Address — Collect a separate billing address for the payor. This can be used with credit card transactions to perform AVS validation.
• Match Zip Code — Require that the billing zip code entered on the form match the billing zip code for the credit card.
• Match Street Number — Require that the billing street address entered on the form match the billing street address for the credit card.
• Require AVS "Yes" Response — Address Verification Service (AVS) is offered by many issuers and enables the merchant to compare the street number and/or zip code provided by a cardholder to those on record with the card issuer. Whether these fields are available depends on the Online Processor selected; not all processors support AVS.
• Collect CSC Number — Add a field on the form to collect the Card Security Code for the credit card (CSC/CVC2/CVV2/CID).
• Require CSC "Yes" Response — Require that the CSC entered on the form match the CSC for the credit card.
• Auto-enforce CSC — If this check box is selected, then Collect CSC and Require CSC 'Yes' Response are both selected and cannot be cleared. When this processor account is assigned to an event, the Collect CSC and Require CSC 'Yes' options will both be selected (and disabled from being cleared) in these two places: At the event level (Plan > Event Setup > Financials), and at the form level (Plan > Forms > Payment).
• Note: Disabling CSC/CVC and Address Verification options at the account level will not disable the same options in forms and events. The setting must be disabled in those accounts on a per-form and per-event basis.
• User Notes — Enter any useful reference information, for internal use.

Processor-specific fields

Setting Up a PayPal Gateway Account

• Account Merchant/Vendor ID — The unique identifier assigned by the online payment processor. Note that each processing account's Account Merchant/Vendor ID must be unique.
• Account Partner ID — Used by PayPal to identify the partner company who set up the PayPal account.
• Account User ID — Used by PayPal as a secondary level of security for the PayPal account. If you don't have a unique User ID, it will default to the Vendor ID.
• Account Password — The secret code required to access the processing account. Click the Generate New link to create a random, secure password automatically.
• PayPal Manager URL — Click this link to access the detailed transaction information for your account. PayPal stores information not available in Certain, such as the card issuing bank's authorization number and voice authorization information. It is useful for reconciling bank statements and tracking down discrepancies. You should also periodically (quarterly or annually, at least) change the password to your PayPal account, and then update that password in Certain.
• If AVS is performed on the transactions processed in your account, then each individual sale processed in Certain will record 3 transactions in PayPal: an Auth for $0.01, a Void of the $0.01 Auth, and a Sale for the full amount. In order to see only the actual Sale transactions, use the PayPal custom report generator to create reports that do not display these Auth and Void transactions.
• Important Note for UK customers: PayPal UK no longer supports the "PayFlow Pro" product to which Certain integrates, so UK based customers should consider using Stripe instead.

Setting Up a Pay.gov Account

• Agency ID — The unique customer identifier for the application provided by Pay.gov.
• Form ID — The assigned form identifier from Pay.gov used to look up the applicable collection options for the government agency.
• Currency — Only US Dollars (USD) are offered for Pay.gov transactions.
• Pay.gov Account Username — The user name provided by Pay.gov to access their reporting system.
• Pay.gov Account Password — Corresponding password to access Pay.gov reports.
• Pay.gov Reports URL — URL to log in to the Pay.gov reporting system which should always be https://www.pay.gov/paygov/
• Single transaction limit — The largest single transaction that you wish to be allowed through the processing account.
• Available Payment Methods — Pay.gov supports all major credit card types (Visa, MasterCard, Amex, Diners, Discover) as well as ACH payments. AVS and CSC checks are not offered by the Pay.gov configuration for Certain.

Note: AVS and CSC checks are not offered by Pay.gov for Certain.

Setting Up a Cybersource Account

• Merchant ID / Account Username — The unique identifier for the CyberSource account; this is required.
• Transaction Key for Live Transactions — Required.
• Transaction Key for Test Transactions — Required.
• Business Center Password — Required.
• Confirm Business Center Password — Required.
• CyberSource Business Center URL — URL to the CyberSource Business Center.

Setting Up an Authorize.Net Account

• Authorize.Net API ID — Uniquely identifies your account to the payment gateway when transactions are submitted. Supplied by Authorize.Net when you set up your account with them. This is separate from the ID to Authorize.Net's Merchant Interface, although in some cases it may be the same.
• Transaction Key — A 16-character randomly-generated password used with the API ID to authenticate your account as an authorized Authorize.Net user when transactions are submitted. Click Generate New to log into Authorize.Net's Merchant Interface website and generate a new key, which you then need to enter immediately on this page in Certain as well.
• Authorize.Net Test POST URL — The URL assigned by Authorize.Net to be used for test transactions.
• Authorize.Net Production POST URL — The URL assigned by Authorize.Net to be used for live transactions.
• Note: AVS and CSC checks for Address Verification Service (AVS) and Credit Card Security Code (CSC) checks can only be configured on Authorize.Net's Merchant Interface; these fields are not included on this page.

Setting Up a Stripe Account

• Stripe Secret API Key — Required.
• Merchant Account URL — Required.
• Stripe Publishable API Key — Required.

Setting Up a Chase Orbital Account

• Merchant ID — Required.
• Terminal ID — Required.
• Orbital Username — Required.
• Orbital Password — Required.
• BIN — Required. The Transaction Routing Definition assigned by Chase Orbital. The following BINs apply to the corresponding Chase payment platforms: 000001 – Salem/Stratus; 000002 – TampaTandem.

Setting Up a Shift4 Payments Account

• Merchant ID — Required.
• Authorization Token — Required.
• Note: Shift4 Payments can be used in an Accommodations form section to generate a payment token to be stored for room guarantee.

Was this article helpful? 0 out of 0 found this helpful

Have more questions? Submit a request

Related articles

• Financial
• Logic Rules (Attendee Form)
• E-Commerce FAQ - Planning for E-commerce
• Administrators - Enabling E-Commerce for Payment Processing

Comments 0 comments Please sign in to leave a comment.