Payment Integrations | Authorize.Net

Payment Integrations | Authorize.Net

Authorize.Net Integration

What does it do?

Our Authorize.Net payment integration allow suppliers to automatically take payment from retailers for the orders that come into OMS by registering a credit or debit card that is used every time an order is placed. 

Any orders placed using this payment integration should be set to come into the OMS on the status “On Hold”, the system will then routinely check orders “On Hold” and attempt to send payment to Authorize.net automatically. When payment has been taken, a payment reference will be added to the order history and the order status will be changed to “Received” allowing the order to then flow through normal production.



What do we need?

To initiate this integration you need
  1. A live Authorize.net account (you should be able to login as a “Merchant” https://account.authorize.net/).
  2. The Client needs to be set up with an Admin company.

Authorize.Net Integration

This Integration is found on the Dropship company under the Payment Integration tab.
The Client signs into Authorize.Net and retrieves the following:

1. API Login ID

2. Transaction Key

3. Seller is the Admin Company GUID/Ref ID.

4. Currency refers to type of payment.

5. Customer Profile ID { See page 6 ‘Setting up a new Retailer’ }

6. Payment Profile ID { See page 6 ‘Setting up a new Retailer’ }

CPP Product

Pricing (Beta)
The Product needs to have the Seller set as the Admin company with the Buyer set to ‘Any’.
Pricing is adjusted in CPP under the Pricing Beta tab within the E-Commerce & Data section.



Setting up a new Retailer

Creating a Payment Reference
OMS does not store any card details. The Client will sign into their Authorize.net account and create customer.
Once a customer is created in Authorize.net, you will need the following:
  1. Customer Profile ID
  2. Payment Profile ID


Next Steps

To enable automatic payments in OMS, please contact support@custom-gateway.com or contact your Onboarder. Please provide them the following information:
1. API Login ID
2. Transaction Key
3. Customer Profile ID
4. Payment Profile ID
5. Your accepted currency

CPP Product


Authorize.Net Integration
What does it do?
What does it do?
What does it do?
What does it do?

    • Related Articles

    • Payment Integration | Stripe

      Introduction This article has been created to show how to setup the payment integration Kornit X has built to connect to Stripe.  Setup To setup the Stripe payment integration, please head to your company  and withn the advance settings head to ...

    • Product Integrations | What Are They?

      Introduction This article has been written to explain what product integrations are in use with the Kornit X platform. This type of integration allows you to send products to multiple platforms and API channels connected via the advanced settings of ...

    • Supplier Integrations | T-Shirt And Sons

      Introduction This article has been created to show how to setup the supplier integration Kornit X has built to connect to T-Shirt And Sons. Setup To setup the T-Shirt And Sons integration, please head to your company and within the advanced settings ...

    • Payment Integration: Trust Payments (Formally Secure Trading)

      Introduction This document covers how a fulfiller can configure their sales channel company to automatically charge retailers via Trust Payments for the cost of their orders. Please note, the company is called Trust Payments but was formally known as ...

    • Production Integrations : Hotfolder Feed

      Custom Gateway have produced a production solution we call Hotfolder Feed. This is made up of the system modules we offer and an local piece of software used to manage queues and move artwork and jobsheets to printing locations. A high level view of ...