Defines customer billing address and contact information fields for Remote API transaction processing.

Billing Address and Customer Contact Fields

Use the fields below to provide customer billing and contact information during Remote API transaction processing.

Variable Requirement Type Max Size Possible Values / Example Description Notes
card-company Optional string 39 Demo Company Company name exactly as it appears on the payment card. Optional on all credit card transactions.
card-name Mandatory string 39 John A. Smith Customer name exactly as it appears on the payment card. Required for all credit card transactions.
card-address1 Optional string 39 123 Main Street Billing street address line 1. Commonly used for AVS verification.
card-address2 Optional string 39 Suite 200 Billing street address line 2. Optional apartment, suite, or unit information.
card-city Optional string 39 Townsville Billing city associated with the payment method. Used for address verification and fraud screening.
card-state Optional string 2 NY Billing state or province abbreviation. Use standard 2-character state codes for U.S. addresses.
card-prov Optional string 39 Ontario International province or region name. For addresses outside the U.S. and Canada, set card-state to ZZ and provide the province name here.
card-zip Optional string 10 11779 Billing ZIP or postal code. Supports international postal code formats.
card-country Optional string 2 US Billing country code. Use standard 2-character ISO country codes.
phone Optional / Conditional string 15 5551234567 Customer phone number. Numeric values only. May be required depending on processor or fraud settings.
fax Optional string 10 5552345678 Customer fax number. Numeric values only. Primarily used for legacy integrations.
email Optional / Fraud string 39 customer@example.com Customer email address. Required when certain fraud protection services are enabled.

Notes

The fields above are commonly used for AVS validation, fraud screening, customer communication, and processor compliance requirements during Remote API transaction processing.