AMP information
Request help with an existing AMP-related service while using the applicable provider's device, portal, or agreement contact for urgent funding, fraud, outage, or account-security issues.
Plain-language definition
Merchant Support is a routing and troubleshooting path; response responsibility and timing depend on the product, provider, agreement, severity, and available account information.
Day-to-day workflow
Identify the product and location, record safe error details and timing, note impact and steps already tried, avoid sensitive credentials, contact the urgent provider channel where required, and track case references and resolution.
Implementation
The implementation requirement is specific: business and safe callback details, product or provider, location, issue category, start time, business impact, non-sensitive error text, steps tried, and existing case number. AMP can document dependencies and questions, but the merchant and applicable providers must confirm compatibility, account approval, responsibilities, testing, training, and support in writing.
Complete cost
support entitlement and charges depend on the applicable provider, software, hardware, implementation, warranty, replacement, and written agreement Compare recurring, transaction-based, one-time, optional, and exit costs separately. A proposal is incomplete if it omits equipment ownership, software term, support scope, or cancellation obligations.
Failure planning
Do not send passwords, full card numbers, security codes, SSNs, or bank credentials; a web form may not meet urgent provider deadlines or restore third-party systems directly.
Decision guide
Use device or provider emergency support for active outages and funding or security events; use AMP support for AMP-related routing; use general Contact for pre-sale questions.
Know before you decide
Complete-cost view
Only a written proposal and agreement can establish actual pricing and terms.
Owner questions
Provide the business and location, affected product, start time, business impact, safe error text, transaction reference where permitted, steps already tried, and existing case number. Never send passwords, full card data, security codes, or complete bank credentials.
Ownership depends on where the failure occurs and the applicable agreements. Record whether orders, authorizations, batches, deposits, or reports are affected, open cases with the responsible providers, and preserve each reference so cross-provider escalation can be coordinated.
Check the POS and provider status using the available transaction identifier before charging again. Blind retries can create duplicates. If status remains ambiguous, follow the provider's documented recovery path and keep the customer receipt or order record.
No. A web request is not necessarily an emergency channel or guaranteed response time. Use the provider contact in the portal, device, statement, or agreement for active outages, fraud, funding, account security, and formal dispute deadlines.
Published 2026-08-03 · Modified
Primary standards-body background for merchant payment-data security responsibilities. Source reviewed .
Current Visa acceptance-rule materials; the applicable provider must confirm implementation. Source reviewed .
Share the current process, the constraint you need to remove, and the systems that must remain. AMP can return a scoped next step without treating a headline rate or feature list as a complete recommendation.