Plan specialized terminal workflows
Distinguish non-payment card allowlisting, healthcare amounts and terminal profile configuration from a standard card sale.
Allowlist only non-payment cards
Allowlisting can expose approved non-payment magnetic-stripe data, such as a loyalty card. It does not apply to chip/contactless reads. Submit the non-payment BIN range, number length, device, SDK platform and merchant/estate scope for approval. Payment-card ranges are not eligible.
Separate healthcare-eligible items
The Lane guide uses an eligibility lookup for FSA/HSA items and merchant substantiation configuration. Separate eligible and noneligible portions of a mixed basket. Configuration indicator id51 distinguishes IIAS, no-IIAS and the source’s 90-percent-rule category; applicability must be agreed for the merchant.
Send the healthcare amount fields
The source lists fsa_amount_healthcare and fsa_amount_rx for Visa/Mastercard, and fsa_amount_vision, fsa_amount_clinic and fsa_amount_dental for Visa. Match healthcare totals to the eligible purchase. These fields do not establish eligibility by themselves or replace the processor’s account setup.
Read terminal profile data
The Query API gateway_processors report identifies the EMV processor; the source selects the first entry marked emv true. The profile report with processor_details true supplies merchant, address, country, time zone, scheme, currency and processor details. These operational profiles are distinct from a payment request and require the appropriate merchant key.