These are fields included in Elavon API requests.
Other fields are not included, and therefore you should not require these in your Elavon account (e.g., ssl_description
or ssl_card_type
). We don't have a reasonable way to assume values for other Elavon fields for all merchants using this plugin.
Any custom order info a merchant wants to include can be added via the wc_elavon_converge_credit_card_request_data
and wc_elavon_converge_echeck_request_data
filters the plugin provides.
One exception we've seen is the ssl_description
field, which for some reason is not recognized by the Elavon API even if added with our filters and thus cannot be set as required for any account.
ssl_transaction_type
ssl_merchant_id
ssl_user_id
ssl_pin
ssl_invoice_number
ssl_amount
ssl_salestax
ssl_first_name
ssl_last_name
ssl_company
ssl_avs_address
ssl_address2
ssl_city
ssl_state
ssl_avs_zip
ssl_country
ssl_email
ssl_phone
ssl_cardholder_ip
ssl_customer_code
ssl_card_number
ssl_exp_date
ssl_cvv2cvc2_indicator
ssl_cvv2cvc2
ssl_transaction_currency
(if Multicurrency enabled)
ssl_bank_account_number
ssl_aba_number
ssl_check_number
ssl_agree
ssl_bank_account_type
ssl_token
ssl_get_token
ssl_add_token
(always 'Y')
ssl_card_number
(if adding CC token)
ssl_exp_date
(if adding CC token)
ssl_txn_id
ssl_txn_id
ssl_amount