a u t h e n t i c a t i o n
s o f t w a r e
Cardinal CentinelTM for Merchants
Thin Client Integration Guide
Green Dot MoneyPak
8.0
Acknowledgements
CardinalCommerce Corporation acknowledges with gratitude the contribution of its associates who
developed the Cardinal Payment Authentication Platform.
© 2006 by CardinalCommerce Corporation. All rights reserved.
Trademark Information
CardinalCommerce, Cardinal Centinel Authentication Software for Merchants, and Centinel are trademarks of CardinalCommerce Corporation.
Green Dot MoneyPak is a registered trademark of Green Dot Corporation.
Microsoft is a registered trademark of Microsoft Corporation. Microsoft Internet Explorer is a trademark of the Microsoft Corporation.
All other trademarks are the properties of their respective owners.
This manual may not, in whole or in part, be copied, photocopied, reproduced, translated, or converted
to any electronic or machine readable form without prior written consent of CardinalCommerce Corporation.
Contact Information
CardinalCommerce Corporation
6119 Heisley Rd.
Mentor, OH 44060
USA
www.cardinalcommerce.com
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
2
TABLE OF CONTENTS
1 Introduction........................................................................................................................... 4
2 Transaction Overview...........................................................................................................5
2.1 The Green Dot MoneyPak Transaction Using Centinel......................................................................... 5
3 Implementation Checklist.................................................................................................... 6
4 Thin Client............................................................................................................................. 7
4.1 Thin Client Architecture......................................................................................................................... 7
5 Thin Client Integration.........................................................................................................9
5.1 Lookup Message Integration.................................................................................................................. 9
5.1.1 cmpi_lookup.................................................................................................................................10
5.2 Authenticate Message Integration........................................................................................................ 14
5.2.1 cmpi_authenticate........................................................................................................................ 14
5.3 Authorization Message Integration.......................................................................................................16
5.3.1 cmpi_authorize.............................................................................................................................16
5.4 Capture Message Integration................................................................................................................ 17
5.4.1 cmpi_capture................................................................................................................................ 18
5.5 Sale Message Integration...................................................................................................................... 19
5.5.1 cmpi_sale..................................................................................................................................... 20
5.6 Refund Message Integration................................................................................................................. 21
5.6.1 cmpi_refund................................................................................................................................. 21
6 Integration Notes.................................................................................................................24
7 Integration Configuration.................................................................................................. 25
7.1 Configuring Centinel Test for Green Dot MoneyPak Transactions..................................................... 25
7.2 Configuring Production for Green Dot MoneyPak Transactions......................................................... 28
8 Integration Testing..............................................................................................................33
8.1 Integration Test Cases...........................................................................................................................33
9 Moving To Production........................................................................................................37
10 Integration Error Handling............................................................................................. 38
10.1 Common Centinel MAPS Errors........................................................................................................ 38
10.2 cmpi_lookup....................................................................................................................................... 38
10.3 cmpi_authenticate............................................................................................................................... 41
10.4 cmpi_authorize................................................................................................................................... 43
10.5 cmpi_capture.......................................................................................................................................45
10.6 cmpi_sale............................................................................................................................................ 46
10.7 cmpi_refund........................................................................................................................................ 47
11 Appendix A - ISO Codes.................................................................................................. 51
11.1 ISO 4217 Currency Codes.................................................................................................................. 51
11.2 ISO 3166 Country Codes....................................................................................................................57
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
3
1 Introduction
This guide is intended for Merchants that are implementing Green Dot MoneyPak acceptance and processing through the use of the Cardinal Centinel Thin Client. This guide outlines the integration and
testing procedures for completing the Thin Client implementation within an ecommerce system.
Thin Client Versions
The Cardinal Thin Client version number does not correspond to the Cardinal Centinel version number. The Thin Client version is specific to the respective Thin Client. The most recent version of all
Thin Clients are available for download from the software downloads section of the Centinel Merchant
Administration portal.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
4
2 Transaction Overview
2.1 The Green Dot MoneyPak Transaction Using Centinel
Green Dot MoneyPak is an easy to use online payment solution that gives the consumer the choice to
pay for web based purchases through the use of a Green Dot MoneyPak Number.
Green Dot MoneyPak Transaction Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
Consumer shops online at Merchant website. At checkout, the Consumer selects the Green
Dot MoneyPak payment type to complete the purchase.
Based on the payment information, the Merchant, via the Thin Client, passes a Lookup
message to Centinel identified as a Green Dot MoneyPak transaction request. Centinel will
store the transaction details and provide the URL of the Green Dot MoneyPak collection
page on the Lookup Response.
The Merchant interprets the Lookup response and redirects the Consumer with a HTTP
Form POST to the Green Dot MoneyPak collection URL. The redirect URL represents a
Centinel website that will present the Green Dot MoneyPak collection form to the Consumer.
Centinel constructs the collection form and prompts the Consumer to enter a MoneyPak
Number in order to complete the transaction.
Consumer submits a MoneyPak Number using the collection form and is redirected back to
the Merchant's website.
The Merchant receives the Consumer's redirect from the Centinel website.
The Merchant formats and sends an Authenticate request message to Centinel for processing. Centinel will return the status of the MoneyPak Number collection process to the
Merchant on the Authenticate response message.
Based on Authenticate response values, the Merchant updates their order management system. In the event that the Consumer has successfully entered a valid MoneyPak Number,
the payment status will be pending. If the Consumer cancelled while at the collection form,
the status will reflect the cancellation. In the case of a cancellation, the Consumer should be
prompted for another form of payment to complete the transaction.
In the event that the Authenticate response values indicates the Consumer entered a valid
MoneyPak Number successfully, the Merchant will send an Authorization/Sale request
message to Centinel platform for processing. In the event that the processing with Green
Dot completes successfully, funds will be transferred from the Consumer's MoneyPak.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
5
3 Implementation Checklist
A successful implementation is dependent on a few key components. The following checklist is intended to highlight these items to define a clear implementation task list covering installation, integration
and configuration. During the implementation process, please use this checklist to track progress and
address any remaining open items prior to deployment.
Implementation Checklist
1.
Perform Thin Client installation on test and production servers.
Refer to the installation guide for the specific Thin Client(s) used for detailed installation instructions.
2.
Register for Green Dot MoneyPak merchant account.
Contact your sales representative for additional information.
3.
Perform Green Dot MoneyPak API integration with your website.
Refer to the integration samples provided in the Thin Client download and section 5 of this
guide for detailed information on completing this task.
4.
Update your website with the required Green Dot MoneyPak messaging and branding details.
Refer to section 6 of this guide for detailed information on completing this task.
5.
Configure the Centinel Test platform with your Green Dot MoneyPak merchant information.
Refer to section 7.1 of this guide for detailed information on completing this task.
6.
Complete all integration test cases using the Centinel Test environment.
Refer to section 8 of this guide for detailed information on completing this task.
7.
Configure the Production Centinel platform with your Green Dot MoneyPak merchant information.
Refer to section 7.2 of this this guide for detailed information on completing this task.
8.
From your test environment, execute transactions using the Centinel production environment to
verify your profile configuration information.
9.
From your Merchant website, run Live Test Transactions using the Green Dot MoneyPak payment option to verify that all components are in place and working correctly.
Refer to section 8 of this guide for more information on completing this task.
10.
Ensure that all business and operation requirements have been met before releasing the Green
Dot MoneyPak payment option.
11.
Release the website changes to production enabling the Green Dot MoneyPak payment option
to your consumers.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
6
4 Thin Client
To assist merchants with the integration of our services with their ecommerce website, the Thin Client
technology is available to minimize any custom development required by the Merchant. The Thin Client integration enables merchants to quickly communicate with the CardinalCommerce Application
Service Provider (ASP) platform. This communication allows all the changing business rules and configuration information to be managed centrally within the ASP platform. As business rules or payment
initiative programs evolve, these modifications are made centrally and do not effect the Merchant's
ecommerce website directly. The hosted services minimize any ongoing maintenance, further allowing
Merchants to focus on their business objectives instead of maintaining software.
The following Centinel Thin Clients are currently available:
Cold Fusion
COM
Java
Microsoft .NET
Perl
PHP
Included with the Thin Client technology are integration samples. These samples can be used as templates for integration and provide code samples for processing the API messages with the hosted service. The code samples include comments, which highlight error handling and general usage examples.
Note: If one of the available Thin Clients does not meet your system requirements a direct XML integration
solution is available. A XML Integration Guide is available for Merchants who wish to explore this option.
4.1 Thin Client Architecture
The Thin Client has a common API for message handling. Each Thin Client exposes methods for request message creation, the sending and receiving of transaction data, and response message interpretation.
Note: Detailed API information is available for each Thin Client in the Thin Client installation guides.
Request Object
Method
Add
Description
Adds name / value pairs used to construct the XML Messages.
Usage :
void Add(String name, String value)
Parameters :
name - name of the parameter
value - value of the parameter
Returns :
void
SendHTTP
Sends the request message to the Centinel MAPS. MAPS returns a response
message. The response message is deserialized into name / value pairs and re-
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
7
turned from the method in the form of a Thin Client response object.
Usage :
ResponseObject SendHTTP(String transactionURL)
Parameters :
transactionURL - fully qualified transaction URL
Returns :
ResponseObject
Note: The various platform versions of the Thin Client may overload this
method and allow you to specify optional timeout parameters for the MAPS
message communication.
Response Object
Method
GetValue
Description
Returns the value for a named element returned on the response message.
Usage :
String GetValue(String name)
Parameters :
name - name of the parameter
Returns :
String value of the name parameter
GetUnparsedResponse
Returns the entire raw XML response message. Useful for debugging purposes.
Usage :
String GetUnparsedResponse()
Parameters :
none
Returns :
String value of the XML response
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
8
5 Thin Client Integration
The Thin Client provides a communication shell that accepts name / value pairs. The name / value
pairs are serialized to an XML message and communicated to the Centinel MAPS. The Centinel
MAPS communicates the response message to the Thin Client, which makes the message elements
available to the Merchant as name / value pairs.
Centinel supports six transaction messages for Green Dot MoneyPak payment processing and post
payment management.
Message Name
Description
cmpi_lookup
This message provides the order information to the Centinel platform to facilitate the processing of the Green Dot MoneyPak transaction.
cmpi_authenticate
This message returns the status of the MoneyPak Number collection process
to the Merchant.
cmpi_authorize
This message is used to settle a Green Dot MoneyPak payment transaction
and obtain payment for either the full or partial amount of the previous transaction.
This message is available for systems that do not support a sale transaction.
cmpi_capture
This message returns the same results as the previous authorization.
This message is available for systems that do not support a sale transaction.
cmpi_sale
This message is used to settle a Green Dot MoneyPak payment transaction
and obtain payment for either the full or partial amount of the previous transaction.
cmpi_refund
This message performs a refund on a previously settled transaction. Both full
and partial refunds are available.
Note: Note that all API elements are case sensitive.
Note: All Green Dot MoneyPak transactions must be processed in USD currency. Currently no other currency types are supported.
The core transaction integration involves implementation of three messages, the Lookup
(cmpi_lookup), Authenticate (cmpi_authenticate), and Sale (cmpi_sale) messages. Each message requires the Merchant to construct the message using the Thin Client and send the request message on to
the Centinel platform. Merchants must utilize the response values to control the flow of the consumer's
transaction.
Included with the Thin Clients are integration samples, documentation and logos needed to complete the Green Dot MoneyPak integration. Within the code samples are additional comments on
how to construct and process the required API messages.
5.1 Lookup Message Integration
The Lookup Message (cmpi_lookup) is responsible for initiating the Green Dot MoneyPak payment.
The integration point for the Lookup Message is immediately following the capture of the order information and the Green Dot MoneyPak option has been selected by the consumer as the method of
payment.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
9
The Lookup Message is constructed and sent to the Centinel platform for processing. The Lookup
Message requires transaction specific data elements to be formatted on the request message. Please
refer to the Message API section for the complete list of required message elements.
The response message is returned from the Centinel platform, and the merchant integration utilizes the
Thin Client to reference the response values. In the event that the Enrolled value is Y the ACSUrl element will contain a fully qualified URL that the consumer must be redirected to complete the Green
Dot MoneyPak collection form. The url will represent a Centinel website that will use the data passed
on the cmpi_lookup message to construct the MoneyPak Number collection form.
5.1.1 cmpi_lookup
First transaction of the Lookup/Authenticate pair that is used to process the Green Dot MoneyPak
transaction.
In the event that the consumer selects Green Dot MoneyPak as a method of payment, the transaction
will initiate the payment transaction.
Request Message
Field Name
Description
Field
Definition
Required
MsgType
cmpi_lookup
AN(50)
Y
Version
Application message version identifier. "1.7"
AN(3)
Y
ProcessorId
Merchant processor identification code. This value is
assigned to the Merchant.
AN(20)
Y
MerchantId
Merchant identification code. This value is assigned
to the Merchant.
AN(50)
Y
TransactionPwd
A password to secure and verify the transaction originated from merchant represented by the transaction
details. The password value is configured through the
merchant profile. Limit 50 characters
AN(50)
Y
TransactionType
Identifies the Transaction Type used for processing.
AN(2)
Y
N(20)
Y
N(3)
Y
AN(50)
Y
GD - Green Dot MoneyPak
Amount
Unformatted Total transaction amount without any
decimalization.
For example, $100.00 = 10000, $123.67 = 12367,
$.99 = 99
CurrencyCode
3 digit numeric, ISO 4217 currency code for the sale
amount.
Green Dot MoneyPak Supported Currency Codes
840 - U.S. Dollar
OrderNumber
Order Number or transaction identifier from the Merchant commerce website.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
10
OrderDescription
Brief description of items purchased.
AN(125)
N
EMail
Consumer's email address.
AN(255)
Y
BillingFirstName
Consumer's first name.
AN(50)
N
BillingLastName
Consumer's last name.
AN(50)
N
BillingAddress1
Consumer's billing address information.
AN(50)
N
BillingAddress2
Consumer's billing address information.
AN(50)
N
BillingCity
Consumer's city of their billing address.
AN(50)
N
BillingState
Consumer's state or province of their billing address.
For example: Ohio - OH, Texas - TX.
AN(50)
N
BillingPostalCode
Consumer's postal code of their billing address.
AN(10)
N
BillingCountryCode
Consumer's country code of their billing address.
Complete list of ISO 3166 country codes are available in the appendix of this guide. For example,
United States - US
A(3)
N
ShippingFirstName
Consumer's first name.
AN(50)
N
ShippingLastName
Consumer's last name.
AN(50)
N
ShippingAddress1
Consumer's shipping address information.
AN(50)
N
ShippingAddress2
Consumer's shipping address information.
AN(50)
N
ShippingCity
Consumer's city of their shipping address.
AN(50)
N
ShippingState
Consumer's state or province of their shipping address. For example: Ohio - OH, Texas - TX. Limit 50
characters.
AN(50)
N
ShippingPostalCode
Consumer's postal code of their shipping address.
AN(10)
N
ShippingCountryCode
Consumer's country code of their shipping address.
For example, United States - US
AN(3)
N
IPAddress
The IP Address of the consumer. Format
NNN.NNN.NNN.NNN
AN(20)
Y
Sample Message
<CardinalMPI>
<MsgType>cmpi_lookup</MsgType>
<Version>1.7</Version>
<ProcessorId>100</ProcessorId>
<MerchantId>123456</MerchantId>
<TransactionPwd>passw0rd</TransactionPwd>
<TransactionType>GD</TransactionType>
<OrderNumber>992397541265</OrderNumber>
<Amount>12399</Amount>
<CurrencyCode>840</CurrencyCode>
<OrderDescription>Order #182397541265</OrderDesc>
<EMail>[email protected]</EMail>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
11
<BillingFirstName>Joe</BillingFirstName>
<BillingLastName>User</BillingLastName>
<BillingAddress>2333 Main Street</BillingAddress>
<BillingCity>Mentor</BillingCity>
<BillingState>OH</BillingState>
<BillingPostalCode>44060</BillingPostalCode>
<BillingCountryCode>US</BillingCountryCode>
<BillingPhone>4402554444</BillingPhone>
<ShippingFirstName>Joe</ShippingFirstName>
<ShippingLastName>User</ShippingLastName>
<ShippingAddress>2333 Main Street</ShippingAddress>
<ShippingCity>Mentor</ShippingCity>
<ShippingState>OH</ShippingState>
<ShippingPostalCode>44060</ShippingPostalCode>
<ShippingCountryCode>US</ShippingCountryCode>
<ShippingPhone>4402554444</ShippingPhone>
<IPAddress>207.48.141.20</IPAddress>
</CardinalMPI>
Response Message
This message is generated as a response to the cmpi_lookup message.
Field Name
Description
Field
Definition
Required
ErrorNo
Application error number(s). A non-zero value represents the error encountered while attempting to process the message request.
AN(500)
Y
ErrorDesc
Application error description for the associated error
number(s).
AN(500)
Y
TransactionId
Centinel transaction identifier. This value identifies
the transaction within the Centinel system. To complete the transaction, the value is required to be
passed on the Authenticate message to link the Lookup and Authenticate message together.
AN(20)
Y
Enrolled
Status of availability.
AN(2)
Y
Y - Green Dot MoneyPak processing available
U - Green Dot MoneyPak processing is unavailable
ACSUrl
The fully qualified URL to redirect the consumer to
collect a MoneyPak Number in order to complete the
Green Dot MoneyPak transaction. Available if Enrolled = Y.
AN(2083)
N
Payload
The encoded payment request. Available if Enrolled = Y.
AN(7000)
N
Sample Message
<CardinalMPI>
<ErrorNo>0</ErrorNo>
<ErrorDesc></ErrorDesc>
<TransactionId>75f986t76f6fd5h68f5d</TransactionId>
<Payload>eNpVUk1TwjAQ/SsM402nSUuKwSC/3gSoH5PL</Payload>
<Enrolled>Y</Enrolled>
<ACSUrl>https://www.somewebsite.com/acs</ACSUrl>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
12
</CardinalMPI>
Processing the Response Message
Verify the payment can be processed by evaluating the Enrolled element on the cmpi_lookup response message. In the event that the Enrolled element contains a Y value, the Green Dot MoneyPak
payment is available and the consumer should be redirected to complete the transaction. The ACSUrl
element contains the URL that the consumer should be redirected to in order to initiate the next step of
the transaction.
HTTP POST
Redirect the consumer to the ACSUrl via a HTTP Form POST. Construct the following form populated with the values returned on the cmpi_lookup response message.
Note: The form field names are case sensitive.
<HTML>
<BODY onload="document.frmLaunch.submit();">
<FORM name="frmLaunch" method="POST" action="ACSUrl Value">
<input type=hidden name="PaReq" value="Payload Value">
<input type=hidden name="TermUrl" value="Fully Qualified URL">
<input type=hidden name="MD" value="Session Tracking Value">
</FORM>
</BODY>
</HTML>
Form Field Descriptions
Field Name
Description
Field
Definition
Required
ACSUrl
The fully qualified URL to redirect the consumer to
collect a MoneyPak Number in order to complete the
Green Dot MoneyPak transaction. Value should be
retrieved from the cmpi_lookup response message
and inserted into the form.
AN(2083)
Y
PaReq
The encoded authentication or payment request.
Value should be retrieved from the cmpi_lookup response message and inserted into the form.
AN(7000)
Y
TermUrl
The fully qualified URL of the Merchant webpage
configured to receive the consumer returning from
completing the Green Dot MoneyPak collection
form. This URL will represent the webpage that will
process the cmpi_authenticate message.
AN(2083)
Y
MD
Merchant session tracking identifier. The value will
be returned to the TermUrl when the consumer is returned after completing the Green Dot MoneyPak
collection form. The field is available if necessary. If
not needed, simply pass an empty value on the form.
AN(1024)
Y
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
13
5.2 Authenticate Message Integration
The Centinel platform will then redirect the consumer back to the TermUrl representing a web page on
the Merchant's website. At that point, the merchant will process the Authenticate message
(cmpi_authenticate) to retrieve the status from the MoneyPak Number collection process.
The Authenticate Message is responsible for processing the Green Dot MoneyPak payment and returning the payment status to the merchant. The message will return the status of the payment, enabling
the merchant to handle the order according to the outcome.
In the event that the ErrorNo element is 0 (zero) and the SignatureVerification element is Y, indicating all fraud checks were satisfied, then the PAResStatus value will define how the transaction
should be processed. Based on the transaction outcome the Merchant's order mangement system
should be updated and the appropriate message should be displayed to the consumer.
In the event that a non zero ErrorNo value is returned or the SignatureVerification element is N,
the consumer should be prompted for an alternate form of payment.
5.2.1 cmpi_authenticate
Second message of the Lookup/Authenticate pair used in processing the Green Dot MoneyPak transaction.
Centinel will determine the outcome from the collection of the MoneyPak Number from the consumer
and return the results on the response message. The PaRes value will be passed on the PAResPayload
field of the request message.
Request Message
Field Name
Description
Field
Definition
Required
MsgType
cmpi_authenticate
AN(50)
Y
Version
Application message version identifier. "1.7"
AN(3)
Y
ProcessorId
Merchant processor identification code. This value is
assigned to the Merchant.
AN(20)
Y
MerchantId
Merchant identification code. This value is assigned
to the Merchant.
AN(50)
Y
TransactionType
Identifies the Transaction Type used for processing.
AN(2)
Y
GD - Green Dot MoneyPak
TransactionPwd
A password to secure and verify the transaction originated from merchant represented by the transaction
details. The password value is configured through the
merchant profile.
AN(50)
Y
PAResPayload
PARes generated by the external system that processed the payment or authentication with the consumer.
AN(10000)
Y
Sample Message
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
14
<CardinalMPI>
<Version>1.7</Version>
<MsgType>cmpi_authenticate</MsgType>
<ProcessorId>100</ProcessorId>
<MerchantId>123456</MerchantId>
<TransactionType>W</TransactionType>
<TransactionPwd>Passw0rd</TransactionPwd>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
<PAResPayload>********* Payload Message *********</PAResPayload>
</CardinalMPI>
Response Message
This message is generated in response to the cmpi_authenticate request message.
Field Name
Description
Field
Definition
Required
ErrorDesc
Application error description for the associated error
number.
AN(500)
Y
ErrorNo
Application error number. A non-zero value represents the error encountered while attempting the process the message request.
AN(500)
Y
PAResStatus
Transaction status result identifier.
AN(2)
Y
AN(2)
Y
N(16)
Y
P - Pending Transaction
X - Canceled Transaction
E - Error Processing Transaction
SignatureVerification
Transaction Signature status identifier.
Y - Indicates that the signature of the PARes has been
validated successfully and the message contents can
be trusted.
N - Indicates that for a variety of reasons; tampering,
certificate expiration, etc. the PARes could not be
validated, and the result should not be trusted.
OrderId
Centinel generated order identifier that is used to
identify the Green Dot MoneyPak order within the
Centinel system.
Sample Message
<CardinalMPI>
<ErrorDesc></ErrorDesc>
<ErrorNo>0</ErrorNo>
<PAResStatus>Y</PAResStatus>
<SignatureVerification>P</SignatureVerification>
<OrderId>4563218654876248</OrderId>
</CardinalMPI>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
15
5.3 Authorization Message Integration
The Authorization message (cmpi_authorize) is available for order management systems that do not
support a sale transaction. The authorize message is responsible for processing the settlement of the
Green Dot MoneyPak transaction. Upon successful completion, funds are transferred from the Consumer's MoneyPak to the Merchant. More than one authorization transaction can be processed against
an original Green Dot MoneyPak transaction.
5.3.1 cmpi_authorize
The cmpi_authorize message is used to settle a previously created Green Dot MoneyPak transaction.
During processing of the authorize message, funds are transferred from the consumer's MoneyPak to
the merchant. This message is available for systems that do not support a sale transaction.
Either the TransactionId returned on the cmpi_lookup response must be passed in the TransactionId
field in the cmpi_authorize request, or the OrderId returned on the cmpi_authenticate response must be
passed in the OrderId field of the cmpi_authorize request in order for the transaction to process successfully.
Request Message
Field Name
Description
Field
Definition
Required
MsgType
cmpi_authorize
AN(50)
Y
Version
Application message version identifier. "1.7"
AN(3)
Y
ProcessorId
Merchant processor identification code. This value is
assigned to the Merchant.
AN(20)
Y
MerchantId
Merchant identification code. This value is assigned
to the Merchant.
AN(50)
Y
TransactionPwd
A password to secure and verify the transaction originated from merchant represented by the transaction
details. The password value is configured through the
merchant profile.
AN(50)
Y
TransactionType
Identifies the Transaction Type used for processing. [
AN(2)
Y
GD ]
GD Green Dot MoneyPak
OrderId
Centinel generated order identifier.
N(16)
N
TransactionId
Centinel generated transaction identifier.
AN(20)
N
Amount
Unformatted transaction amount without any decimalization.
N(20)
Y
N(3)
Y
For example, $100.00 = 10000, $123.67 = 12367,
$.99 = 99
CurrencyCode
3 digit numeric, ISO 4217 currency code for the sale
amount.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
16
Green Dot MoneyPak Supported Currency Codes
840 - U.S. Dollar
Description
Brief description of items purchased, limited to 125
characters.
AN(125)
N
Description
Field
Definition
Required
ErrorNo
Application error number. A non-zero value represents the error encountered while attempting the process the message request.
AN(500)
Y
ErrorDesc
Application error description for the associated error
number.
AN(500)
Y
StatusCode
Status Result of the transaction.
AN(2)
Y
AN(20)
Y
Sample Message
<CardinalMPI>
<MsgType>cmpi_authorize</MsgType>
<Version>1.7</Version>
<ProcessorId>100</ProcessorId>
<MerchantId>123456</MerchantId>
<TransactionPwd>Passw0rd</TransactionPwd>
<TransactionType>GD</TransactionType>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
<Amount>34920</Amount>
<CurrencyCode>840</CurrencyCode>
<Description>Goods Shipped to Consumer</Description>
</CardinalMPI>
Response Message
This message is generated in response to the cmpi_authorize message.
Field Name
Y Transaction successful
E Transaction resulted in Error
TransactionId
Centinel generated transaction identifier.
Sample Message
<CardinalMPI>
<ErrorNo>0</ErrorNo>
<ErrorDesc></ErrorDesc>
<StatusCode>Y</StatusCode>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
</CardinalMPI>
5.4 Capture Message Integration
The Capture message (cmpi_capture) is available for order management systems that do not support a
sale transaction. The Capture transaction will return the same results as the previously processed au-
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
17
thorization transaction.
5.4.1 cmpi_capture
The cmpi_capture message can be used to return the same results as the previous authorization that
was processed for those systems that do not support the use of a sale transaction. Since funds are transferred from the consumer's MoneyPak Number during the processsing of the cmpi_authorize message,
no funds are transferred during the cmpi_capture processing.
Either the TransactionId returned on the cmpi_lookup response must be passed in the TransactionId
field in the cmpi_capture request, or the OrderId returned on the cmpi_authenticate response must be
passed in the OrderId field of the cmpi_capture request in order for the transaction to process successfully.
Request Message
Field Name
Description
Field
Definition
Required
MsgType
cmpi_capture
AN(50)
Y
Version
Application message version identifier. "1.7"
AN(3)
Y
ProcessorId
Merchant processor identification code. This value is
assigned to the Merchant.
AN(20)
Y
MerchantId
Merchant identification code. This value is assigned
to the Merchant.
AN(50)
Y
TransactionPwd
A password to secure and verify the transaction originated from merchant represented by the transaction
details. The password value is configured through the
merchant profile.
AN(50)
Y
TransactionType
Identifies the Transaction Type used for processing. [
AN(2)
Y
GD ]
GD Green Dot MoneyPak
OrderId
Centinel generated order identifier.
N(16)
N
TransactionId
Centinel generated transaction identifier.
AN(20)
N
Amount
Unformatted transaction amount without any decimalization.
N(20)
Y
N(3)
Y
AN(125)
N
For example, $100.00 = 10000, $123.67 = 12367,
$.99 = 99
CurrencyCode
3 digit numeric, ISO 4217 currency code for the sale
amount.
Green Dot MoneyPak Supported Currency Codes
840 - U.S. Dollar
Description
Brief description of items purchased, limited to 125
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
18
characters.
Sample Message
<CardinalMPI>
<MsgType>cmpi_capture</MsgType>
<Version>1.7</Version>
<ProcessorId>100</ProcessorId>
<MerchantId>123456</MerchantId>
<TransactionPwd>Passw0rd</TransactionPwd>
<TransactionType>GD</TransactionType>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
<Amount>34920</Amount>
<CurrencyCode>840</CurrencyCode>
<Description>Goods Shipped to Consumer</Description>
</CardinalMPI>
Response Message
This message is generated in response to the cmpi_capture message.
Field Name
Description
Field
Definition
Required
ErrorNo
Application error number. A non-zero value represents the error encountered while attempting the process the message request.
AN(500)
Y
ErrorDesc
Application error description for the associated error
number.
AN(500)
Y
StatusCode
Status Result of the transaction.
AN(2)
Y
AN(20)
Y
Y Transaction successful
E Transaction resulted in Error
TransactionId
Centinel generated transaction identifier.
Sample Message
<CardinalMPI>
<ErrorNo>0</ErrorNo>
<ErrorDesc></ErrorDesc>
<StatusCode>Y</StatusCode>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
</CardinalMPI>
5.5 Sale Message Integration
The Sale message (cmpi_sale) is responsible for processing the settlement of the Green Dot MoneyPak
transaction. Upon successful completion, funds are transferred from the Consumer's MoneyPak to the
Merchant. More than one sale transaction can be processed against an original Green Dot MoneyPak
transaction.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
19
5.5.1 cmpi_sale
The cmpi_sale message is used to settle a previously created Green Dot MoneyPak transaction. During processing of the sale message, funds are transferred from the consumer's MoneyPak to the merchant.
Either the TransactionId returned on the cmpi_lookup response must be passed in the TransactionId
field in the cmpi_sale request, or the OrderId returned on the cmpi_authenticate response must be
passed in the OrderId field of the cmpi_sale request in order for the transaction to process successfully.
Request Message
Field Name
Description
Field
Definition
Required
MsgType
cmpi_sale
AN(50)
Y
Version
Application message version identifier. "1.7"
AN(3)
Y
ProcessorId
Merchant processor identification code. This value is
assigned to the Merchant.
AN(20)
Y
MerchantId
Merchant identification code. This value is assigned
to the Merchant.
AN(50)
Y
TransactionPwd
A password to secure and verify the transaction originated from merchant represented by the transaction
details. The password value is configured through the
merchant profile.
AN(50)
Y
TransactionType
Identifies the Transaction Type used for processing. [
AN(2)
Y
GD ]
GD Green Dot MoneyPak
OrderId
Centinel generated order identifier.
N(16)
N
TransactionId
Centinel generated transaction identifier.
AN(20)
N
Amount
Unformatted transaction amount without any decimalization.
N(20)
Y
N(3)
Y
AN(125)
N
For example, $100.00 = 10000, $123.67 = 12367,
$.99 = 99
CurrencyCode
3 digit numeric, ISO 4217 currency code for the sale
amount.
Green Dot MoneyPak Supported Currency Codes
840 - U.S. Dollar
Description
Brief description of items purchased, limited to 125
characters.
Sample Message
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
20
<CardinalMPI>
<MsgType>cmpi_sale</MsgType>
<Version>1.7</Version>
<ProcessorId>100</ProcessorId>
<MerchantId>123456</MerchantId>
<TransactionPwd>Passw0rd</TransactionPwd>
<TransactionType>GD</TransactionType>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
<Amount>34920</Amount>
<CurrencyCode>840</CurrencyCode>
<Description>Goods Shipped to Consumer</Description>
</CardinalMPI>
Response Message
This message is generated in response to the cmpi_sale message.
Field Name
Description
Field
Definition
Required
ErrorNo
Application error number. A non-zero value represents the error encountered while attempting the process the message request.
AN(500)
Y
ErrorDesc
Application error description for the associated error
number.
AN(500)
Y
StatusCode
Status Result of the transaction.
AN(2)
Y
AN(20)
Y
Y Transaction successful
E Transaction resulted in Error
TransactionId
Centinel generated transaction identifier.
Sample Message
<CardinalMPI>
<ErrorNo>0</ErrorNo>
<ErrorDesc></ErrorDesc>
<StatusCode>Y</StatusCode>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
</CardinalMPI>
5.6 Refund Message Integration
The Refund message (cmpi_refund) is responsible for crediting the consumer some portion of the original settlement amount. Multiple refunds can be processed against the original Green Dot MoneyPak
transaction.
5.6.1 cmpi_refund
The cmpi_refund message is used to refund a previously settled Green Dot MoneyPak transaction.
During processing of the refund message, funds are transferred from the merchant to the consumer's
MoneyPak.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
21
Either the TransactionId returned on the cmpi_lookup response must be passed in the TransactionId
field in the cmpi_refund request, or the OrderId returned on the cmpi_authenticate response must be
passed in the OrderId field of the cmpi_refund request in order for the transaction to process successfully.
Request Message
Field Name
Description
Field
Definition
Required
MsgType
cmpi_refund
AN(50)
Y
Version
Application message version identifier. "1.7"
AN(3)
Y
ProcessorId
Merchant processor identification code. This value is
assigned to the Merchant.
AN(20)
Y
MerchantId
Merchant identification code. This value is assigned
to the Merchant.
AN(50)
Y
TransactionPwd
A password to secure and verify the transaction originated from merchant represented by the transaction
details. The password value is configured through the
merchant profile.
AN(50)
Y
TransactionType
Identifies the Transaction Type used for processing. [
AN(2)
Y
GD ]
GD Green Dot MoneyPak
OrderId
Centinel generated order identifier.
N(16)
N
TransactionId
Centinel generated transaction identifier.
AN(20)
N
Amount
Unformatted transaction amount without any decimalization.
N(20)
Y
N(3)
Y
AN(125)
N
For example, $100.00 = 10000, $123.67 = 12367,
$.99 = 99
CurrencyCode
3 digit numeric, ISO 4217 currency code for the sale
amount.
Green Dot MoneyPak Supported Currency Codes
840 - U.S. Dollar
Description
Brief description of items purchased, limited to 125
characters.
Sample Message
<CardinalMPI>
<MsgType>cmpi_refund</MsgType>
<Version>1.7</Version>
<ProcessorId>100</ProcessorId>
<MerchantId>123456</MerchantId>
<TransactionPwd>Passw0rd</TransactionPwd>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
22
<TransactionType>GD</TransactionType>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
<Amount>34920</Amount>
<CurrencyCode>840</CurrencyCode>
<Description>Goods Shipped to Consumer</Description>
</CardinalMPI>
Response Message
This message is generated in response to the cmpi_refund message.
Field Name
Description
Field
Definition
Required
ErrorNo
Application error number. A non-zero value represents the error encountered while attempting the process the message request.
AN(500)
Y
ErrorDesc
Application error description for the associated error
number.
AN(500)
Y
StatusCode
Status Result of the transaction.
AN(2)
Y
AN(20)
Y
Y Transaction successful
E Transaction resulted in Error
TransactionId
Centinel generated transaction identifier.
Sample Message
<CardinalMPI>
<ErrorNo>0</ErrorNo>
<ErrorDesc></ErrorDesc>
<StatusCode>Y</StatusCode>
<TransactionId>7fDSaySnCmDGCjPglzqX</TransactionId>
</CardinalMPI>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
23
6 Integration Notes
In addition to the API integration to facilitate the Green Dot MoneyPak process, the Merchant must
also make some important enhancements to the website to support the Green Dot MoneyPak transaction.
Please refer to the Green Dot MoneyPak Integration materials for additional information.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
24
7 Integration Configuration
To support integration testing the Centinel Test system (https://centineltest.cardinalcommerce.com) is
available. This allows merchants to integrate and maintain test systems separate from their production
deployments.
To test the Centinel transaction processing specific configuration parameters must be defined within
the Centinel Test system.
7.1 Configuring Centinel Test for Green Dot MoneyPak Transactions
To support the Green Dot MoneyPak payment processing, specific parameters must be defined within
the Centinel Test Merchant profile. The following steps detail the configuration process and cover all
parameters that must be configured to support the integration.
The test environment has been pre-configured with Green Dot MoneyPak profile information
collected during the Centinel registration process.
Step 1 - Login to your Centinel Test Merchant account.
By default your username/password credential to login to the test system is your assigned MerchantId
value and the password "changeit." Go to the Centinel Test Website
(https://centineltest.cardinalcommerce.com) and login to your test Merchant account.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
25
Step 2 - Configure your test Merchant Profile for Green Dot MoneyPak.
The Centinel Test system requires specific configuration settings to enable the Green Dot MoneyPak
payment processing. Once you are logged into the Centinel Test website, Click through the following :
Manage Profile > Manage Payment Initiative Configuration > Create Payment Initiative Configuration
Select Green Dot MoneyPak from the dropdown box and click the enter button. Note that if your profile already has a Green Dot MoneyPak configuration defined, an error message will be returned. If
configuration updates must be made go to the Update Payment Inititive Configuration section.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
26
The Green Dot MoneyPak configuration requires the following information.
Configuration
Description
Green Dot MoneyPak Partner Id
Green Dot provided partner identifier.
Green Dot MoneyPak Settlement Group
Group name provided by Green Dot that is used during settlement.
Green Dot MoneyPak Payment
Type Code
Green Dot provided code that identifies the type of payment that is being
made.
Merchant Display Name
The name that will be displayed to the Consumer on the MoneyPak Number collection form.
Merchant Address1
Business address that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchant Address2
Business address that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchnat City
Business city that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchant State
Business state that will be displayed to the Consumer on the MoneyPak
Number collection form.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
27
Merchant Country
Business country that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchant Postal Code
Business postal code that will be displayed to the Consumer on the
MoneyPak Number collection form.
Merchant Phone
Contact phone number that will be displayed to the Consumer on the
MoneyPak Number collection form. Consumers should be able to use this
phone number to contact the merchant's customer service department.
Merchant Support Email Address
Merchant support email address that will be displayed to the Consumer on
the MoneyPak Number collection form. Consumers should be able to use
this email address to contact the merchant's customer service department.
7.2 Configuring Production for Green Dot MoneyPak Transactions
To support the Green Dot MoneyPak payment processing, specific parameters must be defined within
the Production Centinel Merchant profile. The following steps detail the configuration process and
cover all parameters that must be configured to support the integration.
Step 1 - Login to your Production Centinel Merchant account.
Your username and password for your production account are provided to you through the registration
Welcome Pack email. Please contact Cardinal Merchant support if you have any difficulties accessing
your account.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
28
Step 2 - Configure your Merchant Profile for Green Dot MoneyPak.
The Centinel platform requires specific configuration settings to enable the Green Dot MoneyPak payment processing. Once you are logged into the Production Centinel website, Click thru the following :
Manage Profile > Manage Payment Initiative Configuration > Create Payment Initiative Configuration
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
29
Select Green Dot MoneyPak from the dropdown box and click the enter button. Note that if your profile already has a Green Dot MoneyPak configuration defined, an error message will be returned. If
configuration updates must be made go to the Update Payment Inititive Configuration section.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
30
The Green Dot MoneyPak configuration requires the following information.
Configuration
Description
Green Dot MoneyPak Partner Id
Green Dot provided partner identifier.
Green Dot MoneyPak Settlement Group
Group name provided by Green Dot that is used during settlement.
Green Dot MoneyPak Payment
Type Code
Green Dot provided code that identifies the type of payment that is being
made.
Merchant Display Name
The name that will be displayed to the Consumer on the MoneyPak Number collection form.
Merchant Address1
Business address that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchant Address2
Business address that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchnat City
Business city that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchant State
Business state that will be displayed to the Consumer on the MoneyPak
Number collection form.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
31
Merchant Country
Business country that will be displayed to the Consumer on the MoneyPak
Number collection form.
Merchant Postal Code
Business postal code that will be displayed to the Consumer on the
MoneyPak Number collection form.
Merchant Phone
Contact phone number that will be displayed to the Consumer on the
MoneyPak Number collection form. Consumers should be able to use this
phone number to contact the merchant's customer service department.
Merchant Support Email Address
Merchant support email address that will be displayed to the Consumer on
the MoneyPak Number collection form. Consumers should be able to use
this email address to contact the merchant's customer service department.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
32
8 Integration Testing
Testing is critical to successful implementations. It is important that all the positive and negative response codes be tested and handled according to the recommended guidelines. Included in this guide is
a list of specific test cases that cover the testing of these scenarios. Each of these scenarios should be
verified using the Centinel Test system.
Note: Each of these scenarios can be processed through production Centinel and Green Dot MoneyPak systems, however, actual funds will be transferred and the respective transaction fees will apply.
8.1 Integration Test Cases
To assist your integration efforts, the Centinel Testing Facility is available to perform various predefined integration tests. Once you have completed integration with your site, testing can begin by
sending messages to the test platform using the defined test case parameters outlined within this section.
Note: Centinel Test Transaction URL : https://centineltest.cardinalcommerce.com/maps/txns.asp
Note: The Centinel Test system requires merchants to use their assigned ProcessorId and MerchantId values
for transaction processing.
Test cases cover the processing of the Green Dot MoneyPak, TransactionType = GD, transactions
within the Centinel platform. These integration test cases apply to the cmpi_lookup,
cmpi_authenticate, cmpi_authorize, cmpi_capture, cmpi_sale, and cmpi_refund message types.
The integration testing uses the First Name (BillingFirstName API field) of the consumer making the purchase to determine the test case to be executed. Each test case outlines the expected
BillingFirstName value and the corresponding test case outcome below.
Test Case
1
BillingFirstName =
Test1
Description
Consumer places order
with Green Dot
MoneyPak as method of
payment. The consumer
enters a valid MoneyPak
Number on the collection
form and the transaction
is created. The transaction is successfully
settled by the merchant.
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = Y
Payload= <value>
ACSUrl = <value>
TransactionId = <value>
Merchant Action
Display order confirmation status message to the
consumer. Ship the
goods to the consumer
when the cmpi_sale response results in a success.
cmpi_authenticate response
PAResStatus = P
SignatureVerification = Y
ErrorNo = 0
ErrorDesc = <blank>
OrderId = <value>
cmpi_sale response
StatusCode = Y
ErrorNo = 0
ErrorDesc = <blank>
TransactionId = <value>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
33
Test Case
2
BillingFirstName =
Test2
Description
Consumer places order
with Green Dot
MoneyPak as method of
payment. The consumer
enters multiple valid pins
on the collection form in
order to complete the
transaction. The transaction is successfully
settled by the merchant.
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = Y
Payload= <value>
ACSUrl = <value>
TransactionId = <value>
Merchant Action
Display order confirmation status message to the
consumer. Ship the
goods to the consumer
when the cmpi_sale response results in a success.
cmpi_authenticate response
PAResStatus = P
SignatureVerification = Y
ErrorNo = 0
ErrorDesc = <blank>
OrderId = <value>
cmpi_sale response
StatusCode = Y
ErrorNo = 0
ErrorDesc = <blank>
TransactionId = <value>
Test Case
3
Description
BillingFirstName =
Test3
Green Dot MoneyPak
payments are currently
unavailable.
Test Case
4
Description
BillingFirstName =
Test4
Test Case
5
BillingFirstName =
Test5
An error was encountered processing the
cmpi_lookup message.
Description
Consumer places order
with Green Dot
MoneyPak as method of
payment, however, the
authenticate message res-
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = U
Payload= <blank>
ACSUrl = <blank>
TransactionId = <value>
Messages
cmpi_lookup response
ErrorNo = <value>
ErrorDesc = <value>
Enrolled = U
Payload= <blank>
ACSUrl = <blank>
TransactionId = <value>
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = Y
Payload= <value>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
34
Merchant Action
Display message indicating that Green Dot
MoneyPak is currently
unavailable for payment
processing. Prompt the
consumer for another
form of payment to complete the purchase.
Merchant Action
Display message indicating that Green Dot
MoneyPak is currently
unavailable for payment
processing. Prompt the
consumer for another
form of payment to complete the purchase.
Merchant Action
Display a message to the
consumer indicating that
the payment was unable
to complete and prompt
for another form of pay-
ults in an error.
ACSUrl = <value>
TransactionId = <value>
ment to complete the
purchase.
cmpi_authenticate response
PAResStatus = E
SignatureVerification = Y
ErrorNo = <value>
ErrorDesc = <value>
Test Case
6
BillingFirstName =
Test6
Description
Consumer places order
with Green Dot
MoneyPak as method of
payment. The consumer
enters a valid MoneyPak
Number on the collection
form, however, an error
is encountered processing the cmpi_sale
message.
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = Y
Payload= <value>
ACSUrl = <value>
TransactionId = <value>
Merchant Action
Display a message to the
consumer indicating that
the payment was unable
to complete and prompt
for another form of payment to complete the
purchase.
cmpi_authenticate response
PAResStatus = P
SignatureVerification = Y
ErrorNo = 0
ErrorDesc = <blank>
OrderId = <value>
cmpi_sale response
StatusCode = E
ErrorNo = <value>
ErrorDesc = <value>
TransactionId = <value>
Test Case
7
BillingFirstName =
Test7
Description
Consumer places order
with Green Dot
MoneyPak as method of
payment. The consumer
enters a valid MoneyPak
Number on the collection
form and the authorize
results in a success to
transfer funds from the
MoneyPak Number,
however, the capture results in an error.
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = Y
Payload= <value>
ACSUrl = <value>
TransactionId = <value>
cmpi_authenticate response
PAResStatus = P
SignatureVerification = Y
ErrorNo = 0
ErrorDesc = <blank>
OrderId = <value>
Merchant Action
Display order confirmation status message to the
consumer. Ship the
goods to the consumer
because the authorize response resulted in a success and the funds have
been transferred from the
MoneyPak Number. Review the error codes
from the capture response and resubmit the
transaction if necessary.
cmpi_authorize response
StatusCode = Y
ErrorNo = 0
ErrorDesc = <blank>
TransactionId = <value>
cmpi_capture response
StatusCode = E
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
35
ErrorNo = <value>
ErrorDesc = <value>
TransactionId = <value>
Test Case
8
BillingFirstName =
Test8
Description
Consumer places order
with Green Dot
MoneyPak as method of
payment. The consumer
enters a valid MoneyPak
Number on the collection
form and the transaction
is created. The transaction is successfully
settled by the merchant,
however, and error occurs when the transaction
is attempted to be refunded.
Messages
cmpi_lookup response
ErrorNo = 0
ErrorDesc = <blank>
Enrolled = Y
Payload= <value>
ACSUrl = <value>
TransactionId = <value>
cmpi_authenticate response
PAResStatus = P
SignatureVerification = Y
ErrorNo = 0
ErrorDesc = <blank>
OrderId = <value>
cmpi_sale response
StatusCode = Y
ErrorNo = 0
ErrorDesc = <blank>
TransactionId = <value>
cmpi_refund response
StatusCode = E
ErrorNo = <value>
ErrorDesc = <value>
TransactionId = <value>
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
36
Merchant Action
Review the error codes
returned from the refund
response, and resubmit
the transaction if needed.
9 Moving To Production
Once the integration testing is complete and you are ready to go live with Green Dot MoneyPak payments, the same configurations defined within the Centinel Test system must be configured within the
production Centinel platform. In addition to the configuration information, it is important to use the
implementation checklist in section 3 to verify that all implementation tasks are complete.
The final step before releasing Green Dot MoneyPak as a payment option on your Merchant website is
to run a Live Transaction Test. To perform this test, make a purchase on the Merchant website using
the Green Dot MoneyPak payment option. Ensure that all steps necessary to carrying out a successful
Green Dot MoneyPak transaction are performed.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
37
10 Integration Error Handling
The following list of Centinel MAPS error codes, descriptions and explanations are provided to assist
merchants with error code handling during integration. When an error is returned by the cmpi_lookup
or cmpi_authenticate messages, the simplest approach is to retry the authentication process. If an error
is received on the cmpi_authenticate, the cmpi_authenticate should not be resubmitted. The entire authentication must be retried starting with a new cmpi_lookup message being sent. For those merchants
integrating with a more enhanced error handling model, all error codes are provided with a suggested
merchant action. It is possible for multiple error codes to be returned. These will be in a comma-separated form, and merchant decisions only need to be based on the first error code in the list.
10.1 Common Centinel MAPS Errors
Error Code
Error Description
Explanation
Merchant Action
2001
Unsupported Message Type
The MsgType element value
within the message does not
meet the API requirements.
Complete transaction
without authentication, contact technical support.
2003
Internal Error: Unable to
handle message type at this
time
The message could not be
handled properly by the
Centinel MAPS server. This
error only occurs when the
Centinel MAPS Server has
not been configured properly.
Complete transaction
without authentication, contact technical support
2006
Unsupported Message Version
The Version element value
within the message does not
meet the API requirements.
The value specified in Version is either not recognized
or not supported.
Complete transaction
without authentication,
check message values.
2007
Message Group Disabled
Transaction messages have
been disabled. If they should
be enabled, contact technical
support.
Complete transaction
without authentication, contact technical support.
2009
Invalid Request Format: Invalid XML
Transaction message was not
valid XML.
Complete transaction
without authentication,
check message values.
2010
Invalid Request Format:
Empty Request
Transaction message was
empty.
Complete transaction
without authentication,
check message values.
10.2 cmpi_lookup
Error Code
Error Description
Explanation
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
38
Merchant Action
350
Unable to locate Merchant
Configuration Information
Within System
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Complete transaction
without authentication,
check message values. Confirm the values passed on the
message match the values
configured within your account profile.
789
Error Communicating with
PayPal
General processing error.
Verify information, retry
transaction. If problem continues contact technical support.
798
Merchant PayPal Configuration Not Found in System
System configuration error.
Contact technical support.
826
Error Retrieving Processor
In System
System configuration error.
Contact technical support.
870
Error Retrieving Credential
From System
System configuration error.
Contact technical support.
1001
Error Processing Message
Request
Common Error Code returned when a processing error was encountered during
the processing of a 3-D Secure message.
Retry transaction, a component within the 3-D Secure infrastructure responded incorrectly.
1002
Error Processing Lookup
Request Message
General error encountered.
Complete transaction
without authentication.
1010
Error Processing VEReq
Common Error Code returned when a processing error was encountered. A detailed error code is also returned with this error code.
Retry transaction, a component within the 3-D Secure infrastructure responded incorrectly.
1036
Unsupported Cardholder Enrolled Value
Value within the VERes
message does not meet the
format requirements defined
by 3-D Secure protocol.
Retry transaction, a component within the 3-D Secure infrastructure responded incorrectly.
1070
Error processing VERes
Value within the VERes
message does not meet the
format requirements defined
by 3-D Secure protocol.
Retry transaction, a component within the 3-D Secure infrastructure responded incorrectly.
1085
Error processing PAReq,
Display Amount Could Not
Be Determined
The amount could not be determined based on the raw
amount formatting or the
purchase amount.
Complete transaction
without authentication,
check message values.
1090
Unsupported PAReq Version requested by ACS
Value within the VERes
message does not meet the
format requirements defined
by 3-D Secure protocol.
Retry transaction, a component within the 3-D Secure infrastructure responded incorrectly.
1120
Error Persisting Authentication Information
Unforeseen error occurred
while persisting Authentica-
Complete transaction
without authentication, con-
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
39
tion Information.
tact technical support.
1125
Error Persisting Transaction_Lookup Information,
possibly duplicate Order
Number
Unforeseen error occurred
while persisting transaction
information. Commonly encountered when multiple
messages were sent using
the same order number.
Retry transaction, restart
payer authentication.
1130
Error Persisting VERes Information
General transaction error encountered.
Complete transaction
without authentication.
1150
Error Persisting PAReq Information
General transaction error encountered.
Complete transaction
without authentication.
1160
Error Persisting VEReq Information
General transaction error encountered.
Complete transaction
without authentication.
1360
Payment Initiative Not Supported
General transaction error encountered.
Complete transaction
without authentication.
1380
Payment Initiative Not Supported Under Specified Message Version
General transaction error encountered.
Complete transaction
without authentication.
1390
Card Type and Message
Type Mismatch
General transaction error encountered.
Complete transaction
without authentication.
1400
Message Version Not Supported
General transaction error encountered.
Complete transaction
without authentication.
1710
SECURE-eBill Configuration Not Available, Please
Contact Support
General transaction error encountered.
Complete transaction
without authentication.
2107
Unable to Insert BML Application Data
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
2112
Unable to Locate BML Application Configuration Data
Configuration Issue
Contact technical support.
4000
Error Validating Processor
Id Value
Unable to validate the Processor Id value passed on the
request.
Complete transaction
without authentication.
4020
Error Validating Merchant
Id Value
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4240
Merchant unable to process
transactions, not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4243
Merchant unable to process
transactions, Payment Initiative configuration not
found.
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
40
4245
Merchant unable to process
transactions, Payment Initiative not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4310
Error parsing VERes Message Elements
General transaction error encountered.
Complete transaction
without authentication.
4375
Error Validating Recurring
Value
General transaction error encountered.
Complete transaction
without authentication.
4930
Error Processing PayPal Express Checkout
General transaction error encountered.
Complete transaction
without authentication.
4951
Error Processing PayPal
Transaction, Merchant Pull
not activated
General transaction error encountered.
Complete transaction
without authentication.
4955
System PayPal Configuration Not Available, Please
Contact Support
General transaction error encountered, unable to complete PayPal payment
Verify profile configuration,
and retry transactions.
4960
Error Persisting PayPal
Transaction Information
General transaction error encountered.
Retry Transaction
5960
Error Persisting SECUREeBill Transaction Information
General transaction error encountered.
Retry Transaction
10.3 cmpi_authenticate
Error Code
Error Description
Explanation
Merchant Action
350
Unable to locate Merchant
Configuration Information
Within System
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Contact technical support.
1001
Error Processing Message
Request
General error encountered.
Complete transaction
without authentication.
1051
Error Processing PARes, Error Response Returned By
ACS
General Protocol error encountered.
Complete transaction
without authentication.
1055
Error Deserializing PARes
General transaction error encountered.
Complete transaction
without authentication.
1060
Missing or Invalid PARes
General transaction error en-
Complete transaction
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
41
countered.
without authentication.
1120
Error Persisting Authentication Information
General transaction error encountered.
Complete transaction
without authentication.
1140
Error Persisting PARes Information
General transaction error encountered.
Complete transaction
without authentication.
1355
Transaction Lookup Not
Successfull, Check Transaction Id
General transaction error encountered.
Complete transaction
without authentication.
1360
Payment Initiative Not Supported
General transaction error encountered.
Complete transaction
without authentication.
1390
Card Type and Message
Type Mismatch
General transaction error encountered.
Complete transaction
without authentication.
1752
Error Processing SECUREeBill Complete Transaction
General transaction error encountered.
Complete transaction
without authentication.
1755
Unable to complete SECURE-eBill Transaction
General transaction error encountered.
Complete transaction
without authentication.
1789
Error Communicating with
SECURE-eBill
General transaction error encountered.
Complete transaction
without authentication.
4000
Error Validating Processor
Id Value
Unable to validate the Processor Id value passed on the
request.
Complete transaction
without authentication.
4020
Error Validating Merchant
Id Value
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4240
Merchant unable to process
transactions, not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4243
Merchant unable to process
transactions, Payment Initiative configuration not
found.
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4245
Merchant unable to process
transactions, Payment Initiative not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4268
Error Validating Message,
Transaction Id is Empty
General transaction error encountered.
Complete transaction
without authentication.
4400
Error Parsing PARes Message Elements
General transaction error encountered.
Complete transaction
without authentication.
4770
Error Validating AAV Control byte
General transaction error encountered.
Complete transaction
without authentication.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
42
4780
Error Validating AAV Sale
Amount
General transaction error encountered.
Complete transaction
without authentication.
4790
Error Validating AAV Sale
Amount Truncation Value
General transaction error encountered.
Complete transaction
without authentication.
4800
Error Validating AAV
Transaction Currency Code
General transaction error encountered.
Complete transaction
without authentication.
4810
Error Validating Merchant
Name Hash
General transaction error encountered.
Complete transaction
without authentication.
4820
Error Validating Merchant
Transaction Stamp
General transaction error encountered.
Complete transaction
without authentication.
4963
Error Locating Express
Checkout Data For Processing, Check TransactionId
General transaction error encountered.
Complete transaction
without authentication.
4965
Error Locating Transaction
Results, Check TransactionId
General transaction error encountered.
Complete transaction
without authentication.
10.4 cmpi_authorize
Error Code
Error Description
Explanation
Merchant Action
350
Unable to locate Merchant
Configuration Information
Within System
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Complete transaction
without authentication,
check message values. Confirm the values passed on the
message match the values
configured within your account profile.
826
Error Retrieving Processor
In System
System configuration error.
Contact technical support.
870
Error Retrieving Credential
From System
System configuration error.
Contact technical support.
1360
Payment Initiative Not Supported
System configuration error.
Contact technical support.
2100
Field Mismatch Between the
Application Data Fields and
Data Values
General transaction error encountered, unable to complete transaction
Verify data being sent, and
retry transactions.
2101
Unable to Extract Application Data Fields and Data
Values
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
43
2102
Unable to Locate Application Data by TransactionId
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
2103
Unable to Insert BML Authorization Data
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
2108
Unable to Locate Merchant
Configuration By Promo
Code
Configuration Issue
Contact technical support.
2120
Error Processing Payment
Authorization
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
4000
Error Validating Processor
Id Value
Unable to validate the Processor Id value passed on the
request.
Complete transaction
without authentication.
4020
Error Validating Merchant
Id Value
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4240
Merchant unable to process
transactions, not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4243
Merchant unable to process
transactions, Payment Initiative configuration not found
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4245
Merchant unable to process
transactions, Payment Initiative not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4885
Error Locating the Merchant's Payment Processor
Configuration
Configuration Issue
Contact technical support.
4930
Error Processing PayPal Express Checkout
General transaction error encountered.
Complete transaction
without authentication.
4931
Error Processing PayPal Express Checkout Payment
General transaction error encountered.
Complete transaction
without authentication.
4938
Error Processing PayPal Direct Payment Transaction
General transaction error encountered.
Complete transaction
without authentication.
4939
Error Processing PayPal
Transaction
General transaction error encountered.
Complete transaction
without authentication.
4955
System PayPal Configuration Not Available, Please
Contact Support
General transaction error encountered, unable to complete PayPal payment
Verify profile configuration,
and retry transactions.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
44
10.5 cmpi_capture
Error Code
Error Description
Explanation
Merchant Action
350
Unable to locate Merchant
Configuration Information
Within System
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Complete transaction
without authentication,
check message values. Confirm the values passed on the
message match the values
configured within your account profile.
826
Error Retrieving Processor
In System
System configuration error.
Contact technical support.
870
Error Retrieving Credential
From System
System configuration error.
Contact technical support.
1360
Payment Initiative Not Supported
System configuration error.
Contact technical support.
2104
Unable to Insert BML Capture Data
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
2110
Unable to Locate Merchant's
BML Configuration Data
Configuration Issue
Contact technical support
2111
Unable to Locate Original
Transaction Data By TransactionId
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
2130
Error Processing Payment
Capture, Authorization Not
Eligible For Capture
The transaction that is attempting to be captured is
not eligible
Verify that the original
transaction is able to be captured and retry transaction.
2131
Error Processing Payment
Capture, Referenced Transaction is Not An Authorization Type
The transaction that is attempting to be capture is not
an authorization
Verify that the original
transaction is of the type authorization and retry transaction.
4000
Error Validating Processor
Id Value
Unable to validate the Processor Id value passed on the
request.
Complete transaction
without authentication.
4020
Error Validating Merchant
Id Value
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4240
Merchant unable to process
transactions, not active
Configuration Issue
Complete transaction
without authentication,
check merchant configura-
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
45
tion.
4243
Merchant unable to process
transactions, Payment Initiative configuration not found
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4245
Merchant unable to process
transactions, Payment Initiative not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4851
Error Locating BML Configuration Data
Configuration Issue
Contact technical support.
4938
Error Processing PayPal Direct Payment Transaction
General transaction error encountered.
Complete transaction
without authentication.
4939
Error Processing PayPal
Transaction
General transaction error encountered.
Complete transaction
without authentication.
4952
Error Locating the Merchant's PayPal Configuration
System configuration error.
Contact technical support.
4955
System PayPal Configuration Not Available, Please
Contact Support
General transaction error encountered, unable to complete PayPal payment
Verify profile configuration,
and retry transactions.
4964
Error Locating Authorization Data for Capture, Check
TransactionId
Value was formatted incorrectly.
Verify the information and
retry transcation.
Explanation
Merchant Action
10.6 cmpi_sale
Error Code
Error Description
350
Unable to locate Merchant
Configuration Information
Within System
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Contact technical support.
826
Error Retrieving Processor
In System
System configuration error.
Contact technical support.
870
Error Retrieving Credential
From System
System configuration error.
Contact technical support.
1360
Payment Initiative Not Supported
System configuration error.
Contact technical support.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
46
4000
Error Validating Processor
Id Value
Unable to validate the Processor Id value passed on the
request.
Complete transaction
without authentication.
4020
Error Validating Merchant
Id Value
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4240
Merchant unable to process
transactions, not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4243
Merchant unable to process
transactions, Payment Initiative configuration not found
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4245
Merchant unable to process
transactions, Payment Initiative not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4930
Error Processing PayPal Express Checkout
General transaction error encountered.
Complete transaction
without authentication.
4931
Error Processing PayPal Express Checkout Payment
General transaction error encountered.
Complete transaction
without authentication.
4938
Error Processing PayPal Direct Payment Transaction
General transaction error encountered.
Complete transaction
without authentication.
4939
Error Processing PayPal
Transaction
General transaction error encountered.
Complete transaction
without authentication.
4955
System PayPal Configuration Not Available, Please
Contact Support
General transaction error encountered, unable to complete PayPal payment
Verify profile configuration,
and retry transactions.
10.7 cmpi_refund
Error Code
Error Description
350
Unable to locate Merchant
Configuration Information
Within System
Explanation
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Merchant Action
Contact technical support.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
47
826
Error Retrieving Processor
In System
System configuration error.
Contact technical support.
870
Error Retrieving Credential
From System
System configuration error.
Contact technical support.
1360
Payment Initiative Not Supported
System configuration error.
Contact technical support.
2002
Invalid Merchant Id or Processor Id
The Merchant Id, Processor
Id data pair could not be located within the system.
Commonly the merchant account is not configured within the system or invalid Merchant Id or Processor Id data
elements were sent on the request message.
Verify the information within your merchant profile.
2020
Invalid Transaction Password
The transaction password
provided on the request message was incorrect.
Verify the transaction password within your merchant
profile.
2021
Merchant Profile is not configured with a Transaction
Password
The transaction password
provided on the request message was incorrect.
Verify the transaction password within your merchant
profile.
2105
Unable to Insert BML Refund Data
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
2110
Unable to Locate Merchant's
BML Configuration Data
Configuration Issue
Contact technical support.
2111
Unable to Locate Original
Transaction Data By TransactionId
General transaction error encountered, unable to complete transaction
Verify the original transaction id, and retry transactions.
2132
Error Processing Payment
Refund, Capture Not Eligible For Refund
The transaction that is attempting to be refunded is
not eligible
Verify that the original
transaction is eligible to be
refunded, and retry transaction.
2133
Error Processing Payment
Refund, Referenced Transaction is Not A Capture
Type
The transaction that is attempting to be refunded is
not of a type capture
Verify that the original
transaction is of a type capture, and retry transaction.
4000
Error Validating Processor
Id Value
Unable to validate the Processor Id value passed on the
request.
Complete transaction
without authentication.
4020
Error Validating Merchant
Id Value
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4240
Merchant unable to process
transactions, not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
48
4243
Merchant unable to process
transactions, Payment Initiative configuration not found
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4245
Merchant unable to process
transactions, Payment Initiative not active
Configuration Issue
Complete transaction
without authentication,
check merchant configuration.
4490
Error Validating ISO Currency Code
Value was formatted incorrectly.
Verify the information and
retry transcation.
4537
Error Validating TransactionId value
Value was formatted incorrectly.
Verify the information and
retry transcation.
4538
Error Validating Refund
Type value
Value was formatted incorrectly.
Verify the information and
retry transcation.
4539
Error Validating Refund
Amount value
Value was formatted incorrectly.
Verify the information and
retry transcation.
4851
Error Locating BML Configuration Data
Configuration Issue
Contact technical support.
4938
Error Processing PayPal Direct Payment Transaction
General transaction error encountered.
Complete transaction
without authentication.
4939
Error Processing PayPal
Transaction
General transaction error encountered.
Complete transaction
without authentication.
4941
Error Processing PayPal PreApproved Refund
General transaction error encountered.
Complete transaction
without authentication.
4955
System PayPal Configuration Not Available, Please
Contact Support
System configuration error.
Contact technical support.
4965
Error Locating Transaction
Results, Check TransactionId
System configuration error.
Contact technical support.
4975
Error Processing PayPal Refund Transaction
General error occured while
processing the refund transaction.
Retry transaction, if the
problem persists then contact
technical support.
4978
Unable to Refund Transaction, Status is not Completed
The transaction is not in a
refundable state.
Verify the information and
retry transcation.
4979
Unable to Refund Transaction, Refund Amount greater
than Transaction Amount
Refund Amount greater than
Transaction Amount.
Verify the information and
retry transaction.
4980
Error Processing API Transaction, Merchant Configuration Not Available
The merchant PayPal configuration is not defined.
Verify the information and
retry transcation.
5976
Unable to Refund Transaction, Invalid Reason Code
The reason code for the
transaction was invalid.
Verify the reason code and
retry transaction.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
49
5983
Unable to Locate SEB
Transaction for processing
TransactionId value that was
passed was formatted incorrectly.
Verify TransacitonId and
retry transaction.
5984
Unable to Refund Transaction based on Transaction
Status
The transaction status for the
current transaction is not of a
type that can be refunded.
Contact technical support.
5987
Unable to Refund Transaction based on Payment
Source
General transaction error encountered, unable to complete transaction
Verify profile configuration,
and retry transactions.
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
50
11 Appendix A - ISO Codes
Appendix lists all ISO standard codes used by the Centinel systems.
11.1 ISO 4217 Currency Codes
Alpha Code
Country
Currency Name
ADP
020
Andorran Peseta
AED
784
UAE Dirham
AFA
004
Afghani
ALL
008
Lek
AMD
051
Armenian Dram
ANG
532
Netherlands Antillian Guilder
AON
024
Kwanza
ARS
032
Argentine Peso
ATS
040
Austrian Schilling
AUD
036
Australian Dollar
AWG
533
Aruban Guilder
AZM
031
Azerbaijanian Manat
BAM
977
Convertible Marks
BBD
052
Barbados Dollar
BDT
050
Bangladesh Taka
BEF
056
Belgium Franc
BGL
100
Bulgarian Lev
BHD
048
Belgium Franc
BIF
108
Burundi Franc
BMD
060
Bermudian Dollar
BND
096
Brunei Dollar
BOB
068
Boliviano
BRL
986
Brazilian Real
BSD
986
Brazilian Real
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
51
BTN
064
Ngultrum
BWP
072
Botswana Pula
BYR
974
Belarussian Rouble
BZD
084
Belize Dollar
CAD
124
Canadian Dollar
CDF
976
Franc Congolais
CHF
756
Swiss Franc
CLP
152
Chilean Peso
CNY
156
Chinese Renminbi Yuan
COP
170
Colombian Peso
CRC
188
Costa Rican Colon
CUP
192
Cuban Peso
CVE
132
Cape Verde Escudo
CYP
196
Cyprus Pound
CZK
203
Czech Koruna
DEM
276
Deutsche Mark
DJF
262
Djibouti Franc
DKK
208
Danish Krone
DOP
214
Dominican Peso
DZD
012
Algerian Dinar
EEK
233
Kroon
EGP
818
Egyptian Pound
ERN
232
Nakfa
ETB
230
Ethiopian Birr
EUR
978
EURO
FIM
246
Finnish Markka
FJD
242
Fiji Dollar
FKP
238
Falkland Islands Pound
FRF
250
French Franc
GBP
826
Sterling
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
52
GEL
981
Lari
GHC
288
Ghana Cedi
GIP
292
Gibraltar Pound
GMD
270
Dalasi
GNF
324
Guinea Franc
GTQ
320
Quetzal
GWP
624
Guinea-Bissau Peso
GYD
328
Guyana Dollar
HKD
344
Hong Kong Dollar
HNL
340
Lempira
HRK
191
Croatian Kuna
HTG
332
Gourde
HUF
348
Hungary Forint
IDR
360
Rupiah
IEP
372
Irish Punt
ILS
376
New Israeli Sheqel
INR
356
Indian Ruppe
IQD
368
Iraqi Dinar
IRR
364
Iranian Rial
ISK
352
Iceland Krona
ITL
380
Italian Lira
JMD
388
Jamaican Dollar
JOD
400
Jordanian Dinar
JPY
392
Japanese Yen
KES
404
Kenyan Shilling
KGS
417
Som
KHR
116
Riel
KMF
174
Comoro Franc
KPW
408
North Korean Won
KRW
410
South Korean Won
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
53
KWD
414
Kuwaiti Dinar
KYD
136
Cayman Islands Dollar
KZT
398
Tenge
LAK
418
Kip
LBP
422
Lebanese Pound
LKR
144
Sri Lanka Rupee
LRD
430
Liberian Dollar
LSL
426
Loti
LTL
440
Lithuanian Litus
LUF
442
Luxembourg Franc
LVL
428
Latvian Lats
LYD
434
Libyan Dinar
MAD
504
Moroccan Dirham
MDL
498
Moldovan Leu
MGF
450
Malagasy Franc
MKD
807
Denar
MMK
104
Kyat
MNT
496
Tugrik
MOP
446
Pataca
MRO
478
Ouguiya
MTL
470
Maltese Lira
MUR
480
Mauritius Rupee
MVR
462
Rufiyaa
MWK
454
Kwacha
MXN
484
Mexican Peso
MYR
458
Malaysian Ringgit
MZM
508
Mozambique Metical
NAD
516
Namibia Dollar
NGN
566
Naira
NIO
558
Cordoba Oro
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
54
NLG
528
Dutch Guilder
NOK
578
Norwegian Krone
NPR
524
Nepalese Rupee
NZD
554
New Zealand Dollar
OMR
512
Rial Omani
PAB
590
Balboa
PEN
604
Nuevo Sol
PGK
598
Kina
PHP
608
Philippine Peso
PKR
586
Pakistan Rupee
PLN
985
Zloty
PTE
620
Portuguese Escudo
PYG
600
Guarani
QAR
634
Qatari Rial
ROL
642
Leu
RUB
643
Russian Ruble
RUR
810
Russian Ruble
RWF
646
Rwanda Franc
SAR
682
Saudi Riyal
SBD
90
Solomon Islands Dollar
SCR
690
Seychelles Rupee
SDD
736
Sudanese Dinar
SEK
752
Swedish Krona
SGD
702
Singapore Dollar
SHP
654
Saint Helena Pound
SIT
705
Tolar
SKK
703
Slovak Koruna
SLL
694
Leone
SOS
706
Somali Shilling
SRG
740
Suriname Guilder
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
55
STD
678
Dobra
SVC
222
El Salvador Colon
SYP
760
Syrian Pound
SZL
748
Lilangeni
THB
764
Thailand Baht
TJS
972
Somoni
TMM
795
Manat
TND
788
Tunisian Dinar
TOP
776
Pa'anga
TPE
626
Timor Escudo
TRL
792
Turkish Lira
TTD
780
Trinidad and Tobago Dollar
TWD
901
New Taiwan Dollar
TZS
834
Tanzanian Shilling
UAH
980
Hryvnia
UGX
800
Uganda Shilling
USD
840
US Dollar
UYU
858
Peso Uruguayo
UZS
860
Tanzanian Shilling
VEB
862
Bolivar
VND
704
Dong
VUV
548
Vatu
WST
882
Tala
XAF
950
CFA Franc BEAC
XCD
951
East Caribbean Dollar
XOF
952
CFA Franc BCEAO
XPF
953
CFP Franc
YER
886
Yemeni Rial
YUM
891
Yugoslavian Dinar
ZAR
710
South Africa Rand
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
56
ZMK
894
Kwacha
ZWD
716
Zimbabwe Dollar
11.2 ISO 3166 Country Codes
Alpha Code
Country
AD
Andorra
AE
United Arab Emirates
AF
Afghanistan
AG
Antigua & Barbuda
AI
Anguilla
AL
Albania
AM
Armenia
AN
Netherlands Antilles
AO
Angola
AQ
Antarctica
AR
Argentina
AS
American Samoa
AT
Austria
AU
Australia
AW
Aruba
AZ
Azerbaijan
BA
Bosnia and Herzegovina
BB
Barbados
BD
Bangladesh
BE
Belgium
BF
Burkina Faso
BG
Bulgaria
BH
Bahrain
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
57
BI
Burundi
BJ
Benin
BM
Bermuda
BN
Brunei Darussalam
BO
Bolivia
BR
Brazil
BS
Bahama
BT
Bhutan
BU
Burma (no longer exists)
BV
Bouvet Island
BW
Botswana
BY
Belarus
BZ
Belize
CA
Canada
CC
Cocos (Keeling) Islands
CF
Central African Republic
CG
Congo
CH
Switzerland
CI
Cote D'ivoire (Ivory Coast)
CK
Cook Iislands
CL
Chile
CM
Cameroon
CN
China
CO
Colombia
CR
Costa Rica
CS
Czechoslovakia (no longer exists)
CU
Cuba
CV
Cape Verde
CX
Christmas Island
CY
Cyprus
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
58
CZ
Czech Republic
DD
German Democratic Republic (no longer exists)
DE
Germany
DJ
Djibouti
DK
Denmark
DM
Dominica
DO
Dominican Republic
DZ
Algeria
EC
Ecuador
EE
Estonia
EG
Egypt
EH
Western Sahara
ER
Eritrea
ES
Spain
ET
Ethiopia
FI
Finland
FJ
Fiji
FK
Falkland Islands (Malvinas)
FM
Micronesia
FO
Faroe Islands
FR
France
FX
France, Metropolitan
GA
Gabon
GB
United Kingdom (Great Britain)
GD
Grenada
GE
Georgia
GF
French Guiana
GH
Ghana
GI
Gibraltar
GL
Greenland
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
59
GM
Gambia
GN
Guinea
GP
Guadeloupe
GQ
Equatorial Guinea
GR
Greece
GS
South Georgia and the South Sandwich Islands
GT
Guatemala
GU
Guam
GW
Guinea-Bissau
GY
Guyana
HK
Hong Kong
HM
Heard & McDonald Islands
HN
Honduras
HR
Croatia
HT
Haiti
HU
Hungary
ID
Indonesia
IE
Ireland
IL
Israel
IN
India
IO
British Indian Ocean Territory
IQ
Iraq
IR
Islamic Republic of Iran
IS
Iceland
IT
Italy
JM
Jamaica
JO
Jordan
JP
Japan
KE
Kenya
KG
Kyrgyzstan
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
60
KH
Cambodia
KI
Kiribati
KM
Comoros
KN
St. Kitts and Nevis
KP
Korea, Democratic People's Republic of
KR
Korea, Republic of
KW
Kuwait
KY
Cayman Islands
KZ
Kazakhstan
LA
Lao People's Democratic Republic
LB
Lebanon
LC
Saint Lucia
LI
Liechtenstein
LK
Sri Lanka
LR
Liberia
LS
Lesotho
LT
Lithuania
LU
Luxembourg
LV
Latvia
LY
Libyan Arab Jamahiriya
MA
Morocco
MC
Monaco
MD
Moldova, Republic of
MG
Madagascar
MH
Marshall Islands
ML
Mali
MN
Mongolia
MM
Myanmar
MO
Macau
MP
Northern Mariana Islands
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
61
MQ
Martinique
MR
Mauritania
MS
Monserrat
MT
Malta
MU
Mauritius
MV
Maldives
MW
Malawi
MX
Mexico
MY
Malaysia
MZ
Mozambique
NA
Nambia
NC
New Caledonia
NE
Niger
NF
Norfolk Island
NG
Nigeria
NI
Nicaragua
NL
Netherlands
NO
Norway
NP
Nepal
NR
Nauru
NT
Neutral Zone (no longer exists)
NU
Niue
NZ
New Zealand
OM
Oman
PA
Panama
PE
Peru
PF
French Polynesia
PG
Papua New Guinea
PH
Philippines
PK
Pakistan
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
62
PL
Poland
PM
St. Pierre & Miquelon
PN
Pitcairn
PR
Puerto Rico
PT
Portugal
PW
Palau
PY
Paraguay
QA
Qatar
RE
Reunion
RO
Romania
RU
Russian Federation
RW
Rwanda
SA
Saudi Arabia
SB
Solomon Islands
SC
Seychelles
SD
Sudan
SE
Sweden
SG
Singapore
SH
St. Helena
SI
Slovenia
SJ
Svalbard & Jan Mayen Islands
SK
Slovakia
SL
Sierra Leone
SM
San Marino
SN
Senegal
SO
Somalia
SR
Suriname
ST
Sao Tome & Principe
SU
Union of Soviet Socialist Republics (no longer exists)
SV
El Salvador
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
63
SY
Syrian Arab Republic
SZ
Swaziland
TC
Turks & Caicos Islands
TD
Chad
TF
French Southern Territories
TG
Togo
TH
Thailand
TJ
Tajikistan
TK
Tokelau
TM
Turkmenistan
TN
Tunisia
TO
Tonga
TP
East Timor
TR
Turkey
TT
Trinidad & Tobago
TV
Tuvalu
TW
Taiwan, Province of China
TZ
Tanzania, United Republic of
UA
Ukraine
UG
Uganda
UM
United States Minor Outlying Islands
US
United States of America
UY
Uruguay
UZ
Uzbekistan
VA
Vatican City State (Holy See)
VC
St. Vincent & the Grenadines
VE
Venezuela
VG
British Virgin Islands
VI
United States Virgin Islands
VN
Viet Nam
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
64
VU
Vanuatu
WF
Wallis & Futuna Islands
WS
Samoa
YD
Democratic Yemen (no longer exists)
YE
Yemen
YT
Mayotte
YU
Yugoslavia
ZA
South Africa
ZM
Zambia
ZR
Zaire
ZW
Zimbabwe
ZZ
Unknown or unspecified country
Thin Client Integration Guide - Green Dot MoneyPak (Revision 01)
65