cybersourcery | pain removal gem for working with Cybersource Secure

This generates 2 files: config/cybersourcery_profiles.yml and config/initializers/cybersourcery.rb.
Add it to your Gemfile and run bundle:
Run the config generator:
Add information about your Cybersource profiles to the config/cybersourcery_profiles.yml file. You must first create these profiles in the Cybersource Business Center. We recommend that you do not check this file into version control, since it will contain sensitive data about your Cybersource profiles.
Each profile in the yml file must have a key that corresponds to a "Profile ID" in the Cybersource Business Center. Each profile has the following fields: name: a human readable name service: test or live access_key: the access key for the profile secret_key: the secret key for the profile success_url: this is an optional field - if you provide it, you can redirect users to it after a successful transaction (it can be an absolute or relative URL) transaction_type: a Cybersource transaction type, for example: sale,create_payment_token. See the list of supported transaction types. endpoint_type: indicates the Cybersource URL endpoint appropriate for the transaction - supported values are: standard create_payment_token update_payment_token iframe_standard iframe_create_payment_token iframe_update_payment_token payment_method: card or echeck locale: any locale supported by Cybersource, for example, en-us currency: any currency supported by Cybersource, for example, USD unsigned_field_names: a comma separated list of the fields that will not be signed in the transaction - this typically includes all the visible fields in the credit card payment form
In your controller method for displaying your credit card form, you can add a line like this:. The first argument is the profile ID for the Cybersource profile you want to use.
For a successful transaction, the params must include an amount.
The params should not include any of fields in the cybersourcery_profiles.yml file's list of unsigned fields.
The form action URL is determined based on the information provided in cybersourcery_profiles.yml.
Calling the add_signed_fields helper method is crucial, for passing the signature and signed fields to Cybersource as hidden inputs.
Cybersourcery provides support for HTML5 front-end validation, but no specific approach to front-end form validation is required. As mentioned above, you can subclass the non-persisted Payment model to add your own fields and indicate which are required.
The optional call to the add_expiry_date_fields helper method makes it easy to include a month and date picker in your form that's appropriate for indicating credit card expiry dates. Used in conjunction with this javascript from the demo project, it will then submit a date in the user-unfriendly format that Cybersource requires.
The javascript file in the demo project also provides dynamic switching of the input type for the "State" field, based on whether the US is selected as the country (it provides a select list of states for the US, or a text input field for other countries).
The field_pattern and field_validation_message methods in the PaymentsHelper include only one pattern matching requirement, for the credit card number format. You can add your own pattern matching rules by overriding these methods, like this.