AMP information
Route a sales, partnership, or general business question with enough non-sensitive context for useful follow-up; use merchant support and provider emergency channels for active account issues.
Plain-language definition
The contact page is a general inquiry path and should not receive passwords, cardholder data, Social Security numbers, full bank credentials, or urgent dispute deadlines.
Day-to-day workflow
Choose the request type, provide contact and business context, describe the goal and current system without sensitive credentials, and retain urgent provider contacts for time-sensitive account issues.
Implementation
The implementation requirement is specific: name, safe contact method, business name and type, request category, high-level goal, current platform where relevant, and preferred follow-up context. 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
general inquiry has no stated fee; any product, provider, implementation, support, financing, or software cost appears only in later written scope 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
A general message is not a secure underwriting channel, support SLA, application, contract, approval, or guaranteed response time.
Decision guide
Use Contact for discovery; use Merchant Support for an AMP-related active service; use the provider number on the device, portal, or agreement for urgent funding, fraud, outage, or account-security events.
Know before you decide
Complete-cost view
Only a written proposal and agreement can establish actual pricing and terms.
Owner questions
Use it for sales discovery, partnership questions, general product fit, or routing help. Active outages, suspected fraud, urgent funding issues, and deadline-driven disputes should also go directly to the emergency or support contact listed by the responsible provider.
Include a safe callback method, business type, location count, current platform, sales channels, high-level goal, and desired timing. Do not submit passwords, security codes, full card numbers, Social Security numbers, or complete bank credentials.
No. A general inquiry can start discovery or be routed to another process, but it is not merchant-account approval, a financing application, a binding quote, a support service level, or acceptance of provider terms.
Start with the number or channel on the device, merchant portal, statement, or agreement for the affected service, then use AMP support for AMP-related coordination. Record timestamps and case numbers, but never place authentication secrets in a general message.
Published 2026-08-03 · Modified
Government operational-planning reference; not a product endorsement. Source reviewed .
Primary standards-body background for merchant payment-data security responsibilities. 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.