Types of Payments Integrations in a Nutshell

Deciding on a payments integration or upgrading a current integration is an important step in the evolution of your software solution. But how many features do you really need? How long will the integration setup take? And how will it impact your current users and how they interact with your system? All excellent questions that we aim to answer!

So, let’s first answer these two simple questions.

What do you have available to you currently in your payments interface?

If you were to move why would you?

Really the key is getting both a payment processing (authorize/capture/settle) gateway interface and an API interface for contracting and obtaining a live merchant ID.

Does your interface have this? Or is your payments interface just a gateway and you are forcing your clients who use your software to go to their Bank or go to Stripe for their merchant account?

It comes down to this. Show me the $$ (fair revenue share of dollars processed), show me the API!

The first thing you should ask when considering a payments integration partner is what is the specific plan to acquire and onboard the existing base of customers? Whether your software currently has 1,000 or 10,000 users, getting them contracted and onboarded and using the payments integration is the most important and often the most difficult piece of the puzzle. That’s where your money is at. The merchants must be processing to make your time and efforts in implementing a payments integration worth it.

Ask the potential payments integration partner/ISO the following critical questions BEFORE signing a deal:

What is your % of converted merchants typically?

What is your marketing/follow-up and customer service/support protocol?

Who handles what exactly? (sales/support/setup)

Is the process AUTOMATED? This is the key – automation through API is the secret sauce to converting all the merchants as quickly as possible.

With our unique API we have fully automated the onboarding process and guarantee MID (merchant ID) creation for 100% of the software’s users within 2-weeks. Where else can you go to obtain this?

One of the most fun things we get to do with software developers is go through a scope of work call to review the goals, objectives and functionality need through the integration to ensure once we map out the plan everyone is getting what they want.

Anytime you’re considering a payments integration as a software developer you should ask for a scope of work consultation that includes a review of the following critical items:

☐ – Card Present ☒ – Card Not Present ☐ – Both

Point of Sale

☐- Yes, what type of POS Click here to enter text. ☒- No

Mobile, P&P, SI

Click here to enter text.

Operating System, Language

Click here to enter text.

Current Setup

Click here to enter text.

Current Hardware

Click here to enter text.

EMV

☐ – Yes ☒ – No If Yes, Hardware Used: Click here to enter text.

P2P Encryption

☐ – Yes ☒ – No If Yes, who does the decryption: Click here to enter text.

E-Commerce

☒ – Yes ☐ – No

Mobile App

☒ – Yes ☐ – No mobile web, and some on client by client basis

Website

☐ – Yes ☐ – No If Yes, Click here to enter text.

Hosted Payments Used

☐ – Yes ☐ – No If Yes, Click here to enter text.

Recurring Payments/tokenization

☐ – Yes ☐ – No If Yes, Click here to enter text.

Electronic Invoice

☐ – Yes ☐ – No If Yes, Click here to enter text.

Mobile Wallets

☐ – Yes ☐ – No If Yes, Click here to enter text.

MOTO

☒ – Yes ☐ – No

Now that you know what’s possible explore the options with us! Reach out now to Ben Kauder at bkauder@singularpayments.com or by phone at 419-344-5403. We are excited to help you create the payments integration that will deliver a smoother UI for users and a consistent revenue stream to you.