0% found this document useful (0 votes)

112 views53 pages

Gateway Integration Guide Connect

This document provides guidance on integrating an online payment gateway called Connect. It describes two main options for structuring the payment process: 1) using hosted payment forms on separate pages for payment, billing, and shipping details, or 2) submitting customer data directly from a merchant's website. It outlines required and optional form fields, and how to process transactions in different modes ranging from minimum to full data collection. Additional topics covered include 3D Secure authentication, recurring payments, supported currencies and payment methods, and transaction responses.

Uploaded by

maliknawaz1253

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

112 views53 pages

Gateway Integration Guide Connect

Uploaded by

maliknawaz1253

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 53

International Payment Gateway

Connect Integration Guide

1.0 Introduction 4
2.0 Payment Process Options 4
2.1 Checkout Option ‘Classic’ 4
2.2 Checkout Option ‘Combinedpage’ 5
3.0 Getting Started 5
3.1 Checklist 5
3.2 ASP Example 5
3.3 PHP Example 6
3.4 Amounts for Test Transactions 7
4.0 Mandatory Fields 7
5.0 Optional Form Fields 8
6.0 Using Your Own Forms to Capture The Data 12
6.1 Payonly Mode 13
6.2 Payplus Mode 14
6.3 Fullpay Mode 14
6.4 Validity Checks 15
7.0 Additional Custom Fields 15
8.0 3D Secure 16
8.1 3DSecure Split Authentication 18
8.2 Dynamic 3D Secure Based on The Card Issuer’s Country 19
9.0 MCC 6012 Mandate in UK 20
10.0 Data Vault 20
11.0 Solvency Information from Bürgel 21
12.0 Recurring Payments 22
13.0 Global Choice™ and Dynamic Pricing 22
14.0 Purchasing Cards 24
15.0 Transaction Response 25
15.1 Response to your Success/Failure URLs 25
15.2 Server-to-Server Notification 29
Appendix I – How to Generate a Hash 30
Appendix II – ipg-util.asp 31
Appendix III – ipg-util.php 32
Appendix IV – Currency Code List 33
Appendix V – Payment Method List 35
Appendix VI – PayPal 38
Appendix VIII – MasterPass 39
Appendix IX – Fraud Detect 41
Appendix X – Local Payments™ 42
Appendix XI – UnionPay SecurePlus 47
Appendix XII – China Domestic 48
Appendix XIV – Korea Domestic 50
Appendix XV - Debit Disbursement 51

There are different manuals available for the digital solutions provided by Fiserv. This Integration Guide will
be the most helpful for integrating hosted payment forms or a Direct Post.
For information about settings, customization, reports and how to process transactions manually (by keying
in the information) please refer to the User Guide Virtual Terminal.
If you have read the documentation and cannot find the answer to your question, please contact your local
support team.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
1.0 Introduction
The Connect solution provides a quick and easy way to add payment capabilities to your website.
Connect manages the customer redirections that are required in the checkout process of many payment
methods or authentication mechanisms and gives you the option to use secure hosted payment pages
which can reduce the burden of compliance with the Data Security Standard of the Payment Card Industry
(PCI DSS).
This document describes how to integrate your website using Connect and provides step by step
instructions on how to quickly start accepting payments from your webshop.
When making decisions on your way of integration, please consider that we do not recommend to
use the hosted payment forms inside an iFrame since some Internet browsers do not allow cookies
to be sent to the third-party hosts, moreover some features (for example: 3D Secure authentications)
and some Alternative Payment methods that involve redirections to the third party services
(for example, iDEAL or PayPal) do not allow displaying their screens within an iFrame.
Depending on your business processes, it can also make sense to additionally integrate our Web Service
API solution (see Web Service API Integration Guide).

2.0 Payment Process Options

The Connect solution provides a number of different options for the payment process to support integrations
where you handle most of the customer interactions on your own website up to integrations where you use
ready-made form pages for the entire payment process.
In the scenarios where you prefer not to use a hosted form, you can submit the required customer data
directly from your own form to Fiserv but please be aware that if you store or process sensitive cardholder
data within your own application, you must ensure that your system components are compliant with the Data
Security Standard of the Payment Card Industry (PCI DSS).

2.1 Checkout Option ‘Classic’

The checkout option ‘classic’ splits the payment process into multiple pages where you can easily decide,
what kind of information you want to get collected by one of the gateway’s hosted forms or what you want to
collect yourself within your webshop environment.
You can for example, let customers select their preferred payment method within your webshop and submit
that payment method in your request to Connect – or if you should prefer not to send the payment method,
the Connect solution will automatically show a payment method selection page to your customer where they
can choose from all payment methods that are activated for your store.
With three different modes, you can define the range of data that shall be captured by the payment gateway:
 payonly: Shows a hosted page to collect the minimum set of information for the transaction
(for example, cardholder name, card number, expiry date and card code for a credit card transaction)
 payplus: In addition to the above, the payment gateway collects a full set of billing information on an
additional page
 fullpay: In addition to the above, the payment gateway displays a third page to also collect shipping
information
The most important aspect around the usage of hosted payment pages is the security of sensitive
cardholder data. When you decide to let your customers enter their credit card details on the page that we
provide and host on our servers for this purpose, it facilitates your compliance with the Data Security
Standard of the Payment Card Industry (PCI DSS) as the payment processing is completely hosted by
Fiserv.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
The hosted pages can be customized with your own logo, colors, and font types in order to make them fit to
the look and feel of your webshop. Please refer to the User Guide Virtual Terminal to learn about how to
make such customizations.

2.2 Checkout Option ‘Combinedpage’

The checkout option ‘combinedpage’ consolidates the payment method choice and the typical next step
(for example, entry of card details or selection of bank) in a single page which gets automatically optimized
for different kinds of user devices, for example, PC, smartphone, tablet and so on.
This hosted page also shows your merchant name at the top and allows you to display a summary of the
purchased items to your customer.
Please note that this checkout option has some functional limitations in comparison to the ‘classic’ option:
 Supported payment methods are currently limited to: Credit cards, Maestro, PayPal, iDEAL, SEPA
Direct Debit, SOFORT Banking, giropay, MasterPass, Google Pay as well as payment methods covered
by the Fiserv Local Payments product option
 It makes use of technical mechanisms that may not work with out-dated browser versions

3.0 Getting Started

This section provides a simple example on how to integrate your website using the “classic” checkout option
in payonly Mode. Examples are provided using ASP and PHP. This section assumes that the developer has
a basic understanding of his chosen scripting language.

3.1 Checklist
In order to integrate with the payment gateway, you must have the following items:

 Store Name

This is the ID of the store that was given to you by Fiserv.

For example: 10123456789

 Shared Secret

This is the shared secret provided to you by Fiserv.

This is used when constructing the hash value (see below).

3.2 ASP Example

The following ASP example demonstrates a simple page that will communicate with the payment gateway in
payonly mode.
When the cardholder clicks Submit, they are redirected to the Fiserv secure page to enter the card details.
After payment has been completed, the user will be redirected to the merchants receipt page. The location
of the receipt page can be configured.

<html>
<head><title>IPG Connect Sample for ASP</title></head>
<body>
<p><h1>Order Form</h1></p>

<form method="post" action=" https://test.ipg-

online.com/connect/gateway/processing ">

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
<input type="hidden" name="txntype" value="sale">
<input type="hidden" name="timezone" value="Europe/Berlin"/>
<input type="hidden" name="txndatetime" value="<% getDateTime() %>"/>
<input type=”hidden” name=”hash_algorithm” value=”HMACSHA256”/>
<input type="hidden" name="hashExtended" value="<% call
createExtendedHash( "13.00","978" ) %>"/>
<input type="hidden" name="storename" value="10123456789" />
<input type="hidden" name="mode" value="payonly"/>
<input type="hidden" name="paymentMethod" value="M"/>
<input type="text" name="chargetotal" value="13.00" />
<input type="hidden" name="currency" value="978"/>
<input type="submit" value="Submit">
</form>
</body>
</html>

The code presented in Appendix II represents the included file ipg-util.asp. It includes code for generating a
hash as is required by Fiserv. The provision of a hash in the example ensures that this merchant is the only
merchant that can send in transactions for this store.
Note, the POST URL used is for integration testing only. When you are ready to go into production, please
contact Fiserv and you will be provided with the live production URL.
Note, the included file, ipg-util.asp uses a server side JavaScript file to build the hash. This file can be
provided on request. To prevent fraudulent transactions, it is recommended that the hash is calculated within
your server and JavaScript is not used like shown in the samples mentioned.

3.3 PHP Example

The following PHP example demonstrates a simple page that will communicate with the payment gateway in
payonly mode.
When the cardholder clicks Submit, they are redirected to the Fiserv secure page to enter the card details.
After payment has been completed, the user will be redirected to the merchants receipt page. The location
of the receipt page can be configured.

<? include("ipg-util.php"); ?>

<html>
<head><title>IPG Connect Sample for PHP</title></head>
<body>
<p><h1>Order Form</h1>

<form method="post" action="https://test.ipg-

online.com/connect/gateway/processing">
<input type="hidden" name="txntype" value="sale">
<input type="hidden" name="timezone" value="Europe/Berlin"/> <input
type="hidden" name="txndatetime" value="<?php echo getDateTime() ?>"/>
<input type=”hidden” name=”hash_algorithm” value=”HMACSHA256”/>

<input type="hidden" name="hashExtended" value="<?php echo createExtendedHash (

"13.00","978" ) ?>"/>
<input type="hidden" name="storename" value="10123456789"/>
<input type="hidden" name="mode" value="payonly"/>
<input type="hidden" name="paymentMethod" value="M"/>
<input type="text" name="chargetotal" value="13.00"/>
<input type="hidden" name="currency" value="978"/>

<input type="submit" value="Submit">

</form>
</body>
</html>

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Note that the POST URL used in this example is for integration testing only. When you are ready to go into
production, please contact Fiserv and you will be provided with the live production URL.
The code presented in Appendix III represents the included file ipg-util.php. It includes code for generating a
hash as is required by Fiserv. The provision of a hash in the example ensures that this merchant is the only
merchant that can send in transactions for this store.

3.4 Amounts for Test Transactions

When using our test system for integration, odd amounts (for example, 13.01 EUR or 13.99 EUR) can cause
the transaction to decline as these amounts are sometimes used to simulate unsuccessful authorizations.
We therefore recommend using even amounts for testing purpose, for example, 13.00 EUR like in the
example above.

4.0 Mandatory Fields

Depending on the transaction type, the following form fields must be present in the form being submitted to
the payment gateway (X = mandatory field). Please refer to this Integration Guide’s Appendixes for
implementation details in relation to alternative payment methods and the other product options.

PayerAuth**
transaction

PostAuth*
PreAuth*

Void
Field Name
Description, Possible Values and Sale
Format

txntype 'sale’, 'preauth’, 'postauth’, 'void’ or X X X X X

‘payer_auth’ (sale) (preauth) (postauth) (void) (payer_auth)

(the transaction type – please note the

descriptions of transaction types in the User
Guide Virtual Terminal)
The possibility to send a ‘void’ using the
Connect interface is restricted. Please
contact your local support team if you want
to enable this feature.

timezone Time zone of the transaction in X X X X X

Area/Location format, for example,
Africa/Johannesburg
America/New_York
America/Sao_Paulo
Asia/Calcutta
Australia/Sydney
Europe/Amsterdam
Europe/Berlin
Europe/Dublin
Europe/London
Europe/Rome

txndatetime YYYY:MM:DD-hh:mm:ss X X X X X
(exact time of the transaction)

hash_algorithm This is to indicate the algorithm that you use X X X X X

for hash calculation. The possible values are:
 HMACSHA256
 HMACSHA384
 HMACSHA512
Only one algorithm value should be used.

hashExtended The extended hash needs to be calculated X X X X X

using all request parameters in ascending

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
order of the parameter names.
When you are using Direct Post, there is also
an option where you do not need to know the
card details (PAN, CVV and Expiry Date) for
the hash calculation. This will be managed
with a specific setting performed on your
store. Please contact your local support team
if you want to enable this feature.
An example of how to generate a hash is
given in Appendix I.

storename This is the ID of the store provided by Fiserv. X X X X X

mode ‘fullpay’, ‘payonly’ or ‘payplus’ X X

(the chosen mode for the transaction when
using the ‘classic’ checkout option)

chargetotal This is the total amount of the transaction X X X X X

using a dot or comma as decimal separator,
for example, 12.34 for an amount of 12 Euro
and 34 Cent. Group separators
like1,000.01/1.000,01 are not allowed.

currency The numeric ISO code of the transaction X X X X

currency, for example, 978 for Euro (see
examples in Appendix IV)

oid The order ID of the initial action a PostAuth X

shall be initiated for.

ipgTransactionId Exact identification of a transaction that shall X

or be voided. You receive this value as result
merchantTransactionId parameter‚ ‘ipgTransactionId’ of the
corresponding transaction.
Alternatively ‘merchantTransactionId’ can be
used for the Void in case the merchant has
assigned one.

* The transaction types ‘preauth’ and ‘postauth’ only apply to the payment methods credit card, PayPal.
** The transaction type ‘payer_auth’ is only required if you want to split the 3D Secure authentication
process from the payment transaction (authorization) process. See more information in the 3D Secure
section of this guide.
Please see a list of currencies and their ISO codes in Appendix IV.

5.0 Optional Form Fields

Field Name Description, Possible Values and Format
cardFunction This field allows you to indicate the card function in case of combo cards which
provide credit and debit functionality on the same card. It can be set to ‘credit’ or
‘debit’.
The field can also be used to validate the card type in a way that transactions
where the submitted card function does not match the card’s capabilities will be
declined. If you for example, submit “cardFunction=debit” and the card is a credit
card, the transaction will be declined.

checkoutoption This field allows you to set the checkout option to:
 ‘classic’ for a payment process that is split into multiple pages,
 ‘combinedpage’ for a payment process where the payment method choice
and the typical next step (for example, entry of card details or selection of

comments Place any comments here about the transaction.

customerid This field allows you to transmit any value, for example, your ID for the
customer.
Please note that for:
 Direct Debit transactions, the Customer ID can be submitted to the bank,
depending on the length of the Order ID. The maximum amount of
characters that can be submitted to the bank is 78. Please note that this is
not applicable when processing Direct Debit through the Fiserv Local
Payments offering.
 iDEAL transactions, the Customer ID can be submitted in your request filled
in with any relevant data which can be populated in a field in the iDEAL
TransactionRequest to be displayed on your consumers’ bank account
statements. Please note that this is not applicable when processing iDEAL
through the Fiserv Local Payments offering.

dccInquiryId Inquiry ID for a Dynamic Pricing request. Used to send the Inquiry ID you have
obtained through a Web Service API call
(RequestMerchantRateForDynamicPricing). This value will be used to retrieve
the currency conversion information (exchange rate, converted amount) for this
transaction.

dccSkipOffer If the cardholder declines the currency conversion offer within your environment,
the request parameter ‘dccSkipOffer’ can be set to ‘true’ so that the hosted
consumer dialogue will automatically be skipped.

dynamicMerchantName The name of the merchant to be displayed on the cardholder’s statement. The
length of this field should not exceed 25 characters. If you want to use this field,
please contact your local support team to verify if this feature is supported in
your country.

idealIssuerID This parameter can be used to submit the iDEAL issuing bank in case you let
Not Available in Australia your customers select the issuer within your shop environment. If you do not
pass this value for an iDEAL transaction, a hosted selection form will be
displayed to your customer. Please note that this is not applicable when
processing iDEAL through the Fiserv Local Payments offering.

iDEAL issuer Value

ABN AMRO ABNANL2A

ING INGBNL2A

SNS Bank SNSBNL2A

van Lanschot FVLBNL22

Triodos Bank TRIONL2U

Knab KNABNL2H

Rabobank RABONL2U

RegioBank RBRBNL21

ASN Bank ASNBNL21

Bunq BUNQNL2A

Handelsbanken HANDNL2A

Moneyou MOYONL21

invoicenumber This field allows you to transmit any value, for example, an invoice number or
class of goods. Please note that the maximum length for this parameter is 48
characters.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
item1 up to item999 Line items are regular Connect integration key-value parameters
(URL-encoded), where:
 the name is a combination of the keyword item and a number, where the
number indicates the list position for example: item1
 the value is represented by a semicolon-separated list of values, where the
position indicates the meaning of the list item property for example,
<1>;<2>;<3>;<4>;<5>;<6>;<7>

The ‘item1’ to ‘item999’ parameters allow you to send basket information in the
following format:

id;description;quantity;item_total_price;sub_total;vat_tax;shipping

‘shipping’ always has to be set to ‘0’ for single line item. If you want to include a
shipping fee for an order, please use the predefined id IPG_SHIPPING.

For other fees that you may want to add to the total order, you can use the
predefined id IPG_HANDLING.

When you want to apply a discount, you should include an item with a negative
amount and change accordingly the total amount of the order. Do not forget to
regard the ‘quantity’ when calculating the values for example: subtotal and VAT
since they are fixed by items.
Examples:
A;Product A;1;5;3;2;0
B;Product B;5;10;7;3;0
C;Product C;2;12;10;2;0
D;Product D;1;-1.0;-0.9;-0.1;0
IPG_SHIPPING;Shipping costs;1;6;5;1;0
IPG_HANDLING;Transaction fee;1;6.0;6.0;0;0

language This parameter can be used to override the default payment page language
configured for your merchant store.
The following values are currently possible:

Language Value

Chinese (simplified) zh_CN

Chinese (traditional) zh_TW

Czech cs_CZ

Danish da_DK

Dutch nl_NL

English (USA) en_US

English (UK) en_GB

Finnish fi_FI

French fr_FR

German de_DE

Greek el_GR

Hungarian hu_HU

Italian it_IT

Japanese ja_JP

Norwegian (Bokmål) nb_NO

Polish pl_PL

Serbian (Serbia) sr_RS

Slovak sk_SK

Spanish es_ES

Swedish sv_SE

mandateDate This field allows you to reference to the date of the original mandate when
Not Available in Australia performing recurring Direct Debit transactions. The date needs to be submitted
in format YYYYMMDD.
Please note that this is a mandatory field for recurring Direct Debit
transactions.

mandateReference This field allows you to transmit a Mandate Reference for Direct Debit payments.
Not Available in Australia Please note the regulatory requisite to keep the Mandate Reference
unambiguous.

mandateType This field allows you to process Direct Debit transactions that are based on
Not Available in Australia mandates for recurring collections. The mandate type can be set to ‘single’ for
single (one-off) debit collections, to ‘firstCollection’ when submitting the initial
transaction related to a mandate for recurring Direct Debit collections, to
‘recurringCollection’ for subsequent recurring transactions or to ‘finalCollection’
for the last direct debit in a series of recurring direct debits. Transactions where
this parameter is not submitted by the merchant will be flagged as a single debit
collection.
Please note that it is mandatory to submit a mandateReference in case of
recurring collections.

mandateUrl When your store is enabled for SEPA Direct Debit as part of the Local Payments
Not Available in Australia offering, this field allows you to transmit a valid URL of SEPA Direct Debit
mandate to enable the Risk and Compliance department to access the details.
Please note that it is mandatory to submit a mandateReference and a
mandateDate together with a mandateUrl in case you manage SEPA Direct
Debit mandates on your side in the combination with the Local Payments
offering.

merchantTransactionId Allows you to assign a unique ID for the transaction. This ID can be used to
reference to this transactions in a PostAuth or Void request
(referencedMerchantTransactionId).

mobileMode If your customer uses a mobile device for shopping at your online store you can
submit this parameter with the value ‘true’, when using the ‘classic’ checkout
option. This will lead your customer to a payment page flow that has been
specifically designed for mobile devices.

numberOfInstallments This parameter allows you to set the number of instalments for a Sale
transaction if your customer pays the amount in several parts.

installmentsInterest This parameter allows you to choose, if instalment interest should be applied or
not, the values “true” or “false” are currently possible.

installmentDelayMonths This parameter allows you to delay the first instalment payment for several
months, values 2-99 are currently possible.

oid This field allows you to assign a unique ID for your order. If you choose not to
assign an order ID, the Fiserv system will automatically generate one for you.
Please note that for Direct Debit transactions, a maximum of 78 characters can
be submitted to the bank.

paymentMethod If you let the customer select the payment method (For example, Mastercard,
Visa, Direct Debit) in your shop environment or want to define the payment type
yourself, transmit the parameter ‘paymentMethod’ along with your Sale or
PreAuth transaction.
If you do not submit this parameter, the payment gateway will display a drop-
down menu to the customer to choose from the payment methods available for

ponumber This field allows you to submit a Purchase Order Number with up to 50
characters.

refer This field describes who referred the customer to your store.

referencedMerchantTransactionID This field allows to reference to a merchantTransactionId of a

transaction when performing a Void. This can be used as an alternative to
ipgTransactionId if you assigned a merchantTransactionId in the original
transaction request.

referencedSchemeTransactionId Credentials on file (COF) specific parameter. This field allows you to include in
your request ‘schemeTransactionId’ that has been returned in the response of
the initial transaction in order to provide a reference to the original transaction,
which stored the credentials for the first time.

responseFailURL The URL where you wish to direct customers after a declined or unsuccessful
transaction (your Sorry URL) – only needed if not setup in Virtual
Terminal/Customisation.

responseSuccessURL The URL where you wish to direct customers after a successful transaction (your
Thank You URL) – only needed if not setup in Virtual Terminal/Customisation.

reviewOrder MasterPass-specific parameter for scenarios where the final amount needs to be
Not Available in Australia confirmed by the customer after returning from the Wallet. Set the value for this
parameter to ‘true’ in order to indicate that the final transaction amount needs to
be reviewed by the cardholder.

reviewURL MasterPass-specific parameter for scenarios where the final amount needs to be
Not Available in Australia confirmed by the customer after returning from the MasterPass environment.
Use this parameter to indicate where the customer shall be redirected to in order
to review and complete the transaction after having clicked on “Finish shopping”
within the Wallet.

shipping This parameter can be used to submit the shipping fee, in the same format as
‘chargetotal’. If you submit ‘shipping’, the parameters ‘subtotal’ and ‘vattax’ have
to be submitted as well. Note that the ‘chargetotal’ has to be equal to ‘subtotal’
plus ‘shipping’ plus ‘vattax’.

trxOrigin This parameter allows you to use the secure and hosted payment form
capabilities within your own application. Possible values are:
 ‘MAIL’ (for transactions where the payment details are captured manually
and provided in written form the Card Code entry is not allowed)
 ‘PHONE’ (for transactions where you have received the order over the
phone and enter the payment details yourself the Card Code entry is
required)
 ‘ECI‘ (for standard usage in an eCommerce environment where your
customer enters the payment details).

unscheduledCredentialOnFileType Credentials on file (COF) specific parameter. This field allows you to flag
transactions as unscheduled credential on file type. Currently the valid values
are: FIRST, CARDHOLDER_INITIATED or MERCHANT_INITIATED to advise
the scenario if the credential is stored on your side.

vattax This field allows you to submit an amount for Value Added Tax or other taxes,
for example, GST in Australia. Please ensure the sub total amount plus shipping
plus tax equals the charge total.

6.0 Using Your Own Forms to Capture the Data

If you decide to create your own forms, that is, Direct Post (not to use the ones provided and hosted by
Fiserv), there are additional mandatory fields that you need to include. These fields are listed in the following
sections, depending on the mode you choose.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Using Direct Post allows you to have full control over the look and feel of the form where your customers
enter their card details for payment while simultaneously avoiding the need to have sensitive card data
within your systems.
In addition, you should check if JavaScript is activated in your customer’s browser and if necessary, inform
your customer that JavaScript needs to be activated for the payment process.
Following Fields in grey are not available in Australia

6.1 Payonly Mode

After your customer has decided how to pay, you present a corresponding HTML-page with a form to enter
the payment data as well as hidden parameters with additional transaction information.
In addition to the mandatory fields listed above, your form needs to contain the following fields (part of them
can be hidden):

UnionPay SecurePlus
Description, Possible Debit/Electron/Delta)
Field Name

Direct Debit
Credit Card

Bancontact
Values and Format

Maestro
(+ Visa

SEPA

cardnumber Your customer’s card number. X X X X

12–24 digits.

expmonth The expiry month of the card X X X (X)

(two digits) mandatory
if credit
card

expyear The expiry year of the card X X X (X)

(four digits) mandatory
if credit
card

cvm The card code, in most cases on X X (X)

the backside of the card as an optional mandatory
field “if on if credit
(three to four digits) card” card

iban Your customer’s IBAN – X

International Bank Account
Number (22 digits)

bic Your customer’s BIC – Business (X)

Identifier Code (eight or 11 digits) mandatory if
foreign IBAN

bname Name of the bank account owner X

that will be debited (alphanumeric
characters, spaces, and dashes
limited
to 96)

For the Local Payments method specific (mandatory/optional) fields please refer to Appendix X.
For the China Domestic method specific (mandatory/optional) fields please refer to Appendix XII.
For the Korea Domestic method specific (mandatory/optional) fields please refer to Appendix XIV.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
6.2 Payplus Mode
Using payplus mode, it is possible to additionally transfer billing information to the payment gateway. The
following table describes the format of these additional fields:

Field Name Possible Values Description

bcompany Alphanumeric Customers Company

characters,
spaces and
dashes limited to 96

bname Alphanumeric Customers Name

characters,
spaces and
dashes limited to 96

baddr1 Limit of 96 Customers Billing Address 1

characters,
including
spaces

baddr2 Limit of 96 Customers Billing Address 2

characters,
including
spaces

bcity Limit of 96 Billing City

characters,
including
spaces

bstate Limit of 96 State, Province or Territory

characters,
including
spaces

bcountry Two Letter Country Code Country of Billing Address

bzip Limit of 24 Zip or Postal Code

characters,
including
spaces

phone Limit of 32 Characters Customers Phone Number

fax Limit of 32 Characters Customers Fax Number

email Limit of 254 Characters Customers Email Address

6.3 Fullpay Mode

Using fullpay mode, it is possible to additionally transfer shipping information to the payment gateway. The
billing information is as specified above. The following table describes the format of the shipping fields:

Field Name Possible Values Description

sname Alphanumeric Ship-to Name
characters,
spaces and
dashes limited to 96

saddr1 Limit of 96 Shipping Address Line 1

characters,
including

saddr2 Limit of 96 Shipping Address Line 2

characters,
including
spaces

scity Limit of 96 Shipping City

characters,
including
spaces

sstate Limit of 96 State, Province or Territory

characters,
including
spaces

scountry Two letter country code Country of Shipping Address

szip Limit of 24 Zip or Postal Code

characters,
including
spaces

6.4 Validity Checks

Prior to the authorization request for a transaction, the payment gateway performs the following validation
checks:
 The expiry date of cards needs to be in the future
 The Card Security Code field must contain three or four digits
 The structure of a card number must be correct (LUHN check)
 An IBAN must contain 22 digits
 A BIC needs to contain eight or 11 digits
If the submitted data should not be valid, the payment gateway presents a corresponding data entry page to
the customer.
To avoid this hosted page when using your own input forms for the payment process, you can transmit the
following additional parameter along with the transaction data:

full_bypass=true

In that case you get the result of the validity check back in the transaction response and can display your
own error page based on this.
Please note, if the transaction is eligible for DCC (your store is configured for DCC and the customer is
paying by credit card capable of DCC), your customer will be presented the DCC page despite having
full_bypass set to true. This is due to regulatory reasons. You can avoid displaying of DCC choice pages by
doing the DCC Inquiry yourself through our Web Service API (RequestMerchantRateForDynamicPricing).

7.0 Additional Custom Fields

You may want to use further fields to gather additional customer data geared toward your business
specialty, or to gather additional customer demographic data which you can then store in your own database
for future analysis. You can send as many custom fields to the payment gateway as you wish and they will
get returned along with all other fields to the response URL.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Up to ten custom fields can be submitted in a way that they will be stored within the gateway so that they
appear in the Virtual Terminal’s Order Detail View as well as in the response to Inquiry Actions that you send
through our Web Service API .

Field Name Description, Possible Values and Format

customParam_key If you want to use this feature, please send the custom fields in the format
customParam_key=value.

The maximum length of a custom parameter is 100 characters.

Example:<input type="hidden"
name="customParam_color" value="green"/>

8.0 3D Secure
The Connect solution includes the ability to authenticate transactions using Verified by Visa, Mastercard
SecureCode, American Express SafeKey, JCB J/Secure and Diners ProtectBuy to provide an additional
security layer for online card transactions.
If your store is enabled for 3D Secure, all Sale or preAuth transactions that you initiate by posting an HTML
form will by default go through the 3D Secure process without the need for you to do anything, That is
cardholders with an enrolled card will see a page from the card issuer to enter the password unless the card
issuer decides not to check it.
The generic fields to be considered:

Field Name Description, Possible Values and Format

authenticateTransaction Optional parameter to be set either to ‘true’ or ‘false’ to enable or disable 3D
Secure authentication on a Transaction-by-Transaction basis.

Example for a transaction with 3D Secure:

Example for a transaction without 3D Secure:

threeDSRequestorChallengeIndicator Optional parameter for EMV 3D Secure (2.0) to be set to: 01,02,03,04 in
order to indicate the preferred type of authentication:

 01 – no preference (set as default value)

 02 – no challenge requested
 03 – challenge requested 3DS requestor preference
 04 – challenge requested mandate

threeDSTransType The parameter for EMV 3D Secure (2.0) represents the type of purchased
item, mandatory for Visa and Brazilian market, otherwise optional. If no
specific value present in the transaction request, default value is used.

 01 – Goods/Service Purchase (default value)

 03 – Check Acceptance
 10 – Account Funding
 11 – Quasi-Cash Transaction
 28 – Prepaid Activation and Load

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
scaExemptionIndicator1 Optional parameter to request an exemption from Strong Customer
Authentication (SCA) without the need to perform 3-D Secure
authentication. Currently available values:

 Low Value Exemption

 TRA Exemption
 Trusted Merchant Exemption
 SCP Exemption

Note this parameter is relevant only for the European merchants impacted
by the PSD2 requirements.

skipTRA This optional parameter allows you to use 3D Secure even if the transaction
has been evaluated as low risk and would be eligible for an exemption.
Currently available values:

 true
 false

When your store has been set up with Transaction Risk Analysis (TRA)
service, but you do want to force 3D Secure authentication for a certain
transaction, set ‘skipTRA’ to ‘true’.

Note this parameter is relevant only for the European merchants impacted
by the PSD2 requirements.

In principle, it may occur that 3D Secure authentications cannot be processed successfully for technical
reasons. If one of the systems involved in the authentication process is temporarily not responding, the
payment transaction will be processed as a “regular” eCommerce transaction (ECI 7). A liability shift to the
card issuer for possible chargebacks is not warranted in this case. If you prefer that such transactions
shall not be processed at all, our technical support team can block them for your Store on request.
Credit card transactions with 3D Secure hold in a pending status while cardholders search for their
password or need to activate their card for 3D Secure during their shopping experience. During this time
when the final transaction result of the transaction is not yet determined, the payment gateway sets the
Approval Code to „?:waiting 3dsecure“. If the session expires before the cardholder returns from the 3D
Secure dialogue with his bank, the transaction will be shown as “N:-5103:Cardholder did not return from
ACS”.
Please note that the technical process of 3D Secure transactions differs in some points compared to a
normal transaction flow. If you already have an existing shop integration and plan to activate 3D Secure
subsequently, we recommend performing some test transactions on our test environment.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
8.1 3DSecure Split Authentication
If your business or technical processes require the cardholder authentication to be separated from the
payment transaction (authorization), you can use the transaction type ‘payer_auth’. This transaction type
only performs the authentication (and stores the authentication results).

Example of a ‘payer_auth’ request:

<html>
<head><title>IPG Connect Sample for ASP</title></head>
<body>
<p><h1>Order Form</h1></p>

<form method="post" action=" https://test.ipg-

online.com/connect/gateway/processing ">
<input type="hidden" name="txntype" value="payer_auth">
<input type="hidden" name="timezone" value="Europe/Berlin"/>
<input type="hidden" name="txndatetime" value="<%
getDateTime() %>"/>
<input type=”hidden” name=”hash_algorithm”
value=”HMACSHA256”/>
<input type="hidden" name="hashExtended" value="<% call
createExtendedHash( "13.00","978" ) %>"/>
<input type="hidden" name="storename" value="10123456789" />
<input type="hidden" name="mode" value="payonly"/>
<input type="hidden" name="paymentMethod" value="M"/>
<input type="text" name="chargetotal" value="13.00" />
<input type="hidden" name="currency" value="978"/>
<input type="hidden" name="authenticateTransaction"
value="true"/>
<input type="submit" value="Submit">
</form>
</body>
</html>

Example of a ‘payer_auth’ response:

{txndate_processed=17/04/20 17:17:32,
ccbin=542606,
timezone=Europe/Berlin,
oid=C-2101f68a-45e9-4f3c-a6da-1337d5574717,

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
cccountry=N/A,
expmonth=12,
hash_algorithm=HMACSHA256
currency=978,
chargetotal=13.00,
approval_code=Y:ECI2/5:Authenticated,
hiddenSharedsecret=sharedsecret,
hiddenTxndatetime=2020:04:17-17:32:41,
expyear=2024,
response_hash=LarWYFSNgEToq13HlvyslX6hywi2T/nMn8jMY+1kxkI=,
response_code_3dsecure=1,
hiddenStorename=10123456789,
transactionNotificationURL=https://test.ipg-
online.com/webshop/transactionNotification,
tdate=1491824253,
ignore_refreshTime=on,
ccbrand=MASTERCARD,
txntype=payer_auth,
paymentMethod=M,
txndatetime=2020:04:17-17:32:41,
cardnumber=(MASTERCARD) ... 4979,
ipgTransactionId=84120276797,
status=APPROVED}

In a second step, you need to submit a payment transaction (‘sale’ or ‘preauth’) through the IPG Web
Service API and reference it to the prior authentication. To review an example of a ‘sale’ transaction that
refers to a previous ‘payer_auth’ transaction, please review the 3DSecure Split Authentication section, in the
Web Service API integration guide.

8.2 Dynamic 3D Secure Based on The Card Issuer’s Country

With the Dynamic 3D Secure product option you can exclude specific card transactions from the 3D Secure
authentication based on a certain country selection (that is: issuing country) for example: Germany,
Switzerland and Austria, while apply the standard 3D Secure authentication process for other transactions
with card from other countries.
You can improve the consumer experience for the cardholders from the selected countries, while the
chargeback risk for such transactions is still with you.
If you have ordered this product option, the countries that should be excluded from the 3D Secure
authentication process can be set up for you by your local support team.
In case of some specific high-risk transactions, you can override this setting on transaction level and force
the 3D Secure authentication on a Transaction-by-Transaction basis, even if the card used is issued in a
country, which has been defined by you as a country where 3D Secure authentication should not be applied.
In order to do it, you have to send the parameter ‘override3dsCountryExclusion’ set to “true” then the country
setting will be ignored and the 3D Secure authentication process applied.

Field Name Description, Possible Values and Format

override3dsCountryExclusion Optional parameter to be set either to ‘true’ or ‘false’.

Set to ‘true’ if for a transaction you would like to enforce 3D Secure

authentication, despite this country possibly being exempted from
authentication due to the merchant configured list of countries, where 3D
Secure is not required.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
9.0 MCC 6012 Mandate in UK
Not Available in Australia
For U.K.-based Financial Institutions with Merchant Category Code 6012, Visa and Mastercard have
mandated additional information of the primary recipient of the loan to be included in the authorization
message.
If you are a UK 6012 merchant use the following parameters for your transaction request:

Field Name Description, Possible Values and Format

mcc6012BirthDay Date of birth in format dd.mm.yyyy

mcc6012AccountFirst6 First six digits of recipient PAN (where the primary recipient account is
a card)

mcc6012AccountLast4 Last four digits of recipient PAN (where the primary recipient account is a card)

mcc6012AccountNumber Recipient account number (where the primary recipient account is not a card)

mcc6012Surname Surname

mcc6012Zip Post Code

If you are a UK 6051 and 7299 merchant, you can reuse the MCC 6012 parameters to send the optional
data to be included in the authorization message. However, please note that you have to either populate all
the parameters or none otherwise the transaction will be declined.

10.0 Data Vault

With the Data Vault product option you can store sensitive cardholder data in an encrypted database in
Fiserv’s data center to use it for subsequent transactions without the need to store this data within your own
systems.
If you have ordered this product option, the Connect solution offers you the following functions:

 Store or update payment information when performing a transaction

Additionally send the parameter ‘hosteddataid’ together with the transaction data as a unique
identification for the payment information in this transaction. Depending on the payment type, credit card
number and expiry date or IBAN and BIC will be stored under this ID if the transaction has been
successful. In cases where the submitted ‘hosteddataid’ already exists for your store, the stored
payment information will be updated.

If you want to assign multiple IDs to the same payment information record, you can submit the
parameter ‘hosteddataid’ several times with different values in the same transaction.
If you prefer not to assign a token yourself but want to let the gateway do this for you, send the
parameter ‘assignToken’ and set it to ‘true’. The gateway will then assign a token and include it in the
transaction response as ‘hosteddataid’.
If you have use cases where you need some of the tokens for single transactions only (for example, for
consumers that check out as a “guest”, use the additional parameter ‘tokenType’ with the values
‘ONETIME’ (card details will only be stored for a short period of time) or ‘MULTIPAY’ (card details will be
stored for use in future transactions).

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
 Initiate payment transactions using stored data
If you stored cardholder information using the Data Vault option, you can perform transactions using the
‘hosteddataid’ without the need to pass the credit card or bank account data again.
Please note that it is not allowed to store the card code (in most cases on the back of the card) so that
for credit card transactions, the cardholder still needs to enter this value. If you use Fiserv’s hosted
payment forms, the cardholder will see the last four digits of the stored credit card number, the expiry
date and a field to enter the card code.
When using multiple Store IDs, it is possible to access stored card data records of a different Store ID
then the one that has been used when storing the record. In that way you can for example, use a shared
data pool for different distributive channels. To use this feature, submit the Store ID that has been used
when storing the record as the additional parameter ‘hosteddatastoreid’.
 Avoid duplicate cardholder data for multiple records
To avoid customers using the same cardholder data for multiple user accounts, the additional
parameter ‘declineHostedDataDuplicates’ can be sent along with the request. The valid values for
this parameter are ‘true’/’false’. If the value for this parameter is set to ‘true’ and the cardholder data
in the request is already found to be associated with another ‘hosteddataid’, the transaction will be
declined.
See further possibilities with the Data Vault product in the Integration Guide for the Web Service API.

11.0 Solvency Information from Bürgel

Not Available in Australia
The Connect solution is integrated with Bürgel Wirtschaftsinformationen, a leading company in the field of
business information.
This integration allows you to select the payment methods you offer to an individual customer based on
Bürgel’s information on the non-payment risk. Please see information on setting options in the User Guide
Virtual Terminal.
If you have a contract with Bürgel and have ordered this product option, use the following parameters for
your transaction requests:

Field Name Description Mandatory

valueaddedservices Buergel Please submit this parameter for all transactions
where you want to use this feature

bfirstname, blastname, bname Customer name Yes, bfirstname and blastname or bname

baddr1 Customer address Yes, format must be street and house number

bzip Customer ZIP or Postal Yes

Code

bcity Customer city Yes

bcountry Customer country Yes, in the ISO alpha code format, for example, DE

bbirthday Customer birthday Not mandatory.

Format: DD.MM.YYYY

If any of the mandatory address information is missing, the transaction request will be declined.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
12.0 Recurring Payments
For credit card and PayPal transactions, it is possible to install recurring payments using Connect. To use
this feature, the following additional parameters will have to be submitted in the request:

Field Name Possible Values Description

recurringInstallmentCount Number between 1 and Number of installments to be made including the
999 initial transaction submitted

recurringInstallmentPeriod day The periodicity of the recurring payment

week
month
year

recurringInstallmentFrequency Number between 1 and The time period between installments

recurringComments Limit of 100 Any comments about the recurring transaction

characters,
including
spaces

Note that the start date of the recurring payments will be the current date and will be automatically
calculated by the system.
The recurring payments installed using Connect can be modified or cancelled using the Virtual Terminal or
Web Service API.

13.0 Global Choice™ and Dynamic Pricing

Dynamic Currency Conversion is available in Australia, Dynamic Pricing is Not Available in Australia. For
multicurrency needs, please contact the support team.
With Fiserv Global Choice™, foreign customers have the choice to pay for goods and services purchased
online in their home currency when using their Visa or Mastercard credit card for the payment. The currency
conversion is quick and eliminates the need for customers to mentally calculate the estimated cost of the
purchase in their home currency. International Visa and Mastercard eCommerce customers can make
informed decisions about their online purchases and eradicate any unexpected pricing or foreign exchange
conversions on receipt of their monthly statements.
If your Store has been activated for this product option, the Connect solution automatically offers a currency
choice to your customers if the card they use has been issued in a country with a currency that is different to
your default currency.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Please note that for compliance reasons Fiserv’s Global Choice can only be offered on transactions that
take place in full at that time (for example, Sale, Refund) and not on any delayed settlement (for example,
pre/post auth, recurring) due to the fluctuation of the rate of exchange.
Another option for your foreign customers is to display all pricing within your online store in their home
currency using our Dynamic Pricing solution. This solution removes the need for your company to set pricing
in any other currency other than your home currency.
Please see the Integration Guide for our Web Service API for details on how to request the exchange rates.
If your Store has been activated for this product option and you want to submit the payment transaction
through our Connect solution, you need to send the DCC Inquiry ID that you have received along with the
exchange rate request in the parameter ‘dccInquiryId’.
You can also use the ‘dccInquiryId’ for cases where Global Choice is being offered and handled on your side
(for example, within a mobile app). If the cardholder declines the currency conversion offer within your

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
environment, the request parameter ‘dccSkipOffer’ can be set to ‘true’ so that the hosted consumer dialogue
will automatically be skipped.

14.0 Purchasing Cards

Not available for Australia
Purchasing Cards offer businesses the ability to allow their employees to purchase items with a credit card
while providing additional information on sales tax, customer code and so on. When providing specific
details on the payment being made with a Purchasing card favourable addendum interchange rates are
applied.
There are three levels of details required for Purchasing Cards:
 Level I – The first level is the standard transaction data; no enhanced data is required at this level
 Level II – The second level requires that data such as tax amount and customer code be supplied in
addition to the standard transaction date. (Visa only have a level II option)
 Level III – The third level allows a merchant to pass a detailed accounting of goods and services
purchased to the buyer. All the data for Level I and Level II must also be passed to participate in
Level III. (Visa and Mastercard)
You can submit Level II and Level III data in your transaction request using the following parameters

Field Name Description, Possible Values and Format

pcCustomerReferenceID Merchant-defined reference for the customer that will appear on the customer’s
statement.

pcSupplierInvoiceNumber Merchant-defined reference for the invoice, for example, invoice number.

pcSupplierVATRegistrationNumber The Identification number assigned by the taxing authorities to the merchant.

pcTotalDiscountAmount The total discount amount applied to a transaction (that is, total transaction
percentage discounts, fixed transaction amount reductions or summarization of
line item discounts).

pcTotalDiscountRate The rate of the discount for the whole transaction.

pcVatShippingRate The total freight/shipping amount applied to the transaction. Merchants can
choose to deliver the contents of a single transaction in multiple shipments and
this field reflects the total cost of those deliveries.

pcVatShippingAmount The total freight/shipping amount applied to the transaction. Merchants can
choose to deliver the contents of a single transaction in multiple shipments and
this field reflects the total cost of those deliveries.

pcLineItemsJson Line Item Details in JSON format.

See table below for more information.

Purchasing Cards Line Item Details in JSON format:

Field Name Description, Possible Values and Format

CommodityCode A reference to a commodity code used to classify purchased item.

ProductCode A reference to a merchant product identifier, the Universal Product Code (UPC)
of purchased item.

Description Represents a description of purchased item.

Quantity Represents a quantity of purchased items.

UnitPrice Represents mandatory data for Level III transactions.

VATAmountAndRate Represents a rate of the VAT amount, for example, 0.09 (means 9%).

DiscountAmountAndRate Represents a rate of the discount amount, for example, 0.09 (means 9%).

LineItemTotal This field is a calculation of the unit cost multiplied by the quantity and
less the discount per line item. The calculation is reflected as: [Unit Cost *
Quantity] – Discount per Line Item = Line Item Total.

15.0 Transaction Response

15.1 Response to your Success/Failure URLs
Upon completion, the transaction details will be sent back to the defined ‘responseSuccessURL’ or
‘responseFailURL’ as hidden fields:

Field Name Description, Possible Values and Format

approval_code Approval code for the transaction. The first character of this parameter is the most
helpful indicator for verification of the transaction result.

‘Y’ indicates that the transaction has been successful

‘N’ indicates that the transaction has not been successful

“?” indicates that the transaction has been successfully initialized, but a final result
is not yet available since the transaction is now in a waiting status. The transaction
status will be updated at a later stage.

oid Order ID

refnumber Reference number

status Transaction status, for example, ‘APPROVED’, ‘DECLINED’ (by authorization

endpoint or due to fraud prevention settings), ‘FAILED’ (wrong transaction
message content/parameters, and so on) or ‘WAITING’ (asynchronous Alternative
Payment Methods).

txndate_processed Time of transaction processing

ipgTransactionId Transaction identifier assigned by the gateway, for example, to be used for a Void

tdate Identification for the specific transaction

fail_reason Reason the transaction failed

response_hash Hash-Value to protect the communication (see note below)

processor_response_code The response code provided by the backend system.

Please note that response codes can be different depending on the used payment
type and backend system. While for credit card payments, the response code ‘00’
is the most common response for an approval, the backend for giropay
transactions for example, returns the response code ‘4000’ for successful
transactions.

fail_rc Internal processing code for failed transactions

terminal_id Terminal ID used for transaction processing

ccbin Six digit identifier of the card issuing bank

cccountry Three letter alphanumeric ISO code of the cardholder’s country (for example,
USA, DEU, ITA and so on)

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Filled with “N/A” if the cardholder’s country cannot be determined or the payment
type is not credit card

ccbrand Brand of the credit or debit card:

MASTERCARD
VISA
AMEX
DINERSCLUB
JCB
CUP
CABAL
MAESTRO
RUPAY
BCMC
SOROCRED
Filled with “N/A” for any payment method which is not a credit card or debit card

schemeTransactionId Credentials on file (COF) specific parameter. Returned in the response by a

scheme for stored credentials transactions to be used in subsequent transaction
request for future reference.

For 3D Secure transactions only:

response_code_3dsecure Return code indicating the classification of the transaction:

1 – Successful authentication (VISA ECI 05, Mastercard ECI 02)

2 – Successful authentication without AVV (VISA ECI 05, Mastercard ECI 02)
3 – Authentication failed/incorrect password (transaction declined)
4 – Authentication attempt (VISA ECI 06, Mastercard ECI 01)
5 – Unable to authenticate/Directory Server not responding (VISA ECI 07)
6 – Unable to authenticate/Access Control Server not responding (VISA ECI 07)
7 – Cardholder not enrolled for 3D Secure (VISA ECI 06)
8 – Invalid 3D Secure values received, most likely by the credit card issuing bank’s
Access Control Server (ACS)

Please see note about blocking ECI 7 transactions in the 3D Secure section of this
document.

For Global Choice™ transactions only:

dcc_foreign_amount Converted amount in cardholder home currency. Decimal number with dot (.) as a
decimal separator

dcc_foreign_currency ISO numeric code of the cardholder home currency. This transaction is performed
in this currency String

dcc_margin_rate_percentage Percent of margin applied to the original amount. Decimal number with dot (.) as a
decimal separator

dcc_rate_source Name of the exchange rate source (for example, Reuters Wholesale Inter Bank)
String

dcc_rate Exchange rate. Decimal number with dot (.) as a decimal separator.

dcc_rate_source_timestamp Exchange rate origin time. Integer – Unix timestamp (seconds since 1.1.1970)

dcc_accepted Indicates if the card holder has accepted the conversion offer (response value
‘true’) or declined the offer (response value ‘false’)

For iDEAL transactions only:

accountOwnerName Name of the owner of the bank account that has been used for the iDEAL

iban IBAN of the bank account that has been used for the iDEAL transaction

bic BIC of the bank account that has been used for the iDEAL transaction

For MasterPass transactions only:

redirectURL When reviewOrder has been set to ‘true’, the response contains the URL that you
need to finalize the transaction

For Fraud Detect transactions only:

fraudScore Score returned based on Fraud Detect check

When your store is enabled for SEPA Direct Debit as part of the Local Payments offering:

mandateReference Mandate reference as returned for the first direct debit transaction

mandateDate Date of the initial direct debit transaction as returned for the first transaction

For merchants using the Fiserv Global Merchant Acquiring model only:

associationResponseCode The raw association value tells exactly how the issuer has responded to the
transaction without any mapping done either by the authorization platform or the
gateway. It will be returned only for Visa, Mastercard, Amex, and Discover

For merchants activated for the Mastercard real-time account updater service:

When your store is enabled for the Mastercard real-time account updater service on the gateway and you
have the payment information vaulted on your side then when applicable the updates are sent as part of the
gateway response and you have to react upon it accordingly That is: update the account number for a token
when you store PAN and a token on your side.

updatedPAN Updated primary account number

updatedExpirationDate Updated expiration date

updatedAccountStatusType Updated account status with possible values:

Account Status Meaning/Action

ACCOUNT_CHANGED Either the account number or account number
along with the expiration date are being
updated.
Use the new account information going
forward. The new account information should
also be used in case of authorization reversals.
ACCOUNT_CLOSED Closed account advice.
This account has been closed. Try alternate
method of payment on subsequent
authorization or retries.
EXPIRY_CHANGED Expiration date change.
Use the new expiry information going forward.
This should also be used in case of
authorization reversals.
CONTACT_CARDHOLDER Contact cardholder advice.
Account updater cannot provide updates on

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
this account owing to restrictions from
cardholder. Use an alternate method of
payment or contact customer to get one.

accountUpdaterErrorCode Error codes that indicate the system/server communication errors.

For merchants operating on the Fiserv Nashville and activated for the Visa or Mastercard real-time account
updater service:
When you are processing on the Fiserv Nashville end-point and your store is enabled for the Visa real-time
account updater service or for the MasterCard real-time account updater service on the gateway then you
can expect the updates to be sent as part of the gateway response. When you have the payment
information vaulted on your side then you have to react upon it accordingly That is: update the account
number and the parameter ‘hosteddataid’ for a token when you store PAN and a token on your side.

updatedPAN Updated primary account number

updatedExpirationDate Updated expiration date

updatedAccountStatusType Updated account status with possible values:

Account Status Meaning/Action

ACCOUNT_CHANGED Either the account number or account number

along with the expiration date are being
updated.
Use the new account information going
forward. The new account information should
also be used in case of authorization reversals.
ACCOUNT_CLOSED Closed account advice.
This account has been closed. Try alternate
method of payment on subsequent
authorization or retries.
EXPIRY_CHANGED Expiration date change.
Use the new expiry information going forward.
This should also be used in case of
authorization reversals.
CONTACT_CARDHOLDER Contact cardholder advice.
Account updater cannot provide updates on
this account owing to restrictions from
cardholder. Use an alternate method of
payment or contact customer to get one.

hosteddataid Returned when the updates have been applied. New (TransArmor) token has to
be used in place of the old/previous one. Note that the old/previous token will not
be deleted but will be honored by the gateway till the old payment information
(account number) will be honored by the scheme (Visa).

accountUpdaterErrorCode Error codes that indicate the system/server communication errors.

Additionally when using your own error page for negative validity checks (full_bypass=true):

fail_reason_details Comma separated list of missing or invalid variables.

Note that ‘fail_reason_details’ will not be supported in case of payplus and fullpay
mode

invalid_cardholder_data true – if validation of card holder data was negative

false – if validation of card holder data was positive but transaction has been
declined due to other reasons

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
In addition, your custom fields and billing/shipping fields will also be sent back to the specific URL.
Please consider when integrating that new response parameters may be added from time to time in
relation to product enhancements or new functionality.

The parameter ‘response_hash’ allows you to recheck if the received transaction response has really been
sent by Fiserv and can therefore protect you from fraudulent manipulations.

The value is created with a HMAC Hash using the following parameter string:

approval_code|chargetotal|currency|txndatetime|storename

Shared secret (‘sharedsecret’) will be used as a key in HMAC to calculating the hash with the above hash
string.
The hash algorithm is the same as the one that you have set in the transaction request.
Please note that you have to implement the response hash validation, when doing so remember to store the
‘txndatetime’ that you have submitted with the transaction request in order to be able to validate the
response hash. Furthermore, you must always use the https-connection (instead of http) to prevent
eavesdropping of transaction details.

15.2 Server-to-Server Notification

In addition to the response you receive in hidden fields to your ‘responseSuccessURL’ or ‘responseFailURL’,
the payment gateway can send server-to-server notifications with the above result parameters to a defined
URL. This is especially useful to keep your systems in synch with the status of a transaction. To use this
notification method, you can specify an URL in the Customisation section of the Virtual Terminal or submit
the URL in the following additional transaction parameter ‘transactionNotificationURL’.
Please note that:
 The Transaction URL is sent as received therefore please don’t add additional escaping (for example,
using %2f for a Slash (/)
 No SSL handshake, verification of SSL certificates will be done in this process
 The Notification URL needs to listen either on port 80 (http) or port 443 (https) – other ports are not
supported
The response hash parameter for validation (using the same algorithm that you have set in the transaction
request) ‘notification_hash’ is calculated as follows:

chargetotal|currency|txndatetime|storename|approval_code

Shared secret (‘sharedsecret’) will be used as a key in HMAC to calculating the hash with the above hash
string.
Such notifications can also be set up for Recurring Payments that get automatically triggered by the
gateway. Please contact your local support team to get a Shared Secret agreed for these notifications. You
can configure your Recurring Transaction Notification URL in the Virtual Terminal (Customisation/ Store
URL Settings).
In case of the recurring transactions the hash parameter is calculated as follows:

chargetotal|currency|txndatetime|storename|approval_code

Shared secret (‘rcpSharedSecret’) will be used as a key in HMAC to calculating the hash with the above
hash string.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Appendix I – How to Generate a Hash
Transaction request values used for the hash calculation:
 chargetotal= 13.00
 currency= 978
 paymentMethod=M
 responseFailURL=https://localhost:8643/webshop/response_failure.jsp
 responseSuccessURL=https://localhost:8643/webshop/response_success.jsp
 sharedsecret=sharedsecret
 storename=10123456789
 timezone= Europe/Berlin
 transactionNotificationURL=https://localhost:8643/webshop/transactionNotification
 txndatetime=2020:04:17-17:32:41
 txntype=sale
Step 1. Extended hash needs to be calculated using all request parameters in ascending order of the
parameter names. Join the parameters’ values to one string with pipe separator (use only parameters’
values and not the parameters’ names).
stringToExtendedHash =
13.00|978|M|https://localhost:8643/webshop/response_failure.jsp|https://localhost:8643/webshop/response_
success.jsp|10123456789|Europe/Berlin|https://localhost:8643/webshop/transactionNotification|2020:04:17-
17:32:41|sale
Corresponding hash string does not include ‘sharedsecret’, which has to be used as the secret key for the
HMAC instead.
Step 2. Pass the created string to the HMACSHA256 algorithm and using shared secret as a key for
calculating the hash value.

HmacSHA256(stringToExtendedHash, sharedsecret)

Step 3. Use the value returned by the HMACSHA256 algorithm and submit it to our payment gateway in the
given form.

8CVD62a88mwr/Nfc+t+CWB+XG0g5cqmSrN8JhFlQJVM=

<input type="hidden" name="hashExtended" value="

8CVD62a88mwr/Nfc+t+CWB+XG0g5cqmSrN8JhFlQJVM="/>

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Appendix II – ipg-util.asp

<script LANGUAGE=JScript RUNAT=Server src="script/cryptoJS/crypto-js.min.js"></script>
<script LANGUAGE=JScript RUNAT=Server src="script/cryptoJS/enc-base64.min.js"></script>
<script LANGUAGE=JScript RUNAT=Server>
var today = new Date();
var txndatetime = today.formatDate("Y:m:d-H:i:s");

/*
Function that calculates the hash of the following parameters:
- chargetotal
- currency
- paymentMethod
- responseFailURL
- responseSuccessURL
- sharedsecret
- storename
- timezone
- transactionNotificationURL
- txndatetime
- txntype
*/

function createExtendedHash(chargetotal, currency) {

var hashHMACSHA256 = CryptoJS.HmacSHA256(stringToExtendedHash, sharedSecret);

var extendedhash = CryptoJS.enc.Base64.stringify(hashHMACSHA256);

Response.Write(extendedhash);
}

function getDateTime() {
Response.Write(txndatetime);
}
</script>

<?php
// Timezeone needs to be set
date_default_timezone_set('Europe/Berlin');
$dateTime = date("Y:m:d-H:i:s");

function getDateTime() {
global $dateTime;
return $dateTime;
}

/*
Function that calculates the hash of the following parameters:
- Store Id
- Date/Time(see $dateTime above)
- chargetotal
- currency (numeric ISO value)
- shared secret
*/
function createExtendedHash($chargetotal, $currency) {
// Please change the store Id to your individual Store ID
$storeId = "10123456789";
// NOTE: Please DO NOT hardcode the secret in that script. For example read
it from a database.
$sharedSecret = "sharedsecret";
$separator = "|";

$stringToHash = $storeId . $separator . getDateTime() . $separator .

$chargetotal . $separator . $currency;

$hashSHA256 = CryptoJS.HmacSHA384(hashWithAllStrings, sharedSecret);

$hash = CryptoJS.enc.Base64.stringify($hashSHA256);

return $hash;
}
?>

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Appendix IV – Currency Code List
Multicurrency Processing will be available in Australia in July 2020. Please contact the support team to
express your interest.

Currency Name Currency Code Currency Number

Aruban Florin AWG 533

Australian Dollar AUD 036

Bahamian Dollar BSD 044

Bahrain Dinar BHD 048

Barbados Dollar BBD 052

Belarusian Ruble BYR 933

Belize Dollar BZD 084

Bolívar Soberano VES 928

Brazilian Real BRL 986

Burundi Franc BIF 108

Canadian Dollar CAD 124

Cayman Islands Dollar KYD 136

Chinese Renmibi CNY 156

Croatian Kuna HRK 191

Czech Koruna CZK 203

Danish Krone DKK 208

Dominican Peso DOP 214

East Caribbean Dollar XCD 951

Euro EUR 978

Guyanese Dollar GYD 328

Hong Kong Dollar HKD 344

Hungarian Forint HUF 348

Indian Rupee INR 356

Israeli New Shekel ILS 376

Jamaican Dollar JMD 388

Japanese Yen JPY 392

Kuwaiti Dinar KWD 414

Lithuanian Litas LTL 440

Malaysian Ringgit MYR 458

Mexican Peso MXN 484

Netherlands Antillean Guilder ANG 532

New Zealand Dollar NZD 554

Norwegian Krone NOK 578

Polish Zloty PLN 985

Pound Sterling GBP 826

Romanian New Leu RON 946

Russian Ruble RUB 643

Saudi Rihal SAR 682

Serbian Dinar RSD 941

Singapore Dollar SGD 702

South African Rand ZAR 710

South Korean Won KRW 410

Surinamese Dollar SRD 968

Swedish Krona SEK 752

Swiss Franc CHF 756

Taiwan Dollar TWD 901

Trinidad and Tobago Dollar TTD 780

Turkish Lira TRY 949

UAE Dirham AED 784

US Dollar USD 840

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Appendix V – Payment Method List
If you let your consumer select the payment method in your website or want to define the payment method
yourself, submit the parameter ‘paymentMethod’ in your transaction request. If you do not submit this
parameter, the gateway will display a hosted page to the consumer to choose from the payment methods
that are enabled for your store and supported for the combination of the consumer’s country and the
transaction currency.

Payment Method Value

Alipay* aliPay

Alipay (China Domestic) aliPay_domestic

American Express A

Argencard (local Argentinian brand) ARGENCARD

Asian local payment methods through Razer Merchant Services asian_apm

Automatica (local Argentinian brand) AUTOMATICA

Bancontact BCMC

BBPS (local Argentinian brand) BBPS

Boleto Bancário* boleto

Cabal CA

Cabal (local Argentinian brand) CABAL_ARGENTINA

Cetelem (local Argentinian brand) CETELEM

Clarin 365 (local Argentinian brand) CLARIN_365

Club la Nacion (local Argentinian brand) CLUB_LA_NACION

Consumax (local Argentinian brand) CONSUMAX

Coopeplus (local Argentinian brand) COOPEPLUS

Crediguia (local Argentinian brand) CREDIGUIA

Dina Card (local Serbian brand) DI

Diners C

Elebar (local Argentinian brand) ELEBAR

ELO (local Brazilian brand) EL

eps* eps

Equated Monthly Installments (EMI) emi

Falabella CMR (local Argentinian brand) FALABELLA_CMR

Favacard (local Argentinian brand) FAVACARD

Finnish Online Banking Transfer (Verkkopankki) finlandOnlineBanking

Giropay giropay

Google Pay on the web googlePay

Grupar (local Argentinian brand) GRUPAR

Hiper (local Brazilian brand) hiper

iDEAL ideal

Italcred (local Argentinian brand) ITALCRED

JCB J

Kadicard (local Argentinian brand) KADICARD

Korean Payment Service (Korea Domestic) kps

Local Wallets India indiawallet

Maestro MA

Maestro UK maestroUK

Mastercard M

MasterPass masterpass

Mira (local Argentinian brand) MIRA

MyBank* mybank

Naranja (local Argentinian brand) NARANJA

Nativa (local Argentinian brand) NATIVA

Netbanking (India) netbanking

Nevada (local Argentinian brand) NEVADA

PayLater by ICICI Bank payLater

PayPal paypal

Patagonia 365 (local Argentinian brand) PATAGONIA365

Paysafecard* paySafeCard

POLi* poli

Przelewy24 (P24)* przelewy24

Pyme Nacion (local Argentinian brand) PYME_NACION

Qida (local Argentinian brand) QIDA

RuPay RU

SafetyPay* safetypay

Santander (Online Banking)* santander

Santander Cash (Cash Payment)* santanderCash

SEPA Direct Debit debitDE

SEPA Direct Debit* direct_debit-apm

SOFORT Banking (SOFORT Überweisung) sofort

Sorocred SO

Tarjeta Shopping (local Argentinian brand) TARJETA_SHOPPING

Tarjeta Sol (local Argentinian brand) TARJETA_SOL

Trustly* trustly

TrustPay* trustPay

UnionPay CUP

UnionPay (China Domestic) CUP_domestic

Visa (Credit/Debit/Electron/Delta) V

WeChat Pay* wechat-apm

*Only supported in a collecting model through the Fiserv Local Payments offering.

Connect
PayPal Operation
Transaction Type (txntype)
SetExpressCheckoutPayment
Sale (sets PaymentAction to Authorization in SetExpressCheckout and
DoExpressCheckoutPayment requests)
Preauth GetExpressCheckoutDetails
sale – with additional parameters for
DoExpressCheckoutPayment*
installing a Recurring Payment
Postauth DoCapture (,DoReauthorization)
Void DoVoid

Address Handling
If you pass a complete set of address values within your request to Connect (name, address1, zip, city and
country within billing and/or shipping address), these values will be forwarded to PayPal, setting the PayPal
parameter ‘addressOverride’ to ‘1’.
Please note that it is an eligibility requirement for PayPal’s Seller Protection that the shipping address will be
submitted to PayPal.
If you submit no or incomplete address data within the Connect request, no address data will be forwarded
to PayPal and the PayPal parameter ‘addressOverride’ will not be set.
Regardless of that logic, the payment gateway will always store the shipTo address fields received from
PayPal in the GetDetails request in the ShippingAddress fields, possibly overwriting values passed in the
request to Connect (such overwriting depends on the above logic).
* If you want to use PayPal’s Reference Transactions feature for recurring payments, please contact PayPal
upfront to verify if your PayPal account meets their requirements for this feature.
Recurring Payment Transaction
You have to submit a SALE transaction request with the corresponding parameters to install the recurring
payments. The first transaction is always conducted immediately along with the request.
The subsequent transactions are executed by the Gateway’s scheduler, through the API Web Service, as
defined during the initial SALE transaction with the installation.

Refer to the following information when integrating MasterPass as a payment method.

MasterPass is a digital wallet solution provided by participating banks and supported by Mastercard. When
purchasing online, customers log in to their MasterPass account and select a stored card for the payment.
MasterPass allows users to store Mastercard, Maestro, VISA, American Express and Diners cards. Please
note that your customers will however only be able to select the card brands that your Store has been set up
for in general.
To learn more about MasterPass, please visit www.masterpass.com.
Checkout Process with MasterPass
The checkout process with MasterPass can be initiated with a “BUY WITH MasterPass” button that you
place on your website either as a specifically alternative checkout option or next to other payment methods
that you offer.
When consumers click this button, you construct a ‘sale’ or ‘preauth’ request with the parameter
‘paymentMethod’ set to ‘masterpass’.
This will take your customer to the MasterPass login screen, from there to the subsequent pages of the
digital wallet and finally back to your web shop (responseSuccessURL, responseFailURL or reviewURL).
Alternatively you can let your customers select the payment method on the gateway’s hosted payment
method selection page. If you prefer that option, simply do not submit the parameter ‘paymentMethod’.
Good to Know Prior the Integration
 The Billing Address for a MasterPass transaction is associated with the card stored inside the wallet
thus even if you should use the payment gateway’s ‘payplus’ or ‘fullpay’ mode, there will be no
additional entry form for the Billing Address when a customer uses MasterPass. The Billing Address
stored in the wallet will also automatically override any billing address data you may send within your
transaction request to the gateway. You will always receive the Billing Address from the wallet in the
transaction response - even in ‘payonly’ mode, which is different compared to other payment methods
 If you use the gateway’s ‘fullpay’ mode, the Shipping Address can be selected by the customer inside
the wallet (no additional page for that from the gateway). If you use the ‘payonly’ or ‘payplus’ mode, the
Shipping Address selection in the wallet gets omitted as a non-required step. Thus you can send the
Shipping Address with your request and your customers will not have to select/provide it again inside
the wallet (it reduces the number of steps in the transaction flow when purchasing for example,
software products available as downloads where no shipping address is really required)
 For the cases where the shipping address and thus Shipping Fee is not clear yet when your customer
enters the wallet process by clicking the ‘BUY WITH Masterpass’ button, you can send additional
parameters in your transaction request which allow you to present a final confirmation page with the
final amount to your customers when they return from the wallet. The parameter ‘reviewOrder’ needs to
be set to ‘true’ in order to indicate that the final transaction amount needs to be reviewed by your
customer before completion. In addition you will need to provide the URL for your confirmation page in
the parameter ‘reviewURL’. When your customer confirms the final amount on this page, you will need
to send a request to finalize the transaction to the ‘redirectURL’ that you received in your response from
the gateway. This final request needs to include: oid, ipgTransactionId, subtotal, shipping, vattax,
chargetotal, currency and hashExtended
Note that you can also set a static ‘reviewURL’ through the Virtual Terminal (in Customisation/Online
store integration/Define the URLs for the integration with your online store section)

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
 When your Store is activated for 3D Secure, these settings will also apply to your MasterPass
transactions. In the specific case of MasterPass, the authentication process will however be handled by
Mastercard inside the wallet (MasterPass Advanced Checkout), where supported programmes are
limited to Mastercard SecureCode and Verified by Visa (no American Express SafeKey). However, the
parameter ‘authenticateTransaction’ can also be used to dynamically steer the behaviour for
MasterPass for example, depending on the purchase amount. If you submit the parameter
‘authenticateTransaction’ and set it to ‘false’, the MasterPass transaction will be initiated using the
MasterPass Basic Checkout which doesn't include 3D Secure authentication
Note that merchants requesting liability shift for MasterPass transactions should use the
MasterPass Advanced Checkout/3D Secure and must enable 3D Secure service such that it is
invoked within the MasterPass wallet
 The Card Code (CVV2/CVC2/4DBC) is not required for MasterPass transactions unless otherwise
required in network rules. At the time when a customer adds a card to the wallet, the Card Code gets
entered and checked once. No further Card Code entry is required from your customers. Requesting a
CVC2/CVV/4DBC is allowed when required by network rules
 Address Verification Service (AVS) is handled for MasterPass transactions in the same way as for
any other card transaction, however as the billing address is associated with a card and stored inside
the wallet, the AVS result is based on the address stored inside the wallet and not the billing address
provided by your customer in your web shop
 MasterPass is not available for Betting/Casino Gambling merchants (MCC 7995)

Activate MasterPass for your Test Store

 Obtain the credentials for the sandbox consumer accounts listed in the online documentation provided
by Mastercard
 Make sure your payment gateway test Store ID has been enabled for MasterPass

<input type="hidden" name="customParam_deviceRiskId" value="*****"/>

These fields are handled in the same way as other optional request parameters. The gateway stores these
parameters and passes them on to Fraud Detect. These parameters have no impact on the transaction
processing flow.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Appendix X – Local Payments™
Refer to the following information when you have ordered this product option and your store is enabled for
the Local Payments offering.
The Local Payments solution offers a unique combination of global coverage, a single contracting and
integration experience, and a broad and expanding portfolio of local payment methods.
Local Payments, also often referred to as Alternative Payment Methods, are defined as payment
transactions where neither credit/debit cards or paper currencies are used as the form of payment. These
payment methods are primarily used in eCommerce and mCommerce transactions, although some solutions
are making a push for adoption at point of sale locations. In many markets, they are more commonly used
than credit/debit cards.
Local Payments differ from card/association processing in a number ways. They are generally designed to
meet local needs and used in one or a limited number of markets. Unlike traditional credit/debit card
processing, pricing across these payment methods is not uniform and retail pricing depend on local costs
and merchant industries (for example, high-risk vs. low-risk). Local Payments offerings and user
experiences also vary greatly, though most are quite different from debit/credit user experiences.
There are over 300 local payment methods in use across the globe. Most of these fall into various
categories: Online Banking, Direct Debits, Direct Carrier Billing, Cash on Delivery, Invoice/Installments,
eWallets /mWallets, Cash/Voucher Payments and Payouts.
Consumer demand and preference are driving the growth in new methods of payment across the globe. In
fact, local payment methods are growing more rapidly than major card schemes, and merchant demand for
non-card (credit/debit) methods of payment is on the rise. These new payment methods deliver many
benefits to both merchants and consumers.
Local Payments help you reach and securely process payments from a broader base of consumers in each
local market, reduce shopping cart abandonment/improve conversion and improve customer experiences.
They enable more consumers to easily and confidently shop online (That is provide easy access to secure
payment methods for those that are unbanked and/or without credit or debit cards), expand their ability to
access international merchants and enable them to ‘pay their way,’ all of which improve their shopping
experiences and overall satisfaction.
Initiating a Sale Transaction
A Sale transaction for most Local Payments requires a direct interaction with the consumer who needs to be
redirected to the payment method’s screens (for example, the login page of the consumer’s bank or a wallet
provider) and back to your website after all required steps are completed.
As we handle all the required redirections to the various stakeholders for you, all you need to do is to post a
form to a URL with the parameters and values required for the transaction.
URL for Test Transactions

https://test.ipg-online.com/connect/gateway/processing

You will get the production URL with your production account credentials.
When building a request, independently of the payment method, there are some mandatory fields that need
to be included in every request for a Sale transaction.
Example of a form with the minimum number of fields:

<form method="post" action="https://test.ipg-

online.com/connect/gateway/processing">
<input type="hidden" name="txntype" value="sale">
<input type="hidden" name="timezone" value="America/New_York"/>
<input type="hidden" name="txndatetime" value="<% getDateTime() %>"/>

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
<input type=”hidden” name=”hash_algorithm” value=”HMACSHA256”/>
<input type="hidden" name="hashExtended" value="<% call createExtendedHash (
"13.00","840" ) %>"/>
<input type="hidden" name="storename" value="541234567" />
<input type="text" name="chargetotal" value="13.00" />
<input type="hidden" name="currency" value="840"/>
<input type="submit" value="Submit">
</form>

Other generic fields to be considered:

Field Name Description, Possible Values and Format

checkoutoption Set the value for this parameter to ‘combinedpage’ for a payment process where the payment
method choice and the typical next step (for example, entry of card details or selection of bank)
in consolidated in a single page.

paymentMethod You can submit the parameter ‘paymentMethod’ in your transaction request relevant for a
selected local payment method, as defined in Appendix V.
If you do not submit this parameter, gateway will display a page to your consumer to choose
from the payment methods that are supported for the combination of the consumer’s country and
the transaction currency.

bname The consumer’s name, for example, Albert Einstein. This is required for all Local Payments
transactions.
If you do not submit this field, a hosted page will be displayed to the consumer to capture the
name.

bcountry The consumer’s country in Two Letter Country Code format, for example, U.S. for the
United States or DE for Germany. The country is required for many Local Payments methods so
we recommend to include it in every Sale transaction request.
If you do not submit this field and the payment method requires it, a hosted page will be
displayed with the country that we have identified based on IP address and the option to change
the country, if not appropriate.

Many of the payment methods are available for customers coming from a certain country. In the scenarios
where you use the hosted payment page for payment selection, the gateway can display to your consumers
a hosted page with only these payment methods that are set up for your store and supported for the
combination of the consumer’s country and the transaction currency. This validation is done either based on
the submitted billing country (‘bcountry’) or the customer’s IP address.
See below an example of a hosted payment page in the checkout option ‘combinedpage’, where the country
is pre-set to ‘Germany’ based on the customer’s IP address but still it can be changed through a dedicated
drop-down, where else the payment methods are limited based on the combination country/currency.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
When building a request for a specific payment method, a part from the mandatory fields required for Sale
transaction and some generic fields to be considered, you might also have to include some specific fields in
your transaction request.
The payment method specific fields to be considered:
(M)=Mandatory (O)=Optional

Field Name Relevant for Description, Possible Values and Format

nationalId Boleto Bancário (M) Consumer’s National ID (up to 30 characters)
Santander (M)
Santander Cash (M)
Trustly (O)

customerid Boleto Bancário (M) Unique reference to identify the consumer

Santander (M)
Santander Cash (M)
Trustly (M)

email Boleto Bancário (M) Consumer’s email address

Przelewy24 (P24) (M)
SEPA Direct Debit (M)
Santander (M)
Santander Cash (M)

bbirthday Boleto Bancário (O) Consumer’s birthdate, format: DD.MM.YYYY

Santander (O)
Santander Cash (O)

bic giropay (O) Consumer’s BIC – Business Identifier Code (eight or 11 digits)
SOFORT Banking (O)

iban SEPA Direct Debit (M) Consumer’s IBAN – International Bank Account Number (22 digits)

mandateDate SEPA Direct Debit (M)

mandateReference SEPA Direct Debit (M)

mandateType SEPA Direct Debit (M)

mandateUrl SEPA Direct Debit (M)

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
mobileMode Alipay (O) You can submit this parameter with the value ‘true’ to enable Alipay
for mobile web That is: the mobile enabled variant of Alipay.

phone Przelewy24 (P24) (O) Consumer’s phone number

language WeChat Pay (O) Locale identifier for the payment page

Initiating a Return Transaction

When Return is supported for a selected local payment, you can initiate a Return transaction with a
reference to the Transaction ID of the original Sale transaction to the API Web Service. Please see details in
the Integration Guide for the Web Service API, chapter Generic Transaction Type for Voids and Returns.
There is the limit for the amount of Return transaction to a maximum of 100 000 either EUR or USD, which
are the only currencies that are applicable for these limit for the moment. Returns using other currencies will
not be limited.
Options for SEPA Direct Debit
When you manage SEPA Direct Debit mandates on your side you can use these in combination with the
Local Payments offering by submitting the reference and date of the mandate as well as a link to the
mandate itself. This is especially useful in cases where you have a large number of mandates on file from
previously used solutions and want to continue to use these mandates.
Single Payment or Recurring Payment

Field Name M/O Description

email O Consumer’s email address

iban M Consumer’s IBAN – International Bank Account Number (22 digits)

mandateType O Sequence type of Direct Debit, defaults to ‘single’

Values:
single – Direct Debit is executed once
firstCollection – First Direct Debit in a series of recurring
recurringCollection – Follow-up Direct Debit in a series of recurring
finalCollection – Last Direct Debit in a series of recurring

mandateReference M To be populated with the mandate reference

mandateDate M To be populated with the initial mandate signature date

mandateUrl M To be populated with the valid URL of the SEPA mandate to enable the Risk and
Compliance department to access the details

When you do not want to manage the SEPA Direct Debit mandates on your side, you can instead use the
out-of-box solution offered by Fiserv. Upon receiving the valid transaction request, the gateway displays a
hosted page to your customer with the mandate text and assigned mandate reference. As part of the
gateway’s response, you receive the mandate reference and mandate date, which have to be used in case
of the subsequent payments under this mandate.
Single Payment or First Payment in Recurring Series

Field Name M/O Description

email M Consumer’s email address

iban M Consumer’s IBAN – International Bank Account Number (22 digits)

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
mandateType O Sequence type of Direct Debit, defaults to ‘single’
Values:
single – Direct Debit is executed once
firstCollection – First Direct Debit in a series of recurring

Follow-up Payments in Recurring Series

Field Name M/O Description

email M Consumer’s email address

iban M Consumer’s IBAN – International Bank Account Number (22 digits)

mandateType M Sequence type of Direct Debit

Values:
recurringCollection – Follow-up Direct Debit in a series of recurring
finalCollection – Last Direct Debit in a series of recurring

mandateReference M To be populated with the mandate reference from the response

mandateDate M To be populated with the initial mandate signature date from the response

The generic fields to be considered:

Field Name Description, Possible Values and Format

paymentMethod You can submit the parameter ‘paymentMethod’ in your transaction request for UnionPay as
defined in Appendix V. If you do not submit this parameter, gateway will display a page to your
consumer to choose from the payment methods activated for your store.

bname You can submit the consumer’s name (cardholder’s name) in your transaction request. In some
cases, when integration the checkout option ‘combinedpage’, the consumer’s name might be
required as a mandatory parameter. If you do not submit this field, gateway will display a page to
your consumer to capture the name.

phone You can submit the consumer’s phone number in your transaction request only as digits limited
to: 4–15 digits and without the phone country code extension, which is set to +86 by default. If
you do not submit this field, a hosted page will be displayed to the consumer to capture the
phone and allow him to change the phone country code extension, when applicable.

The phone is mandatory when going through security check since it is the phone number that is
checked against the card number unless you are happy to hold the responsibility of transactions
without the security check and your store is configured accordingly to skip this authentication
then your customer would be able to perform a credit card transaction, where no phone number
would be needed.

You can also consider integrating UnionPay SecurePlus through the gateway’s Web Service API. See the
further information in the Integration Guide for the Web Service API.

Field Name Relevant for Description, Possible Values and Format

item1 aliPay_domestic (M) Submit exactly one line item parameter with four (4) property
CUP_domestic (M) values in the following format:

id;description;quantity;item_total_price

Transaction request without a line item or with multiple line items

will be declined.

Example: 100018;The Hobbit;1;3.50

Position Property Description

Product code (编码Code) from
"Product category list"

Productcatelog_3.3.
xlsx
1 id
2 description Product name
3 quantity Quantity of product(s)
4 item_total_price Product price
customerid CUP_domestic (M) Unique reference to identify the consumer

custom_domesticBankId CUP_domestic (M) Submit a bank identifier for reporting purpose in relation to
promotions with local Chinese banks. Max length eight.

Example of a form with the minimum number of fields:

<form method="post" action=" https://test.ipg-online.com/connect/gateway/processing

">
<input type="hidden" name="full_bypass" value="true">
<input type="hidden" name="txntype" value="sale">
<input type="hidden" name="timezone" value="Asia/Hong_Kong"/>
<input type="hidden" name="txndatetime" value="<% getDateTime() %>"/>
<input type=”hidden” name=”hash_algorithm” value=”HMACSHA256”/>

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
<input type="hidden" name="hashExtended" value="<% call createExtendedHash(
"13.00","978" ) %>"/>
<input type="hidden" name="storename" value="4799500011057" />
<input type="hidden" name="paymentMethod" value="aliPay_domestic"/>
<input type="text" name="chargetotal" value="13.00" />
<input type="hidden" name="currency" value="156"/>
<input type="hidden" name="item1" value="100018;The Hobbit;1;3.50" />
<input type="submit" value="Submit">
</form>

Field Name M/O Description, Possible Values and Format

paymentMethod O Set the value for this parameter to ‘kps’

checkoutoption M Set the value for this parameter to ‘combinedpage’

oid M Unique order ID, alphanumeric string (32 max)

customParam_kps_ItemInfo M Type of purchased item, alphanumeric string (1 max)

Possible values are:
 ‘1’: Goods
 ‘2’: Online content

customParam_kps_CcProdDesc M Description of purchased items to be displayed on the KPS payment page,

alphanumeric string (256 max)

Full or partial Returns can be done through the Virtual Terminal interface.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
Appendix XV – Debit Disbursement
Refer to the following information only when you are operating in U.S. and your store is enabled to allow
credit transaction processing.
Debit Disbursement (Visa OCT, Mastercard MoneySend) allows businesses to disburse funds in real-time,
directly to a debit card. Faster payouts can increase loyalty and satisfaction, reduce costs for businesses.
The Debit Disbursement solution is cheaper, faster, more convenient and more traceable than traditional
payment methods. It facilitates payments and transfers such as:
 Fund disbursements by e-commerce marketplaces
 Government disbursements (such as VAT refunds)
 Forex and binary option trade payouts
 Affiliate and contractor payouts
 Expense reimbursements
 Corporate and manufacturing rebates
 Insurance claims
The functionality for disbursements can be used with Direct Post and hosted payment page integrations. It is
also available for REST API originated transactions.
The funding source may be a credit card, debit card, prepaid card or bank account, but the receiving
account must be a debit card. Note currently only Visa and Mastercard brand debit cards can be used as the
recipient for debit disbursements.
For person-to-person payments (P2P) and P2PBankInit – Person to Person Bank Initiated, the merchant
must perform the operation as two individual transactions, one for funding (Pull transaction to debit funds
from sender) and one for disbursement (Push transaction to receive funds by receiver).
Disbursement types supported:
 P2P – Person to Person
 P2PBankInit – Person to Person Bank Initiated
 MerchDisb – Merchant Disbursement
 FundsDisb – Funds Disbursement
 Pay Roll Pension Disbursement
 MerchInitMT – Money Transfer – Merch Initiate
Pull transactions for getting funds from the sender can be done using the transaction type ‘sale’, while Push
transactions for the disbursement to the receiver using the transaction type ‘credit’.
When building a request for Pull transaction a part from the mandatory fields required for Sale transaction,
you can also need to include some custom fields in your transaction request.
The payment method specific fields to be considered:
(M)=Mandatory (O)=Optional

Field Name M/O Description, Possible Values and Format

Sender Information

sdrName O Customer’s Name

sdrReference O Reference Number

sdrAddr O Address

sdrCity O City

sdrState O State

sdrCountry O Country

sdrZip O Zip

sdrPhone O Phone

sdrBirthDate O Birthdate

When building a request for Push transaction a part from the mandatory fields required for Credit
transaction, you will also need to include some fields in your transaction request. Note that the possibility to
send ‘credit’ using the Connect interface is restricted and needs to be enabled for your store.

Field Name M/O Description, Possible Values and Format

Billing Information

bname M Customer’s Name

Receiver Information

rAccountNumber O Account Number

rReferenceNumber O Reference Number

The transactions will be presented in the Virtual Terminal Reports as ‘sale’ for Pull transactions and as
‘return’ for Push transactions.

© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.
© 2020 Fiserv, Inc. or its affiliates. All rights reserved. Fiserv is a registered trademark of Fiserv, Inc. Other products
referenced in this material may be trademarks or registered trademarks of their respective companies.

Eposnet: A Fiserv Global Digital Commerce Platform
No ratings yet
Eposnet: A Fiserv Global Digital Commerce Platform
34 pages
Fiserv Gateway Overview
No ratings yet
Fiserv Gateway Overview
25 pages
Documentation Paymob
No ratings yet
Documentation Paymob
58 pages
PayZone PHP Payment Integration Guide
No ratings yet
PayZone PHP Payment Integration Guide
5 pages
IPG - Integration Guide - API - 2024-1
No ratings yet
IPG - Integration Guide - API - 2024-1
177 pages
Payment GatewayTesting
100% (1)
Payment GatewayTesting
8 pages
IPG IntegrationGuide API 2023-1
No ratings yet
IPG IntegrationGuide API 2023-1
162 pages
Akurateco Presentation - WLPG
No ratings yet
Akurateco Presentation - WLPG
20 pages
Ebook Picking An Online Payment Processors
No ratings yet
Ebook Picking An Online Payment Processors
18 pages
FD Globalgatewayconnect Usermanualnorthamerica
No ratings yet
FD Globalgatewayconnect Usermanualnorthamerica
86 pages
Emea Integrationguide Connect 2 0
No ratings yet
Emea Integrationguide Connect 2 0
18 pages
eCommercePaymentSolutions sg246177
No ratings yet
eCommercePaymentSolutions sg246177
352 pages
Pay Direct
No ratings yet
Pay Direct
27 pages
IPG UserGuide VirtualTerminal v2023-2
No ratings yet
IPG UserGuide VirtualTerminal v2023-2
47 pages
UMS Banking Gateway-Direct-Post-API
No ratings yet
UMS Banking Gateway-Direct-Post-API
46 pages
White Label Payment Solutions
No ratings yet
White Label Payment Solutions
16 pages
Perfect Money API
No ratings yet
Perfect Money API
22 pages
Best Payment Gateway Development Platform
No ratings yet
Best Payment Gateway Development Platform
13 pages
IPG IntegrationGuide API NBD
No ratings yet
IPG IntegrationGuide API NBD
103 pages
IS402.3-4 Payment Integration and Related Services
No ratings yet
IS402.3-4 Payment Integration and Related Services
29 pages
Youth Payment Trends in Mumbai
No ratings yet
Youth Payment Trends in Mumbai
51 pages
Electronic Payment Systems Guide
No ratings yet
Electronic Payment Systems Guide
29 pages
PHP Readme
No ratings yet
PHP Readme
3 pages
Payment Gateway
100% (2)
Payment Gateway
17 pages
Magento 2 Plugin Integration Guide
No ratings yet
Magento 2 Plugin Integration Guide
18 pages
Web Service API: Integration Guide
No ratings yet
Web Service API: Integration Guide
124 pages
ISG PAY - Integration Document - V1 2 Latest
No ratings yet
ISG PAY - Integration Document - V1 2 Latest
26 pages
PayGate OpenPayAPI Quick Install Guide
No ratings yet
PayGate OpenPayAPI Quick Install Guide
13 pages
Payment System: Product Description
No ratings yet
Payment System: Product Description
24 pages
Billdeskpgintegrationdoc v1
No ratings yet
Billdeskpgintegrationdoc v1
11 pages
WebPay Payment Gateway Business Plan
100% (2)
WebPay Payment Gateway Business Plan
125 pages
Payment Gateway Integration Guide
No ratings yet
Payment Gateway Integration Guide
69 pages
Perfectmoney-Sci-2 0 Edited
No ratings yet
Perfectmoney-Sci-2 0 Edited
21 pages
Paystation API: 3-Party Payment Guide
No ratings yet
Paystation API: 3-Party Payment Guide
8 pages
Digital Payment System
No ratings yet
Digital Payment System
5 pages
Easypay Checkout - Integration Guide 6.1
No ratings yet
Easypay Checkout - Integration Guide 6.1
20 pages
Lesson 9 - Payment Gateways
No ratings yet
Lesson 9 - Payment Gateways
28 pages
Fss Merchant Hub Brochure
No ratings yet
Fss Merchant Hub Brochure
16 pages
PayGate PayWebv2 v1.15
0% (1)
PayGate PayWebv2 v1.15
23 pages
Customer Service & E-Payment Guide
No ratings yet
Customer Service & E-Payment Guide
10 pages
PayWay Net Developers Guide
No ratings yet
PayWay Net Developers Guide
38 pages
E Payment
No ratings yet
E Payment
15 pages
Payment Gateway PP T
No ratings yet
Payment Gateway PP T
24 pages
E-commerce Payment Essentials
No ratings yet
E-commerce Payment Essentials
8 pages
Trak N Pay
No ratings yet
Trak N Pay
53 pages
E Wallet
No ratings yet
E Wallet
22 pages
Pay Eer Merchant en
No ratings yet
Pay Eer Merchant en
14 pages
Sage Pay SERVERProtocoland Integration Guidelines
No ratings yet
Sage Pay SERVERProtocoland Integration Guidelines
52 pages
How To Integrate A Payment Gateway Into A Website - JustCoded
No ratings yet
How To Integrate A Payment Gateway Into A Website - JustCoded
26 pages
Integrate Payments Direct Post API
No ratings yet
Integrate Payments Direct Post API
31 pages
PAYWARE CONNECT Manual
No ratings yet
PAYWARE CONNECT Manual
395 pages
Dragonpay PS API
No ratings yet
Dragonpay PS API
23 pages
Merchant Guide - Knowledge Base
No ratings yet
Merchant Guide - Knowledge Base
8 pages
PP WebsitePaymentsStandard IntegrationGuide
No ratings yet
PP WebsitePaymentsStandard IntegrationGuide
194 pages
Test Cases For Your E-Commerce Payment Gateway Page - LoginRadius Fuel
No ratings yet
Test Cases For Your E-Commerce Payment Gateway Page - LoginRadius Fuel
6 pages
PayflowGateway Guide
No ratings yet
PayflowGateway Guide
238 pages
Payflowgateway Guide
No ratings yet
Payflowgateway Guide
256 pages
Structures in Architecture, 1990-2006 Edition
100% (1)
Structures in Architecture, 1990-2006 Edition
300 pages
Ancient Egyptian Science A Source Book v3
67% (3)
Ancient Egyptian Science A Source Book v3
446 pages
7th Basic Plan English 20160303
No ratings yet
7th Basic Plan English 20160303
102 pages
Hannan Et Al 2024 Laparoscopic Versus Open Appendicectomy Performed by Adult General Surgeons in Pre Teenage Years
No ratings yet
Hannan Et Al 2024 Laparoscopic Versus Open Appendicectomy Performed by Adult General Surgeons in Pre Teenage Years
6 pages
AZ-900.prepaway - Premium.exam.186q: Number: AZ-900 Passing Score: 800 Time Limit: 120 Min File Version: 10.1
No ratings yet
AZ-900.prepaway - Premium.exam.186q: Number: AZ-900 Passing Score: 800 Time Limit: 120 Min File Version: 10.1
160 pages
D355c-3 Maintenance and Operation
No ratings yet
D355c-3 Maintenance and Operation
220 pages
SU-BFP-10071-9-V9B-MPGB-00021-Instrument List & Excel Spreadsheet (STARTUP)
100% (1)
SU-BFP-10071-9-V9B-MPGB-00021-Instrument List & Excel Spreadsheet (STARTUP)
3 pages
Designof Retaining Wall
100% (1)
Designof Retaining Wall
7 pages
Business Invoice for GST Credit
No ratings yet
Business Invoice for GST Credit
1 page
18 Special Purpose Audit Engagement
No ratings yet
18 Special Purpose Audit Engagement
2 pages
OSI PI Interface With IFIX PI - IntFix - 2.4.3.0
No ratings yet
OSI PI Interface With IFIX PI - IntFix - 2.4.3.0
128 pages
Gramática 7
No ratings yet
Gramática 7
1 page
Course Syllabus - Winter 2013: Instructor: Dr. Mohamed Ismail, Industrial Systems Engineering
No ratings yet
Course Syllabus - Winter 2013: Instructor: Dr. Mohamed Ismail, Industrial Systems Engineering
5 pages
Lesson Plan Year 4 English
No ratings yet
Lesson Plan Year 4 English
3 pages
Manual of Standards On QMS in The Clinical Laboratory - 2nded
No ratings yet
Manual of Standards On QMS in The Clinical Laboratory - 2nded
69 pages
JavaOBjEX User Guide
No ratings yet
JavaOBjEX User Guide
15 pages
Renewable Energy for Students
No ratings yet
Renewable Energy for Students
219 pages
Sipawards 2019 Results
No ratings yet
Sipawards 2019 Results
81 pages
WPS-Starting Point Rev1
50% (2)
WPS-Starting Point Rev1
170 pages
IC Vendor Scorecard Template
0% (1)
IC Vendor Scorecard Template
6 pages
Barbara Ward Origins of Sustainable Development
No ratings yet
Barbara Ward Origins of Sustainable Development
77 pages
Cs3501 Compiler Design Laboratory
No ratings yet
Cs3501 Compiler Design Laboratory
50 pages
Application For Cert of Compliance Squatting
100% (1)
Application For Cert of Compliance Squatting
13 pages
Lesson Plan Unit 6 Lesson 2 11-6-2023
No ratings yet
Lesson Plan Unit 6 Lesson 2 11-6-2023
3 pages
301 SS
No ratings yet
301 SS
5 pages
Physical Sciences Paper 1 Winter Classes 2018
No ratings yet
Physical Sciences Paper 1 Winter Classes 2018
50 pages
Drama Find Me Practice Paper 1
No ratings yet
Drama Find Me Practice Paper 1
5 pages
AI Problem Solving & Search Techniques
No ratings yet
AI Problem Solving & Search Techniques
66 pages
Whiteglove Service Procedure (UPDATE - 1.16.19)
No ratings yet
Whiteglove Service Procedure (UPDATE - 1.16.19)
1 page
Grade 6 Movie
No ratings yet
Grade 6 Movie
2 pages