Support

MyPaymentVault — Support

Overview MyPaymentVault is committed to delivering reliable, secure, and user-friendly payment solutions. This document explains the support resources available to customers, how to access them, what to expect when you reach out, and best practices to get faster resolution to common issues. The goal is to ensure your payment operations run smoothly and that any disruptions are handled quickly and professionally.

Support Channels and Hours

  1. Help Center (Self-Service) — 24/7
  • Access our searchable Help Center for step-by-step guides, FAQs, troubleshooting walkthroughs, and API documentation.
  • Topics include onboarding, account setup, KYC/verification, payment processing (cards, ACH, bank transfers), refunds, disputes/chargebacks, reporting and reconciliation, security and compliance, and integration troubleshooting.
  1. Email Support — Business hours with SLA tiers
  • Email: support@salaryatseas.com
  • Typical response times:
    • Standard inquiries: within 24 business hours.
    • Urgent billing or transaction-impacting issues (classified per account plan): within 4 business hours.
  • When emailing, include: Merchant ID, timestamp(s) of affected transaction(s), transaction ID(s), customer email or last 4 digits of card, a clear summary of the issue, steps you’ve already taken, and any relevant screenshots or logs.
  1. Live Chat — Extended hours
  • In-product live chat is available during extended support hours for quick questions, troubleshooting, and guidance.
  • Best for clarifying configuration settings, checking transaction status, or getting immediate guidance during integrations.
  1. Phone Support — Priority customers and escalations
  • Phone support is available to accounts with premium or enterprise plans and for critical incidents that affect transaction flow or cause downtime.
  • Phone lines: see account portal for assigned support representative and phone numbers.
  • For phone support, have Merchant ID and recent logs/transaction IDs ready.
  1. Account Manager / Technical Account Manager (TAM)
  • Enterprise customers receive a dedicated account manager and/or technical account manager for proactive support, onboarding assistance, regular review meetings, tuning payment flows, and help with dispute reduction strategies.
  1. Developer Support & API Status
  • Developer Documentation: comprehensive API reference, SDK guides (server and client), webhook guide, code samples in multiple languages, and best practices for error handling and idempotency.
  • Developer support channels for integration questions are available via the developer portal and email support@salaryatseas.com.
  • System Status Page: public status page (status.mypaymentvault.com) shows uptime, incidents, scheduled maintenance, and historical incident reports. Subscribe to real-time updates via email or SMS.

Incident Management and Escalation

  • Incident Prioritization:
    • P0 (Critical): Complete outage or system failure that blocks payment acceptance or fund movement for multiple merchants. Response: immediate acknowledgement, mobilize incident response team, continuous updates until resolved.
    • P1 (High): Significant degradation affecting many customers (e.g., slow API responses, failed payment gateway connectivity). Response: acknowledge within 1 hour, continuous updates.
    • P2 (Medium): Single-customer-impacting issues or degraded non-critical functionality. Response: acknowledge within 4 business hours, periodic updates.
    • P3 (Low): Minor bugs, documentation requests, or feature questions. Response: standard SLA.
  • Escalation Path:
    • Tier 1 Support (Frontline): handles initial diagnosis, standard troubleshooting, common fixes, and routing.
    • Tier 2 (Technical): engineers for deeper technical investigations, logs analysis, configuration checks, and patching.
    • Tier 3 (Platform/Engineering): senior engineers and product owners for code-level fixes, platform changes, or architectural issues.
    • Executive escalation for unresolved business impacts.
  • Communication: All incidents provide estimated time to resolution (ETR) when possible, regular status updates, incident postmortems for major incidents, and remediation plans to prevent recurrence.

What We Need From You (Information to Provide) To expedite support, supply the following where relevant:

  • Merchant ID and registered business name.
  • Exact timestamps (with timezone), transaction IDs, and payment method details.
  • Customer identifier or partial card details (last 4 digits) when applicable.
  • Full error messages, response codes, and webhook payloads.
  • Screenshots, logs, request/response headers (with sensitive fields redacted), and the steps to reproduce the issue.
  • Environment: production vs. sandbox and SDK or integration version.
  • Any recent configuration changes, rule updates (e.g., risk rules), or deployments.

Common Issues and Troubleshooting Steps

  1. Payments Declined
  • Check bank decline codes in transaction details. Declines can be due to insufficient funds, authentication failures, issuer blocks, or AVS/CVV mismatches.
  • Recommend retry logic for transient declines and guidance for customers to contact their card issuer when declines persist.
  • Use fallback or alternative payment methods where enabled (e.g., different card, ACH, digital wallets).
  1. Webhooks Not Being Received
  • Verify webhook endpoint URL, ensure it’s accessible from our IP ranges, and not blocked by firewalls.
  • Confirm the endpoint responds with HTTP 200 to webhook requests.
  • Check delivery attempts and error messages in the dashboard; replay failed events from the dashboard once the endpoint is fixed.
  • Validate webhook signatures to ensure messages are authentic.
  1. API Authentication Errors
  • Confirm API keys: production keys should be used in production environment; sandbox keys for test environment.
  • Check key rotation: if keys were rotated recently, update them in your application.
  • Ensure request headers are formatted correctly (Authorization header, content-type).
  1. Disputes and Chargebacks
  • Overview: A chargeback occurs when a cardholder disputes a transaction with their card issuer. Our platform notifies you and provides documentation requirements.
  • Response steps: gather evidence (proof of delivery, customer communications, transaction metadata), submit before the dispute window closes, and follow up via the dashboard.
  • Best practices: clear descriptions on receipts, robust order confirmation emails, delivery tracking, and fraud-prevention rules to reduce disputes.
  1. Refunds and Partial Refunds
  • Refunds can be initiated in the dashboard or via API (include original transaction ID and amount).
  • Refund timing: typical refund settlement times depend on card networks and issuing bank policies; allow several business days for funds to appear.
  • Troubleshooting: if refund doesn’t appear, check refund status, ensure correct currency and amount, and confirm with issuing bank if needed.
  1. Payouts and Settlements
  • Payout schedule: review your account payout frequency and settlement timing in the dashboard.
  • Missing payout: check payout history, verify your bank account details and any holds on account (e.g., compliance review, chargeback reserves).
  • For urgent payment to your bank, contact support with payout ID and bank reference.

Security, Compliance, and Fraud

  • PCI Compliance: MyPaymentVault is PCI-compliant and uses strong encryption for card data. You should follow required PCI controls on your integration type (e.g., redirect, tokenization, client-side encryption).
  • Two-Factor Authentication (2FA): strongly recommended for all user accounts. Admin users can be required to use 2FA.
  • Suspicious activity: if you detect unusual transaction patterns or account access, contact support immediately. We may place temporary holds and initiate fraud investigation procedures.
  • Data handling: we limit access to sensitive data in support tickets and may require additional verification steps before discussing or releasing sensitive information.

Onboarding and Account Verification

  • New merchant setup: step-by-step onboarding checklist (business and personal details, bank account verification, KYC documents, accepted payment methods).
  • Verification turnaround: typical KYC review times vary by region; provide documents outlined in the onboarding checklist to avoid delays.
  • Temporary limits and holds: newly onboarded accounts may have processing limits until verification is complete or risk profile stabilizes.

Integrations and SDKs

  • SDKs and Libraries: official SDKs with setup guides, code examples, and best practices. Keep SDKs up to date to benefit from security patches and feature updates.
  • Best practices: implement idempotency keys for safe retries, handle transient errors with exponential backoff, validate and log webhook events, and sanitize logs that may contain sensitive data.
  • Migration support: if migrating from another gateway or upgrading plans, request migration assistance to minimize downtime and reconcile historical data.

Reporting, Billing, and Invoices

  • Dashboard reports: real-time reporting for transactions, disputes, refunds, and settlements. Use filters and export features for reconciliation.
  • Billing: review your pricing plan, monthly invoice, and history in the billing section. For invoice disputes or questions about fees, contact support@mypaymentvault.com.
  • Tax and regulatory reporting: customers receive year-end statements and are responsible for tax filings; we can provide transaction reports to assist with accounting.

Response Expectations and SLA

  • We aim to respond quickly, transparently, and with actionable guidance. SLAs vary by plan: standard, priority, and enterprise tiers have different response times and dedicated resources.
  • Escalations: if you’re dissatisfied with a support outcome, request an escalation. We document and review escalations and provide timelines for follow-up.

Post-Incident Reviews and Continuous Improvement

  • For major incidents, MyPaymentVault publishes postmortems that describe root cause, timeline, mitigation steps, and corrective actions.
  • We use customer feedback from support interactions and user surveys to improve documentation, tooling, and platform reliability.

Privacy and Data Retention

  • We adhere to applicable privacy laws and limit the retention of personal data to the duration required for business, legal, and compliance purposes.
  • Support interactions may be recorded for quality and training purposes. Sensitive details shared in support tickets are redacted where possible and access is restricted.

Accessibility and Language Support

  • Our Help Center and dashboard follow accessibility guidelines; users can request alternative formats.
  • Support is offered primarily in English; additional language support is available for enterprise accounts in specified languages.

How to Provide Feedback

  • Help Center feedback: use article feedback controls to indicate helpfulness.
  • Support survey: after ticket resolution, you may receive a satisfaction survey. Your feedback helps prioritize improvements.
  • Feature requests and product feedback: submit through the dashboard or via your account manager. Product teams review feedback for roadmap consideration.

Summary — How to Get the Fastest Resolution

  1. Check the Help Center and system status page first.
  2. Provide complete information: Merchant ID, transaction IDs, timestamps, exact error messages, environment, and reproduction steps.
  3. Use the appropriate channel: live chat for quick questions, email for detailed cases, phone for critical incidents (if available for your plan).
  4. Keep logs, screenshots, webhook payloads, and API request/response details handy.
  5. If needed, request escalation and provide permission for deeper diagnostics (e.g., temporary access or log sharing).

Contact Information (Quick Reference)

If you need help right now, tell me the issue you’re experiencing (include Merchant ID, environment, and any relevant transaction IDs), and I’ll walk you through next steps.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to Top