If a charge on your Coinepay virtual card looks wrong, act promptly—but first identify what went wrong. An unfamiliar merchant name, a duplicate payment, an undelivered order and a transaction you never authorized call for different explanations. A card dispute asks the card issuer to investigate; a chargeback is one possible reversal through the card-payment system, not a guaranteed refund. This guide explains how to prepare your case and where to start with Coinepay.
Check the charge before choosing a dispute reason
Open your Coinepay app or self-service dashboard and find the transaction. Compare its date, amount and merchant description with your receipts, order confirmations and subscriptions. An unfamiliar description can belong to a purchase you made under a different trading name. Also check whether someone authorized to use the relevant account made the purchase.
Next, decide which description fits the facts:
- Unauthorized transaction: You did not make or authorize the payment. Report it promptly. Do not label a purchase you made as fraud simply because the seller disappointed you.
- Incorrect charge: The amount is wrong, the transaction appears twice, or a refund you were promised has not appeared.
- Purchase problem: Goods or services were not delivered as agreed, or you canceled or returned an order and the seller has not resolved the payment.
- Quality disagreement: You received and accepted the purchase but are unhappy with its quality. This may require a different review from a billing error; explain exactly what the seller promised and what happened.
For a purchase problem, ask the merchant for a correction or refund and keep its reply. Do not let that conversation run past a dispute deadline. If you do not recognize the transaction at all, report it without waiting for a merchant response.
How to start a Coinepay card dispute
- Locate the payment. In the Coinepay app or dashboard, collect the transaction date, displayed merchant name, amount and any transaction reference shown. If you hold more than one virtual card, note which card was used, but do not send its full card number or CVV in an ordinary message.
- Gather your explanation and evidence. Write a short timeline: what you bought or expected, what appeared on your account, when you contacted the merchant, and what response you received. Match each document to the point it supports.
- Contact Coinepay support promptly. Say that you want to dispute a virtual-card charge and provide the transaction details and reason. Ask which institution handles the card dispute, how to submit evidence securely, whether a separate notice is required, and what deadline applies to your account. Coinepay card issuance and fund services are provided by licensed partner financial institutions; do not assume that an ordinary support message alone completes every required issuer procedure.
- Follow the instructions for your account. Submit the requested dispute form or notice through the channel you are given. If the issuer directs you to a statement address, use the billing-disputes address rather than a payment address. Save copies of what you submit and proof of when it was received.
- Track and answer follow-up requests. Record your case reference, if one is provided. Respond to requests for clearer receipts, merchant correspondence or an explanation of the charge. Ask for the outcome in writing and keep the response with your records.
If you cannot access your Coinepay account, use support rather than waiting until you can sign in. Do not post card credentials or identity documents in a public channel.
What evidence should you prepare?
Useful records depend on the dispute. For a wrong amount or duplicate charge, include the receipt and identify both entries. For an undelivered order, provide the order confirmation, promised delivery terms, tracking information if available, and messages asking the seller to resolve it. For a canceled subscription, include the cancellation confirmation, the effective date and the charge you believe came afterward. For a return, keep the return authorization, proof of shipment or receipt, and the merchant’s refund policy or written promise.
For an unauthorized charge, state that you did not approve it and when you first noticed it. Explain any relevant account-access concern truthfully. The reviewer may need to distinguish an unauthorized payment from a dispute about a purchase you did authorize. Make sure dates and amounts in your account records, receipts and written explanation agree; if they do not, explain why.
Use your real identity and accurate account and billing details. Identity checks, transaction records and supporting documents may be needed to review a case. Provide requested material through the secure channel specified by support or the issuer, and keep your own copies. Do not alter receipts or omit merchant messages that materially change the timeline.
Understand deadlines and possible outcomes
Start as soon as you spot the problem. There is no single dispute deadline that fits every card transaction: the applicable issuer procedure, card-payment rules, account terms and local law can differ. A merchant’s promise to investigate does not necessarily pause a deadline. Ask the institution handling your dispute which date applies and how it determines when your notice was received.
If your account is a U.S. consumer credit-card account, federal billing-error rules under Regulation Z may require a written notice that the issuer receives within 60 calendar days after it sent the first statement showing the error. The notice should identify your account and, as far as possible, the type, date, amount and reason for the error. Use the billing-disputes address on the statement. An electronic submission meets this written-notice requirement only if the issuer’s billing-rights statement says it accepts electronic notices and explains how. Calling or opening an ordinary online case may not, by itself, preserve those rights.
If your account is instead covered by U.S. consumer debit-card error-resolution rules, Regulation E generally permits oral or written notice no later than 60 days after the first statement showing the error was sent. Unauthorized-use reporting can involve additional timing considerations. These are different legal procedures; neither description establishes which one applies to a Coinepay card. Ask the institution handling your account about your applicable rights and follow its instructions promptly.
Under the U.S. credit-card billing-error procedure, an accepted purchase that was merely poor quality is not automatically a billing error, though other rights or dispute processes may be relevant. Explain the issue to the issuer rather than selecting an inaccurate reason. If you receive a temporary or provisional credit, do not treat it as a final decision: it may be reversed if the investigation does not support the dispute. A successful review may correct the charge; an unsuccessful one should come with an explanation under applicable procedures.
Troubleshooting a dispute
The merchant name is unfamiliar
Compare the charge with recent orders, receipts and subscriptions before reporting fraud. If you still cannot identify it, tell support when you noticed it and what you checked.
The seller says it will refund you, but nothing has appeared
Keep the seller’s written promise and the relevant transaction record. Ask the seller for its refund reference or confirmation, then contact support if the issue remains unresolved. Do not assume a pending merchant response extends your dispute deadline.
You already sent a support message
Ask whether a formal issuer notice or additional form is needed and where it must go. For a potentially applicable U.S. credit-card billing error, check the billing-rights statement rather than assuming an app message counts as written notice.
Your case was declined or the evidence request is unclear
Ask for the specific reason, the findings and any supporting documents available under the applicable process. Supply relevant missing evidence and ask whether reconsideration is available. Keep the original decision and your follow-up together.
Card charge or remittance transfer?
These steps concern a payment made with a Coinepay virtual card. If the transaction was a Coinepay Global Remittance transfer instead, describe it to support as a transfer issue and provide its reference and status; a card chargeback is not the same process. Transfer reviews are subject to identity verification, sanctions screening and local regulations, and Coinepay may request documents explaining the purpose or source of funds. In either case, reporting the issue clearly and preserving your records gives the reviewer a usable starting point.
Get your Coinepay virtual card: Sign up · App Store · Google Play · Customer support
FAQ
Is a card dispute the same as a chargeback?
No. A dispute asks the issuer to investigate a charge. A chargeback is a possible card-payment reversal, not a guaranteed outcome.
Should I contact the merchant before disputing a charge?
For a purchase problem, ask the merchant to fix it and keep the correspondence, but do not miss a dispute deadline. Report a transaction you did not authorize promptly.
Does a Coinepay support message count as a formal dispute notice?
Do not assume it does. Ask Coinepay support which institution handles your dispute and whether its process requires a separate form or notice.
What if I received a temporary credit?
A temporary or provisional credit is not a final decision. Keep following the case and respond to any requests for evidence.
Can I request a card chargeback for a Coinepay remittance?
A remittance transfer is not a virtual-card purchase. Contact Coinepay support with the transfer reference and describe the transfer issue instead.
Related guides
- Why Does a Refund to Your Card Take Days to Arrive?
- How to Check Whether a Website Accepts Your Card Before Buying
- How to Pay in a Foreign Currency Online with Coinepay
- What Is a Card Authorization vs. a Settled Payment?
- What Is a Merchant Category Code? A Coinepay Card Guide
- Why Do Online Payments Fail With a “Do Not Honor” Error?

