Responding to a Chargeback - ePayPolicy
The content from ePayPolicy explains their use of necessary cookies—such as those from Cloudflare and WordPress—to enable essential website functions like secure login, session management, real-time content updates, and emoji support, while also providing users options to customize their cookie consent preferences in accordance with privacy policies.
We Value Your Privacy
We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies. Please see our Privacy Policy for more information.
CustomizeReject AllAccept All
Customize Consent Preferences
We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site.... Show more
For more information on how Google's third-party cookies operate and handle your data, see: Google Privacy Policy
NecessaryAlways Active
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
- Cookie
__cf_bm
- Duration
1 hour
- Description
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
- Cookie
_cfuvid
- Duration
session
- Description
Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services
- Cookie
elementor
- Duration
Never Expires
- Description
The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time.
- Cookie
wpEmojiSettingsSupports
- Duration
session
- Description
WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly.
- Cookie
m
- Duration
1 year 1 month 4 days 1 minute
- Description
Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.
- Cookie
VISITOR_PRIVACY_METADATA
- Duration
6 months
- Description
YouTube sets this cookie to store the user's cookie consent state for the current domain.
- Cookie
_calendly_session
- Duration
21 days 1 minute
- Description
Calendly, a Meeting Schedulers, sets this cookie to allow the meeting scheduler to function within the website and to add events into the visitor’s calendar.
- Cookie
_zm_mtk_guid
- Duration
1 year 1 month 4 days
- Description
Zoom sets this cookie for the Zoom support team.
- Cookie
_zm_ctaid
- Duration
2 hours
- Description
Zoom sets this cookie for the Zoom support team.
- Cookie
cookieyes-*
- Duration
1 year
- Description
CookieYes sets this cookie for consent solution management.
- Cookie
wordpress_test_cookie
- Duration
session
- Description
WordPress sets this cookie to determine whether cookies are enabled on the users' browsers.
Functional
Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.
- Cookie
_gcl_au
- Duration
3 months
- Description
Google Tag Manager sets this cookie to experiment advertisement efficiency of websites using their services.
- Cookie
ea11y-global-state
- Duration
Never Expires
- Description
Elementor sets this cookie to store the persistent accessibility preferences selected by the user, such as panel visibility or interface adjustments, so these settings remain the same when the user revisits the sit
- Cookie
ea11y-session-state
- Duration
session
- Description
Elementor sets this cookie to temporarily store accessibility preferences for the duration of the current browsing session, ensuring the selected settings remain consistent while the user navigates the site.
- Cookie
VISITOR_INFO1_LIVE
- Duration
6 months
- Description
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
- Cookie
ytidb::LAST_RESULT_ENTRY_KEY
- Duration
Never Expires
- Description
The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future.
- Cookie
nitroCachedPage
- Duration
session
- Description
Description is currently not available.
- Cookie
_zitok
- Duration
1 year
- Description
Description is currently not available.
- Cookie
__Secure-BUCKET
- Duration
6 months
- Description
Description is currently not available.
- Cookie
_zm_chtaid
- Duration
2 hours
- Description
Zoom sets this cookie to facilitate video conferences via zoom from the website.
- Cookie
_hcc
- Duration
session
- Description
Used to load and display hosted image content from WordPress, supporting proper page rendering and a consistent visual browsing experience.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
- Cookie
__Secure-YNID
- Duration
6 months
- Description
YouTube cookie used to protect user security and prevent fraud, especially during the login process.
- Cookie
_ga
- Duration
1 year 1 month 4 days 1 minute
- Description
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
- Cookie
_gid
- Duration
1 day
- Description
Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously.
- Cookie
_ga_*
- Duration
1 year 1 month 4 days 1 minute
- Description
Google Analytics sets this cookie to store and count page views.
- Cookie
__rafm
- Duration
session
- Description
Ruler analytics sets this cookie to monitor and analyse the effectiveness of our online marketing spend.
- Cookie
ajs_anonymous_id
- Duration
Never Expires
- Description
This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
- Cookie
YSC
- Duration
session
- Description
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
- Cookie
vuid
- Duration
1 year 1 month 4 days 1 minute
- Description
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
- Cookie
navless-live-visitor
- Duration
1 year 1 month 4 days
- Description
Description is currently not available.
- Cookie
__hstc
- Duration
6 months
- Description
Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
- Cookie
hubspotutk
- Duration
6 months
- Description
HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.
- Cookie
__hssrc
- Duration
session
- Description
HubSpot cookie sets this cookie to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
- Cookie
__hssc
- Duration
1 hour
- Description
HubSpot sets this cookie to keep track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (which increments with each pageview in a session), and session start timestamp.
- Cookie
pardot
- Duration
past
- Description
The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking.
Performance
Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.
No cookies to display.
Advertisement
Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.
- Cookie
__Secure-ROLLOUT_TOKEN
- Duration
6 months
- Description
Description is currently not available.
- Cookie
__Secure-YEC
- Duration
past
- Description
Description is currently not available.
- Cookie
_rdt_uuid
- Duration
3 months
- Description
Reddit sets this cookie to build a profile of your interests and show you relevant ads.
- Cookie
MUID
- Duration
1 year 24 days
- Description
Bing sets this cookie to recognise unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations.
- Cookie
test_cookie
- Duration
15 minutes
- Description
doubleclick.net sets this cookie to determine if the user's browser supports cookies.
- Cookie
_uetsid
- Duration
1 day
- Description
Bing Ads sets this cookie to engage with a user that has previously visited the website.
- Cookie
_uetvid
- Duration
1 year 24 days
- Description
Bing Ads sets this cookie to engage with a user that has previously visited the website.
- Cookie
IDE
- Duration
1 year 24 days
- Description
Google DoubleClick IDE cookies store information about how the user uses the website to present them with relevant ads according to the user profile.
Uncategorised
Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet.
- Cookie
__obref
- Duration
1 year
- Description
Description is currently not available.
- Cookie
_hcr
- Duration
session
- Description
Used to support website functionality by storing visitor session or preference information associated with embedded content, page interactions, and related data.
Reject AllSave My PreferencesAccept All
Powered by 
Responding to a Chargeback
Everything you need to know about how to respond to a chargeback can be found below
How do I dispute the chargeback?
When will funds be withdrawn from my account?
What is a chargeback?
A chargeback is a notification that a customer is refuting the charge on their account. Chargebacks are rare in the insurance industry, but they do occur. The most common reason for a chargeback is that the cardholder does not recognize the charge on their credit card. (ePayPolicy ensures that it is the insurance entity’s name that appears on the credit card statement and not our name.)
Keep in mind that the chargeback notification is the start of the process; not the end. As the “merchant” on the chargeback you have the opportunity to respond and dispute the chargeback.
For more detailed information, visit our Help Knowledge Base.
How do I dispute the chargeback?
We recommend two steps to dispute the chargeback. First, please gather any and all documentation you have between you and your customer leading up to the chargeback. This can include email correspondence, signed contracts, or any other written documentation. Each chargeback has a deadline to respond. Chargeback response periods vary by card network, with most schemes allowing a window between 7 – 30 days to submit a rebuttal.
The second step is to contact the customer and notify them that you have received the chargeback notification. If the chargeback was a mistake on their part, they should notify their bank that they will allow the charge to go through.
IMPORTANT: Even if the customer has agreed to let the original transaction go through, you will still need to send the requested documentation to ePayPolicy. This is because the chargeback process has already started and the issuing bank is waiting on a response. If no response is given, the chargeback will be approved by default.
If you respond with required documentation in the allotted timeframe and the issuing bank does not fight your dispute, it will take approximately 80 days for you to win by default at which point the funds will be returned to your account.
When will funds be withdrawn from my account?
Your account will automatically be debited at the point the chargeback is reported. The funds will be returned to you if you win the dispute.
Shopping Basket
Text
Bigger text
Line height
Text align
Readable font
Visual
Contrast
Grayscale
Hide images
Pause animations
Orientation
Highlight links
Reading mask
Outline focus
Sitemap
Page structure