Support
Support
Get help faster by choosing the right support path and including the transaction, payout, refund, dispute, or API details Moneybag needs to investigate.
Support Options
- Use the support channel listed in the merchant dashboard for account-specific requests.
- Email Moneybag support for general merchant questions and non-urgent operational issues.
- Use developer documentation and sandbox tools for API, webhook, and integration questions.
- Check the approved status or incident channel when Moneybag publishes one.
What to Include
- Merchant ID and account email.
- Transaction ID, payout ID, refund ID, dispute ID, API request ID, or webhook ID.
- Amount, currency, payment method, environment, and date or timestamp.
- Clear summary of the issue, screenshots when useful, and logs with no sensitive card data.
Common Categories
- Onboarding and account review
- Integration, APIs, sandbox, and webhooks
- Failed payments and authorization outcomes
- Settlements, payouts, and reconciliation
- Refunds, chargebacks, fees, and billing
Help topics
FAQ
Moneybag FAQ for founders, merchants, and finance teams covering integration, onboarding, payments, settlements, fees, refunds, chargebacks, and support.
Read more →Approval Timeline
Moneybag merchant approval timeline guidance, review steps, common delays, and ways to submit a stronger application.
Read more →Settlement Timing
Moneybag settlement timing guide explaining how payouts work, what affects timing, and where merchants can track settlement activity.
Read more →Fees
Moneybag fees guide explaining where merchants can see fees, common fee types, and report fields.
Read more →Refunds
Moneybag merchant refund guide covering refund options, status tracking, support details, and reconciliation notes.
Read more →Chargebacks
Moneybag chargeback guide for merchants covering dispute reasons, response steps, evidence, and prevention practices.
Read more →Failed Payments
Moneybag failed payments guide explaining common decline reasons, merchant actions, support data, and retry guidance.
Read more →