From 665345fd7c0540bcc6726ff7fe47ee7b47707d29 Mon Sep 17 00:00:00 2001
From: Shendy <73803630+shendy-a8c@users.noreply.github.com>
Date: Thu, 12 Oct 2023 01:12:34 +0700
Subject: [PATCH 1/7] Delete legacy `acceptDispute()` action and renamed
`acceptTransactionDetailsDispute()` to `acceptDispute()`.
---
client/data/disputes/actions.js | 62 +--------------------------------
client/data/disputes/hooks.ts | 4 +--
2 files changed, 3 insertions(+), 63 deletions(-)
diff --git a/client/data/disputes/actions.js b/client/data/disputes/actions.js
index 4a0f82197e1..3979390e3cf 100644
--- a/client/data/disputes/actions.js
+++ b/client/data/disputes/actions.js
@@ -13,7 +13,6 @@ import { __, sprintf } from '@wordpress/i18n';
import { NAMESPACE, STORE_NAME } from '../constants';
import TYPES from './action-types';
import wcpayTracks from 'tracks';
-import { getAdminUrl } from 'wcpay/utils';
import { getPaymentIntent } from '../payment-intents/resolvers';
export function updateDispute( data ) {
@@ -48,66 +47,7 @@ export function updateDisputesSummary( query, data ) {
};
}
-export function* acceptDispute( id ) {
- try {
- yield controls.dispatch( STORE_NAME, 'startResolution', 'getDispute', [
- id,
- ] );
-
- const dispute = yield apiFetch( {
- path: `${ NAMESPACE }/disputes/${ id }/close`,
- method: 'post',
- } );
-
- yield updateDispute( dispute );
- yield controls.dispatch( STORE_NAME, 'finishResolution', 'getDispute', [
- id,
- ] );
-
- // Redirect to Disputes list.
- window.location.replace(
- getAdminUrl( {
- page: 'wc-admin',
- path: '/payments/disputes',
- filter: 'awaiting_response',
- } )
- );
-
- wcpayTracks.recordEvent( 'wcpay_dispute_accept_success' );
- const message = dispute.order
- ? sprintf(
- /* translators: #%s is an order number, e.g. 15 */
- __(
- 'You have accepted the dispute for order #%s.',
- 'woocommerce-payments'
- ),
- dispute.order.number
- )
- : __( 'You have accepted the dispute.', 'woocommerce-payments' );
- yield controls.dispatch(
- 'core/notices',
- 'createSuccessNotice',
- message
- );
- } catch ( e ) {
- const message = __(
- 'There has been an error accepting the dispute. Please try again later.',
- 'woocommerce-payments'
- );
- wcpayTracks.recordEvent( 'wcpay_dispute_accept_failed' );
- yield controls.dispatch( 'core/notices', 'createErrorNotice', message );
- }
-}
-
-// This function handles the dispute acceptance flow from the Transaction Details screen.
-// It differs from the `acceptDispute` function above in that it also fetches and updates
-// the payment intent associated with the dispute to reflect changes to the dispute
-// on the Transaction Details screen.
-//
-// Once the '_wcpay_feature_dispute_on_transaction_page' is enabled by default,
-// the `acceptDispute` function above can be removed and this function can be renamed
-// to `acceptDispute`.
-export function* acceptTransactionDetailsDispute( dispute ) {
+export function* acceptDispute( dispute ) {
const { id, payment_intent: paymentIntent } = dispute;
try {
diff --git a/client/data/disputes/hooks.ts b/client/data/disputes/hooks.ts
index e3797499537..fac77fd28b3 100644
--- a/client/data/disputes/hooks.ts
+++ b/client/data/disputes/hooks.ts
@@ -72,8 +72,8 @@ export const useDisputeAccept = (
},
[ dispute.id ]
);
- const { acceptTransactionDetailsDispute } = useDispatch( STORE_NAME );
- const doAccept = () => acceptTransactionDetailsDispute( dispute );
+ const { acceptDispute } = useDispatch( STORE_NAME );
+ const doAccept = () => acceptDispute( dispute );
return { doAccept, isLoading };
};
From a8499d99f4b7a83e2af5e147bf5006220fe45dab Mon Sep 17 00:00:00 2001
From: Shendy <73803630+shendy-a8c@users.noreply.github.com>
Date: Thu, 12 Oct 2023 01:53:15 +0700
Subject: [PATCH 2/7] Pass dispute object instead of dispute id to
`acceptDispute()`.
---
client/data/disputes/hooks.ts | 2 +-
client/data/disputes/test/actions.js | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/client/data/disputes/hooks.ts b/client/data/disputes/hooks.ts
index fac77fd28b3..57ecae1bac0 100644
--- a/client/data/disputes/hooks.ts
+++ b/client/data/disputes/hooks.ts
@@ -47,7 +47,7 @@ export const useDispute = (
);
const { acceptDispute } = useDispatch( STORE_NAME );
- const doAccept = () => acceptDispute( id );
+ const doAccept = () => acceptDispute( dispute );
return { dispute, isLoading, error, doAccept };
};
diff --git a/client/data/disputes/test/actions.js b/client/data/disputes/test/actions.js
index f70a2d8da5e..fa79fcecffc 100644
--- a/client/data/disputes/test/actions.js
+++ b/client/data/disputes/test/actions.js
@@ -27,7 +27,7 @@ describe( 'acceptDispute action', () => {
} );
test( 'should close dispute and update state with dispute data', () => {
- const generator = acceptDispute( 'dp_mock1' );
+ const generator = acceptDispute( mockDispute );
expect( generator.next().value ).toEqual(
controls.dispatch( 'wc/payments', 'startResolution', 'getDispute', [
@@ -65,7 +65,7 @@ describe( 'acceptDispute action', () => {
} );
test( 'should show notice on error', () => {
- const generator = acceptDispute( 'dp_mock1' );
+ const generator = acceptDispute( mockDispute );
generator.next();
expect( generator.throw( { code: 'error' } ).value ).toEqual(
From 887af5466cecc2d5ea28f92902f841e9e3396ea5 Mon Sep 17 00:00:00 2001
From: Shendy <73803630+shendy-a8c@users.noreply.github.com>
Date: Thu, 12 Oct 2023 01:54:00 +0700
Subject: [PATCH 3/7] Fix unit test around `acceptDispute()` action.
---
client/data/disputes/test/actions.js | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/client/data/disputes/test/actions.js b/client/data/disputes/test/actions.js
index fa79fcecffc..68639fc1e20 100644
--- a/client/data/disputes/test/actions.js
+++ b/client/data/disputes/test/actions.js
@@ -10,12 +10,14 @@ import { controls } from '@wordpress/data';
* Internal dependencies
*/
import { acceptDispute, updateDispute } from '../actions';
+import { getPaymentIntent } from '../../payment-intents/resolvers';
describe( 'acceptDispute action', () => {
const mockDispute = {
id: 'dp_mock1',
reason: 'product_unacceptable',
status: 'lost',
+ payment_intent: 'payment_intent',
};
beforeEach( () => {
@@ -43,6 +45,9 @@ describe( 'acceptDispute action', () => {
expect( generator.next( mockDispute ).value ).toEqual(
updateDispute( mockDispute )
);
+ expect( generator.next().value ).toEqual(
+ getPaymentIntent( mockDispute.payment_intent )
+ );
expect( generator.next().value ).toEqual(
controls.dispatch(
'wc/payments',
@@ -53,7 +58,6 @@ describe( 'acceptDispute action', () => {
);
const noticeAction = generator.next().value;
- expect( window.location.replace ).toHaveBeenCalledTimes( 1 );
expect( noticeAction ).toEqual(
controls.dispatch(
'core/notices',
From ab9ce76644e66fd0a19c5ab2083f548347af24b2 Mon Sep 17 00:00:00 2001
From: Shendy <73803630+shendy-a8c@users.noreply.github.com>
Date: Thu, 12 Oct 2023 01:57:25 +0700
Subject: [PATCH 4/7] Changelog.
---
changelog/remove-7363-unused-dispute-details-code | 5 +++++
1 file changed, 5 insertions(+)
create mode 100644 changelog/remove-7363-unused-dispute-details-code
diff --git a/changelog/remove-7363-unused-dispute-details-code b/changelog/remove-7363-unused-dispute-details-code
new file mode 100644
index 00000000000..da3e0db1cf4
--- /dev/null
+++ b/changelog/remove-7363-unused-dispute-details-code
@@ -0,0 +1,5 @@
+Significance: patch
+Type: dev
+Comment: Removing unused legacy dispute details code that does not affect user facing UX.
+
+
From 0cc1db389e250ab33eaeafe1cbf9c0c438d44ef5 Mon Sep 17 00:00:00 2001
From: Shendy <73803630+shendy-a8c@users.noreply.github.com>
Date: Thu, 12 Oct 2023 06:42:46 +0700
Subject: [PATCH 5/7] Remove unused `LegacyDisputeDetails` /
`client/disputes/details/index.tsx`.
---
client/disputes/details/index.tsx | 159 ------------------------------
1 file changed, 159 deletions(-)
delete mode 100644 client/disputes/details/index.tsx
diff --git a/client/disputes/details/index.tsx b/client/disputes/details/index.tsx
deleted file mode 100644
index e8af4bbcf97..00000000000
--- a/client/disputes/details/index.tsx
+++ /dev/null
@@ -1,159 +0,0 @@
-/** @format **/
-
-/**
- * External dependencies
- */
-import React from 'react';
-import { __, sprintf } from '@wordpress/i18n';
-import { Card, CardBody, CardFooter, CardHeader } from '@wordpress/components';
-
-/**
- * Internal dependencies.
- */
-import { useDispute } from 'data/index';
-import { reasons } from '../strings';
-import Actions from './actions';
-import Info from '../info';
-import Paragraphs from 'components/paragraphs';
-import Page from 'components/page';
-import ErrorBoundary from 'components/error-boundary';
-import DisputeStatusChip from 'components/dispute-status-chip';
-import Loadable, { LoadableBlock } from 'components/loadable';
-import { TestModeNotice, topics } from 'components/test-mode-notice';
-import '../style.scss';
-import { Dispute } from 'wcpay/types/disputes';
-
-const LegacyDisputeDetails = ( {
- query: { id: disputeId },
-}: {
- query: { id: string };
-} ): JSX.Element => {
- const { dispute, isLoading, doAccept } = useDispute( disputeId );
- const disputeObject = dispute || ( {} as Dispute );
- const disputeIsAvailable = ! isLoading && dispute && disputeObject.id;
-
- const actions = disputeIsAvailable && (
-
- { ' ' }
- { __(
- 'Required to overturn dispute',
- 'woocommerce-payments'
- ) }{ ' ' }
-
- ) }
-
- { __(
- 'How to respond',
- 'woocommerce-payments'
- ) }
-
- ) }
-
+ { ' ' }
+ { __(
+ 'Required to overturn dispute',
+ 'woocommerce-payments'
+ ) }{ ' ' }
+
+ ) }
+
+ { __(
+ 'How to respond',
+ 'woocommerce-payments'
+ ) }
+
+ ) }
+
- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If your customer was not refunded appropriately, you will need to accept the dispute, or resolve the issue with your customer. The credit card networks place liability for accepting disputed payments with you, the business. -
-- The customer claims that the purchased product was returned or the transaction was otherwise canceled, but you have not yet provided a refund or credit. -
-- Demonstrate that you have refunded your customer through other means or that your customer is not entitled to a refund. You cannot issue a refund while a payment is being disputed. If you believe that your customer was entitled a refund that you did not provide, you can accept the dispute. -
-- You should first get in touch with your customer. If you understand what their complaint is, there is a chance for you to explain the misunderstanding or to make it right. If you’re able to resolve the issue with your customer, you can ask that they withdraw the dispute. -
-- If the cardholder agrees to withdraw the dispute, you should still submit evidence for the dispute using the forms on the next screen. In addition to the following evidence, your submission should include correspondence with the cardholder saying they would withdraw the dispute and a written statement from their card issuer confirming that the dispute has been withdrawn. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If there were duplicate payments, you should accept the dispute. You cannot issue a refund while a payment is being disputed. The credit card networks place liability for accepting disputed payments with you, the business. -
-- The customer claims they were charged multiple times for the same product or service. -
-- Demonstrate that each payment was for a separate product or service. -
-- Determine if your customer was incorrectly charged multiple times. -
-- If they were not, collect any and all information documenting that each payment was made separately, such as copies of receipts. If the receipts don’t include the items purchased, be sure to include an itemized list. Each receipt should clearly indicate that the payments are for separate purchases of items or services. If you’ve been able to get in touch with the customer you should be sure to address any concerns they had in your evidence. -
-- If there have been two or more separate payments, you should get in touch with your customer. If you understand what their complaint is, there is a chance for you to explain the misunderstanding or to make it right. If you’re able to resolve the issue with your customer, you can ask that they withdraw the dispute. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- This is an uncategorized dispute, so you should contact the customer for additional details to find out why the payment was disputed. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you can not prove the customer received their product or service, you should accept the dispute. You cannot issue a refund while a payment is being disputed. The credit card networks place liability for accepting disputed payments with you, the business. -
-- The customer claims they did not receive the products or services purchased. -
-- Prove that the customer received a physical product or offline service, or made use of a digital product or online service. This must have occurred prior to the date the dispute was initiated. -
-- First, get in touch with your customer. Understanding why they filed the dispute will be important for helping make sure your customer gets the product and will give you critical information to prevent this from happening to others. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you can not prove the customer received their product or service as described, you should accept the dispute. You cannot issue a refund while a payment is being disputed. The credit card networks place liability for accepting disputed payments with you, the business. -
-- The product or service was received but was defective, damaged, or not as described. -
-- Demonstrate that the product or service was delivered as described at the time of purchase. -
-- If the product or service is as described, provide specific information (invoice, contract, etc.) to refute the cardholder’s claims. Quality disputes are where the customer does not agree with the condition of merchandise or service received (e.g., a car repair situation or quality of a hotel room). There may be instances where you will need to obtain a neutral third-party opinion to help corroborate your claim against the cardholder. Provide as much specific information and documentation as possible to refute the cardholder’s claims. It is recommended that you address each point that the cardholder has made. -
-- If the customer has not yet returned the product or canceled the service, provide specific information to that effect. You should double-check your incoming shipping records to verify that you have not received a return before you respond. If you have processed a credit or reversal for this transaction, provide evidence of this which includes the amount and date processed. -
-- For products that have been repaired or replaced, provide evidence that the cardholder agreed to a repair or replacement, it has been received by the customer, and the repair or replacement has not since been disputed. -
-- If your customer made no attempt to return the product or cancel the service, or if you provided a replacement product or service, make sure to note that as well. -
-- If the customer withdraws their dispute you should still submit evidence using the forms on the next screen. Be sure to provide a letter or email from the cardholder stating that they are no longer in dispute. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you can not prove the customer’s subscription was canceled, and or they did not follow your cancellation policy, you should accept the dispute. You cannot issue a refund while a payment is being disputed. The credit card networks place liability for accepting disputed payments with you, the business. -
-- The customer claims that you continued to charge them after a subscription was canceled. -
-- Prove that the subscription was still active and that the customer was aware of, and did not follow, your cancellation procedure. -
-- First, get in touch with your customer. If you understand what they believe happened, there is a chance for you to explain the misunderstanding or to make it right. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- Otherwise, use the forms on the next screen to submit evidence that the subscription was still active and that the customer was aware of, and did not follow, your cancellation procedure. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you can not prove the customer’s subscription was canceled, and or they did not follow your cancelation policy, you should accept the dispute. You cannot issue a refund while a payment is being disputed. The credit card networks place liability for accepting disputed payments with you, the business. -
-- The customer doesn’t recognize the payment appearing on their card statement. -
-- Get your customer to withdraw the dispute by helping them identify the payment. Otherwise, challenge the dispute with appropriate evidence that proves the purchase was legitimate. -
-- First, try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-- If you believe the dispute is invalid, you can challenge it by submitting the appropriate evidence using the response forms on the next screen. -
-- If you believe the payment was actually made using a stolen credit card, you will need to accept the dispute. The credit card networks place liability for accepting unauthorized transactions with you, the business. -
-- This is the most common reason for a dispute, and happens when a cardholder claims that they didn’t authorize the payment. This can happen if the card was lost or stolen and used to make an unauthorized transaction. It can also happen if the cardholder doesn’t recognize the payment as it appears on the billing statement from their card issuer. -
-- Provide adequate payment and order details so that a legitimate customer recognizes it, or proves to the card issuer that their cardholder authorized the transaction. -
-- Try to get in touch with your customer. Sometimes people forget about payments they make or don’t recognize the way they appear on their card statement. If this is the case, ask them to contact their card issuer and let them know they no longer dispute the transaction. -
-- Even if your customer agrees to withdraw the dispute, you must still submit appropriate evidence using the forms on the next screen. Simply saying that your customer is going to withdraw the dispute is not sufficient evidence. -
-- It may be more efficient—and provide a better customer experience—to accept an accidental dispute and charge the customer again, if appropriate. Even when a dispute is withdrawn, it usually takes approximately 75 days to be finalized. Remember, it doesn’t matter to the card networks whether you win or lose a dispute; what matters is how many disputes a business receives, regardless of how many disputes are won. -
-