Netswipe Processing Implementation



Similar documents
Payvision Payment Processor. Technical Integration

Merchant e-solutions Payment Gateway Back Office User Guide. Merchant e-solutions January 2011 Version 2.5

Merchant Account Service

ipayment Gateway API (IPG API)

Credit Card Retrieval API Implementation Guide This guide illustrates how to implement the Credit Card Retrieval API.

Volume PLANETAUTHORIZE PAYMENT GATEWAY. vtiger CRM Payment Module. User Guide

Fraud Detection. Configuration Guide for the Fraud Detection Module v epdq 2014, All rights reserved.

Network Merchants Inc (NMI) Integration Resources. Direct Post API Documentation April 2010

Global Transport Secure ecommerce Decision Tree

Gateway Direct Post API

Merchant Console User Guide. November 2013 CRXE-MCNT-MCON-UG07

Bitcoin Payment Gateway API

Realex Payments. Magento Community / Enterprise Plugin. Configuration Guide. Version: 1.1

The Wells Fargo Payment Gateway Business Center. User Guide

Virtual Payment Client Integration Reference. April 2009 Software version:

WEB TERMINAL AND RECURRING BILLING

Elavon Payment Gateway- Reporting User Guide

Merchant Application Form

Secure XML API Integration Guide. (with FraudGuard add in)

Virtual Terminal User s Guide

DalPay Internet Billing. Virtual Terminal User Guide

Merchant Account Glossary of Terms

Three Step Redirect API V2.0 Patent Pending

Merchant One Payment Systems Integration Resources. Direct Post API Documentation June 2007

Process Transaction API

Virtual Terminal Solution

Global Transport Secure ecommerce. Web Service Implementation Guide

Fraud Detection Module (basic)

Address Verification System (AVS) Checking

Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained.

Contents Error! Bookmark not defined.

PROCESS TRANSACTION API

Account Management System Guide

Credomatic Integration Resources. Browser Redirect API Documentation June 2007

MasterCard In tern et Gatew ay Service (MIGS)

DIRECT INTEGRATION GUIDE DIRECT INTEGRATION GUIDE. Version: 9.16

Card-Present Transactions Implementation Guide Version 1.0

Internet Payment Gateway

Credit Card Overview & Processing Guide entrée Version 3

Merchant Web Services API

Direct Post. Integration Guide

MiGS Merchant Administration Guide. July 2013 Software version: MR 29

SPARROW Gateway. Developer API. Version 2.00

Credit Card Processing

iyzico one-off payment and installment easy payment integration

Payment Card Industry (PCI) Data Security Standard

Recurring Payments Manual

MyGate Response Codes. Version 2.1

Acceptance to Minimize Fraud

Server and Direct Shared Protocols

PayDollar PayGate. Integration Guide (For third party shopping cart platform v1.0)

CRM4M Accounting Set Up and Miscellaneous Accounting Guide Rev. 10/17/2008 rb

Payment Card Industry (PCI) Data Security Standard

Remote Integration Guide. Online Payment Processing for Businesses Worldwide.

USER GUIDE. Rev 9/05

CyberSource and NetSuite Getting Started Guide

My Sage Pay User Manual

Hosted Credit Card Forms Implementation Guide

First Data E-commerce Payments Gateway

Credit Card Processing Overview

Authorize.Net Mobile Application

HOSTED INTEGRATION GUIDE HOSTED INTEGRATION GUIDE. Version: 9.16

First Data Merchant Solutions EMEA Payment Gateway

Transaction Details Guide

Emdeon ecashiering Manual. February 22, 2010

Testing Transactions

Recurring Credit Card Billing

MiGS Merchant Administration User Manual. MiGS User Manual

Three Step Redirect API

Chargebacks & Retrievals. Expand Your Knowledge

Getting Started. Quick Reference Guide for Payment Processing

QIWI Wallet Pull Payments API

Magento Extension User Guide: Payment Pages. This document explains how to install the official Secure Trading extension on your Magento store.

CardControl. Credit Card Processing 101. Overview. Contents

Alpha e-pay v2 Merchant User Manual (v1.9)

Secure XML API Integration Guide - Periodic and Triggered add in

Visa Checkout September 2015

Web Services Credit Card Errors A Troubleshooter

Virtual Terminal User Guide

(877) City: State: Zip: Physical Business Address: City: State: Zip:

JetPay JetDirect Integration Guide

PayWithIt for Android Devices User Guide Version 1.0.0

Merchant e-solutions Payment Gateway. Merchant e-solutions October 2013 Version 4.10

Office Depot Merchant Services Mobile Application User Guide

Merchant Application Form for Credit and Debit Card Payment Gateway

GTPayment Merchant Integration Manual

THE ABC s of Credit Card Processing

Merchant Web Services API Advanced Integration Method (AIM)

First Data Merchant Solutions Virtual Terminal & Manager

Virtual Terminal User Guide

Web Services Credit Card Errors A Troubleshooter

MiGS Virtual Payment Client Integration Guide. July 2011 Software version: MR 27

Payment Card Industry (PCI) Data Security Standard

Card-Present Transactions

The Science of Credit Card Processing

Ecommerce Setup Wizard Site Setup Wizards

Transcription:

Netswipe Processing Implementation Direct Integration with Jumio s Payment Gateway Revision History Version Date published Description 1.0.0 November 22 nd, 2011 Initial release. 1.0.1 January 12 th, 2012 Added basic authentication 1.0.2 July 19 th, 2012 Changed credentials for basic authentication 1.0.3 October 25 th, 2012 Added sample request

Netswipe Processing Implementation... 1 Authorize... 4 Capture... 4 Void... 4 Payment... 4 Refund... 5 Credit... 5 Card Fund Transfer... 5 Referral Approval... 5 General settings... 6 JSON request... 6 Basic Authentication... 6 Basic Operations... 7 Authorize... 7... 7... 8 Capture... 8... 8... 8 Void... 8... 8... 8 Payment... 9... 9... 9 Refund... 10... 10... 10 Referral Approval... 10... 10... 11 Credit... 11... 11... 12

Card Fund Transfer... 12... 12... 13 Recurring Operations... 14 Register Card... 14... 14... 14 Authorize... 14... 14... 15 Payment... 15... 15... 15 Credit... 16... 16... 16 Card Fund Transfer... 16... 16... 17 Appendix... 18 Result code... 18

This section provides a functional overview of the operations that Jumio supports for processing card transactions: Authorize Capture Void Payment Refund Credit Card Fund Transfer Referral Approval Authorize The authorize operation allows the merchant to book the desired money from the card that will be invoiced. This is the preferred method since it provides the bank authorization to collect the money from the customer, but without collect immediately. This operation has two-steps and must always be completed by voiding the transaction or capturing, the completion can be done within an average time of 20 days. If the capture is not performed, the system will purge authorizations older than 20 days. This means that you will not be able to capture authorizations after they are purged. If you don t execute a Void operation, the money of purged authorizations will be blocked for the card until the issuing bank releases it. To avoid that, always call the Void method. Capture The Capture operation consists of collecting the money from authorizations previously done. Normally a Capture is performed for the total amount of the transaction, however, it might be possible to capture only part of the money reserved. Note: Only one Capture operation can be performed per Authorization. Void The Void operation is used to avoid collecting the money from authorizations previously done. This releases the money blocked from the credit card without collecting it. The Void can only be performed for the total amount of the Authorization, if exists a Capture or Partial Capture the Void operation will not be performed. Payment This is the easiest way to bill an amount over a card. The Payment operation collects the amount desired immediately. This is the equivalent of doing both an authorization and a capture at once.

Refund The Refund operation, as its name states, consists of returning money already collected by a Payment or a Capture transaction. The amount collected can be refunded in total or partially. You cannot refund amounts larger than the one sent in the original transaction. Refund can only be performed if a customer has not initiated a chargeback procedure. Note: You can perform multiple refunds until you reach the total amount of the original Payment or Capture. Credit The Credit operation allows refunding to the card holder. The main difference with a Refund operation is that it is a stand-alone operation. That means a Credit does not need to match a prior Payment or Capture. NOTE: This operation is disabled by default. You need you own payment gateway account when you want to use credit operation. Please contact support@jumio.com for more details. Card Fund Transfer The card fund transfer is the ability to transfer money from a merchant account to a cardholder account and is limited to 7995 coded (gambling) accounts. The amount that can be transferred is not limited by the amount collected in the first place. NOTE: This operation can only be used to transfer money to cards that have been already used to perform a Capture or Payment in the same merchant account. NOTE: This operation is disabled by default. You need you own payment gateway account when you want to use credit operation. Please contact support@jumio.com for more details. Referral Approval During an Authorize or Payment it is possible that a transaction is not declined nor approved. In this case you will get a Referral. The most common case for this error includes large transactions. When a Referral occurs the bank requires an extra authorization via telephone as an additional security measure. The procedure to follow in order to get your transaction approved consists of calling the Authorization Center and obtaining an Approval Code, after which you will need to perform a ReferralApproval request to Jumio.

General settings JSON request Jumio offers a payment API for merchants needing a RESTful solution for credict card processing without a Jumio hosted user interface. All you have to do is send a HTTP POST to the URLs mentioned below with JSON parameters. Note: Set "accept: application/json" and "content-type: application/json" in the "header" section of your request. Sample request: POST https://processing.jumio.com/api/pay/v1/basicoperations/authorize Accept: application/json Content-Type: application/json Authorization: Basic { "country":"usa", "amount":"10.99", "currency":"usd", "cardnumber":"1234123412341234", "cardexpirymonth":"1", "cardexpiryyear":"2015", "cardcvv":"123" } Basic Authentication Every processing API call is protected. Please use HTTP Basic Authentication, with your Jumio merchant API token as "userid" and your API secret as "password." The merchant API token can be found at the bottom of each page on www.jumio.com after you are logged in. The API secret is provided on the Settings page under Change Credentials.

Basic Operations Authorize This operation allows the merchant to book money from the card that will be invoiced. This is the preferred method since it provides the bank authorization to collect the money from the customer, but without collect it immediately. It is a two-step operation which must be completed by either a capture or a void operation. https://processing.jumio.com/api/pay/v1/basicoperations/authorize country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) cardnumber String Yes Card holder account number. cardholder String No Card holder name as it appears in the card. cardexpirymonth Int Yes Card expiration Month. Valid values are from 1 to 12. cardexpiryyear Int Yes Card expiration Year expressed with 4 digits. i.e. 2007 cardcvv String No Card validation code. Each card type has a unique name for this field. Visa (Cvv2), Mastercard (Cvc2), Amex (CID) This field is optional depending on the merchant account type. Moto and Recurring transactions don t require it. dynamicdescriptor String No Please ask for more information avsaddress String No Street address for AVS verification. avszip String No Zip Code for AVS verification. merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal

Capture This is for collecting money from the customer. An authorize operation must be done before. Only one Capture can be done per Authorization. https://processing.jumio.com/api/pay/v1/ basicoperations /capture jumiopaymentreference String Yes Guid obtained with an Authorize transaction. Void This is for closing a transaction previously opened by an Authorization-operation without collecting money. https://processing.jumio.com/api/pay/v1/basicoperations/void jumiopaymentreference String Yes Guid obtained with an Authorize transaction

Payment This is a one-step operation for collecting money from the customer. https://processing.jumio.com/api/pay/v1/basicoperations/payment country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) cardnumber String Yes Card holder account number. cardholder String No Card holder name as it appears in the card. cardexpirymonth Int Yes Card expiration Month. Valid values are from 1 to 12. cardexpiryyear Int Yes Card expiration Year expressed with 4 digits. i.e. 2007 cardcvv String No Card validation code. Each card type has a unique name for this field. Visa (Cvv2), Mastercard (Cvc2), Amex (CID) This field is optional depending on the merchant account type. Moto and Recurring transactions don t require this field. dynamicdescriptor String No Please ask for more information avsaddress String No Street address for AVS verification avszip String No Zip Code for AVS verification. merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal

Refund This is for returning money from a previously done transaction to the customer. https://processing.jumio.com/api/pay/v1/basicoperations/refund jumiopaymentreference String Yes Guid obtained with a Payment or Capture transaction. Referral Approval During an Authorize or Payment it s possible that a transaction is not declined nor approved, but you get a Referral. The most common case for this error includes large transactions. When a Referral occurs the bank requires an extra authorization via telephone as an additional security measure. The procedure to follow in order to get your transaction approved, consists of calling the Authorization Center and obtaining an Approval Code, after which you will need to perform a ReferralApproval request. https://processing.jumio.com/api/pay/v1/basicoperations/referralapproval jumiopaymentreference String Yes Guid obtained with an Authorize or Payment transaction. approvalcode String Yes Approval code obtained calling the Authorization Center.

Credit This is a one-step operation for refunding without previously done Payment or Capture. NOTE: This operation is disabled by default. You need you own payment gateway account when you want to use credit operation. Please contact support@jumio.com for more details. https://processing.jumio.com/api/pay/v1/basicoperations/credit country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) cardnumber String Yes Card holder account number. cardholder String No Card holder name as it appears in the card. cardexpirymonth Int Yes Card expiration Month. Valid values are from 1 to 12. cardexpiryyear Int Yes Card expiration Year expressed with 4 digits. i.e. 2007 cardcvv String No Card validation code. Each card type has a unique name for this field. Visa (Cvv2), Mastercard (Cvc2), Amex (CID) This field is optional depending on the merchant account type. Moto and Recurring transactions don t require this field. dynamicdescriptor String No Please ask for more information avsaddress String No Street address for AVS verification. avszip String No Zip Code for AVS verification. merchantpaymentreference String No This is a merchant definable value

which will be shown a reference in payment portal Card Fund Transfer This is limited to gambling accounts. Please get in touch for further information. NOTE: This operation is disabled by default. You need you own payment gateway account when you want to use credit operation. Please contact support@jumio.com for more details. https://processing.jumio.com/api/pay/v1/basicoperations/cardfundtransfer country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) cardnumber String Yes Card holder account number. cardholder String No Card holder name as it appears in the card. cardexpirymonth Int Yes Card expiration Month. Valid values are from 1 to 12. cardexpiryyear Int Yes Card expiration Year expressed with 4 digits. i.e. 2007 cardcvv String No Card validation code. Each card type has a unique name for this field. Visa (Cvv2), Mastercard (Cvc2), Amex (CID) This field is optional depending on the merchant account type. Moto and Recurring transactions don t require this field. dynamicdescriptor String No Please ask for more information

avsaddress String No Street address for AVS verification. avszip String No Zip Code for AVS verification. merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal

Recurring Operations Register Card This method allows you to register credit cards in the system to be used later. https://processing.jumio.com/api/pay/v1/recurringoperations/registercard cardnumber String Yes Card holder account number. cardholder String Yes Card holder name as it appears in the card. cardexpirymonth Int Yes Card expiration Month. Valid values are from 1 to 12. cardexpiryyear Int Yes Card expiration Year expressed with 4 digits. i.e. 2007 result Integer This value indicates if the card was successfully registered or not. A 0 means Ok, different than 0 means error. response String Friendly message indicating the result of the card registration jumiocardreference Guid GUID of the card to be used on Authorize and Payment operations. Authorize https://processing.jumio.com/api/pay/v1/recurringoperations/authorize country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. jumiocardreference String Yes Card Guid obtained previously. dynamicdescriptor String No Check the Appendix of your acquirer, provided separately, to know how to format this parameter.

merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal Payment https://processing.jumio.com/api/pay/v1/recurringoperations/payment country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. jumiocardreference String Yes Card Guid obtained previously. dynamicdescriptor String No Check the Appendix of your acquirer, provided separately, to know how to format this parameter. merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal

Credit NOTE: This operation is disabled by default. You need you own payment gateway account when you want to use credit operation. Please contact support@jumio.com for more details. https://processing.jumio.com/api/pay/v1/recurringoperations/credit country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, ) currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. jumiocardreference String Yes Card Guid obtained previously. dynamicdescriptor String No Check the Appendix of your acquirer, provided separately, to know how to format this parameter. merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal Card Fund Transfer NOTE: This operation is disabled by default. You need you own payment gateway account when you want to use credit operation. Please contact support@jumio.com for more details. http://processing.jumio.com/api/pay/v1/recurringoperations/cardfundtransfer country String Yes ISO 3166 Country code that indicates from which country comes the transaction (e.g. AUT, USA, )

currency String Yes ISO 4217 Currency code that indicates the currency of the transaction (e.g. EUR, USD, ) amount Decimal Yes Transaction amount. The decimal separator must be a point. jumiocardreference String Yes Card Guid obtained previously. dynamicdescriptor String No Check the Appendix of your acquirer, provided separately, to know how to format this parameter. merchantpaymentreference String No This is a merchant definable value which will be shown a reference in payment portal

Appendix Result code Code Description 0 OK There were no errors during the execution of the operation 1000 Error This code groups all errors related to the parameters sent. 2000 PaymentGatewayError Groups all errors related to paymentgateway 3000 Declined Groups all responses related to declines 3100 ReferralTransactionError Groups all responses related to Referral transactions. 3200 AcquiringBankError all errors related to the acquiring bank 4000 SecurityError all errors regarding security issues. 5000 UnexpectedError Groups all unexpected errors BusinessRuleError Groups all codes different than 0 given by the business rules 6000 applied to the execution of an operation. i.e. A rule preventing the execution of a Refund because a manual refund is required will produce an operation returning Result = 6000.