Tevau-openApi
    • Get started
    • Signature instructions
    • Transaction description
    • FAQ
    • Exception Codes
    • Reason for transaction rejection
    • Tevau Card Transaction Dispute Guide
    • 01. User
      • 1.1 Create User
        POST
      • 1.2 Query User
        POST
    • 02. KYC
      • 2.1 V1 submits the customer's KYC information
        POST
      • 2.2 Get the URL
        POST
      • 2.3 Query liveness results
        POST
      • 2.4 Query KYC
        POST
      • 2.5 [Sandbox] Simulate KYC Review
        POST
      • 2.6 Create Document File
        POST
      • 2.7 Upload Document Files
        POST
      • 2.8 V2 Submit customer's KYC information
        POST
    • 03. Card
      • 3.1 Create Card
        POST
      • 3.2 Query Card List
        POST
      • 3.3 Adjust Card Balance
        POST
      • 3.4 Card Details
        POST
      • 3.5 Bind Card
        POST
      • 3.6 Close Card
        POST
      • 3.7 Freeze Card
        POST
      • 3.8 Unfreeze card
        POST
      • 3.9 Activate Card
        POST
      • 3.10 Card PAN
        POST
      • 3.11 Card PIN
        POST
      • 3.12 Card Limit
        POST
      • 3.13 Set Card Fee
        POST
      • 3.14 Query Card Fee
        POST
      • 3.15 3DS
        POST
      • 3.16 Update Phone
        POST
      • 3.17 Update Email
        POST
      • 3.18 Modify Card PIN
        POST
      • 3.19 Query the list of card tokens
        POST
      • 3.20 Activate the card with Google/Apple Token
        POST
      • 3.21 Card transaction limit
        POST
      • 3.22 Check card account transaction history
        POST
    • 04. Query logistics information
      • 4.1 Query Order
    • 05. Prefund
      • 5.1 Prefund Balance
      • 5.2 Query Bill Details
    • 06. Transaction
      • 6.1 Transaction History
      • 6.2 Transaction Details
    • 07. Simulated Trading
      • 7.1 Authorisation
      • 7.2 Clearing
      • 7.3 Refund
      • 7.4 Reversal
      • 7.5 3DS
      • 7.6 Simulate card status
    • 08. Webhook
      • 8.1 KYC Results
      • 8.2 Card Status
      • 8.3 Changes in card balance
      • 8.4 3DS
      • 8.5 Transaction
      • 8.6 Logistics status
      • 8.7 Token Notification
      • 8.9 Risk Control - Notification of Frozen Card Results
      • 8.10 Notification of failure to bind Google and Apple
      • 8.11 Notification of Fund Pool Top-up Arrival
    • Rests
      • [Sandbox] Edit WebHook-Url
      • JIT Authorized Transaction

    Tevau Card Transaction Dispute Guide

    November 2026
    Download the required template: Tevau Card Dispute Request Form (.xlsx)
    This guide is for Tevau clients who submit card transaction disputes on behalf of cardholders. It explains when a case may be eligible, what evidence to collect, how to complete the companion workbook, and how to send the package to Tevau. Tevau reviews every case before filing. Submission does not guarantee recovery.
    Enter one transaction per row and send the completed workbook with all supporting documents to chargeback@tevau.io.

    1 Immediate Actions#

    Freeze a lost, stolen, or compromised card immediately and contact Tevau. Record when the card was lost, discovered missing, frozen, and reported.
    Report every suspected or confirmed fraudulent transaction to Tevau. This includes transactions below USD 10 and unrecognized declined transactions.
    For processing and consumer cases, ask the merchant to correct the charge or provide a refund first. Keep the complete communication history.
    Collect the transaction record, merchant documents, cardholder statement, and other evidence before submission. Make sure dates, amounts, and merchant details are readable.
    Start the case immediately. Filing limits run from the disputed transaction date, and Tevau needs time to review the package.

    2 Eligibility Check#

    Complete every check below before submitting the case. A case may be rejected when a condition is not met or the supporting record is incomplete.
    CheckRequirementRequired action
    Transaction statusThe transaction must be posted or cleared.Wait until a pending transaction clears before requesting a formal dispute.
    Minimum amountAn individual transaction must be at least USD 10 or the equivalent for a formal dispute.Report suspected fraud to Tevau even when the transaction is below the minimum.
    Time limitThe case must be submitted within the applicable filing period.Use the deadline table below and submit as soon as possible.
    Card actionA lost, stolen, or compromised card must be frozen promptly.Provide the loss, discovery, freeze, and report times.
    Fraud authorizationThe cardholder must not have approved the transaction or allowed a known person to use the card.Check PIN, wallet token, card-present, and 3DS records.
    Merchant contactProcessing and consumer cases require an attempt to resolve the issue with the merchant.Attach the full communication chain and the merchant's response.
    Merchant termsThe claim must not be excluded by agreed terms, normal fees, or a valid cancellation timetable.Attach the terms, invoice, listing, or cancellation policy that supports the claim.
    EvidenceThe information and documents must support the selected reason.Use the evidence matrix in Section 5.

    3 Submission Time Limits#

    Dispute typeLatest filing pointCount from
    FRAUD120 daysDisputed transaction date
    AUTH75 daysDisputed transaction date
    PROCESSING75 daysDisputed transaction date
    CONSUMER60 daysDisputed transaction date
    A late or incomplete package may be rejected. Do not wait until the final day to contact Tevau.

    4 Dispute Types#

    TypeUse whenCommon scenariosImportant exclusions
    FRAUDThe cardholder does not recognize or authorize the transaction.Unrecognized card-not-present transaction. Lost or stolen card used after it was reported.Transactions approved by the cardholder or authenticated by PIN, card-present methods, wallet token, or successful 3DS are normally treated as authorized.
    AUTHA transaction cleared without a valid prior authorization.Clearing without matching authorization. Tevau will confirm whether this category applies.Do not use this category only because the cardholder regrets an authorized purchase.
    PROCESSINGThe transaction is valid but its processing is wrong.Cancelled recurring charge. Refund not received. Incorrect amount or currency. Duplicate billing or payment by another method.Exchange-rate differences, normal fees, charges allowed by merchant terms, and cancellations effective in a later billing cycle are not eligible.
    CONSUMERThe merchant did not provide the goods or service as agreed and did not resolve the issue.Goods or service not received. Goods defective, counterfeit, or not as described. Service materially different from the agreement.Personal preference, final-sale terms, or unsupported complaints about service quality are not eligible.

    Fraud Checks#

    Card still in the cardholder's possession. Confirm that no family member or known person used the card without the cardholder's knowledge.
    Card missing, lost, or stolen. The cardholder must report the loss and freeze the card immediately after discovery. Transactions made before reporting may remain the cardholder's responsibility.
    Strong authentication. Card-present contactless, chip and PIN, magnetic-stripe, wallet-token, and successfully authenticated 3DS transactions are normally outside the fraud dispute process.
    Fraud filing limit. No more than 15 fraud transactions may be filed against the same card number.

    Processing Checks#

    Cancelled recurring charge. Confirm the cancellation followed the merchant's policy and was effective before the disputed charge.
    Refund not received. Provide the merchant's refund confirmation and evidence that the credit is still absent.
    Incorrect amount or currency. Show the original billed amount or currency. Exchange-rate changes and normal fees do not qualify.
    Duplicate billing or payment by another method. Provide both transaction records or proof of the other payment. Recurring, installment, or GIRO billings are not duplicate-billing disputes.

    Consumer Checks#

    Goods not received. Provide the invoice, expected delivery date, tracking record, and merchant communication.
    Goods defective, counterfeit, or not as described. Show the product listing, objective difference or defect, photos, return attempt, and merchant response.
    Service not received or materially different from the agreement. Provide the service agreement or listing and show the merchant's failure to resolve the issue.
    Final-sale terms and personal preference are not valid consumer dispute reasons. General dissatisfaction without objective evidence may also be ineligible.

    5 Evidence Requirements#

    Provide the documents for the selected scenario. Keep originals where possible and submit clear copies in chronological order.
    ScenarioInformation requiredSupporting documentsChecks before submission
    Unrecognized transactionTransaction details and dated chronology. State whether the card remained in the cardholder's possession.Cardholder statement or transaction record. Cardholder attestation. Additional details when available.Confirm no family member or known person used the card. Check PIN, wallet token, and 3DS authentication.
    Lost or stolen cardDate and time the card was lost, discovered missing, frozen, and reported. List each disputed transaction.Cardholder attestation. Loss or police report if available. Transaction record.Freeze the card immediately. Identify any transactions that occurred before reporting.
    Cancelled recurring chargeSubscription details, cancellation date, and charges after cancellation.Proof of cancellation. Proof of payment. Merchant communication.Confirm cancellation followed the merchant's policy and was effective before the disputed charge.
    Refund not receivedPurchase details and chronology, including the merchant's refund commitment and expected refund date.Proof of payment. Refund confirmation or reference. Merchant communication. Statement showing the credit was not received.Confirm the merchant agreed to refund and the credit is still absent.
    Incorrect amount or currencyOriginal billed amount or currency and the posted transaction details.Invoice, receipt, or other proof of the agreed amount or currency.Exclude exchange-rate differences and normal bank or merchant fees.
    Duplicate billing or paid another wayIdentify the original and duplicate charge, or explain the failed card payment and other payment method.Original invoice if available. Both transaction records, or proof of cash or other-card payment.Confirm the entries are separate charges for the same purchase.
    Goods or service not receivedDescription, purchase date, and expected delivery or service date.Invoice or receipt. Delivery promise. Tracking record if applicable. Merchant communication.The cardholder must first ask the merchant for delivery or a refund.
    Goods not as described or counterfeitDescription and chronology, including the merchant's response and any return attempt.Proof of payment. Product listing. Photos. Return tracking if applicable. Merchant communication.Show an objective difference, defect, or misrepresentation.
    Service not as describedDescription and chronology showing how the service materially differed from the agreement.Proof of payment. Service agreement or listing. Merchant communication.General dissatisfaction without objective misrepresentation may be ineligible.

    Cardholder Attestation#

    For a fraud case, obtain a signed or otherwise authenticated cardholder statement accepted by Tevau. It should include the following information.
    Cardholder name and the last four digits of the card.
    Each disputed transaction, including merchant, amount, currency, and date.
    Whether the card remained in the cardholder's possession or when it was lost or stolen.
    Confirmation that the cardholder did not authorize the transaction and no family member or known person used the card.
    Confirmation that the cardholder did not approve the transaction through PIN, a digital wallet, or 3DS.
    For a lost or stolen card, the date and time of discovery, freezing, and reporting.
    The date of the statement and the cardholder's signature or accepted authentication.

    6 Completing the Workbook#

    Download the workbook: Tevau Card Dispute Request Form (.xlsx)
    Use one workbook per card. Enter one disputed transaction per row. Complete all 13 fields exactly as shown below.
    FieldWorkbook columnRequired entryCompletion rule
    1date_of_disputeSubmission dateEnter the date the complete package is sent to Tevau in YYYY-MM-DD format.
    2card_opaque_idTevau Card IDUse the card identifier shown in the Tevau portal or transaction record.
    3card_last_four_digitsLast four digitsEnter exactly four digits. Use the same digits in the workbook and evidence filenames.
    4cardholder_last_nameCardholder surnameEnter the surname exactly as recorded for the cardholder.
    5visa_transaction_idTransaction referenceUse the transaction identifier shown in the Tevau portal or transaction record.
    6transaction_amountAmountEnter the posted transaction amount as a number without a currency symbol.
    7transaction_currencyCurrencyEnter the three-letter currency code, such as USD, EUR, or GBP.
    8transaction_auth_dateAuthorization dateEnter the authorization date in YYYY-MM-DD format.
    9transaction_capture_dateCapture dateEnter the capture or clearing date in YYYY-MM-DD format.
    10merchant_nameMerchantUse the merchant name shown on the transaction record.
    11dispute_typeFRAUD, AUTH, PROCESSING, or CONSUMERSelect the category from the workbook list. Use the guide in Section 4.
    12descriptionReason and chronologyState the specific scenario, key dates, merchant contact, and result. Use complete sentences.
    13evidenceEvidence filenamesList every attached filename and briefly identify what each file proves.
    The User Code is also required. Put it in the submission email body so Tevau can identify the account.

    7 File Naming and Submission#

    ItemRequired formatExample
    WorkbookUserCode_Last4_YYYYMMDD.xlsxABC123_3933_20261102.xlsx
    EvidenceLast4_TransactionID_DocumentType_01.ext3933_TX123_invoice_01.pdf
    Email subjectCard dispute - User Code - Last4Card dispute - ABC123 - 3933
    Email bodyState the User Code and any brief context needed to identify the package.User Code ABC123
    Recipientchargeback@tevau.ioSend the workbook and all evidence in one complete email.

    8 Review and Outcome#

    Tevau checks the submission for completeness, eligibility, timing, and evidence. Tevau may ask for corrections before filing.
    When the case is eligible, Tevau submits the dispute through the card-network process. The merchant or acquiring bank may accept the claim or provide evidence to challenge it.
    If new evidence is received, Tevau may ask for the cardholder's response or additional documents. Send the requested material by the deadline in Tevau's message. Urgent requests may require a response within 24 hours.
    A case can proceed through further review, prearbitration, and arbitration. The final decision must be accepted by the parties.
    If a case proceeds to Visa arbitration, the party that does not meet the applicable requirements may be charged a USD 600 filing fee per transaction in addition to the disputed amount. Tevau will notify you via email to confirm whether to escalate to arbitration in the event that a chargeback fails. Please note that an arbitration fee will be charged if you choose to proceed; however, this $600 fee will be refunded if the arbitration is successful.
    Dispute handling can take several months. Tevau will notify you of the outcome and handle any recovered funds under your agreement.

    9 Final Submission Checklist#

    CheckConfirm before sending
    Card safetyThe card is frozen when it is lost, stolen, or compromised.
    Fraud reportingAll suspected fraud is reported, including low-value and declined transactions.
    EligibilityThe transaction is cleared, the amount and deadline requirements are met, and the reason is not excluded.
    Merchant contactThe full merchant communication chain is attached for processing and consumer cases.
    EvidenceAll scenario-specific evidence and the cardholder attestation are included where required.
    WorkbookAll 13 fields are complete and match the transaction record.
    DescriptionsEach row states the specific reason, chronology, merchant contact, and result.
    FilenamesThe workbook and evidence files use the required naming format.
    EmailThe subject, User Code, recipient, workbook, and all attachments are correct.
    ReadabilityScreenshots and documents are complete, dated, and legible.
    Modified at 2026-11-04 06:50:58
    Previous
    Reason for transaction rejection
    Next
    1.1 Create User
    Built with