Payment page requirements

Your payment page must include all required information.

Requirements for credit card payment pages

For credit card payments, it’s important that you gather the appropriate cardholder details in your payment form. Cardholder details fall into one or more of the following categories:

Cardholder dataWhy collect it?
card numberRequired for successful transaction (On a hosted fields form, this must be a hosted field.)
card expirationRequired for successful transaction.
card CVVRequired payment field for merchants; required payment field for partners. (On a hosted fields form, this must be a hosted field.) Collecting CVV helps prevent fraud and reduce the probability of chargebacks. If you don’t collect CVV and the cardholder disputes a charge, the chargeback committee will likely rule in favor of the cardholder and return funds.
cardholder nameOptional. If you’re using an external system to manage customers, be sure to map the “name” field in that system to the name property on card or bank objects in the AffiniPay system; otherwise, transactions will show up in the AffiniPay system without a name.
emailOptional
address 1Required payment field for merchants. If you don’t submit this information, you may not get the best processing rate.
address 2Optional
cityOptional
stateOptional
postal codeRequired payment field for merchants; required payment field for partners (for manually-keyed transactions). If you don’t submit this information, you may not get the best processing rate.
countryOptional
phoneOptional

See the token object type for parameter names and descriptions of these fields.

Requirements for eCheck payment pages

Electronic check (eCheck) payments move funds electronically between banks using routing and account numbers.

Check whether the merchant can take eCheck payments

Before a merchant can take eCheck payments in your application, they must be eCheck-enabled in LawPay/CPACharge/AffiniPay. To verify that a merchant can take eCheck payments, send a GET request to the https://api.chargeio.com/api/v1/merchant endpoint.

Include all required information on the payment page

it’s important that you gather the appropriate cardholder details in your payment form.

eCheck account holder dataWhy collect it?
account holder typeRequired for successful transaction (business or individual)
nameRequired for successful transaction (for business account holder type only)
given nameRequired for successful transaction (for individual account holder type only)
surnameOptional (for individual account holder type only)
routing numberRequired for successful transaction (On a hosted fields form, this must be a hosted field.)
account numberRequired for successful transaction (On a hosted fields form, this must be a hosted field.)
account typeRequired for successful transaction

See the token object type for parameter names and descriptions of these fields.

In addition, you must include the following text (with <Merchant Name> replaced with the name of the Merchant) above the Submit button:

By clicking “Submit Payment”, I am authorizing <Merchant Name> to initiate a single or recurring ACH/electronic debit in the amount indicated from the bank account I designed above. I understand that this Authorization will remain in full force and effect until the transaction is cancelled by me by contacting <Merchant Name>, or the ACH/electronic debit is processed from the designed account. I certify that (1) I am authorized to debit the bank account above and (2) the ACH/electronic payment I am authorizing complies with all applicable laws.