Already an expert with Providers? Jump ahead to Step 8 - Creating Campaigns.
Understanding Providers
Providers, also commonly referred to as integrations are the heart and soul of every sticky.io account. From Payment Gateways and Fulfillment to Fraud Mitigation Tools and much more.
With over 400+ integrations, this article can't encompass everything. All hope is not lost however, we have articles for every single integration via our Help Desk. Simply click here or use the search bar above and type in the name of the provider you're looking to integrate. e.g. Authorize.net or Shipbob.
This article will cover the most common and critical provider type, Payment Gateways.
Navigating to Providers
To begin, let's navigate over to Settings > Providers.
Following, we'll land on the Providers page. Every sticky.io account comes with a "Dry Run Testing" Payment Gateway. As the name implies, it's used for testing early on in your setup on sticky.io.
Adding & Reviewing Provider Types
Click into Actions > Add New Provider Profile.
Type
The type of integration you're looking to add. e.g. Payment Gateways, Fulfillment, Tax, Notification.Provider
Once you specify a Type, the provider list will populate with every integration that matches your selection. e.g. You specify the Type as Payment Gateway, Provider will show all Payment Gateways.
Let's opt for a Payment Gateway and in this article, we'll cover Authorize.net. Other gateways such as NMI (Network Merchant Inc) and many others have a very similar integration process.
Naming Your Provider
There's a dedicated section for naming your provider... really? Yes! As you scale with sticky.io, you'll inevitably obtain more processing. It's possible you'll end up with several different MIDs all under Authorize.net or an equivalent gateway.
To get the most use of our Reporting & Analytics, it's encouraged that the alias be something similar to Gateway > Processor > Descriptor. As seen below:
Note: You can always revisit any of your providers and change the alias on the fly without any impact on operations.
First Tab - Credentials - Requirements
Irrespective of the gateway, there will be 3 tabs presented. Credentials, Merchant Account Details & Limits & Fees.
The contents of each tab for each gateway are mostly the same with some outliers requiring different ways to login or have enhanced functionality.
In Authorize.net's case, we need:
Note: If you specify USD (as an example), you can still receive different types of currencies. They will simply be converted to the currency the MID processes.
While there are a myriad of other fields, let's first focus on simply getting the MID integrated and tested. Let's segue over into the second tab.
Second Tab - Merchant Account Details - Requirements
For Merchant Account Details, the following fields are required:
Descriptor - What shows up on the customer's bank statement.
Customer Service Number - Your customer service number. The one you provided when obtaining processing. Typically available on your VAR sheet.
On most Payment Gateways these are the only two fields that are required. Other fields such as the Processor and Vertical are only used internally for our Reporting & Analytics.
Enabling you to segment processing by vertical and processor can be valuable data in determining what MIDs you want to push more of your traffic toward. However, it isn't a requirement to add your MID, much less to process live transactions on them.
Third Tab - Limits & Fees
And rounding out Payment Gateways, Limits & Fees. Tackling the requirements first,
CVV - Or card verification value, e.g. the 3-4 digits on the back of your credit card. Either this is Never Required, Required on Initial, or Always Required.
Global Monthly Cap - Generally, most payment gateways have a monthly processing threshold that they do not want you to process beyond. Leaving this value at $0.00 will result in all transactions failing because you immediately hit your monthly cap.
What about the other fields? Every other value beyond what we discussed above is to help you calculate P&L (Profit & Loss) margins in sticky.io using our Reporting & Analytics.
For example, Visa isn't charging you 100% per transaction, maybe it's 0.75%. And providing us with this information will help you to track real recognized revenue.
That said, leaving these values at 100% during testing and going live does not impact your transactions. These are internal metrics only stored on sticky.io.
Enabling Your Providers
You've boarded your first provider, now what? Whether it's a Payment Gateway to Fullfillment or Email Marketing Tools, they all tie into a Campaign.
All providers except Payment Gateways can be integrated directly from the Providers page. Payment Gateways can only be added manually to Campaigns or Payment Routers.
Integrating Providers from Providers UI
Find the provider you intend on integrating to your campaign > Click the ellipsis ● > Assign to Campaigns.
Following, an additional window will appear enabling you to specify any and all campaigns that the provider should be integrated with.
Here you can select individual campaigns or select all of them. Once you're done, click Save.
Integrating Providers from Campaigns
To begin, let's navigate over to Products > Campaigns.
Following, choose a campaign of your choice. Once your campaign loads, we'll scroll down to Gateway Configuration to integrate our campaign of choice.
After specifying the gateway, click Save.
For all other providers, click Third Party Providers off to the top right of the screen.
After enabling Third Party Providers, we'll scroll to the bottom of the Campaign UI.
After integrating your providers, click Save.
For a more comprehensive breakdown of campaigns, let's segue into Step 8 - Creating Campaigns.