Compared to the average sole trader, card-accepting merchants are a group with understandably more complex needs when it comes to payment acceptance. This begs the question – what do merchants truly want in a payment acceptance solution?
There are, of course, the hygiene factors:
Despite many providers focusing on these areas, one key aspect remains historically overlooked: flexibility. What exactly is flexibility? In this context, it refers to the ability for providers to tailor solutions based on an understanding of each merchant’s uniqueness: what may work for merchants in the hospitality sector may not necessarily translate to those in retail. Merchants are becoming increasingly discerning when it comes to their payment providers and are more likely to switch if their needs are not being met consistently.
How do you navigate these ever-changing needs and preferences of merchants, providing flexible solutions that are cost effective, innovative and don’t negatively impact your bottom line? Here are some recommendations on how to drive value with merchants and set you in a winning position.
Prioritise ease of use and time saving
Whilst merchants do have a plethora of solutions available to choose from, they lack the most valuable commodity of all: time. Time-poor merchants want a plug-and-play solution that will not take a long time to set up and learn. Providers that excel in this area are gaining traction; RFI Global data indicates that in the UK, as of 2021, providers with “easier” onboarding processes like Square and Shopify have grown their awareness to 33% and 21% respectively.
Merchants are increasingly looking for integrated, holistic services, reducing the need for manual intervention and reconciliation.
Build trust by showing appreciation for their unique needs
RFI Global data also shows that the ability to understand the needs of merchants, and leveraging this understanding to offer solutions to meet those needs and drive growth can have a clear impact on recommendations and NPS. This is because an appreciation of the unique needs of individual merchants will help foster a strong perception of trust – a top 2 driver of acquirer choice in the UK (38%), Canada (39%), and the USA (35%), and consistently strong driver of satisfaction. Conversely, how can a merchant trust a provider that does not appreciate and understand their needs?
Invest in innovation to curb switching
Now is the time for traditional payments providers to invest in innovation, with merchant switching appetite increasing from an average of 40% in 2020 to 49% at the end of 2021. Whilst the five key hygiene factors previously mentioned are undeniably important, merchants may increasingly look towards providers that innovate in order to provide solutions more suitable to their unique needs. If traditional providers fail to innovate, there is a substantial risk that merchants will leave these providers for those that do.
Furthermore, merchants who have had positive experiences when switching are more likely to do so again. RFI Global data shows that 62% of merchants who have switched providers successfully are willing to switch again, compared to only 21% willing to switch among those who have never switched. Understanding your merchant clients, and using that understanding to innovate and offer more relevant products and services will not only drive acquisition, but also improve retention as merchants will have no reason to look towards alternative providers to have their needs addressed.
Be more than a payments tool
Overall, merchants want a provider that fulfils the five key hygiene factors, but there is also an increasing desire for innovative solutions that meet the unique needs of their businesses. This can be achieved by offering flexible solutions that help support merchants as they grow, Moving forward, the providers that will find the most success will not be those offering merchants a payments solution, but instead those that become a trusted partner on their journey.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
AWSALBCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wpEmojiSettingsSupports | session | 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. |
XSRF-TOKEN | 2 hours | This cookie enhances visitor browsing security by preventing cross-site request forgery. |
Cookie | Duration | Description |
---|---|---|
AWSALB | 7 days | AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. |
AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
Cookie | Duration | Description |
---|---|---|
__hstc | 6 months | 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). |
_ga | 1 year 1 month 4 days | 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. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
hubspotutk | 6 months | 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. |
wmc | 1 year 1 month 4 days | Workable sets this cookie to assign a unique visitor ID for statistical purposes. |
Cookie | Duration | Description |
---|---|---|
_cfuvid | session | Description is currently not available. |