📃
Developer Docs
  • Overview
  • Integration Options
  • Webhooks
    • Build a webhook endpoint
    • Check signature
  • Getting Started
    • 1. Creating User Accounts
    • 2. User Account Types & Permissions
    • 3. Generate Access Tokens
    • 4. Choose Integration Options
    • 5. Securing Embedded UIs
      • 5a. Securing Embedded UIs Using HMAC (deprecated)
    • 6. Loading the frontend library
      • 6a. Preloading PayEngine Web-Component in SPA
    • 7. Custom styling the Web-Components
    • 8. Handling Callbacks from Web-Components
    • 9. Available Web-Components
    • 10. Available Webhooks
  • Merchant Onboarding
    • Overview
    • Integration Options
    • Onboarding/Payments Application Workflow
    • Embedded Onboarding UI
    • Merchant onboarding APIs
    • Partner's Onboarding UI
    • Merchant Lifecycle
    • Onboarding to Partner Relationships
  • Processing Payments
    • Introduction
      • Transaction Flow and Status
    • SecureFields JS
      • SecureFields Bank Account
      • Using tokens
    • Credit Card Form
    • Connect with Plaid
    • Connect Mailgun
    • 3D Secure
    • Payments API
    • Searching Transactions
    • Registering a cloud connected device
    • Apple Pay
      • Apple Pay in your native app
    • Google Payâ„¢
    • Level 2 and Level 3 Data
    • Fraud Prevention
    • Reporting
    • PCI Compliance
    • Address Verification Service (AVS) Check
    • Hosted Payments
    • Tap to Pay
  • Card Account Updater
  • ORCHESTRATION SYSTEM
    • Orchestration Overview
    • Onboarding Orchestration
    • Transactions Orchestration
    • Omnicommerce Orchestration
    • Merchant Servicing
    • Universal Reporting
  • TOKENIZATION
    • Automatic Network Tokenization
    • Token Migration Process
  • DISPUTE MANAGEMENT
    • Retrieval Requests & Chargebacks
  • Certification
    • Partner Certification
  • Data Sharing
    • Secure Data Sharing with PayEngine
  • eCommerce Integration
    • PayEngine Payment Gateway for WooCommerce
Powered by GitBook
On this page
  1. DISPUTE MANAGEMENT

Retrieval Requests & Chargebacks

The Interplay of Chargebacks and Retrieval Requests in Credit Card Networks

In the realm of credit card transactions, understanding the difference between chargebacks and retrieval requests is crucial for merchants. These two processes serve distinct purposes, have unique implications, and play integral roles in maintaining a balanced and fair transaction ecosystem.

A chargeback is a process initiated by a credit card issuer at the request of a cardholder disputing a specific transaction. It essentially reverses a payment, withdrawing funds from the merchant's account and returning them to the cardholder. This mechanism provides a layer of protection to consumers against fraudulent charges or unsatisfactory services. However, chargebacks can lead to potential financial losses and reputation damage for merchants.

On the other hand, a retrieval request is a preliminary step often taken when a cardholder questions a specific charge on their statement. This process does not immediately involve the movement of funds but rather seeks additional information about the transaction from the merchant. The issuer requests documentation or evidence to verify the validity of the transaction.

Interestingly, the retrieval request phase presents an opportunity for merchants to circumvent the possible negative repercussions of a chargeback. If a merchant issues a refund during a retrieval request, this pre-empts the need for a chargeback, thereby saving on associated costs and avoiding potential damage to their standing with the credit card network. Many chargeback prevention service companies use this tactic as a key strategy in their operations. These firms closely monitor transaction disputes and, upon identification of a retrieval request, guide merchants to proactively issue refunds where applicable.

This is an effective method for preventing an actual chargeback from occurring, thus offering a win-win situation for all parties involved: the customer receives their refund, the merchant avoids additional fees and potential reputational damage, and the overall integrity of the transaction process is upheld.

PreviousToken Migration ProcessNextPartner Certification

Last updated 10 months ago