PAYMENT ACCEPTANCE: PROVIDER QUESTIONS AND PILOT RECORD
Yenra | Prepared October 3, 2026 | Editable planning aid
Guide: https://yenra.com/card-payment/

HOW TO USE
Complete one copy per proposed provider/device/site combination. Record exact
versions, dates and written sources. Ask the provider to confirm unanswered
items. This worksheet supplies no assumed fees, ratings or compliance approval.
Use the provider's test environment and agreed live validation procedure.
Never put full card numbers, PINs, passwords or customer personal data here.

1. SITE AND TRANSACTION
Business/site:
Prepared by / date:
Country and settlement currency:
Setting: counter / mobile / drive-through / unattended / other
Normal and peak transaction counts per day:
Typical transaction amount and currency:
Customer position, reach and accessibility needs:
Power / connectivity / expected weather exposure:
Order or machine system to integrate:

2. EXACT PROPOSAL
Provider and support contact:
Device model / software / operating system:
Supported card brands, debit routes and wallets:
Chip / contactless / PIN methods supported:
Relevant security listing and provider's written confirmation:
Applicable merchant validation and operating responsibilities:
Outdoor installation documentation and environmental ratings (if relevant):
Mounting, enclosure, cables and installer responsibility:
Product support period / update process / replacement service:
Receipt delivery options:
Refund and partial-refund process:
Order matching and settlement report identifiers:

3. COSTS — USE ONE CONSISTENT PERIOD AND CURRENCY
Comparison period / currency:
Equipment purchase or rental:
Software subscription and connectivity:
Processing charges for representative transaction mix:
Refund / dispute / other charges:
Support / replacement / termination charges:
Quote date and written terms:
Expected total for the stated period:

4. FAILURE PROCEDURES
Internet failure: stop acceptance or provider-supported offline mode?
Exact offline limits, forwarding deadline and merchant risk:
Power or device failure fallback:
How to look up an uncertain payment before trying another charge:
Payment approved but machine/service fails: exception and refund route:
Inspection, tamper-response and lost-device responsibilities:

5. PILOT RECORD
For each case, record: date | configuration | expected result | actual result
| non-sensitive reference | issue owner | resolved date.

Supported card and wallet methods:
Declined payment:
Canceled transaction:
Full refund:
Partial refund (where supported):
Receipt request:
Loss of connection:
Uncertain result and duplicate-charge prevention:
Payment succeeded but fulfillment failed:
Daily sales/refunds/fees/payout reconciliation:
Keyboard/accessibility or customer-reach checks:

6. ROLLOUT DECISION
Unresolved issues and their effect:
Provider confirmations received:
Staff training completed:
Support and fallback instructions available:
Decision / responsible person / date:
Next review trigger (software change, device replacement, new location, etc.):

SOURCE LOOKUPS
PCI MPoC: https://www.pcisecuritystandards.org/standards/mobile-payments-on-cots-mpoc/
Consult your provider's exact product documentation and agreement for fees,
offline behavior, approved configurations and merchant responsibilities.