• DeutschEnglish

Vantiv

Logo

Info

Vantiv

Type

Payments by Credit Card

Introduction

For more information about acquirers and connection, integration with Computop Paygate and Implementation of 3-D Secure (2.x), see chapter Card processing - common introduction.

Specific parameters for Vantiv

Besides the general parameters described below for the credit card connection, Vantiv requires the following additional parameters. An authorisation with 3-D Secure is possible.

Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the additional encrypted payment request parameters described below for "interface via form" and "interface via Server-to-Server" :

Key

Format

CND

Description

RefNr

ns..25

O

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

CustomerID

ans..50

O

Customer number. Format must be mutually agreed beforehand with Computop Helpdesk!

RTF

a1

O

for repeat payments (subscriptions): I = Initial payment of a new subscriptionR = Routine payment (Recurring)

ChDesc

ans..25

O

Text printed on the customer’s credit card bill alongside the payee.

TaxAmount

n..10

O

Tax amount of the entire order in the smallest currency unit.

TaxExempt

an..5

O

Code which indicates whether the transaction is subject to Sales Tax: true or false.True=taxless. Default value=false.

OrderID1

ans..15

O

Invoice reference number

Contact data/Address verification (AVS)

bdFirstName

ans..25

O

First name in the invoicing address (for AVS)

bdLastName

ans..25

O

Last name in the invoicing address (for AVS)

bdStreet

ans..35

O

Street name in the invoicing address (for AVS)

Please note that bdStreet and bdStreetNr together may have 34 characters maximum.

bdStreet and bdStreetNr are combined with a space character between and forwarded together. The total content is truncated after 35 characters.

bdStreetNr

ans..35

O

Street number in the invoicing address (for AVS)

Please note that bdStreet and bdStreetNr together may have 34 characters maximum.

bdStreet and bdStreetNr are combined with a space character between and forwarded together. The total content is truncated after 35 characters.

bdStreet2

ans..35

O

Address addition in the billing address

bdZIPCode

ans..20

O

Postcode in the invoicing address (for AVS)

bdCity

ans..35

O

Town/city in the invoicing address

bdState

ans..30

O

State/country in the invoicing address

bdCountryCode

a2

O

Country code of invoicing address according to ISO-3166-1, alphanumeric 2 chars

bdMail

ans..100

O

Email address in the invoicing address

bdPhone

ans..20

O

Phone number in the invoicing address

sdFirstName

ans..25

O

First name in the delivery address

sdLastName

ans..25

O

Last name in the delivery address

sdStreet

ans..35

O

Street name in the delivery address

Please note that sdrStreet and sdStreetNr together may have 34 characters maximum.

sdStreet and sdStreetNr are combined with a space character between and forwarded together. The total content is truncated after 35 characters.

sdStreetNr

ans..35

O

Street number in the delivery address

Please note that sdStreet and sdStreetNr together may have 34 characters maximum.

sdStreet and sdStreetNr are combined with a space character between and forwarded together. The total content is truncated after 35 characters.

sdStreet2

ans..35

O

Address addition in the delivery address

sdZIPCode

ans..20

O

Postcode in the delivery address

sdCity

ans..35

O

Town/city in the delivery address

sdState

ans..30

O

State/country in the delivery address

sdCountryCode

a2

O

Country code of delivery address according to ISO-3166-1, alphanumeric 2 chars

sdMail

ans..100

O

Email address in the delivery address

sdPhone

ans..20

O

Telephone number in the delivery address

Additional parameters for credit card payments

The following table describes the result parameters with which the Computop Paygate responds to your system.

these result parameters are additional to the standard parameters for "interface via form" and "interface via Server-to-Server" described below

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. MerchantId, RefNr) should not be checked case-sentive

Key

Format

CND

Description

RefNr

ns..25

O

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

ErrorText

ans..128

O

Original error text from Vantiv (if an error occurs), if agreed with Computop Helpdesk

CodeExt

n..10

O

Original error code from Vantiv (if an error occurs), if agreed with Computop Helpdesk

Match

a1

O

Total result of an address verification: For possible values see A3 AVS match parameters

ResponseTime

an19

O

Time stamp of response in the format YYYY-MM-DDDHH:MM:SS

LitleTxnID

an19

M

Litle transaction ID

ApprovalCode

ans..6

O

Authorisation code of the Auth- or Sale-transaction

ApprovedAmount

n8

O

Approved amount

PayfacFraudResult

enum

O

Result fraud prevention

„“ Ecom, CAVV nonexistent

„0“ CAVV data field formatted not correctly; check not possible.

„1“ CAVV check failed

„2“ CAVV check successful

„3“ CAVV check successful

„4“ CAVV check failed

„5“ Presently not used

„6“ CAVV not checked, because issuer does not require a check. VisaNet processed as if CAVV would be valid

„7“ CAVV check failed

„8“ CAVV check successfu

l“9” CAVV test failed; Visa generated CAVV because issuer ACS was not available.

“A” CAVV test successful; Visa generated CAVV because issuer Access Control Server (ACS) was not available

.“B” CAVV test successful but no liability shift because

a) ECI was not 5 or 6 or

b) the card type is excluded (e.g. customer card)

“C” issuer selected the return of a CAVV test result and the field 44.13 is empty. The value is set by VisaNet; means that CAVV result is valid

“D” issuer selected the return of a CAVV test result and the field 44.13 is empty. The value is set by VisaNet; means that CAVV result is valid.

CVVResult

enum

an..2

O

Check result:

"M"=Correlation;

"N"=No correlation

"P"=Not processed

"S"=Should be on the card but is not available

"U"= Not certified for processing

"" = Test not carried out for unknown reason

FundingSourceType

enum

a..7

O

„UNKNOWN“

„PREPAID”

„CREDIT”

„DEBIT

”„FSA“ (Flexible Spending Account, IRS approved healthcare)

FundingSourceBalance

an..20

O

Available amount or „Not Available“

FundingSourceReloadable

enum

an..7

O

„UNKNOWN“

„YES“

„NO“

FundingSourcePrepaidCardType

enum

an..7

OC

Only if FundingSourceType="PREPAID": Prepaid card type, e.g. „TEEN“, „GIFT“, „PAYROLL“ etc.

IssuerCountry

an3

O

Country code of issuing bank

CardProductType

enum

an..10

O

„COMMERCIAL“„CONSUMER“„UNKNOWN“

Affluence

enum

an..13

O

Only parts from VISA and MasterCard

„MASS AFFLUENT“ > 100K yearly income

„AFFLUENT“ >100 K yearly income + > 40K revenue

If below 100K the parameter is not returned to Paygate

Additional response parameters for credit card payments

Card processing - Credit Card Form

For more information about credit card processing via forms, please see chapter Credit Card Form (paySSL).

Card processing - Server-2-Server integration

For more information about credit card processing via server-to-server communication, please see chapter Server-2-Server Integration.

Capture / Credit / Reversal

For more information about capture, credit, reversal and credit card payment via POS terminals, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

PayNow

For more information about PayNow, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Batch processing via the interface

For more information about batch processing, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Paygate

Documentation (EN)

Dokumentation (DE)

Paygate Status