Tag Archive for: Single API

Paydock, an enterprise-grade payments orchestration platform appoints Jenela Gunasekaran as its Chief Product Officer. This significant appointment emphasises the increasingly recognised role of payments orchestration as well as Paydock’s leadership in the sector.

Jenela brings over 16 years of experience across product, technology, and financial services to her new role at Paydock. She joins from HSBC where she held the role of Head of Product at its mobile payment service PayMe in Hong Kong for almost three years and led a team of product managers, engineers and tech writers to launch online payments for merchants and numerous distribution models for partners, serving over 2.3 million PayMe consumers.

Prior to her role at HSBC, Jenela spent over five years as Principal Product Manager at PayPal where she was responsible for multiple products focused on minimising seller fraud and credit risk across geographies. In this role, she partnered with global business units and policy makers to create product vision and lead multi-year product strategies and a scalable and robust platform to deliver business positive outcomes for PayPal. 

Commenting on the appointment, Robert Lincolne, founder and CEO of Paydock, said: “We are delighted to be able to attract such high calibre international talent to our team. Innovation sits at the heart of Paydock and our market-leading team, product and services is a testament to this. Jenela’s expertise will undoubtedly add significant value and competitive advantage to our offering. 

Jenela is passionate about creative use of technology to build inclusive and sustainable products. She has vast experience in e-Commerce, Digital Payments, Fraud and Credit Risk, API as a Product and Software Application Life-cycle Management.

Commenting on her appointment, Jenela Gunasekaran said: “With accelerated digitisation and businesses eager to rapidly adapt to changing consumer preferences, Paydock’s payment orchestration is uniquely positioned to play a pivotal role in helping businesses offer fast, secure, reliable, and a cost effective payments experience to their consumers in their preferred mode of payment. I am very excited to join the incredibly talented team at Paydock and I look forward to driving further innovation on the platform.”

We’re ecstatic to announce our partnership with Bleckwen AI as part of the continuation of our vision to ensure merchants are maximising acceptance while minimising fraud.

 

If as a merchant, you are not currently optimising your fraud strategy you are likely leaving significant profit on the table. It’s time to put that  money back in your bank account.
– Rob Lincolne, Founder @ Paydock

 

Bleckwen is an award-winning Behavioural Analytics software company, dedicated to help Banks and Financial Institutions to defeat fraud and make a safer world. They take state-of-the-art technologies, applied research, quality engineering and passion to deliver great solutions.

Matching this with Paydock’s agnostic and accessible  infrastructure, means merchants and charities can rapidly ‘step up’ and adopt leading tools and services without having to undergo disruptive internal change.

We have overnight removed the requirement for you to wait for your gateway to update their fraud infrastructure, removed the requirement for a 12 month internal payments transformation project, and eliminated the need for you to to create an internal fraud division to be ‘best-practice’.

PayDock’s agnostic payment rail is specifically designed to enable you to rapidly capitalise on and adopt best-of-breed solutions such as Bleckwen and ensure you are always ahead of the curve and capturing previously lost profit within your overall payments system.

 

“We’re excited to partner with PayDock as this allows us to combine our expertise and technology to out-smart the bad guys and better protect consumers. Our purpose is to Create a Safer Societe and our relationship with Paydock delivers a cost effective, fast, frictionless and more secure service for merchants.”
– David McLaren, VP Sales EMEA at Bleckwen

A major and fast-growing problem

Card-not-present (CNP) fraud is set to tear a USD $130bn  hole out of the e-commerce and digital market between 2019 and 2023 [1]. Efforts to combat the growing problem are expected to exceed USD $9.6bn in 2018 alone. This is a big deal.

Beyond the 33% CNP fraud increase from 2015 to 2016 [2]  false positives stripped a further $331bn out of the retail market in 2018 [3], itself a significant increase from 2016. So it’s not just a simple case of locking out the fraudsters, many legitimate purchasers have their customer experience disrupted or stopped completely due to efforts to address this growing threat.

A false positive is an expensive problem alongside the legitimate blocking activites – and it’s all expensive and costing the merchant, even if they don’t realise what they’re ‘not getting’.

Old approaches give way to sophisticated solutions

Older ‘rules based’ fraud services simply no longer have the firepower to combat fraud as needed [4] however the rise of AI (artificial intelligence) and ML (machine learning) technologies have provided a number of exciting tools necessary to combat this rise.

The ability to stop fraud in real-time rather than ‘after the fact’ is a gamechanger. AI/ML can analyse transactional information immediately as and when transactions take place and enable assessments that ensure false positives are kept to a minimum while contemporary and nuanced information is incorporated in runtime for results in less than a second.

 

Inflexible rule-based fraud solutions deliver too many false positives, locking out genuine buyers or causing obstacles in their shopping journey. Unsurprisingly, this makes them rethink their purchase decision. In contrast, machine learning continuously monitors buyer data based on identity and behavior, resulting in a highly accurate fraud score. [5]

 

AI and ML is the future. As the fraudsters come to grips with these tools it’s also up to providers like PayDock as well as merchants to make sure they are well protected and consistently ahead of malicious operators in the market.

See our announcement (and why we’re excited)

 

Announcing: PayDock + Bleckwen

[1] Digital card-not-present fraud to hit $130B by 2023 –  https://www.retaildive.com/news/digital-card-not-present-fraud-to-hit-130-billion-by-2023/545171/

[2] Card-Not-Present FraudIs Skyrocketing. – https://www.clear.sale/Infographics/cnp-fraud-is-skyrocketing

[3] False Positives: The Unintended Consequences of Mitigating Card-Not-Present Fraud. – https://www.fisglobal.com/insights/what-we-think/2018/october/card-not-present-fraud-cnp

[4] Rise of the learning machines: How AI is becoming the newest weapon in the fraud fight. – https://www.retaildive.com/news/rise-of-the-learning-machines-how-ai-is-becoming-the-newest-weapon-in-the/434191/

[5] Rules vs Scores: keeping fraud simple with Machine Learning – https://thepaypers.com/expert-opinion/rules-vs-scores-keeping-fraud-simple-with-machine-learning/773108

PayPal recurring payments are dead easy on Paydock.

Online merchants can access rich recurring functionality, improve their brand experience and reduce internal time, cost and effort when taking and managing recurring payments through PayPal with Paydock.

PayPal is a vital part of the payments ecosystem, with over 7bn transactions processed during 2017 (Statista). If you are not taking PayPal as part of your payment strategy, you could be missing out on significant revenue.

PayPal had a higher overall conversion rate than all competitors with the next payment option scoring 36.4% lower than PayPal on average. *

Paydock provides rich benefits to any merchant seeking to drive subscriptions, memberships or recurring donations on PayPal.

Why use PayPal with Paydock?

Showcase

The team at Leafcutter recently developed a donation experience for the Children’s Hospital Foundation lifting conversions and reducing cost of integration and payment management.  See the payment experience in action below. The solution includes both one-off and recurring payments through a single integration.

 

If you would like to find out how Paydock can help improve your conversions, simplify your payments life and reduce effort, contact our friendly payments team and drop us a line.

* Data source comScore Panel, US, Q4 2015

Photo by rawpixel on Unsplash

Following on from our .Net & Java SDKs, we’ve now released our php SDK. This provides a friendly way to access Paydock, making it even easier to use Paydock.

 

You can pull this down through composer on Packagist

The code is open source on github.

Providing the right interface

One of the questions when putting together a new SDK is how to support this in a way that is as language friendly as possible. What we’ve put together for a strongly typed language like .Net, just doesn’t make as much sense for a dynamically typed language like php.

The simplest approach to this would be to simply map through the request, serialised as json, eg something like this:

1 $request = [“amount” => 100, “currency” => “AUD”, “token” => “token_id”]
2 $response = Charges::Create($request);

This works fine with simpler requests, but it tends to make it hard with larger, more complex request. In those cases, it’s easy to create a situation where you send through either too many parameters or too few. Also, when you can send through nested sets of parameters, it’s easy to send through parameters encoded at the wrong depth, e.g.:

1 // missing items object
2 $request = [“amount” => 100, “currency” => “AUD”, “token” => “token_id”, “transfer” => [“amount” => 25, “destination” => “account_id”]]
3 // correct structure
4 $request = [“amount” => 100, “currency” => “AUD”, “token” => “token_id”, “transfer” => [ “items” => [“amount” => 25, “destination” => “account_id”]]]

For this reason we settled on a fluent style interface.

Fluent interface

Using a fluent interface, you build up a request through a number of calls. Some good examples of fluent interfaces are things like LINQ in .Net:

1 var topOrders = orders.Where(o => o.Currency = “AUD”)
2 .OrderBy(o => o.Amount)
3 .Take(100)
4 .Select(o => o.Email);

These are often a very natural way of searching for data, but also work well to build up complex requests.

In order to make this as clear as possible, we’ve followed certain conventions. An example of this in the SDK is creating a charge with bank account details:

1 $response = $svc->create("John","Smith","[email protected]","+61414111111")
2 ->withBankAccount(self::bsbGateway, "test", "012003", "456456")
3 ->includeAddress("1 something st", "", "NSW", "Australia", "Sydney"2000")
4 ->call();

The first call is part of the call specifies the action (create). If this needs additional data, this is send through as with<Something>. Optional data is added through include<something>. And finally call() makes the actual call.

This made the API more complex to build, but provided a better experience of using the API.

As always, we’re open to improving this, so please raise any issues or concerns on on github and we’ll jump on it!

PayDock has now released Java SDK, which can be downloaded from JCentre. There are different dependency snippets to be inserted in your code based on your selected build settings (we support Gradle, Maven or Ivy).

The library is opened sourced and can be found here. Specific tests for you to reference in your program are here.

Planning

Writing the Java SDK was interesting and our approach changed over time. There were a few considerations

  1. Which HTTP library to use: I settled on HttpsURLConnection instead of Apache’s client. I found an example which worked early on so I didn’t change it.
  2. Which JSON library to use to map the data models: I settled on the GSON library from Google as it also handled the date format.
  3. How to deal with ever increasing API functionality while keeping the the code base similar: You will find I extend a few base classes to try maintain the peace.

IDE

I used Android Studio to write the PayDock Java SDK. As I was also planning to write an Android SDK, it only felt natural that I use this IDE to create the library. Creating Java libraries in this IDE are quite simple and it allowed me to use the same repository and build scripts that I would for the Android SDK. Having written a few projects in Android Studio in the past made me feel comfortable using it. From the one IDE, I had the ability to write the Java library, include the functionality tests, link into GitHub for source control and then upload the library to JCentre for distribution. In the project file, I had a simple app which referenced the remote Java library on JCentre. This allowed me to verify that the library worked as expected when downloaded from the repository.

Structure of the SDK

The SDK is split into three sections:

  • Models – contained the structure of the data to be sent and received.
  • Services – contained the methods exposed in the SDK, such as add charges.
  • Tools – contained helpful methods that the services used, such as the HTTP connection class and the query string to url class.

Using this format made it easy to add new endpoints and features as they were added to the API.

Publishing

I used some libraries which easily allowed me to upload the SDK to Jcentre via Bintray. Once some of the artifacts were set, all I had to do was change the library version every time I wanted to upload the library. After the initial set up it now only takes a few seconds to upload a new version of the library to JCentre.

You can use the following steps to upload the library to Bintray, assuming you have already set up an account with them:

  1. In local.properties of your project file set your bintray credentials
    bintray.apikey=<your api key here>
    bintray.user=<your user name>
  2. Add the correct scripts and the library artifacts in your build.gradle
    My build.gradle can be found here
  3. Run the following commands in the terminal
    ./gradlew build
    ./gradlew install
    ./gradlew bintrayUpload

Use the SDK

I put a link to the SDK earlier in the piece so you can download the SDK and I look forward to any reviews and comments. Happy coding!

From prehistoric systems of barter and trade to simple forms of currency, and paper cheques to little plastic cards, it is evident that payment methods are constantly evolving. The modern rise of new alternative payments methods (non cash methods of transaction) such as E-wallets, digital currency, mobile payment methods and so forth can be seen as a new chapter in the world of payments. Alternative payment methods (APMs) are now predicted to take a 59% share in all e-commerce transactions in 2017. An example of an Alternative Payment Method that is changing the e-commerce industry are Buy Now, Pay Later schemes.

 

The increased popularity of Buy Now, Pay Later (BNPL) schemes such as Afterpay and ZipMoney have created new opportunities for savvy e-commerce stores. Consumers are able to pay for their goods with instalments over a period of time while retailers receive payment on the day of the purchase with all credit and fraud risk taken on by the relevant BNPL scheme.

 

In particular, the flexibility of Afterpay has attracted a large amount of consumers, holding a 10% share of all transactions in the Australian online fashion market and a 2.1% share in the online retail market. Various retailers, such as Veronika Maine and General Pants Co have stated that their average order value increased by 22-25% after introducing Afterpay.

 

What can you do?

By offering BNPL schemes such as Afterpay and ZipMoney, you not only capture potential customers but also increase the amount and value of goods they purchase. ZipMoney observed an increase in average order values of between 40%-130% (where zipMoney is the chosen form of tender) and a 40% increase in items per order.

 

How can Paydock help?

Paydock enables e-commerce stores to offer both APMs and traditional payment methods to their consumers. Paydock customers can now snap up more customers and generate additional sales through BNPL schemes with ease through our API.

What is checkout friction?

Checkout friction is anything that stands between your customer wanting a product and being able to purchase it. This includes things that slow down the process, including typos, slow loading pages, pop up ads, sign up processes or even things that stop the purchase altogether, such as an outdated link on a “buy now” button.

Checkout friction is the largest cause of cart abandonment rates; even higher than hidden shipping costs, complicated return policies and security concerns.

How can I decrease the amount of checkout friction on my website?

For larger merchants:

  1. Flexibility: allow customers to pay via mobile apps and mobile optimised sites.
  2. Offer a better customer User Experience (UX): this may mean using autofill APIs to remember customer information, or making the payments process as easy to navigate as possible. A better UX could potentially yield a 400% increase in conversion rates.
    Examples include;

    • Personalised payment process: This might mean keeping the colour, design, and font the same throughout your website. By keeping your payments pages synonymous with the theme of the website, an increased sense of cohesion is created.
    • Reduce checkout time: The Checkout Conversion Index found that the optimal time for checkout success is 134 seconds, with the worst performing sites needing 220 seconds. A way to reduce time taken to checkout is by integrating your payment gateway’s interface directly into your website instead of using a payment redirect page, which means customers no longer need to wait for a pop up to load.

For smaller merchants:

  1. Fewer info fields: More successful merchants ask for as little information from consumers as possible, whether that mean payments information, address fields or even registering for an online account.
  2. Slim your checkout process: Amazon’s patented “one click checkout” is a great example of reducing checkout friction. By allowing consumers to make a purchase through a single click, Amazon’s sales have increased by 5% each year. Instead of offering four or five different pages for consumers to click through as they attempt to pay, a single page interface that provides all the information (including what’s in the cart, the price etc.) drastically reduces checkout friction.
  3. Offer more payment methods: By accepting a variety of payment methods such as credit and debit cards, as well as alternate payment methods such as Afterpay, PayPal and zipMoney, the number of decision points for customers is reduced which maximises conversion rates. On average, better performing sites offer 6.8 payment methods versus 4 for underperformers.

How can Paydock help?

Paydock’s developer friendly REST API makes payment method integration easier. Our clients are able to drive greater conversions with no redirection and offer an optimised customer payments experience.

What are recurring payments?

Recurring payments are automatic payments deducted from a credit card or bank account on an agreed schedule (e.g. daily, weekly, monthly). Recurring payments are useful for a wide range of payments – such as subscriptions for magazines, membership clubs and utilities bills.

What are the advantages for merchants?

  1. Decreases late or missed payments: As recurring billing happens automatically, there is a reduced risk of delayed or missed payments. Furthermore, budgeting is made much easier as payments are expected at regular intervals for customers.
  2. Improve customer relationships: By signing customers up to subscription arrangements, business are able to reduce the risk of churn and build stronger, sustainable customer relationships over time.
  3. Saves time and money: Business owners no longer need to manually manage all billing cycles. This frees up time so they can focus on their core business.

What are the advantages for customers?

  1. Saves time and effort: By setting up automatic payments, customers no longer have to manually input payments for their subscriptions.
  2. No more late fees: Previously, if a customer forgot to input a payment manually, they could potentially be hit with a late fee. The automatic nature of recurring payments means that such scenarios will no longer happen, saving money and effort for the consumer.
  3. Keeps information secure: Recurring billing allows customer information to be managed securely. The lack of paper bills means that the risk of duplicating and circulating sensitive information is minimised, as is the risk of employee error.
  4. Environmentally friendly: Each year, more than 3.6 million tons of greenhouse gas emissions are created by transporting paper bills alone. There is no longer a need for physical bills to be sent out as almost everything can be done online in this day and age.
  5. Leverage the growing demand for subscription services: Research has shown that there is an increased demand for the convenience and ease of subscription services, especially within younger generations. As of 2017, 70% of millennials have a subscription to a product and 89% have a subscription to a service. As a business, offering recurring payments can greatly improve customer experience, and help differentiate your business from others.

How can Paydock help?

Paydock is a smart payments platform that allows merchants to connect to various payment gateways such as Stripe, Braintree, Paypal and more. We offer a recurring payments engine that overlays on top regardless of payment type, gateway, or frequency. Our clients are able to automate flexible customer subscriptions, increase revenue and reduce time spent with managing customer billing.

Paydock would like to congratulate SumoSalad on winning Best Innovation in the Health Category at the prestigious QSR Media Detpak Awards for its My Sumo app! Launched in January 2017, the app allows customers to create and pay for their own salads and wraps before picking them up in-store.

When designing, SumoSalad needed to ensure that the app:

  • Is native on both iOS and Android.
  • Can connect to other APIs and apps such as FitBit to automatically log purchases to the customer’s FitBit diary.
  • Has a centralised menu database that can be updated and rolled out across all franchises on the app in an instant.
  • Has a simplified customer signup solution that can automatically distribute the data to franchises.
  • Can split payments between a customer’s loyalty points and their credit card/debit card
  • Works with any number and a diverse range of payment gateways and methods.
  • Triggers transactions and distributes customer data across multiple franchises and any payment gateway upon request.
  • Allows money and payment sources to be directly connected to the franchisees, so that each store has increased control of their pricing schedule without affecting other stores.

Having fulfilled most of the aims by partnering with Round Table Apps, SumoSalad needed to find a comprehensive payments solution. This is where PayDock came in.

How Paydock helped streamline the checkout experience

  • Paydock’s secure payments token vault gave SumoSalad’s the ability to store and pass on customer information within the app to reduce checkout friction.
  • Paydock enabled SumoSalad to integrate and bolt on additional payment gateways and solutions with ease, without further development costs.
  • Paydock’s ability to connect headquarter’s payment gateway directly with the franchisee’s downstream gateways allowed payments to go directly into the franchisee’s bank account, removing the need for any HQ intervention.

Happy results

SumoSalad is now able to offer a seamless online app experience, scale effortlessly and bolt on additional gateways for new franchises within seconds (they added 94 gateways in December 2016 with ease). Settlement delay is now reduced to as low as 1-2 days and is automated with their chosen payment gateway. In addition, franchisees enjoy the flexibility to add and change their online payments set up without huge development costs and without disrupting the operations of SumoSalad and other franchisees.

How Paydock can help your franchise business

The problem that SumoSalad encountered was not unique in any way. Many franchise businesses lose valuable time and administration cost rerouting payments from HQ back to each separate franchise.

What Paydock offers is an extensive payments solution that enables businesses to directly connect with their downstream gateways and reduce settlement delays. This increases data visibility, upgraded payments flexibility and a synchronised payments system.

According to Statista, the global average cart abandonment rate for the second quarter of 2016 was 74.52%. This means that out of 100 potential customers, 75 are leaving for reasons such as “extra costs too high”, “the site wanted me to create an account” and a “too long/ complicated checkout process”. Yet, the high cart abandonment rate is no cause for despair. Approximately 63% of abandoned sales is potentially recoverable by savvy online retailers.

 

So how can merchants reduce the cart abandonment rate?

  1. Offer free shipping. Savvy online consumers are looking for ways to save money. If you are unable to offer free shipping completely, promotions such as “Free shipping for orders over $75” or even making shipping costs clear and upfront have been shown to increase sales.
  2. Create a guest checkout process. Shoppers are reluctant to provide private information upfront, but are happy to create an account after they have purchased a product to track shipping and delivery times.
  3. Reduce the amount of steps taken to checkout. Conversion studies have shown that the less clicks to checkout there are, the lower the cart abandonment rate. If many pages are needed, it is a good idea to provide a progress bar or another visual indicator.
  4. Improving the security of transactions. Adding a security logo such as Symantec can increase sales by up to 42%
  5. Increasing the amount of payment methods. Offer common payment processes such as PayPal, VISA, MasterCard, AMEX, as well as alternate payment methods (APM). APMs (such as E-wallets and mobile payment methods, transfers, digital currencies etc.) will account for more than half of all transactions by 2017, up from 43% in 2012. In a time where payment methods are becoming increasingly varied and complex, online merchants risk losing sales if they are unable to offer their customer’s preferred method.

 

How can Paydock help?

We aren’t saying that we can offer all solutions to high cart abandonment rates, but Paydock can definitely increase conversion rates by connecting your e-commerce store to multiple payment gateways and allowing access to new payment methods. We allow you to future proof your payments ecosystem in a time of rapid change and development.  

Yes, the client always comes first

You guessed it. Client-side tokenisation and the release of paydock.js. Build secure client-side and javascript apps, reduce your PCI compliance scope and take advantage a lovely drop-in JS script.

Read our friendly docs for how to implement it.

Also delivered direct your door are a fresh batch of Web Client updates we hope you like. Each designed to help you manage Customer and payment settings even easier. See below for specifics.

Love, all of us at Paydock

API Release (v1.2.0)

  • paydock.js
  • client-side tokenisation
  • public key release

Web Client Release (v1.1.1)

  • Customer Reference field now available on the Add Payment page
  • Filtering improvements for list pages: Charges, Subscriptions, Customers
  • Add payment source(s) to your Customers directly through the interface
  • View and manage your Public API key on the My Account page

Interface Screenshots

API Keys

public_key

 

Customer Object Payment Source

payment_source

 

New week, new updates, new value.

We’ve got some tasty treats for you in the latest release – including Pre-Card-Expiry Notifications and support for NAB Transact.

This is great news if you’re an existing Transact customer or looking for the right gateway partner to grow with. Pending-expiry Notifications mean you can pre-emptively connect with your customers/donors and avoid lost income and reduce admin effort.

Payments power to the people. 

Love, all of us at Paydock

 

API Release (v1.1.9f)

  • New Notification type
    • -1 Month Pending Card Expiry
  • New Gateway
  • Updated to new version of PayWay REST API

Web Client Release (v1.0.5)

Updates:

  • Added Description and Reference fields to the Web Client (not just in API now)
  • Manage your new Pending-Expiry Notifications
  • Add and Manage NAB Transact Gateway

Read more

So yeah,

We’re pretty fixated on delivering a platform that builds ever more value into your payments experience.

‘Geneva’ is no exception, but we’ll let the release speak for itself – see below.

As always, we’re here for you,

The Paydock team

API Release (v1.1.9)

Web Client Release (v1.0.4)

Updates:

  • Quickly see what Gateway is currently in-use for any Subscription on the Subscriptions page
  • Easy sort-by headings to order Subscription information
  • Archive transactions
  • Delete customers
  • Create Refund Notifications

Read more

We’re very excited to announce some exciting new features on the Paydock API as well as overall improvements to the admin interface.

Summary: “More goodies we hope will make your life easier – and more exciting”. (well we try)

See the screenshot below then a little more detail of some of the new ‘under the hood’ power.

If there’s something you’d love to see added, please shoot us a line at [email protected].

We love building payment solutions to help your business.

Love,

All of us here at Paydock

API Release (v1.1.8)

  • Searchable parameters when requesting Charges through the API. You can add these as query parameters today. Simply add use like ‘/v1/charges?gateway=1234567890&from=ddmmyyyy’
    • “gateway” – include a specific Gateway ID when requesting the charges log to filter output by gateway
    • “from” – include charges from a specific date (ddmmyyyy)
    • “to” – include charges up to a specific date (ddmmyyyy)

Web Client Release (v1.0.3)

Updates:

  • Ability to manager your user avatar under My Account -> Personal/User Details
  • Ability to manage refund requests through interface
  • Ability to leverage new API capabilities through interface

Read more

With all the issues at NAB’s online payment service recently…

Which also affected Secure Pay customers…

It’s now more clear than ever the need for businesses to safeguard themselves from unexpected and disastrous downtime from their payment service provider.

With extreme losses recently suffered by both businesses and not-for-profits alike many found themselves highly exposed and looking at either one of two solutions.

Pre Paydock Solution #1: Switch providers

This is an obvious yet expensive approach approach I’ve seen many organisations take. Requiring a business-level disentangling of services, websites, applications, management and accounting – it’s always been a highly expensive option (and no more guaranteed) when it comes to stability.

Functional limitations still exist and merchants hold their breath hoping their new partner stays online and their business needs don’t outgrow their gateway.

It really falls into the ‘what else could we do’ department, as Option Two (below) carries its own price tag.

Pre Paydock Solution #2: Incorporate multiple providers

We’ve spoken to organisations who now consider this route. The costs here are extraordinary, with development needing to ‘wire in’ two (or more) gateways to cover functional needs yet provide some kind of backup. There are direct fees from the gateway provider as well as development and administration costs, not to mention the difficulty in managing customer data.

It’s not hard to see that neither of these solutions do not truly represent a elegant insurance policy against gateway downtime.

Paydock provides an alternative approach to the market.

 

The Paydock Solution…

With Paydock customers have the opportunity to wire into a single API – and work with many gateways. You can ‘red-light, green-light’ gateways through a simple check with our API and perform transaction routing depending on the result.

What this means is that if a payment hits a brick wall because a given gateway is down, Paydock customers can literally pass that through to the next gateway in runtime.

 

Paydock will minimise downtime, disruption & loss of income.

Furthermore, because we have a semantic API, it’s easy to add to your existing services and as new gateways are added you can drive down direct costs and increase your functional mix with our built-in recurring engine.

We’ve found our customers often don’t even have to uproot their existing merchant/gateway facility but can maintain established banking relationships but, this time, sleep at night knowing there’s a backup, new features and a better solution, ‘just in case’.

We’d love to have a discussion about how we can help your specific business needs, reduce pain and ensure business stability. Email us on [email protected] or contact us online.

~Rob