Understanding payment statuses
Learn what common transaction labels communicate and what to check before taking action.
Read guideClarity for every payment workflow
Answers that move you forward.
Find practical guidance for accounts, payments and integrations. Follow focused steps, understand transaction outcomes, and prepare better support requests.
Step-by-step guidanceSafe support practicesDeveloper-ready resources
Find the right next stepSearch guidance before repeating a transaction or changing account settings.
Browse by need
A calmer way to find answers
Start with the area you are working in. Each path connects clear explanations, safe checks, and relevant next steps.
01
Start with confidence
Set up your profile, learn the workspace, and complete your first essential checks.
Explore guidance02Protect your account
Strengthen access, review sessions, and respond to suspicious activity.
Explore guidance03Understand payments
Read payment statuses, trace transactions, and resolve common processing issues.
Explore guidance04Build an integration
Plan authentication, requests, webhooks, error handling, and safe testing.
Explore guidance05Manage money movement
Navigate refunds, cancellations, payouts, fees, and reconciliation.
Explore guidance06Get focused support
Follow guided checks or prepare a detailed request for the support team.
Explore guidance
Get started
Build a dependable first-day foundation
Review identity and contact details, learn the workspace, protect access, and understand where to find transaction records.
Verify carefully
Confirm contact details and use only expected verification links.
Secure access
Create unique credentials and enable additional protection when available.
Learn the essentials
Locate payments, payouts, settings, integrations, and help resources.
Frequently used
Popular guides
What to do when a payment is declined
A declined result should be handled calmly, without repeated attempts or requests for sensitive card data.
Read guideHow pending transactions work
Pending transactions are incomplete processing events; this guide helps you decide when to wait and when to investigate.
Read guideUnderstanding refunds and reversals
Use the event history to distinguish a post-completion refund from a cancellation, void, or automatic reversal.
Read guideHow to track a refund
Follow a refund from creation to its latest recorded outcome without confusing it with the original charge.
Read guideUnderstanding payout statuses
Read payout records alongside available and pending balances so reconciliation stays accurate.
Read guideAccount safety
Security is a workflow, not a single setting
Use a unique password, protect recovery methods, review active sessions, and treat unexpected requests for credentials or codes as suspicious.
Never share passwords, one-time codes, CVVs, or full card numbers.
Verify messages through a known channel before taking urgent action.
Respond quickly to unfamiliar sessions or contact-detail changes.
Safety check
Something feels wrong?
Pause. Do not approve an unexpected request, repeat a payment, or disclose sensitive data. Record safe details and follow the appropriate response guide.
Resolve an issuePayments & transactions
Read the lifecycle before you act
A status is a snapshot. Pair it with timestamps, related events, and safe reference IDs to understand the whole transaction.
Identify
Find the correct record using its ID, date, amount, status, and internal order reference.
Interpret
Review the latest event and distinguish pending, completed, declined, reversed, canceled, or refunded activity.
Respond
Choose the safest next step and avoid rapid retries or duplicate adjustments.
For developers
Integrate with security and observability built in
Plan environment separation, secret storage, idempotent writes, controlled retries, webhook verification, and useful redacted logs.
Safe request pattern
curl https://api.example.com/v1/payments/test_payment_id \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: application/json"
Find your path
From question to resolution
Search clearly
Use a specific status, error, workflow, or task.
Follow focused checks
Work through the guide in order and note what changes.
Prepare useful context
If the issue remains, collect safe IDs, timestamps, impact, and redacted evidence.
Quick answers
Common questions
Why is a transaction still pending?
Processing is not final. Check the last event time and avoid repeating the payment while the first outcome is unresolved.
Read the guideWhen should I contact support?
After safe checks are complete, prepare the affected workflow, exact outcome, timestamp, safe reference IDs, and business impact.
Prepare contextCan support ask for my password?
No. Never send passwords, one-time codes, CVVs, API secrets, or full card and bank details.
Review securityHow do I trace an API error?
Capture the request ID, HTTP status, UTC time, environment, and a redacted response before changing the request.
Troubleshoot APIsPersonal support
Prepare a request that is easy to understand
Your request is validated and stored locally on this device. You can download a copy and open a prepared email to send it to our team.
Call
Speak with the support contact line for general guidance.
+1 405 695 9990Send a prepared request with safe, relevant context.
info@welcometothemx.comVisit or write
4300 Amelia Earhart Ln
Oklahoma City, OK 73159