Contact Value.IO Support

Contact Details

Integration Overview

Value.IO℠ empowers payment enabled systems to secure and direct payments where needed. The system is omnichanel. (Card Present Retail, Mobile, Web).

Transactions in the Value.IO system are broken up into two phases - card capture (tokenization) and payment transaction. Both can be completed in one action for simple integrations. While Kernel API end points allow for direct server to server credit card capture, most integrations leverage Value.JS℠ methodologies for card capture.



Example 1 - Instant Payment / Donation Form

Utilizing SecureForm℠, turnkey payment forms can be created for instant integration - including simple destination setup and receipt functionality. These forms can be customized with font and color to more closely match your environment. Receipt functionality including email receipts are included with the most basic integration if desired.

Give Value.JS a try: use card number 4111-1111-1111-1111, any 3 digit CVV and future expiration.

Example 2 - Tokenizing For Web Application

Integrations can be created to meet the needs of traditional and emerging systems. The below model works for creating powerful shopping cart core payment functionality, mobile ordering technologies, and multi-merchant marketplaces. The below integration is a full integration for enterprise functionality. Before integrating, you would be assigned a personal integration specialist to make sure the integration is simple and smooth for you. application integration flow example 2

  1. Value.JS Integration
    Secure Data And Single Use Token Creation. Using value.js, card data and other data you wish to secure is captured and tokenized client side using one of our value.js technologies. A one time token is returned to the client.
  2. Form Submission
    Single use token is sent via your form to your servers.
  3. Kernal API Transaction
    Utilizing the kernal API and the Single Use Token from step 1, a transaction is initiated. If there is more than one "destination" (See Below For Definition) available in your account, then the specific destination is stated as part of step 3. The single use token may be exchanged for a perminent token if desired. Transaction response is returned in a harmonized format.

Example 3 - Cloud POS Integration w/ EMV

Value.IO provides a complete solution for card present environments that requires little to no changes in how you write your code. Example integrations are available on the SecureForm℠ integration page. We do the heavy lifting on our side so you can enjoy your day.

At this time, we support most destinations with MagTek® USB readers. For EMV and Pin Debit transactions, only TSYS is supported at this time. We work with all Dejavoo℠ V and Z series devices. For more information, please contact us.



Destinations are transaction end points. You may have one or thousands, depending on the application you are building. In the payment industry, these are typically known as merchant accounts, however because we support direct processor integrations and payment gateway integrations, our platform can reach almost every processor in the world today inlucing sub-merchant PayFac environments. Custom Destinations allows for delivery of card data anywhere. As long as the end point is a certified PCI environment, we will send the card data where you require for your business logic.

Direct Processor Destinations

  • TSYS
  • Litle
  • Mercury
  • Heartland Payment Systems
  • SecureNet
  • Sage Payments US
  • Stripe

Gateway Destinations

  • Inspire Commerce
  • Network Merchants (NMI)
  • USAePay
  • Authorize.Net

Custom Destinations

  • PassThrough (build your own)

Integration Documentation

Value.IO kernel

Database and API for securely storing, transacting, and retreiving secure data.


The Value.IO kernel has been supplemented with two highly secure integration tools, called Value.JS.