Developers

while(true) {
echo "the payments industry is moving in ever expanding directions.";
}

And integrations are becoming more and more complex in meeting the industry standards. JetPay has launched our JetPay Developers Group with the main focus of making your integration or application development as easy as possible.

In an effort to aid software engineers, web developers and other professionals in their development and integration efforts with JetPay, we offer various documentation, sample scripts, and other resources to the development community. These resources will help you in your projects by providing standard and detailed information about JetPay products and services, all geared to making your project as easy as possible.


Integration Documentation


When integrating to the JetPay Platform there are three top level options to choose from. Direct processing via XML to our front end. batch processing utilizing file uploads for processing based on XML or blind redirect using HTTPS POST method in our JetDirect payment method.


The JetPay XML Schema

Transaction communications with the JetPay front end are sent via XML. The JetPay XML Schema is your road-map to developing applications and products that communicate with the JetPay platform.

Batch Processing

Our Batch Processing system is intended for those merchants that need to do a card AUTH and subsequent CAPTURE. The batch process works via file transfers to SFTP locations using PGP. Special certification is required to use batch processing with the JetPay platform.

JetDirect

The JetDirect Pack contains our integration document, a sample copy of code in PHP with a MySql database table build for storing the returned transaction data and a short white paper on method and use.

Downloads & Sample Code


JetPay Virtual Terminal

The JetPay Virtual Terminal Solution enables gateway-free, PC-based credit card processing via the Internet and eliminates the need for other costly POS hardware and software. Virtual Terminal leverages your existing computer hardware and Internet connection into a comprehensive POS device.

Note: JetPay Virtual Installer package is being phased out starting Q3 of 2017. All users will need to migrate to our cloud based virtual terminal starting end of Q3 through Q4 2017.

Sample Payment Forms

Below are sample source code for generating payment forms to JetPay.

JetPay DLL

JetPay provides a DotNET DLL for those developing on Windows IIS. Our DLL package accepts input from your application, formats the XML, send and captures the JetPay response message.

Testing Information


XML Test URL

XML Testing - https://test3.jetpay.com/test/
JetDirect Testing -https://testapp1.jetpay.com/JetDirect/jdv2/gateway/jp-handler.php

All documentation includes testing credentials to get you going. Once you have tested and you feel ready to move to certification testing please developer our Dev Group Manager for your JetPay DevId and to register you build for certification.

Test Credit Card Numbers

The following is a listing of Test Credit & Debit Card numbers for testing your application. All numbers pass LUHN checking. Please refer to the XML Schema for information on CVV, AVS and ZIP Matching for specific values.

  • American Express - 3111111111111117
  • American Express - 378282246310005
  • American Express - 371449635398431
  • American Express Corporate - 378734493671000
  • Diners Club - 30569309025904
  • Diners Club - 38520000023237
  • Discover - 6111111111111116
  • Discover - 6011111111111117
  • Discover - 6011000990139424
  • MasterCard - 5111111111111118
  • MasterCard - 5555555555554444
  • MasterCard - 5105105105105100
  • Visa - 4111111111111111
  • Visa - 4012888888881881

  • All expiration dates set in the future will return - APPROVED
  • All expiration dates set in the past will return - DECLINED

Test ACH Numbers

JetPay processed Automated Clearing House (ACH) payments as well as Credit & Debit Cards. Use the following to test ACH processing through the JetPay platform.

  • Routing Number (DDA) - 123123123
  • Account Number (ABA) - 123456789

In order to complete a full ACH test you will need to provide and account holder name and a check number.

Not You Typical Development


Integration to the JetPay platform is very straight forward. However, there are a couple of things that you should know when it comes to integrating with JetPay. JetPay is one of about 20 top level processors. As a processor JetPay is not part of the gateway payments class (PayPal®, Authorize.net, MoneyBrokers® etc) that most developers are use to integrating. In the world of payments there is a very simple structure, from top to bottom it looks something like this:

  • Card Associations - Visa, Mastercard, Discover, American Express
  • Payment Processors - JetPay, some banks
  • Gateways - Authorize.net, PayPal, MoneyBrokers, Brain Tree...
  • Sales Organizations - ISOs, VARs
  • Merchants - where cards are accepted
In this structure everything is written to the level above - Sales to Gateway, Gateway to Processor, Processor to Associations. In order to sent transactions to the JetPay platform, your project must have bi-directional communication with JetPay in our standard. Our standard is XML for direct processing and HTTPS POST data via JetDirect. JetPay responds in the respective format received. JetPay only accepts these language standards of communication. How you generate your XML and/or HTTPS POST is up to you. For web developers that are generating shopping carts or other Online payment system this is not to much of an issue since both XML and HTTPS POST are native to most all web languages.

Application developers such as Point of Sale systems, integrated payment software, and mobile applications this can get a little more difficult, but not by much. JetPay will work with you in any capacity you need to get your implementation up and going just let us know how we can help.

Where's your sandbox?

Like we said, we are not your typical implementation route. If you have every done payments integration then you have heard of Payment Card Industry (PCI) Compliance. With JetPay being at the top end of the PCI chain there are some special rules that we have to follow, and one of them is that we can't allow un-vetted code to run within our network, this means no sandbox (even if its on a separate segment) for development testing by outside sources. For the most, every developer has their own testing environments, and since testing certification with JetPay requires your testing to be done on a mirror of your production systems it is really best to develop and test from your built environment.

What if I have questions!

Not to worry, you can send any questions that you might have regarding developing, standards, testing, and so on to our Dev Group Manager. Emails are replied to in the order they come in and you will generally see a reply the same day. If your question needs more detail we will be more than happy to arrange a call to go over anything you need.