E-commerce accounts connect your registration forms to your payment processor so registrants can pay online. You set them up once for the account, then pick one for each event. Only Administrators can see this page.

Where to find it

Go to Account Settings > Registration > Financial Data. The page has these sections:

• E-commerce Accounts: processor accounts you set up with your own credentials. Click Add New, or edit an existing account.
• Connected Stripe Accounts: Stripe accounts connected to Certain.
• PayPal Seller Onboarding: PayPal accounts onboarded to Certain.
• Tax Code Settings: tax codes every event in the account can use.

Fields for every processor

Most fields are the same for every processor. A few extra ones depend on the processor you pick, listed below.

• Descriptive Name for Processing Account: the name you'll see in Certain.
• Online Processor: Authorize.Net, Chase Orbital, Cybersource, Pay.gov, PayPal, PayPal - Connect, Shift4 or Stripe - Payment Intents. Certain doesn't work with PayPal's consumer-to-consumer product. Shift4 is only for collecting a card to guarantee a hotel room in an accommodation section; it can't take form payments.
• Currency: the currency for this account. If events in one account use different currencies, keep them out of the same financial consolidation reports, or filter those reports by the Currency Code column. A separate sub-account per currency makes this easier.
• Exact Business Name on Merchant Account: the "doing business as" name on your merchant account. It's what shows on the cardholder's statement.
• This is the primary processing account: makes this the default for events in the account. Events can still pick a different one.
• Enable this e-commerce account for events and forms in sub-accounts: lets sub-accounts use it too, at every level below.
• Single Transaction Limit: the largest single payment allowed. The default is $1000. Most processors allow up to $25,000.

• Card types: select only the cards your bank has set up for this merchant account. The list depends on the processor.
• Collect Billing Address, Match Zip Code, Match Street Number and Require AVS "Yes" Response: address checks. Not every processor supports them. See E-Commerce FAQ - Planning for E-commerce for how each setting decides whether a card is accepted.
• Collect CSC Number and Require CSC "Yes" Response: ask for and check the card security code (also called CVC or CVV).
• Auto-enforce CSC: when checked, both CSC options are turned on and locked, and they stay locked on any event and form that uses this account.
• User Notes: internal notes.

Processor-specific fields

PayPal

• Account Merchant/Vendor ID: must be unique across processing accounts.
• Account Partner ID: the partner company that set up the PayPal account.
• Account User ID: a second level of security. If you don't have one, it defaults to the Vendor ID.
• Account Password: click Generate New for a random secure password. Change your PayPal password regularly, and update it here each time.
• PayPal Manager URL: opens PayPal's transaction details, useful for reconciling statements.

Certain sends the event code in PayPal's "Comment1" field and the registration code in "Comment2". Add these to your PayPal reports to match payments to registrations. If you use address checks, each sale shows in PayPal as three transactions: a $0.01 authorization, a void of it, and the sale.

PayPal UK no longer supports the PayPal product this connection uses, so UK customers should use Stripe instead.

Pay.gov

Mostly used by government agencies. Fields: Agency ID, Form ID, Pay.gov Account Username, Pay.gov Account Password and Pay.gov Reports URL. Only US dollars are offered. Pay.gov takes the major card types and ACH (bank-to-bank) payments. Address and CSC checks aren't available.

Cybersource

Merchant ID / Account Username, Transaction Key for Live Transactions, Transaction Key for Test Transactions, Business Center Password (and confirmation) and CyberSource Business Center URL. Registrations marked Test use the test key. All others use the live key.

Authorize.Net

• Authorize.Net API Login ID: from Authorize.Net. It's separate from your Merchant Interface login. If it changes, update it here right away.
• Transaction Key: click Generate New to open Authorize.Net's Merchant Interface, make a new key there, and enter it here right away.
• Authorize.Net Test POST URL and Production POST URL.

Address and CSC checks for Authorize.Net are set in Authorize.Net's Merchant Interface, not on this page.

Stripe - Payment Intents

Stripe Secret API Key, Stripe Publishable API Key and Merchant Account Login URL.

Chase Orbital

Merchant ID, Terminal ID, BIN, Orbital Username and Orbital Password. BIN 000001 is Salem/Stratus and 000002 is Tampa/Tandem.

Shift4

Merchant ID and Authorization Token. Used only to collect a card to guarantee a hotel room.

Use the account in an event

Pick the account for the event under Plan > Event Setup > Financials, then turn on Process payments online for this form on each form's Payment page. See Payment Options (Registration Form)

Next step: After you save the account, run a test payment before you open registration.