• Home

Contents Registration Payments Features Usage Making Payments Deferred Payments Credit Cards Card Declines E-Checks Bounced Checks Data Security

Registration Payments

We support a variety of methods for payment.

This is a general overview of the purpose and intent of this feature. If there is more text, it should wrap around the table of contents which appears up at the top right as well.

default size of 400x300

next size up at 640x480, max is about 750 so this is a safe "large" size

Features

Optional section to describe sub-features of this feature. E.g., for Segments, we might list permanent numbers, class and group options and class-group mappings, either as a bulletpoint or with a short description. We can omit this altogether if appropriate. Try to keep short.

Usage

1. Making payments
2. Deferred payments
3. Credit Cards
   1. Card Declines
      1. Address or security code mismatch
      2. 5-digit or 9-digit zip code
      3. Expiration date
4. E-Checks
   1. Bounced checks
5. Data Security

Making Payments

(screencast would go here if available. Max width is about 750px.)

Deferred Payments

This is a detailed approach for method number two.

Credit Cards

This is a detailed approach for method number three.

Card Declines

This is a detailed approach for method number three.

E-Checks

This is a detailed approach for method number three.

Bounced Checks

This is a detailed approach for method number three.

Data Security

As a merchant, we are required to comply with the Payment Card Industry Data Security Standards (aka PCI DSS). PCI DSS is a comprehensive set of more than 200 requirements that applies to any merchant account holder who transmits, stores or processes credit cards. If an organization ever sees the 15 or 16-digit credit card number, even for a split second before sending it to a payment gateway, they are required to comply with the full scope of PCI DSS.

During 2007-2008, we attempted to build and maintain the infrastructure required for compliance in-house before finding it would require at least one full-time person dedicated only to maintaining compliance. Unlike what many solution providers pitch, PCI DSS is not a "set it and forget it" checkbox on a form. It requires daily review of log files, quarterly third-party network scans and annual on-site audits for large merchants. Because hackers are constantly finding new ways to compromise servers and steal data, actual, effective security that protects your personal information in the same way we would like our data to be protected requires daily vigilance and resources that no small business can realistically provide.

The only answer is to leverage the expertise and products of partners. At MotorsportReg.com, we sought out the best in the industry to help us be both compliant and secure. Our partners and their networks completely handle authorizing, storing and processing credit cards and are PCI DSS Level 1 Validated in top-tier SAS70 data centers with annual, on-site audits by third party auditors.