Web Services Interface Specification V2.46.0

Web Services
Interface Specification
Version V2.46
20 Janurary 2017
Confidential
www.fisglobal.com
Web Services Interface Specification
Europe, Middle East and Africa Asia Australasia Latin American and Caribbean
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100
emea.marketing@fisglobal.com ap.marketing@fisglobal.com au.enquiries@fisglobal.com lac.marketing@fisglobal.com
© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 2

Version V2.46 20/01/2017 Confidential
Distribution List
1 Debit and Prepaid Document Library
2 FIS Clients
Revision History
Version Date Detail of Change

0.1 Draft 04/01/05 First draft
0.3 Draft 21/01/05 Further message types added
1.0 05/03/05 First Version
1.1 12/03/05 Enhancing messages with further functionality
1.2 23/04/05 Adding further fields and adding in ACTIONCODE appendix
1.3 08/08/05 Corrections to typos and adding more description in
1.4 10/10/05 Adding more actioncodes and changing tags to match WSDL case
1.5 09/12/05 New messages CardListEnquiry and LoadVerification.

New <authMethod> = 5, based on LoginID
New <loginID> field added to all existing messages
New <authMethod> = 6, based on <PAN>, <DOB> and <lastName>
New <lastName> field added to BalanceEnquiry, AccountEnquiry, CardTransfer,
CashOut, CancelLoad and CashOutStatusChange to support <authMethod> = 6
The <track2> field in CardLoad and CancelLoad has been changed from Mandatory
to Conditional to allow for other load channels when swiping the card is not possible
(e.g Internet), this means that CardLoad and CancelLoad require <PAN>, <DOB>,
<CVV>, <accessCode>, <lastName> and <authMethod> fields
New field <loadFundsType> added to CardLoad and CardActivationLoad
CardActivationLoad requires <authMethod> for the Load interface and the field
<lastName> changes from Optional to Conditional accordingly
Repeated <DOB> field removed from CardActivationLoad
New <sysDate> field added to all message responses
New fields <txnFilter>, <endBal>, <startDate> and <endDate> in AccountEnquiry
New <postDate> field added to TransactionDescription in AccountEnquiry
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


New field <blkAmt> added to BalanceEnquiry, AccountEnquiry, CardTransfer,
CashOut and CashOutStatusChange
Removed following services: ChoosePIN, CardRequest, CardRequestActivateLoad
and CardActivateStatusChangeTransfer
Updated examples for messages
1.6 08/02/06 Clarification of the description of Combination Messages

Added missing fields localDate and localTime to the CardListEnquiry message
New fields <firstName>, <lastName> and <embossName> added to the lists returned
by the CardListEnquiry message
Clarification for <authMethod> 2 and 6, where Date of Birth and Last Name are
those of the cardholder. This is applicable to those cases where the cardholder and
card purchaser are not the same person
1.7 15/03/06 Added new card Status Code 78 and Action Code 107 for cards that are suspected of
fraudulent use
2.0 DRAFT 28/03/06 New mandatory <instCode> tag added to all messages:
Unique txn ID added in response messages for all web services that have a financial
impact. Account Enquiry will also return these same IDs for each financial
transaction
Added new Web Services TransactionVoid, CardholderUpdate and
CardholderEnquiry
Field <loginID> will be present on the response messages if present in the request
and has been changed from Mandatory to Optional in the request of the
LoadVerification message
Field <authMethod> changed from Optional to Conditional in CardLoad, CancelLoad
and CardActivationLoad messages. This field is mandatory unless <track2> is
provided.
Changed the description of the field <accessCode> in all the messages with extra
clarifications in CardActivation and CardActivationLoad messages
Added a new card Status Code 09 (Dormant). In this status, inactive cards cannot be
loaded. CardLoad message description updated accordingly
Changed status 02 description
Change to StatusChange message to add authentication details. Authentication will
be required to change the status back to normal
Note added to CardTransfer message regarding extended conditions of use
Omitted CancelLoad message (redundant due to Void) and changed Cash Out Web
Services to the more generic Card Unload message. Also added new optional tags
<amtUnload> and <currCode> to both Card Unload web services and CardTransfer
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<loadFundsType> made optional and max. length increased to 3
New optional tag <loadSrc> added to CardLoad, CardActivateLoad, CardUnload,
CardTransfer and CardUnloadStatusChange
<amtTransfer> added as optional field in CardTransfer web service. The <currCode>
field in this web service is now conditional in the request if an <amtTransfer> value
is sent
Messages CardLoad, CardUnload and CardTransfer, CardActivationLoad and
CardUnloadStatusChange will return the right itemId (for the financial) and
<actionCode> 913 when the transaction is duplicate
<statCode> field added to message Cardholder Enquiry
Added new Action Codes 121 and 123 for limits exceeded
Added new outgoing (from Nomad Payments to the member) message Outgoing
Loads
Updated Nomad Payments Action Codes section: removed codes not used, and
supplied usage information.
2.0 31/05/06 Formal release of 2.0 DRAFT, plus removal of unused activMethod tag, and replacing
the Activation Code method of activation with the Access Code.
2.1 04/07/06 Added new Web Services for Balance Adjustment and Card Application.
Clarified that the <CVV> field used in Authentication Method ‘3’ actually refers to
the CVC2, the 3-digit security code printed on the back of the card.
Added new Card Status codes.
Added dateActivated to Cardholder Enquiry.
Added amtTxn and curTxn to Outgoing Loads WS.
Clarified use of amtUnload and amtTransfer in Card Unload, Card Unload / Status
Change, and Card Transfer WS.
2.5 13/09/06 Moved <actMethod> values & descriptions to Appendix D.

Moved <authMethod> values & descriptions to Appendix E.
Added new <authMethod> = ‘7’ for full track2 details.
Added new <authMethod> = ‘8’ and <actMethod> = ‘5’ for “Card number & security
data”. See example in BalanceEnquiry message
Added <secChkId> and <secValue> fields to each WS to correspond with the new
<authMethod>/<actMethod> option.
Added <dlvMethod> and <imageID> fields to Cardholder Update, Cardholder
Enquiry, and Card Application.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


The field <authMethod> is now mandatory in all messages that use this field, except
Card Application. The affected messages are Status Change, Cardholder Update and
Balance Adjustment:
The field <track2> has been added to all the messages where a card needs to be
selected and can be used instead of <PAN>. Either <PAN> or <track2> must be
provided in all messages apart from Card List Enquiry and Card Application:
Added <crdAcptID> field to Transaction Description in Account Enquiry. The Web
Service previously returned this value in a termLocation field, which was not
documented in the specification. This value is now returned in the new <crdAcptID>
field.
Distinction made between Card Number and <PAN>. Previously, Card Number was
only provided via <PAN>, now it can be provided either via <PAN> or <track2>. This
mainly affects and authentication and activation methods (<authMethod> and
<actMethod>) usage.
Added new Action Code 921 for failed authentication due to security details not
being setup for the cardholder.
Updated the description for the Action Code 121 in Appendix B to reflect actual
behaviour.
Updated Void Transaction description to reflect it’s capability to void Card Load,
Card Unload, Card Transfer, and Balance Adjustment messages.
Clarified that Core Messages and Combination Messages are Incoming Messages.
Added Notes to Overview section about XML processing in the Web Services.
Clarified description of <itemId> returned in Card Transfer.
Clarified Cardholder Update:
1 - <DOB>: that age-verification applies if so configured
2 - <crdProduct>: that age-verification does not apply, and that <modSecChk> must
be used to update security checks if they are not compatible between products.
Clarified conditions to return <loginID> for Cardholder Enquiry, and Card
Application.
3 - <loginID>: returned if the customer has a <loginID>
Clarified use of age-verification in the <DOB> field description of Card Activation and
Card Activation / Card Load.
The current balance and current amount of blocked funds (<avlBal> and <blkAmt>
fields) at the time of each item are now returned in the Account Enquiry response.
New <reason> field in Status Change, Card Activation, Card Activation / Load, and
Card Unload / Status Change.
New <imageID> field added to Cardholder Update, Cardholder Enquiry, and Card
Application.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Corrected <postdate> field to <postDate> in Account Enquiry.
Added <numTxns> field to Account Enquiry.
Updated incorrect occurrence of incorrect fieldname <loginId> with the correct
<loginID>.
Added new <loadFundsType> values:
4 – Import
5 – Saving stamps
6 – Cheque
7 – Standing order
Added <loginID> to Card Application response at the Card Detail level.
2.5.1 06/10/06 Clarified in Card Application that the <pin> field is conditional not optional.
For Account Enquiry, added new field <billConvRate>, and clarified use of <amtBill>
for authorisations versus financials.
2.5.2 09/10/06 Release of specification compliant with the corresponding version of the Web
Services, which contain the following changes:
Enforced 60 char max <reason> field in Status Change message
Balances contained in Void Transaction responses reflect the balances at the time of
the Void message
Removed potential for date discrepancies due to different timezones on
communicating machines
Added <currCode> in request for Card Unload Status Change message
Changed wsdl field definition for date fields from dateTime to date in Card List
Enquiry message
Added validation of the <countryCode> in the Cardholder Update message
2.6 25/10/06 Added new ‘Manage PIN’ Web Service.

Added Action Codes 167, 168, 169, 184.
Added dlvXXX fields to Cardholder Enquiry, Cardholder Update, and Card
Application.
Clarified conditional use of and inter-relationship between all name and address
fields in Cardholder Update.
2.6.1 DRAFT 14/12/06 Added new ‘Outgoing Transaction’ Web Service.

Clarfied values of posXXX fields in the Outgoing Loads Web Service.
Clarified use of avlBal and blkAmt fields in applicable Web Services.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2.6.1 22/01/07 Formal release of V2.6.1. DRAFT.
In Outgoing Transaction WS, modified the <repeat> and <timeout> fields to use
value 0 and 1 rather than Y and N.
2.6.2 22/03/07 Clarified conditional use of and inter-relationship between all name and address
fields in Card Activation and Card Activate / Card Load message.
Added validation of the <countryCode> in the Card Activation and Card Activate /
Card Load message.
Corrected case of <newPIN>, <currentPIN>, and <confirmPIN> fields in the Manage
PIN WS example message and wsdl file.
2.7 03/05/07 Added new fields to Cardholder Update: <newAccessCode>, <brncode>, <renew>,
<crdDesign>, <crdProgram>.
Added new fields to Cardholder Enquiry and Card Application: <brncode>, <renew>.
In Cardholder Update, added new section ‘Clearing field values’ to specify which
fields will be cleared when a <space> is sent in that field.
2.7.1 31/07/07 Card List Enquiry: <program> and <designRef> fields changed to optional in
response.
Updated this specification (documentation change only) to correctly reflect the wsdl
files, as follows:
Cardholder Update: added <pobox>, <crdprogram> and <crddesign> fields, and
corrected case of <crdproduct> field.
Card Activation: removed <crdAcptID> field.
Card Application: added <dateActivated> field and corrected case of <postcode>,
<crdproduct>, <crdprogram>, and <crddesign> fields.
Cardholder Enquiry: corrected case of <postcode>, <crdproduct>, <crdprogram>,
and <crddesign> fields.
Card Transfer: corrected case of <lastName> and <newPAN> fields.
Outgoing Loads: added <tlogId> and <itemId> fields.
Added new <loadSrc> values:
11 – In-store
12 – EPAY.
2.8 03/08/07 Added usage notes on Manage PIN.

Corrected mis-spelling of <crdAcptID> field name (from crdActpID) in all applicable
wsdl files.
Account Enquiry: clarified use of <txnFilter>
Account Enquiry: ‘Transaction Description’ returns new field <itemType>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Card Application: added new field <cardName>
Balance Adjustment: added new fields <extCode> and <forcePost>
Cardholder Enquiry / Card Application: return new fields <denyMCC>, <denySvc>,
<accType> and <CVC2>
Cardholder Update : added new fields <denyMCC>, <denySvc>, <accType>, <memo>,
<memoUser> and <memoScope>.
Card List Enquiry: added <PAN> & <accno>/<currCode> lookup methods.
Card List Enquiry: added new <custType> field to identify cards owned by the
primary customer.
Card List Enquiry: changed <loginID> field from Mandatory to Conditional in the
request.
Card Activation / Card Activation/Load: added new <actMethod> value 6 for PAN-
only activation.
2.8.1 06/09/07 Cardholder Update: Added information about the details that can be updated by
additional cards.
2.8.2 14/01/08 Updated <ForcePost> definition with information that force posting does not
override maximum balance limits.
2.9 27/02/08 Added new fields to Transaction Description section of Account Enquiry response:
• dataSrc
• txnTime
• localDate
• tlogID
• messageID
Added new field itemSrc to various services
2.9.1 28/02/08 Changed branding from Nomad Payments to Metavante.
2.9.2 21/05/08 Card Transfer: Corrected data type of CURRCODE.
2.9.3 15/07/08 Corrected description of security options in Appendix G and of <forcepost> in

Balance Adjustment message.
Corrected maximum length of <embossName> in all messages.
2.9.4 16/08/08 Corrected data type of <messageID> in all messages.
2.10 05/09/08 Account Enquiry: Added new <feeID> field to specify type of cardholder fee.
2.10.1 09/08/08 Clarified sorting of transactions in Account Enquiry.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2.11 23/10/08 Added <miscSvc> section and <feeTier> element to Cardholder Enquiry and
Cardholder Update services
Added updates to <secDet> and <TxnDesc> sections.
Added sample SOAP messages to each message description.
Added account status changes to list of entries included in <txnFilter>=0.
2.11.1 12/12/08 Updated list of card statuses (Appendix A).
2.11.2 19/01/09 Added rules used to store telephone numbers.
2.12 27/01/09 Added <isoLang> field to Cardholder Update and Cardholder Enquiry.
2.12.1 19/02/09 Added note on voiding card transfers
2.13 10/03/09 Added new fields to Cardholder Update and Cardholder Enquiry services to support
updating and enquiry of an external funds card.
Added new values to <poscdim> field in outgoing messages.
Clarified <txnfilter> field in Account Enquiry.
2.13.1 26/03/09 Added note on card to card transfer.
2.14 15/05/09 Added new card identifier tag <cardID> to all web services.
Added Manage Connection and Validate Card web services.
Added <rev>, <orgItemId>, and <termCode> to the appropriate web services.
Added SecureCode to list of values for <itemSrc>.
Updated definitions of <PAN>, <track2>, and <CardID> in Manage PIN web service.
Improved descriptions of Status Change Web Service.
Added new tags <tel>, <mobTel>, <userdata>, <userdata1>, <userdata2>,
<userdata3>, <userdata4>, <designRef> and <crdproduct> to Card Activation and
Card Activation and Load web services.
Added new tags < loadFundsType> and <loadSrc> to Load Verification web service.
Added <newCardID> to Card Transfer web service.
Modified description of <newPIN> in Modify PIN web service.
Modified description of <PAN> to include masking information.
Added new transaction types to Appendix C.
Renamed <accCurr> to <curBill> and added tag <amtFee> to Outgoing Transaction
web service.
Clarified length of <cardName> and <embossName>.
Clarified the working of the source-of-funds card fields in Cardholder Update.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Clarified effect of <CardID> on the Manage PIN Web Service.
Corrected description of <EMVDATA> in Validate Card Web Service.
2.15 24/07/09 Added <txnSubCode> to Account Enquiry web service.

Clarified that MTL supports only RPC/encoded style for Web Services.
Updated tag names to match with WSDL files.
Added SOAP sample message for Outgoing Transactions Web Service.
2.16 14/09/09 Updated in CardHolderUpdate web service:

• Changed <fundCrdIssNum> from N to AN.
• Added <formFactorID>.
• Added <miscSvcLoadProfile> section.
• Added <svcBalNotifyCycle> and <svcMinBal> in miscSvc section
Updated in CardHolderEnquiry web service:
• Added <formFactorID>
• Added <fundCrdEffDate>
• Added <fundCrdExpDate>
• Added <fundCrdType>
• Added <fundCrdIssNum>
• Added <miscSvcLoadProfile> section.
• Added <svcBalNotifyCycle> and <svcMinBal> in miscSvc section
Removed <keyType> tag from Validate Card web service
Changed branding from Metavante to FIS.
2.16.1 21/10/09 Corrected data type and length of <itemId> and <orgItemId>.
2.16.2 02/11/09 Corrected description of <cardID>.

Clarified which fields in CardActivation and CardHolderUpdate web services can be
cleared by sending a space.
2.17 27/11/09 Added <description> to CardLoad web service.

Added note to CardUnload web service.
Enhanced descriptions of <isoLang> in CardHolderUpdate and CardHolder Enquiry
web services.
2.17.1 21/07/10 Corrected example for Card Application web service.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2.17.2 26/07/10 Modified data type, length and allowed values for <msgType> in Outgoing
Transaction Message web service.
2.18 05/10/10 Added CardID and PAN to the Account Enquiry web service.
Added ctxLocalDate, ctxLocalTime, aVSChkRs, threeDSecChkRs and crdproduct to
Outgoing Transaction web service.
2.18.1 21/02/11 Corrected description of DOB in Card Activation and Card Activate/ Card Load web
service.
2.19 28/10/10 Added <profileRef>, <additionalCrdDet> and <additionalCustDet> to

CardHolderEnquiry and CardHolderUpdate web services.
Added <walletRef>, <additionalTxnDet>, <effectiveDate>, <effectiveTime>,
<expiryDate>, <expiryTime> and <walletProfileRef> to CardLoad and
CardActivationLoad web services.
Added <walletRef> and <additionalTxnDet> to CardUnload and
CardUnloadStatusChange web services.
Added <walletRef> to BalanceAdjustment web service.
Added <amtVoid> and <currCode> to VoidTransaction web service.
Added <srcWalletRef> and <destWalletRef> to CardTransfer web service.
2.19.1 08/11/10 Modified <walletRef> description in CardLoad, CardUnload, CardActivationLoad,

CardUnloadStatusChange and BalanceTransfer web services.
Added <walletID> to CardLoad, CardUnload, CardActivationLoad,
CardUnloadStatusChange, BalanceTransfer and Void Transaction web services.
Added <walletRef> and <additionalTxnDet> to Void Transaction web service.
Removed <amtVoid> and <currCode> from VoidTransaction web service.
Modified description of <srcWalletRef> and <destWalletRef> in CardTransfer web
service.
Added <srcWalletID> and <destWalletID> to CardTransfer web service.
Corrected CVC2 from conditional to mandatory in response of CardHolder Enquiry
web service.
2.19.2 09/09/11 Removed walletRef and walletID 2 from VoidTransaction web service.
2.20 08/03/11 Added Wallet Enquiry web service.

22/03/11 Updated Wallet Enquiry web service.
03/05/11 Added examples of Wallet Enquiry web service.
10/05/11 Added <userdata> and <accno> and modified <cardID>, <loginID> and PAN in Card
List Enquiry web service.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2.20.1 25/05/11 Added LoadFundsType value 12 to all relevant web services.
Added Wallet Enquiry to list of transaction types in Appendix C.
Added <loadSrc> and <loadFundsType> to Balance Adjustment web service.
2.20.2 03/06/11 Corrected description of Card Application web service.
2.20.3 09/06/11 Added note regarding support for UTF-8 character set.
2.21 03/08/11 Added <newCurrCode> to Card Activation/ Load web service.
2.22 04/08/11 Updated <actionCode> in Outgoing Transaction web service to indicate it can be
present in the request message.
Added <amtCashback> to Outgoing Transaction web service.
2.23 05/09/11 Added new web services Balance Update and SMS Reminders.
Added new authentication method ‘9’.
2.23.1 06/10/11 Clarified use of Card Application web service.

Updated telephone number fields to specify that formatting is supported for both
UK and Australian phone numbers.
2.23.2 16/02/12 Appendix F updated to include SMS miscellaneous service fee. Fees section 12
added.
2.23.3 29/06/12 Appendix F updated – added fee codes: 2315, 2320, 2321, 2324, 2325, 2326. Fees
section 12 removed.
2.23.4 13/08/12 Applied FIS corporate template
2.25 12/09/12 Updated Account Enquiry – new field <multiCurAmounts> and Multicurrency
Amounts section; updated descriptions of <startBal>, <endBal>, <avlBal>, and
<blkAmt>.
2.26 29/10/12 Updated SMS Reminders - updated <function> to include function code 114: CVV
PAN Reminder
Added new web service: Reset Fraud Status
Updated Appendix C – added new transcation type, 25: Reset Fraud Status.
2.27 23/01/13 Updated Account Enquiry Web Service – new fields <extCode> and <mcc>.
Updated Balance Enquiry Web Service – new field, <otbAmt>.
2.27.1 23/01/13 Updated Card Unload message – add to description of <currCode>
2.27.2 21/02/13 Updated Appendix A: Card Status Codes – added status codes 14 and 74.
2.27.3 01/03/13 In the Card List Enquiry web service, correct the description of the <statcode> tag.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2.28 03/04/13 Update Validate Card WS: added rejectReason tag.
Update Outgoing Transaction: updated description of TXNCODE to include 11 –
Quasi cash.
2.28.1 24/04/13 Update Cardholder Enquiry WS: corrected <fundCrdPan> to be standard PAN length
and not 4 characters.
2.28.2 05/06/13 Outgoing Loads are no longer supported. Removed references to Outgoing Loads:
Updated Outgoing Messages section
Removed Outgoing Messages section
Updated Appendix C – Transaction Types – removed code 15 Outgoing Loads.
2.28.3 17/06/13 Updated Validate Card WS: updated rejectReason tag, added codes 1133 and 1134.
2.29 06/06/13 Update Cardholder Enquiry WS: 3 new response fields: accProfileRef, cardProfileRef,
custProfileRef.
Update Cardholder Update WS: 3 new request fields: accProfileRef, cardProfileRef,
custProfileRef
2.31 09/12/13 Updated Account Enquiry WS: Change PAN and CARDID to be conditional in
response
Updated Outgoing Transaction WS: Now includes TRN and TXNSUBCODE
2.31.1 26/02/14 Added Appendix J - Card Status and Card Expiry Check by Web Service
2.31.2 03/03/14 Updated Account Enquiry Message and Outgoing Transaction Message sections:
updated <txnSubCode> possible values.
2.32 08/04/14 Updated Card List Enquiry:

• New request/response fields so that it can be invoked by Xpress:
<additionalCustDet>, <additionalAccDet>, <additionalCustDet> in Card List
section, Additional Customer Details and Additional Account Details
sections.
• Updated descriptions for loginid, pan, cardid, accno, userdata1 and
additionalAccdet and additionaCustdet: Following line updated to include
additionalAccdet and additionaCustdet as appropriate.
“Mandatory if neither <PAN>, <cardID>, <accno>, <userdata1>,
<additionalAccdet> nor <additionaCustdet> are provided”
• Removed Request and Response Flag values from Additional Customer
Detail and Additional Account Detail sections – these are driven by the
parent element.
Updated Manage PIN: new field <rev> in request of Manage PIN.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Updated Card Load: Added new fields: <billConvRate>, <amtTxn> and <curTxn>.
Updated Card Activate/Card Load: Added new fields: <billConvRate>, <amtTxn> and
<curTxn>.
Updated Cardholder Update: updated type of <fundCrdCVC> to AN.
Updated optional sections in various Web Services to remove the Request and
Response flag values where they are the same as the parent field.
Updated examples to ensure txntype is correct for the web service.
Replaced Manage PIN example.
2.32.1 13/05/14 Updated Outgoing Transaction Web Service:

<repeat> updated from “Indicates whether the message is a repeat” to “Indicates
whether the message is a repeat of a message already received from the payment
network”
<timeout> updated from “Indicates whether the message is for a timed-out original
transaction:” to “Indicates whether the message is for a timed-out original
transaction i.e. where the payment network timed out:”
2.33 30/06/14 Updated Account Enquiry Web Service: Updated <Txnfilter>: added text as shown in
red:
0 - All account entries.
Includes redemption transactions (including refunds and reversals), loads,
unloads, transfers, balance adjustments, account status changes and fees. Also
includes pending authorisations & authorisation unblocks (expired
authorisations) - available only through configuration , matched (with a
financial) authorisations, and manually cleared authorisations).
Updated Card Load and Card Activate/Card Load: Updated definition of
<billConvRate> to show correct calculation of billConvRate = amtTxn/amtLoad.
Updated Load Verification: Added <amtLoad> and <currCode>.
Updated Appendix B Action Codes: added action code 006.
Updated Appendix F Fee Identifiers: added missing fee ids: 1064, 1065, 2323, 2327,
2328, 2329, 2404, 2405, 2444, 2450.
Updated Appendix J: Card Status and Card Expiry Check by Web Service: * note
changed to indicate that acceptable status codes for this service can be overridden
by client configuration.
2.34 09/09/14 Updated Overview – inserted Outgoing Notification

Inserted new web service section: 26 Outgoing Notification
Updated Appendix C – added transcation type code 26
Corrections to Outgoing Transaction:
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


• <curBill> - updated usage code
• <approvalCode> - updated description, also applies to <AUTHREQ>
messages
• <itemsrc>, updated usage code
• example request message – updated value of <msgtype>
2.35 15/10/14 New web service section: Card Activation Reversal.

Updated Overview and Appendix C Transaction Types
Updated all CardID descriptions to be consistent.
2.35.1 03/11/14 Updated Card Activation Reversal web service: updated (authMethod> Note to
include reference to method 9 not possible in this message.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

2.36 26/11/14 Updated Overview and Appendix C Transaction Types to include reference to new
Limit Enquiry web service.
Updated Appendix J Card Status and Card Expiry Check by Web Service to include
reference to Outgoing Notification, Card Activation Reversal and Limit Enquiry web
service.
New Limit Enquiry web service added.
Updated Manage PIN – removed <rev> tag.
Updated Manage Connection – updated <function> description to include new
functions 03 and 04.
Updated Card List Enquiry – additional tag <pinTries>, part of card list information
and updated example.
2.36.1 08/12/14 Updated Limit Enquiry web service – updated type code of <limRef> and <limDesc>
to AN, updated Size of <limRef>.
2.36.2 10/12/14 Updated Fmt table to include ANS.

Updated Outgoing Transaction web service:
• Updated the type of <termCode>, <crdAcptID> and <crdAcptLoc> to ANS
• Updated description of <aVSChkRs> to refer to Appendix K
• Updated description of <threeDSecChkRs> to include description of
possible values
• Updated description of <amtPad>
Appendix K: AVS Check Results added.
2.36.3 29/12/14 Updated Appendix A – Card Status Codes: added code 15.
2.38 16/09/15 Updated Account Enquiry web service:

• Updated response XML to show masked value for PAN within tag
<description>
2.39 16/09/15 Updated Card List Enquiry web service:

• Added details for new element <additionalCrdDet> in card list record
Description
• Updated request XML to bring in line with response XML message
• Updated response XML message to show additionalCustDet and
additionalCrdDet
2.40 04/11/15 No spec changes required for 2.40
2.41 13/11/15 Update <txnCode> values for Outgoing Transaction
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Added details for new Webservice Remove Authorisation
• Added new section 29 for new webservice Remove Authorisation
• Added new section under table of contents 1.1.24 for Remove
authorisation
• Added new action code 903 in the Appendix B for action codes
Updated Webservice Card holder enquiry
• Added new record field additional record card details in section 15.1.
• Updated section 15.2.2 with the new response.
2.42 04/12/2015 Added details for new element <indCardLimDet>,<indAccLimDet> ,

<indCustLimDet>
in limit enquiry record Description.
Added Details for new Webservice Limit Update

• Added new section 30 for new webservice Limit Update
• Added new section under table of contents 1.1.25 for Limit Update
2.43 08/12/2015 Updated Account Enquiry web service to include new request field <inclDeclined> to
request the inclusion of declined transactions in the response
2.43.1 15/06/2016 Updated Account Enquiry web service to include new response fields <rejectReason
> and <reasonCode> in transaction description
2.44.0 10/07/2016 Updated Card Transfer web service to include new request fields <destAmtTransfer>
and <destCurrCode>
Update Load verification web service to include new request fields
<verificationType>
2.45.0 03/08/2016 Updated CardHolder Enquiry web service to include <prevStatCode>

Updated Card List Enquiry webservice to include <accessCode> for configured
customers
2.45.1 20/09/2016 Updated CardHolder enquiry webservice to include <secDet> in response.

Updated Account Enquiry webservice to include new response field <curBill> in
transaction description
2.46 20/01/2017 The change is for Card Holder Update and Card Holder Enquiry web service.
• Updated Card Holder Update web service to introduce 4 new elements in
the request for <additionalCustDet> and <additionalCrdDet> structures.
These are <valueDate>, <valueTime>, <valueAmt> and <valueCurrCode>.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Refcode is mandatory for additional details. The above fields are passed to
CRI for update. The following combinations are permitted:
a. <reference> and <value>
b. <reference>, <valueDate> and <valueTime>
c. <reference>, <valueAmt> and <valueCurrCode>
Updated Card Holder Enquiry, changing the structure of the elements
<additionalCrdDet>, <additionalCustDet> and <additionalRecCrdDet> in the
response message to include the the 4 extra parameters <valueDate>,
<valueTime>, <valueAmt> and <valueCurrCode>. For
<additionalRecCrdDet> the <currCode> is replaced with <valueCurrCode>.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Table of Contents
About this Guide ........................................................................................................................ 27
Purpose of This Document .......................................................................................................................................... 27
Who Should Use This Document ................................................................................................................................ 27
Structure of This Document ........................................................................................................................................ 27
1. Overview ............................................................................................................................. 28
1.1. Incoming Core Messages ................................................................................................................................... 28
1.1.1. Card Activation .................................................................................................................................... 29
1.1.2. Card Load ............................................................................................................................................. 29
1.1.3. Status Change ...................................................................................................................................... 29
1.1.4. Balance Enquiry ................................................................................................................................... 29
1.1.5. Account Enquiry ................................................................................................................................... 29
1.1.6. Card List Enquiry .................................................................................................................................. 29
1.1.7. Load Verification .................................................................................................................................. 29
1.1.8. Card Transfer ....................................................................................................................................... 29
1.1.9. Card Unload ......................................................................................................................................... 29
1.1.10. Void Transaction .................................................................................................................................. 29
1.1.11. Cardholder Update .............................................................................................................................. 29
1.1.12. Cardholder Enquiry .............................................................................................................................. 30
1.1.13. Balance Adjustment ............................................................................................................................. 30
1.1.14. Card Application .................................................................................................................................. 30
1.1.15. Manage PIN.......................................................................................................................................... 30
1.1.16. Manage Connection ............................................................................................................................. 30
1.1.17. Validate Card ....................................................................................................................................... 30
1.1.18. Wallet Enquiry ..................................................................................................................................... 30
1.1.19. Balance Update .................................................................................................................................... 30
1.1.20. SMS Reminders .................................................................................................................................... 30
1.1.21. Reset Fraud Status ............................................................................................................................... 30
1.1.22. Card Activation Reversal ...................................................................................................................... 30
1.1.23. Limit Enquiry ........................................................................................................................................ 30
1.1.24. Remove Authorisation ......................................................................................................................... 30
1.1.25. Limit Update ......................................................................................................................................... 31
1.2. Incoming Combination Messages ..................................................................................................................... 32
1.2.1. Card Activation and Load ..................................................................................................................... 32
1.2.2. Card Unload and Status Change .......................................................................................................... 32
1.3. Outgoing Messages ........................................................................................................................................... 32
1.3.1. Outgoing Transaction........................................................................................................................... 32
1.3.2. Outgoing Notification .......................................................................................................................... 32
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

1.4. Structure............................................................................................................................................................ 32
1.4.1. Message Types ..................................................................................................................................... 32
1.4.2. Usage Codes......................................................................................................................................... 33
2. Card Activation .................................................................................................................... 34

2.1. Record Description ............................................................................................................................................ 34
2.2. Example ............................................................................................................................................................. 45
2.2.1. Request ................................................................................................................................................ 45
2.2.2. Response .............................................................................................................................................. 46
3. Card Load ............................................................................................................................ 48

3.2. Example ............................................................................................................................................................. 55
3.2.1. Request ................................................................................................................................................ 55
3.2.2. Response .............................................................................................................................................. 57
4. Status Change ...................................................................................................................... 59

4.2. Example ............................................................................................................................................................. 62
4.2.1. Request ................................................................................................................................................ 63
4.2.2. Response .............................................................................................................................................. 64
5. Balance Enquiry ................................................................................................................... 66

5.2. Example ............................................................................................................................................................. 70
5.2.1. Request ................................................................................................................................................ 70
5.2.2. Response .............................................................................................................................................. 71
6. Account Enquiry................................................................................................................... 73
6.2. Example ............................................................................................................................................................. 84
6.2.1. Request ................................................................................................................................................ 84
6.2.2. Response .............................................................................................................................................. 86
7. Card List Enquiry .................................................................................................................. 90

7.2. Example ............................................................................................................................................................. 96
7.2.1. Request ................................................................................................................................................ 97
7.2.2. Response .............................................................................................................................................. 97
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

8. Load Verification................................................................................................................ 102

8.1. Record Description .......................................................................................................................................... 102
8.2. Example ........................................................................................................................................................... 107
8.2.1. Request .............................................................................................................................................. 107
8.2.2. Response ............................................................................................................................................ 109
9. Card Transfer ..................................................................................................................... 110

9.2. Example ........................................................................................................................................................... 116
9.2.1. Request .............................................................................................................................................. 116
9.2.2. Response ............................................................................................................................................ 118
10. Card Unload ....................................................................................................................... 120

10.2. Example ........................................................................................................................................................... 126
10.2.1. Request .............................................................................................................................................. 126
10.2.2. Response ............................................................................................................................................ 127
11. Card Activate/Card Load .................................................................................................... 129

11.2. Example ........................................................................................................................................................... 141
11.2.1. Request .............................................................................................................................................. 141
11.2.2. Response ............................................................................................................................................ 143
12. Card Unload/Status Change ............................................................................................... 145

12.2. Example ........................................................................................................................................................... 151
12.2.1. Request .............................................................................................................................................. 151
12.2.2. Response ............................................................................................................................................ 152
13. Void Transaction ................................................................................................................ 155

13.2. Example ........................................................................................................................................................... 159
13.2.1. Request .............................................................................................................................................. 159
13.2.2. Response ............................................................................................................................................ 161
14. Cardholder Update ............................................................................................................ 163

14.2. Clearing field values ........................................................................................................................................ 194
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

14.3. Example ........................................................................................................................................................... 195

14.3.1. Request .............................................................................................................................................. 195
14.3.2. Response ............................................................................................................................................ 203
15. Cardholder Enquiry ............................................................................................................ 205

15.2. Example ........................................................................................................................................................... 229
15.2.1. Request .............................................................................................................................................. 229
15.2.2. Response ............................................................................................................................................ 231
16. Balance Adjustment ........................................................................................................... 242

16.2. Example ........................................................................................................................................................... 248
16.2.1. Request .............................................................................................................................................. 248
16.2.2. Response ............................................................................................................................................ 250
17. Card Application ................................................................................................................ 252

17.2. Example ........................................................................................................................................................... 273
17.2.1. Request .............................................................................................................................................. 273
17.2.2. Response ............................................................................................................................................ 276
18. Manage PIN ....................................................................................................................... 281

18.2. PIN field usage ................................................................................................................................................. 288
18.3. Example ........................................................................................................................................................... 289
18.3.1. Request .............................................................................................................................................. 289
18.3.2. Response ............................................................................................................................................ 291
19. Outgoing Transaction ......................................................................................................... 293

19.2. Example ........................................................................................................................................................... 303
19.2.1. Request .............................................................................................................................................. 303
19.2.2. Response ............................................................................................................................................ 307
20. Manage Connection ........................................................................................................... 309

20.2. Example ........................................................................................................................................................... 310
20.2.1. Request .............................................................................................................................................. 310
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

20.2.2. Response ............................................................................................................................................ 311
21. Validate Card ..................................................................................................................... 313

21.2. Example ........................................................................................................................................................... 320
21.2.1. Request .............................................................................................................................................. 321
21.2.2. Response ............................................................................................................................................ 323
22. Wallet Enquiry ................................................................................................................... 325

22.2. Example ........................................................................................................................................................... 333
22.2.1. Request .............................................................................................................................................. 334
22.2.2. Response ............................................................................................................................................ 335
23. Balance Update ................................................................................................................. 339

23.2. Example ........................................................................................................................................................... 345
23.2.1. Request .............................................................................................................................................. 345
23.2.2. Response ............................................................................................................................................ 347
24. SMS Reminders .................................................................................................................. 349

24.2. Example ........................................................................................................................................................... 353
24.2.1. Request .............................................................................................................................................. 353
24.2.2. Response ............................................................................................................................................ 354
25. Reset Fraud Status ............................................................................................................. 356

25.2. Example ........................................................................................................................................................... 360
25.2.1. Request .............................................................................................................................................. 360
25.2.2. Response ............................................................................................................................................ 361
26. Outgoing Notification ........................................................................................................ 362

26.2. Example ........................................................................................................................................................... 366
26.2.1. Request .............................................................................................................................................. 366
26.2.2. Response ............................................................................................................................................ 367
27. Card Activation Reversal .................................................................................................... 369

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

27.2. Example ........................................................................................................................................................... 373

27.2.1. Request .............................................................................................................................................. 373
27.2.2. Response ............................................................................................................................................ 374
28. Limit Enquiry ..................................................................................................................... 376

28.2. Example ........................................................................................................................................................... 385
28.2.1. Request .............................................................................................................................................. 385
28.2.2. Response ............................................................................................................................................ 386
29. Remove Authorisation ....................................................................................................... 392

29.2. Example ............................................................................................................................................................ 397
29.2.1 Request .............................................................................................................................................. 398
29.2.2 Response ............................................................................................................................................ 399
30. Limit Update ...................................................................................................................... 401

30.2. Example ............................................................................................................................................................ 410
30.2.1 Request .............................................................................................................................................. 411
30.2.2 Response ............................................................................................................................................ 413
Appendix A: Card Status Codes................................................................................................. 415
Appendix B: Action Codes ........................................................................................................ 417
Appendix C: Transaction Types ................................................................................................. 420
Appendix D: Activation Methods .............................................................................................. 422
Appendix E: Authentication Methods ....................................................................................... 423
Appendix F: Fee Identifiers ....................................................................................................... 424
Appendix G: Security Configuration .......................................................................................... 427

HTTPS ........................................................................................................................................................................ 427
VPN and WS Security ................................................................................................................................................ 427
Appendix H: WS Security Messages .......................................................................................... 428
Appendix I: EMV Data Format .................................................................................................. 434
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Field 55 Integrated Circuit Card (ICC) System Related Data ..................................................................................... 434
Example..................................................................................................................................................................... 447
Appendix J: Card Status and Card Expiry Check by Web Service ................................................ 448
Appendix K: AVS Check Results ................................................................................................ 452
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

About this Guide

Purpose of This Document
This document specifies the message formats used by the standard FIS Web Services interface.
Who Should Use This Document

This document should be used by FIS and FIS Clients involved with the deployment and management of FIS Web
Services. It should also be read by any third party companies who will interface with FIS Web Services.
Structure of This Document

This document consists of the following sections.
• Section 1 - Overview
• Sections 2-26 – Description of each Web Service
• Appendix A – Card Status Codes
• Appendix B – Action Codes
• Appendix C – Transaction Types
• Appendix D – Activation Methods
• Appendix E – Authentication Methods
• Appendix F – Fee Identifiers
• Appendix G – Security Configuration
• Appendix H – WS Security Messages
• Appendix I – EMV Data Format
• Appendix G – Security Configuration
• Appendix H – WS Security Messages
• Appendix I – EMV Data Format
• Appendix J-Card Status and Card Expiry Check by Web Service
• Appendix K-AVS Check Results
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

1. Overview
This document describes the XML Web Services messages that can be used between FIS and front ends such as IVR
(Interactive Voice Recognition), cardholder websites and teller terminals such as UltraPos.
Note: The system using FIS Web Services must be capable of ignoring fields it does not require either in responses (for
Incoming Messages), or in requests (for Outgoing Messages). Meaning, the introduction of new fields to the
specification should not cause systems written to an older version of the specification to fail.
Note: Unless stated otherwise, the ordering of the fields within the message should not be relied upon.
Note: FIS Web Services use RPC/encoded style as indicated in the wsdl files. FIS supports only RPC/encoded style for
Web Services.
Brief overviews of the messages processed by FIS Web Services from the three input streams illustrated above are as
follows:
1.1. Incoming Core Messages
Note: All minimum and maximum lengths are specified in bytes. For the Latin-1 and ASCII character set, one character
is equivalent to one byte. However, for the UTF-8 character set, one character may not be always equal to one
byte. Cortex supports up to 4-byte long UTF-8 characters.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

1.1.1.Card Activation
Prepaid cards distributed by FIS will normally be issued in an inactive state - “Not yet Issued” (see Appendix A). The
Card Activation message will set the status of the card to its active state “00”, thus enabling transactions to be
performed.
1.1.2.Card Load
Not all cards new cards created on FIS are pre-loaded with an initial amount. A typical scenario is when a customer
buys the card and requests a particular value be put on the card. This message should be used to load that amount onto
the card. It may also be used for subsequent re-loads, should the card product support this function.
1.1.3.Status Change
This message allows the status of a card to be changed, for example, to a lost or stolen status, preventing further use.
1.1.4.Balance Enquiry
A request for a Balance Enquiry will return the current available balance on the card. This message may also be used to
authenticate a cardholder for another system, such as IVR or a cardholder website.
1.1.5.Account Enquiry
A request for an account enquiry will return a list of transactions performed on the card, along with the current
available balance.
1.1.6.Card List Enquiry

This message returns the list of cards associated with a customer, indicating the relationship the customer has with
each card: purchaser, cardholder, or loader. The message therefore returns up to three lists per request.
1.1.7.Load Verification
This message reduces the likelihood for payment reversals, by pre-validating the load request in terms of the card
status, limits, and various other checks. It follows that this message should be used before a Card Load request.
1.1.8.Card Transfer
This message should be used to transfer an amount from one card to another. It may be used for a full balance transfer
when for example a card is being replaced by another card, for reasons such as it being lost/stolen or damaged.
1.1.9.Card Unload
This message enables a cardholder to redeem the remaining value or a specified value from the card. This is in essence
the opposite of a Card Load, but is not like a Void Transaction, which reverts the updates of the related transaction.
1.1.10. Void Transaction

This is a Generic Void which allows all Web Services of financial impact to be voided based on supplying a unique item
ID (which is present in all responses to said web services).
1.1.11. Cardholder Update

Provides the ability to update a cardholder’s information.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

1.1.12. Cardholder Enquiry

Returns the cardholder information.
1.1.13. Balance Adjustment

Provides the ability to apply miscellaneous debits and credits to a card balance.
1.1.14. Card Application

Provides the ability to create new anonymous or personalised cards.
1.1.15. Manage PIN

Provides the ability to set, retrieve and change the PIN associated with the card.
1.1.16. Manage Connection

Provides the ability to update the status of the host.
1.1.17. Validate Card

Provides the ability to verify card details. The card details that can be verified are track2 and card PIN.
1.1.18. Wallet Enquiry

Provides details of all unexpired wallets. The service provides details of their effective/expiry dates as well as amount
remaining and spend history.
1.1.19. Balance Update

Provides the ability to update the balance of a cardholder account.
1.1.20. SMS Reminders

Provides the ability to send SMS reminders to the cardholder.
1.1.21. Reset Fraud Status

Provides the ability to reset card status from Fraud Monitoring to previous status prior.
1.1.22. Card Activation Reversal

Reverses the card activation process and also voids the load if any was associated with the activation.
1.1.23. Limit Enquiry

This is an enquiry service that provides details for card, account and customer limits.
1.1.24. Remove Authorisation

The Remove Authorisation removes the pending authorization
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

1.1.25. Limit Update

The Limit Update service to maintain individual Limits.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

1.2. Incoming Combination Messages

For ease of use, certain core messages have been combined into single requests based on a common functional use.
Though these messages appear to perform as single messages, they actually consist of two independent messages.
1.2.1.Card Activation and Load

This combination is typically used when an inactive, zero value card is purchased in a retail environment.
1.2.2.Card Unload and Status Change

When the remaining value on a card is redeemed, it is more than likely that the card will no longer be in use and
therefore should also be inactivated to a status of “06 – Customer Closed” (see Appendix A).
1.3. Outgoing Messages

Some messages will be initiated by FIS and sent to an external member system.
1.3.1.Outgoing Transaction
This message will be used to send an authorisation to another system for approval or for posting.
This message is only available to members configured for its use and will require members to implement a Web Service
message based on the FIS specification contained within this document.
1.3.2.Outgoing Notification
This message is generated from FIS and sent to a client’s Web Service. The message will be used to send a notification
to the client for the card holder.
1.4. Structure
1.4.1.Message Types
For each message, an XML tag is specified. This tag will be the very first tag seen in the message and will be the header
tag for all messages of that type.
In the following tables the following abbreviations are used for the format:
Fmt Description
A Alphabetic
AN Alpha-numeric
ANS Alpha-numeric including printable special characters
D Decimal
N Numeric
All currencies are expressed using ISO Alpha codes.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

All monetary amounts are expressed with the decimal point and the correct number of decimal places for that
currency. For example, an amount of GBP 123.45 would be expressed as <123.45>, and GBP 300 would be expressed as
<300.00>.
All <localDate> and <localTime> fields represent the date and time when the message was generated.
<actionCode> represents the response code supplied in the response message back to the originator of the request.
The field values are in accordance with the ISO field values for the ‘Action Code’. For example, 116 is ‘insufficient funds’,
909 being ‘system malfunction’. The codes applicable to FIS may be found in Appendix B. Note that not all ISO Action
Codes are supported.
1.4.2.Usage Codes
The Usage Codes can be found in the last two columns of the Message Type tables. One column represents the Request
message, and the other the response sent back to the originator.
Fmt Description
M Mandatory
O Optional (i.e. may be left blank with spaces)
C Conditional. May be mandatory depending on other criteria
Om Omit field
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

2. Card Activation
Typically, cards are issued in an inactive state. Therefore, cardholder will have to ensure the new card is activated before the card may be used. The following are the fields needed
by FIS Web Services to activate a card:
2.1. Record Description

Card Activation Message
Tag Type Min Length Max Length Description Request Response
<messageID> N 1 10 Message ID. Should be unique for every message request sent on a particular M M
date.
<instCode> AN 1 4 Name of the issuing financial institution M M
<title> AN 1 4 Customer’s title. O Om

Sending a ‘space’ will clear this field.
<lastName> AN 1 20 Customer’s last name. O Om

This must be present in order to update personal details such as address and
telephone number.
Sending a ‘space’ will clear this field. If <lastName> is cleared, <firstName> will
automatically be cleared.
<firstName> AN 1 20 Customer’s first name. C Om

Mandatory if <lastName> is present and the value of <actMethod> is not ‘6’.
This is updated only if <lastName> is present.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Sending a ‘space’ will clear this field. If <firstName> is cleared, <lastName> will
automatically be cleared.
<DOB> YYYY-MM- 10 10 Date of Birth. C Om

DD
Mandatory if value of <actMethod> is ‘1’. In this case it will be used for
authentication only.
Otherwise, if <actMethod> is not ‘1’ and <lastName> has been provided, this
sets the cardholder’s date of birth.
If age-verification is configured and conditions are met, the <crdProduct>
associated with the card will be changed. Refer to the <crdProduct> field
description in the Cardholder Update message for the impact of this change.
<addrl1> AN 1 35 Address Line 1 C Om

Mandatory if ‘Address’ fields are being specified.
Sending a ‘space’ will clear this field and will also clear <addrl2>, <addrl3>,
<city>, <county>, <postCode>, <country> and <tel>.
<addrl2> AN 1 35 Address Line 2 O Om

Can only be updated if <lastName> is present.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<city> AN 1 20 Home city C Om

Mandatory if <addrL1> is present, and <postcode> is not present.
Can be cleared by sending a space but see restrictions above.
<county> AN 1 20 County O Om
<postCode> AN 1 10 Post Code C Om

Must have a value if <addrL1> is present, and <city> is not present.
<country> AN 1 3 Country of Residence. This is represented as an ISO country code: C Om

e.g.
826: UK
372: Ireland
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


840: US
250: France
276: Germany
724: Spain
124: Canada
Mandatory if <addrL1> is present.
Can be changed (only if <lastName> is present) but cannot be cleared (unless
ADDRL1 is cleared, in which case all address fields will be cleared).
<txnType> AN 1 2 The Transaction Type. See Appendix C M M
<actMethod> AN 1 1 Method used for card activation - refer to Appendix D. M Om
<PAN> AN 16 19 Card Number. C C

Must be in the response if present in the request.
The PAN can be configured at institution code level to be masked in the
response.
If not present, <track2> or <cardID> must be provided.
<cardID> AN 16 19 Unique internal card identification number. C C

Present in response if present in the request. Cannot be sent in response when
not in request and cannot be derived from the PAN/Track2.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


If not present <track2> or <PAN> must be provided.
<CVV> AN 3 3 Card Verification Value, the 3-digit code printed on the back of the card. C Om
Mandatory if the value of <actMethod> is ‘2’
<track2> AN 1 40 The card’s Track 2. C C

Mandatory in request and response if neither <PAN> nor <cardID> is present
or when <actMethod> is ‘4’
<accessCode> AN 1 12 Access code. Mandatory if the value of <actMethod> is ‘3’. C Om

Mandatory if <actMethod> is ‘3’. In this case the provided access code is used
for authentication only.
If <actMethod> is not ‘3’ and <lastName> has been provided, the stored value
is updated.
<expDate> YYYY-MM- 10 10 Expiry Date. O Om

DD
<localDate> YYYY-MM- 10 10 The current date M M

DD
<localTime> HHMMSS 6 6 The current time M M
<loginID> AN 1 64 Login ID of the customer using the service. Only applicable to systems using O C
customer logins.
Returned in the response if present in the request
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<reason>1 AN 1 60 Reason for card status change. The default value is ‘Card Activated’. O Om
Card activation will change the card status from ‘Inactive’ to ‘Normal’.
<itemSrc> AN 1 2 Source field to define alternate fees. It is used in conjunction with existing fee O Om
server Item
Defined options:
1 - Call Centre (used by Panorama)
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<userdata> AN 1 30 Sets a member defined cardholder information field, which is stored at card O Om
level. This is a free text field.
This field can be cleared by sending a space.
<userdata1> AN 1 12 Sets a member defined cardholder information field, which is stored at O Om

customer level. This is a free text field.
1
This tag is extracted into the Card Status Change Report.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100





<crdproduct> AN 1 4 Sets the card product associated with the card. O Om
<designRef> AN 1 8 Sets the design this card associated with the card. O Om
<tel> AN 1 20 Telephone number. O Om

Cortex can format the number based on country. Currently the supported
countries are UK and Australia.
Cortex can be configured to process telephone numbers as follows. If it is not
configured, telephone numbers are stored as received:
Note: The following rules are applicable to the UK only.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1. Strips all special characters, including spaces, left parenthesis, right
parenthesis, and hyphen (-).
2. Strip all leading non-numeric characters (except +). Non-leading non-
numeric characters are not removed.
3. Depending on the country (currently only UK), the international dialling
prefix (e.g. double zeros for UK) is converted to "+".
e.g. 00 33 77 1234567 is converted to +33771234567
4. Depending on the country (currently only UK), the national dialling prefix
(e.g. single zero for UK) is dropped and "+" and the IDD number is prefixed.
e.g. 020 7292 2400 to +442072922400
5. If there is a "+" prefix, Cortex checks if the following numbers match the IDD
number of specified country (UK only currently). If they don’t match, nothing is
done. If they do match, it checks if the following numbers match the national
dialling prefix (e.g. single zero for UK). If they do match, it drops them.
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
6. If there is no leading “+” or national dialling prefix, the number is stored as it
is.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<mobTel> AN 1 20 Mobile telephone number. O Om

configured, telephone numbers are stored as received. However, this
processing is required for using SMS services.
2. Rejects any numbers containing non-numeric characters with the exception
of the prefix “+”.
e.g. 020 7292 2400 to +442072922400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
6. If there is no "+" prefix, international dialling prefix or national dialling
prefix, the number is rejected.
This field can be changed and it can be cleared by sending a space.
<secDet> - - - See SECURITY DETAIL section below. C Om

Mandatory if the value of <actMethod> is ‘5’.
Can occur multiple times within the message.
<sysDate> YYYY-MM- 10 10 The Cortex processing system date. This date is used for reconciliation Om M
DD
<actionCode> AN 3 3 The action code for the response Om M
SECURITY DETAIL BEGINS HERE
<charPos> N 1 2 Identifies the position in the stored security value to which secValue - -
corresponds. charPos 0 maps to the first character of the security value.
Used when the security check associated with the secChkID is for matching
character based verification in a security value, rather than the whole value.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


secChkID is normally mentioned in your member profile, so refer to this if you
would like to know if you are using full value or character based verification.
Mandatory if secChkID indicates character based verification, otherwise field
must be omitted.
<secChkID> N 1 8 Pre-defined security check identifier. - -

Cannot be empty.
<secValue> AN 1 64 Value associated with security secChkID. Each secValue must immediately - -
follow its associated secChkID.
If charPos is present, this field must contain a single character.
If <secValue> is ‘space’ and the security check type is “synchronized”, the
security data will be synchronized by card/customer data.
If <secValue> is ‘space’ and the security check type is normal, the security
value in the database will be ‘space’.
If <secValue> is empty when <action> is '6', the <secChkid>/ <secValue> pair
will be removed.
SECURITY DETAIL ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

2.2. Example
Note: The data in the following examples have been altered for security purposes. The examples give an accurate picture of what the message will look like. However, there may
be slight differences depending upon what data is included.
2.2.1.Request
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:cardActivation xmlns:ns1="urn:CardActivation" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<pobjCardActivationRqstInfo href="#id0" />
</ns1:cardActivation>
<multiRef xmlns:ns2="http://wsvalueobj.CardActivation.prepaid.webservices.cortex.com"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns2:CardActivationRqstInfo">
<messageID href="#id1" />
<instCode xsi:type="soapenc:string">TEST</instCode>
<title xsi:nil="true" xsi:type="soapenc:string" />
<lastName xsi:nil="true" xsi:type="soapenc:string" />
<firstName xsi:nil="true" xsi:type="soapenc:string" />
<DOB xsi:type="xsd:date">1982-01-01</DOB>
<addrl1 xsi:nil="true" xsi:type="soapenc:string" />
<city xsi:nil="true" xsi:type="soapenc:string" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<county xsi:nil="true" xsi:type="soapenc:string" />

<postCode xsi:nil="true" xsi:type="soapenc:string" />
<country xsi:nil="true" xsi:type="soapenc:string" />
<txnType xsi:type="soapenc:string">0</txnType>
<actMethod xsi:type="soapenc:string">1</actMethod>
<PAN xsi:type="soapenc:string">1111111111111111</PAN>
<CVV xsi:nil="true" xsi:type="soapenc:string" />
<track2 xsi:nil="true" xsi:type="soapenc:string" />
<accessCode xsi:nil="true" xsi:type="soapenc:string" />
<expDate xsi:nil="true" xsi:type="xsd:date" />
<localDate xsi:type="xsd:date">2008-12-10</localDate>
<localTime href="#id2" />
<loginID xsi:nil="true" xsi:type="soapenc:string" />
<reason xsi:nil="true" xsi:type="soapenc:string" />
<itemSrc xsi:nil="true" xsi:type="xsd:short" />
<secDet xmlns:ns3="http://wsvalueobj.common.prepaid.webservices.cortex.com" xsi:nil="true"
xsi:type="ns3:SecurityDetailsInfo" />
</multiRef>
<multiRef xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id2" soapenc:root="0"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:long">135409</multiRef>
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:int">1013</multiRef>
</soapenv:Body>
</soapenv:Envelope>
2.2.2.Response
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<soapenv:Body>
<ns1:cardActivationResponse xmlns:ns1="urn:CardActivation"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<cardActivationReturn href="#id0" />
</ns1:cardActivationResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardActivation.prepaid.webservices.cortex.com"
xsi:type="ns2:CardActivationRspsInfo">
<messageID xsi:type="xsd:int">1013</messageID>
<localTime xsi:type="xsd:long">135409</localTime>
<sysDate xsi:type="xsd:date">2008-10-17</sysDate>
<actionCode xsi:type="soapenc:string">000</actionCode>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

3. Card Load
The following are the fields needed by FIS Web Services to load a card with a given amount. Only cards in inactive status or cards already activated can have a ‘Card Load’ performed
upon them. A combined Activate/Load message is also available.

Card Load Message
date.

Mandatory in request and response if neither <cardID> nor <PAN> is present
or when the value of <authMethod> is ‘7’
<authMethod> AN 1 1 Method used for cardholder authentication - refer to Appendix E. M Om

Note that method 5 (loginID) is not possible in this message
<PAN> AN 16 19 Card Number C C

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

If not present, <cardID> or <track2> must be provided.

<DOB> YYYY-MM- 10 10 Date of Birth. Mandatory if the value of <authMethod> is ‘2’ or ‘6’ C Om
DD
<CVV> AN 3 3 CVC2. Mandatory if the value of <authMethod> is ‘3’ C Om
<accessCode> AN 1 12 Access Code. C Om

Mandatory if the value of <authMethod> is ‘4’
<lastName> AN 1 20 Customer’s last name C Om


DD
<crdAcptID> AN 1 15 Card Acceptor Identification O Om
<amtLoad> D 1 20 The amount to load onto the card. M M

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

<currCode> AN 3 3 Alpha currency code of the amount to load. This must match the card’s M Om
currency or the action will fail
customer logins.
<loadFundsType> AN 1 3 Payment method of funds for the load: O Om

0 – Unknown
1 – Cash
2 – Debit card
3 – Credit card
4 – Import
5 – Saving stamps
6 – Cheque
12 – Wallet
<loadSrc> AN 1 3 The source of the load request: O Om

0 – Unknown
2 – Generic Web Service
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
7 - Post Office
8 – Agent
9 – Head Office
10 – Call Centre
11 – In-store
12 - EPAY

Mandatory if the value of <authMethod> is ‘8’.
<walletRef> AN 1 32 Wallet reference. O O

If this is not present for wallet loads, the wallet is created with an empty
reference.
<additionalTxnDet> - - - Additional transaction details O Om

See ADDITIONAL TRANSACTION DETAIL section below.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

<effectiveDate> YYYY-MM- 10 10 Effective date for the wallet. O Om

DD
If this is left blank for a wallet load, the current date is used.
<effectiveTime> HHMMSS 6 6 Effective time for the wallet. O Om

If this is left blank for a wallet load, the current time is used.
<expiryDate> YYYY-MM- 10 10 Expiry date for the wallet. O Om

DD
<expiryTime> HHMMSS 6 6 Expiry time for the wallet O Om
<walletProfileRef> AN 1 32 Wallet profile reference. C Om

This is mandatory for wallet loads when a new wallet is created.
<walletID> N 1 10 Wallet ID. This is used as an alternative to <walletRef> for wallet reloads. O O
<termCode> AN 1 16 Identification code of acquiring terminal O Om
<rev> AN 1 1 Indicates if this is a load reversal message. Possible options: O C

0 – False
1 – True
If the value is 1, the Item ID of the load to be reversed is specified in
<orgItemId>.
Mandatory in response if present in request.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<orgItemId N 1 10 The item ID of the transaction to be reversed. C C

Mandatory in request for reversal messages i.e. where <rev> = 1. Mandatory in
response if present in request.
DD
<itemId> N 1 10 The unique item ID returned for this Load Om M
<description> AN 1 40 Description of balance adjustment. Will appear in Account Enquiry. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

<billConvRate> D 1 8 The conversion rate used to calculate the billing amount amtBill from the Om M
transaction amount amtTxn.
billConvRate = amtTxn/amtLoad
A default value of 1 will be sent in response when curBill is same as curTxn or if
curTxn not provided.
<amtTxn> D 1 20 The transaction amount, given in the transaction currency. O C

Used when the load request is required for a specific transaction.
<curTxn> AN 1 3 The alpha transaction currency code. O C

ADDITIONAL TRANSACTION DETAIL BEGINS HERE
<reference> AN 1 32 Reference Code for additional data M Om
<value> AN 1 255 Additional data for the reference above. M Om
ADDITIONAL TRANSACTION DETAIL ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Load Message

must be omitted.
3.2. Example
3.2.1.Request
<soapenv:Body>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<ns1:cardLoad xmlns:ns1="urn:CardLoad" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<pobjCardLoadRqstInfo href="#id0" />
</ns1:cardLoad>
<multiRef xmlns:ns2="http://wsvalueobj.CardLoad.prepaid.webservices.cortex.com"
xsi:type="ns2:CardLoadRqstInfo">
<authMethod xsi:type="soapenc:string">1</authMethod>
<DOB xsi:nil="true" xsi:type="xsd:date" />
<crdAcptID xsi:nil="true" xsi:type="soapenc:string" />
<amtLoad href="#id3" />
<currCode xsi:type="soapenc:string">GBP</currCode>
<loadFundsType xsi:nil="true" xsi:type="soapenc:string" />
<loadSrc xsi:nil="true" xsi:type="soapenc:string" />
</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:double">2.0</multiRef>
</soapenv:Body>
</soapenv:Envelope>
3.2.2.Response
<soapenv:Body>
<ns1:cardLoadResponse xmlns:ns1="urn:CardLoad" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<cardLoadReturn href="#id0" />
</ns1:cardLoadResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardLoad.prepaid.webservices.cortex.com"
xsi:type="ns2:CardLoadRspsInfo">
<itemId xsi:type="soapenc:string">63471</itemId>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

4. Status Change
To change the status of a card from an activated state to a cancelled, lost, stolen or damaged state. In other words the status change call can used to de-activate the card.
This Web Service may also be used to set a Card Status back to normal if the status had been changed previously for a temporary period of time. For example, it can be used to reset
the number of PIN tries for cards that have the status ‘PIN Tries Exceeded’.

Status Change Message
date.

response.
If not present <track2> or <cardID> must be provided.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



or when the value of <authMethod> is ‘7’.

Note that method 5 (loginID) is not possible in this message.
DD



DD
<newStatCode> AN 2 2 New status code. (See Appendix A) M Om

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
<reason> AN 1 60 Reason for Status Change. O Om

Overrides default of ‘Card Status Change’ that will be shown in Panorama.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


DD
must be omitted.
4.2. Example
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

4.2.1.Request
<soapenv:Body>
<ns1:statusChange xmlns:ns1="urn:StatusChange" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<pobjStatusChangeRqstInfo href="#id0" />
</ns1:statusChange>
<multiRef xmlns:ns2="http://wsvalueobj.StatusChange.prepaid.webservices.cortex.com"
xsi:type="ns2:StatusChangeRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<newStatCode xsi:type="soapenc:string">01</newStatCode>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
4.2.2.Response
<soapenv:Body>
<ns1:statusChangeResponse xmlns:ns1="urn:StatusChange"
<statusChangeReturn href="#id0" />
</ns1:statusChangeResponse>
<multiRef xmlns:ns2="http://wsvalueobj.StatusChange.prepaid.webservices.cortex.com"
xsi:type="ns2:StatusChangeRspsInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

5. Balance Enquiry
The Balance Enquiry returns the card balance.

Balance Enquiry Message
date.

response.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


DD




DD
<loginID> AN 1 64 Login ID of the customer using the service. Only applicable to systems using C C
customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Mandatory if the value of <authMethod> = 5
<itemSrc> N 1 5 Source field to define alternate fees. It is used in conjunction with existing fee O Om
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 – SecureCode

<avlBal> D 1 20 Balance of the card account. This includes all financials but ignores outstanding Om M
authorisations
<blkAmt> D 1 20 Amount of funds blocked on the card account as a result of all outstanding Om M
authorisations
<currCode> AN 3 3 Alpha currency Code of the balance returned Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


DD
<otbAmt> D 1 20 Open To Buy amount for the card account which is usually available balance Om M
minus the blocked amount.
must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

5.2. Example
5.2.1.Request
<soapenv:Body>
<ns1:balanceEnquiry xmlns:ns1="urn:BalanceEnquiry" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<pobjBalanceEnquiryRqstInfo href="#id0" />
</ns1:balanceEnquiry>
<multiRef xmlns:ns2="http://wsvalueobj.BalanceEnquiry.prepaid.webservices.cortex.com"
xsi:type="ns2:BalanceEnquiryRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</multiRef>
</soapenv:Body>
</soapenv:Envelope>
5.2.2.Response
<soapenv:Body>
<ns1:balanceEnquiryResponse xmlns:ns1="urn:BalanceEnquiry"
<balanceEnquiryReturn href="#id0" />
</ns1:balanceEnquiryResponse>
<multiRef xmlns:ns2="http://wsvalueobj.BalanceEnquiry.prepaid.webservices.cortex.com"
xsi:type="ns2:BalanceEnquiryRspsInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<avlBal xsi:type="xsd:double">128.56</avlBal>
<blkAmt xsi:type="xsd:double">35.44</blkAmt>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

6. Account Enquiry
Transactions performed by the cardholder are returned along with a starting balance and current balance.

Account Enquiry Message
date.

The PAN can be configured at institution code level to be masked
in the response.
If not present <track2> or <cardID> must be provided

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



DD



DD
<txnFilter> AN 1 1 Filter method to control the type of account entries returned: O C

0 – All account entries.
Includes redemption transactions (including refunds and reversals), loads,
unloads, transfers, balance adjustments, account status changes and fees.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Also includes pending authorisations & authorisation unblocks (expired
authorisations - available only through configuration, matched (with a
financial) authorisations, and manually cleared authorisations).
1 – Account entries affecting the account balance/available funds: as ‘0’, but
excludes authorisation unblocks and account status changes.
2 – Financial entries only: as ‘0’, but excludes pending authorisations,
authorisation unblocks, and account status changes.
If the field is not present, zero (All entries) is selected by default. The field
must be present in the response if present in the request
<startDate> YYYY-MM- 10 10 Start date for the Enquiry. Only account entries on this day and beyond will be O C
DD returned.
If not specified and if <numTxns> is not present, the search will return results
from the first account entry. These results will be sorted in ascending order of
<itemID>.
The field will be present in the response if appears in the request
<endDate> YYYY-MM- 10 10 End date for the Enquiry. Only account entries on this day and before will be O C
DD returned.
If not specified and if <numTxns> is not present, the search will return results
up to the last account entry. These results will be sorted in ascending order of
<itemID>.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
<numTxns> N 1 4 Number of transactions to return. Used for requesting a specific number of O M

the most recent transactions. The transactions will be sorted in descending
order of <itemID>.
If present, <startDate> and <endDate> are ignored.
In the response, this field will indicate the actual number of transactions
returned.
<dataSrc> N 1 1 The data source to be used to make the Account Enquiry. M Om

It has two predefined values:
0 - Main Datasource
1- Archive Datasource
Note: This is present only in the request.
server Item
Defined options:
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

<inclDeclined> N 1 1 To request the inclusion of declined transactions in the response O Om

It has two predefined values:
0 – Do not include declined transactions
1 – Include declined transactions
If not present, declined transactions will be excluded.
<startBal> D 1 20 The opening balance of the card account for the period required, ignoring Om M
outstanding authorisations. For Multicurrency Cards, this will contain the
accumulated balance in the default currency.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<endBal> D 1 20 The closing balance of the card for the period required, ignoring outstanding Om M
authorisations. For Multicurrency Cards, this will contain the accumulated
balance in the default currency.
<curBill> AN 1 3 The cardholder account (billing) currency, represented in the alphabetic ISO Om M
code.
<txnDesc> - - - See TRANSACTION DESCRIPTION definition below. Om O

<multiCurAmounts> - - - See MULTI CURRENCY AMOUNTS definition below. Only for Multicurrency Om O
cards.
<avlBal> D 1 20 Balance of the card account. This includes all financials but ignores outstanding Om M
balance in the default currency.
blocked amount in the default currency.
DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
TRANSACTION DESCRIPTION BEGINS HERE
<txnDate> YYYY-MM- 10 10 Calendar date on which CORTEX processed the transaction. Om M

DD
<postDate> YYYY-MM- 10 10 CORTEX business date on which CORTEX processed the transaction. Om M
DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Empty for non-financial account entries
<amtTxn> D 1 20 The transaction amount, expressed in the transaction currency Om O
<amtBill> D 1 20 The amount of the transaction billed (for financials) or blocked (for Om M
authorisations) to the cardholder account, expressed in the account currency
<curBill>
<avlBal> D 1 20 The balance on the card account at the time of this item. This includes all Om M
financial transactions, but ignores outstanding authorisations
<blkAmt> D 1 20 The amount of funds blocked amount on the card account at the time of this Om M
item, as a result of all outstanding authorisations
<debOrCred> AN 1 1 ‘0’ – Debit Om M

‘1’ – Credit
<crdAcptID> AN 1 15 Card Acceptor Identification Om C
<RRN> AN 1 12 Reference Number Om O
<curTxn> AN 1 3 Transaction currency, represented in the alphabetic ISO code. Om O
<description> AN 1 40 Transaction description Om M
<itemId> N 1 10 The item ID. Present in all returned items that impact the funds on the Om C
account.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<billConvRate> D 1 8 The conversion rate used to calculate the billing amount amtBill from the Om C
billConvRate = amtTxn / amtBill
<itemType> AN 1 2 The type of the item: Om C

0 – Load
1 – Unload
2 – Financial transaction
3 – Authorisation transaction, pending (currently blocking funds)
4 – Authorisation unblock (no longer blocking funds)
5 – Fee (financial)
6 – Balance Adjustment
7 – Fee (on pending authorisation, currently blocking funds)
8 – Account status change
<txnTime> N 6 6 Time at which CORTEX processed the transaction. Om M
<tlogID> N 1 10 The unique CORTEX-identifier of all network-received transactions. Om C

Applicable to net-work-received transactions only.
<messageID> N 1 10 Member identifier for all Web Service-received transactions. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Applicable to Web Service-received transactions only.
<localDate> YYYY-MM- 10 10 Calendar date the transaction was generated by the terminal (POS/ATM) or Om C
DD acquirer.
Applicable to network-received transactions only.
<PAN> AN 16 19 Card Number Om M

response.
<CardID> AN 16 19 Unique internal card identification number. Om O
<feeID> N 1 4 Specifies the type of the Cardholder fee when applicable. Om O

‘Appendix F - Fee Identifiers’, contains a full list of applicable types.
<txnSubCode> N 1 1 Transaction Sub Code. Possible values are: Om O

0 = Unknown
1 = MasterCard rePower (this value is no longer used and future rePower
transactions will use a value of 4)
2 = Visa Mobile Gateway Transaction
3 = Offline Transaction
4 = Immediate Payment Transaction
5 = Incremental Auth
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


6 = Visa Fast Funds
<extCode> AN 1 20 External Code Om O
<mcc> N 1 5 Merchant Catalogue Code/Card Acceptor Business Code Om O
<reasonCode> N 1 5 Message reason code. Defined ISO 8583:93 A.7. Extended by card schemes. Om O
<rejectReason> N 1 5 Reject reason code. Internal Cortex code indicating exact cause for transaction Om O
rejection. Pls refer to the document CortexDataCodes.pdf for complete list of
valid codes with their descriptions.
<curBill> AN 1 3 Billing currency, represented in the alphabetic ISO code. Om O
TRANSACTION DESCRIPTION ENDS HERE
MULTI CURRENCY AMOUNTS BEGINS HERE
<curBill> AN 1 3 Account Currency Om M
<avlBal> D 1 20 The balance on the card account at the time of this request in account Om M
currency.
<blkAmt> D 1 20 The amount of funds blocked amount on the card account at the time of this Om M
request in account currency.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<otbAmt> D 1 20 Open To Buy amount for the card account which is usually available balance Om M
minus the blocked amount.
MULTI CURRENCY AMOUNTS ENDS HERE
6.2. Example
6.2.1.Request
<soapenv:Body>
<ns1:accountEnquiry xmlns:ns1="urn:AccountEnquiry" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<pobjAccountEnquiryRqstInfo href="#id0" />
</ns1:accountEnquiry>
<multiRef xmlns:ns2="http://wsvalueobj.AccountEnquiry.prepaid.webservices.cortex.com"
xsi:type="ns2:AccountEnquiryRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<txnFilter xsi:nil="true" xsi:type="soapenc:string" />
<startDate xsi:nil="true" xsi:type="xsd:date" />
<endDate xsi:nil="true" xsi:type="xsd:date" />
<numTxns href="#id3" />
<dataSrc xsi:nil="true" xsi:type="xsd:short" />
</multiRef>
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:short">2</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</soapenv:Body>
</soapenv:Envelope>
6.2.2.Response
<soapenv:Body>
<ns1:accountEnquiryResponse xmlns:ns1="urn:AccountEnquiry"
<accountEnquiryReturn href="#id0" />
</ns1:accountEnquiryResponse>
xsi:type="ns2:AccountEnquiryRspsInfo">
<PAN xsi:type="soapenc:string">111111******1111</PAN>
<startBal xsi:type="xsd:double">141.56</startBal>
<endBal xsi:type="xsd:double">128.56</endBal>
<txnDesc soapenc:arrayType="ns2:TransactionDescriptionInfo[2]" xsi:type="soapenc:Array">
<txnDesc href="#id1" />
<txnDesc href="#id2" />
</txnDesc>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<txnFilter xsi:nil="true" xsi:type="soapenc:string" />

<startDate xsi:nil="true" xsi:type="xsd:date" />
<endDate xsi:nil="true" xsi:type="xsd:date" />
<curBill xsi:type="soapenc:string">GBP</curBill>
<numTxns xsi:type="xsd:short">2</numTxns>
</multiRef>
xsi:type="ns3:TransactionDescriptionInfo">
<txnDate xsi:type="xsd:date">2008-09-11</txnDate>
<postDate xsi:nil="true" xsi:type="xsd:date" />
<amtTxn xsi:type="xsd:double">5.0</amtTxn>
<amtBill xsi:type="xsd:double">5.0</amtBill>
<debOrCred xsi:type="soapenc:string">0</debOrCred>
<crdAcptID xsi:type="soapenc:string">11111111</crdAcptID>
<RRN xsi:type="soapenc:string">1111111111</RRN>
<curTxn xsi:type="soapenc:string">GBP</curTxn>
<description xsi:type="soapenc:string">Auth: SHELL,M1 MOTORWAY,GBR</description>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<itemType xsi:type="soapenc:string">3</itemType>
<billConvRate xsi:type="xsd:double">1.0</billConvRate>
<txnTime xsi:type="xsd:long">132030</txnTime>
<tlogID xsi:type="xsd:long">111111</tlogID>
<feeID xsi:nil="true" xsi:type="xsd:short" />
<txnSubCode xsi:nil="true" xsi:type="xsd:int" />
</multiRef>
xsi:type="ns4:TransactionDescriptionInfo">
<postDate xsi:type="xsd:date">2008-10-16</postDate>
<debOrCred xsi:type="soapenc:string">0</debOrCred>
<crdAcptID xsi:type="soapenc:string">11111111</crdAcptID>
<RRN xsi:type="soapenc:string">111111111111</RRN>
<curTxn xsi:type="soapenc:string">GBP</curTxn>
<description xsi:type="soapenc:string">Fin: MORRISONS,BIRMINGHAM,GBR</description>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<itemType xsi:type="soapenc:string">2</itemType>
<billConvRate xsi:type="xsd:double">1.0</billConvRate>
<feeID xsi:nil="true" xsi:type="xsd:short" />
<curBill xsi:type="soapenc:string">GBP</curTxn>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

7. Card List Enquiry

The Card List Enquiry message returns the list of cards related to a particular loginID, PAN or account (accno). A customer may have several roles relating to a card, namely:
purchaser, cardholder, and loader. This message will return all associated cards grouped by role.

Card List Enquiry Message
date.

DD
customer logins.
Login ID is used to differentiate between a 'cardholder' and a 'purchaser' i.e. it
allows a card to have two types of ‘owners’. Purchasers can see all cards they
purchased while cardholders can only see the ones they hold themselves.
Mandatory if neither <PAN>, <cardID>, <accno>, <userdata1>,
<additionalAccdet> nor <additionaCustdet> are provided.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Returned in the response if present in the request.

Mandatory if neither <loginID>, <cardID>, <accno>, <userdata1>,
response.

Mandatory if neither <PAN>, <Track2>, <loginID>, <accno>, <userdata1>,
not in request and cannot be derived from the
PAN/Track2/loginID/accno/userdata1/additionalAccdet/additionaCustdet.
<accno> AN 1 28 Account number of the card C C

Mandatory if neither <PAN>, <cardID>, <loginID>, <userdata1>,
<currCode> AN 3 3 The card currency alpha code C C
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Mandatory if <accno> is provided.
<userdata1> AN 1 30 A member-defined cardholder information field, which is stored at card level. C C

This is used to retrieve the card list.
Mandatory if neither <PAN>, <cardID>, <accno>, <loginID>, <additionalAccdet>
nor <additionaCustdet> are provided.
Present in the response if present in the request.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<purchaserCardList> - - - See Card List structure below Om O
<cardHolderCardList> - - - See Card List structure below Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<loaderCardList> - - - See Card List structure below Om O
DD
<additionalCustDet> - - - Additional customer details O Om

Mandatory if neither <PAN>, <cardID>, <accno>, <userdata1>,
<additionalAccdet> nor <loginID> are provided.
See ADDITIONAL CUSTOMER DETAIL section below.
<additionalAccDet> - - - Additional account details O Om

Mandatory if neither <PAN>, <cardID>, <accno>, <userdata1>, <loginID> nor
<additionaCustdet> are provided.
See ADDITIONAL ACCOUNT DETAIL section below.
CARD LIST BEGINS HERE
<PAN> AN 16 19 Card Number. Om M

response.
<cardID> AN 16 19 Unique internal card identification number. Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<expDate> YYYY-MM- 10 10 Expiry Date of the card Om M

DD
<currCode> AN 3 3 The card currency alpha code Om M
<statCode> AN 2 2 The status of the card Om M
<crdProduct> AN 4 4 The Product this card corresponds to Om M
<program> AN 1 6 The Program this card corresponds to Om O
<designRef> AN 1 8 The Design this card corresponds to Om O
<avlBal> D 1 20 The current balance on the card account. This includes all financial transactions, Om M
but excludes authorisations
<blkAmt> D 1 20 The current blocked amount on the card account. This comprises all Om M
outstanding authorisations
<firstName> AN 1 20 Cardholder’s first name Om M
<lastName> AN 1 20 Cardholder’s last name Om M
<embossName> AN 1 21 or 27 Name embossed on the card. Om M

Note: The maximum length may vary depending on scheme regulations and the
card design. For example, for MasterCard no information can be embossed over
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


the MasterCard logo, which means a maximum length of 21 if the logo is in the
bottom right corner of the card design.
<custType> D 1 1 Identifies the owner of the card: Om M

0 – primary customer
1 – additional customer (authorised user)
<accno> AN 1 28 Card Account Number Om O
<pinTries> N 1 1 The number of PIN tries. Om O

The value reflects the number before the status of the card is changed to 01.
Once the status changes, PIN tries are no longer recorded.
<accessCode> AN 1 12 Access Code for the card. Only returned in response for internaly configured Om C
customers
<additionalCustDet> - - - Additional customer details Om C

See ADDITIONAL CUSTOMER DETAIL section below.
Additional card details
<additionalCrdDet> - - - Om C
See ADDITIONAL CARD DETAIL section below.
CARD LIST ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


ADDITIONAL CUSTOMER DETAIL BEGINS HERE
ADDITIONAL CUSTOMER DETAIL ENDS HERE
ADDITIONAL ACCOUNT DETAIL BEGINS HERE
<reference> AN 1 32 Reference Code for additional data - -
<value> AN 1 255 Additional data for the reference above. - -
ADDITIONAL ACCOUNT DETAIL ENDS HERE
ADDITIONAL CARD DETAIL BEGINS HERE
ADDITIONAL CARD DETAIL ENDS HERE
7.2. Example
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

7.2.1.Request
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:urn="urn:CardListEnquiry"> >
<soapenv:Body>
<urn:cardListEnquiry soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/>
<pobjWSCardListEnquiryRqstInfo xsi:type="wsv:CardListEnquiryRqstInfo"
xmlns:wsv="http://wsvalueobj.CardListEnquiry.prepaid.webservices.cortex.com">
<messageID>9838</messageID>
<instCode>ACL</instCode>
<txnType>5</txnType>
<cardID xsi:type="soapenc:string">7838374070692555</cardID>
<localDate>2012-01-27</localDate>
<localTime>223208</localTime>
<itemSrc>5</itemSrc>
</pobjWSCardListEnquiryRqstInfo>
</soapenv:Body>
</soapenv:Envelope>
7.2.2.Response
<soapenv:Body>
<ns1:cardListEnquiryResponse soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/
xmlns:ns1="urn:CardListEnquiry">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<cardListEnquiryReturn xsi:type="ns2:CardListEnquiryRspsInfo"
xmlns:ns2="http://wsvalueobj.CardListEnquiry.prepaid.webservices.cortex.com">
<instCode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">ACL</instCode>
<txnType xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">5</txnType>
<purchaserCardList soapenc:arrayType="ns2:CardListInfo[0]" xsi:type="soapenc:Array"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"/>
<cardHolderCardList soapenc:arrayType="ns2:CardListInfo[1]" xsi:type="soapenc:Array"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<cardHolderCardList xsi:type="ns2:CardListInfo">
<expDate xsi:type="xsd:date">2011-12-31</expDate>
<statCode xsi:type="soapenc:string">07</statCode>
<crdProduct xsi:type="soapenc:string">ADLT</crdProduct>
<program xsi:type="soapenc:string">BLISS</program>
<designRef xsi:type="soapenc:string">UACB</designRef>
<firstName xsi:type="soapenc:string">PROCESSING</firstName>
<lastName xsi:type="soapenc:string">SERVICES</lastName>
<embossName xsi:type="soapenc:string">PROCESSING SERVICES</embossName>
<custType xsi:type="xsd:int">0</custType>
<accno xsi:type="soapenc:string">BLISS064532300</accno>
<pinTries xsi:type="xsd:int">0</pinTries>
additionalCustDet soapenc:arrayType="ns3:AdditionalDetails[11]" xsi:type="soapenc:Array"
xmlns:ns3="http://wsvalueobj.common.prepaid.webservices.cortex.com">
<additionalCustDet xsi:type="ns3:AdditionalDetails">
<reference xsi:type="soapenc:string">ACL_PASSPORTNO</reference>
<value xsi:type="soapenc:string">981080157</value>
</additionalCustDet>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<reference xsi:type="soapenc:string">ACL_UKDVL</reference>
<value xsi:type="soapenc:string" xsi:nil="true"/>
<reference xsi:type="soapenc:string">ACL_WHERE_HEARD_ABOUT</reference>
<reference xsi:type="soapenc:string">CPFRULES</reference>
<reference xsi:type="soapenc:string">FRT_KYC_RSP_REF</reference>
<reference xsi:type="soapenc:string">FRT_KYC_RSP_RESULT</reference>
<reference xsi:type="soapenc:string">GRG_CONS_CUSTEXT_REF</reference>
<reference xsi:type="soapenc:string">KYC_DONE_BY</reference>
<reference xsi:type="soapenc:string">RATEFEE</reference>
<value xsi:type="soapenc:string"/>
<reference xsi:type="soapenc:string">TST2</reference>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<additionalCrdDet soapenc:arrayType="ns4:AdditionalDetails[6]" xsi:type="soapenc:Array"
<additionalCrdDet xsi:type="ns4:AdditionalDetails">
<reference xsi:type="soapenc:string">CTX_CRD_MCIC_CPNID</reference>
</additionalCrdDet>
</additionalCrdDet>
</additionalCrdDet>
<value xsi:type="soapenc:string"/>
</additionalCrdDet>
</additionalCrdDet>
</additionalCrdDet>
</additionalCrdDet>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</cardHolderCardList>
</cardHolderCardList>
<loaderCardList soapenc:arrayType="ns2:CardListInfo[0]" xsi:type="soapenc:Array"
<loginID xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"/>
<PAN xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">675915******1294</PAN>
<cardID xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">7838374070692555</cardID>
<accno xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"/>
<currCode xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"/>
<userdata1 xsi:type="soapenc:string" xsi:nil="true"
<actionCode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">000</actionCode>
</cardListEnquiryReturn>
</ns1:cardListEnquiryResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

8. Load Verification
The Load Verification message allows checking if a load operation is allowed for a particular card, by verifying that that the card exists, the status is correct, the card is not expired,
the proposed load amount will not put the card over the maximum balance assigned to it, and will not exceed any limits. This message will normally happen prior to a Card Load
message.

Load Verification Message
date.


response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



DD

<lastName> AN 1 20 Last name of customer. C Om


DD
customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<maxLoad> D 1 20 The maximum load amount allowed for the card Om M

0 – Unknown
1 – Cash
2 – Debit card
3 – Credit card
4 – Import
5 – Saving stamps
6 – Cheque
12 – Wallet
The default value is 0.

0 – Unknown
3 – IVR
4 – Website
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


5 – Paypoint
6 – Payzone
7 - Post Office
8 – Agent
9 – Head Office
10 – Call Centre
11 – In-store
12 – EPAY
The default value is 0.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 – SecureCode
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



DD
<amtLoad> D 1 20 The amount to load onto the card. O Om

Currency of the amount to load. This must match the card’s currency or the
<currCode> AN 3 3 C Om
action will fail.
Mandatory if <amtLoad> is provided.

Defined Options
<verificationType> AN 1 3 O Om
0 –load verification for card in the request ( default)
1 –load verification for prospective additional card application for the card in
the request
If not present, 0 is assumed as the default value

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
8.2. Example
8.2.1.Request
<soapenv:Body>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<ns1:loadVerification xmlns:ns1="urn:LoadVerification"
<pobjLoadVerificationRqstInfo href="#id0" />
</ns1:loadVerification>
<multiRef xmlns:ns2="http://wsvalueobj.LoadVerification.prepaid.webservices.cortex.com"
xsi:type="ns2:LoadVerificationRqstInfo">
</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</soapenv:Body>
</soapenv:Envelope>
8.2.2.Response
<soapenv:Body>
<ns1:loadVerificationResponse xmlns:ns1="urn:LoadVerification"
<loadVerificationReturn href="#id0" />
</ns1:loadVerificationResponse>
<multiRef xmlns:ns2="http://wsvalueobj.LoadVerification.prepaid.webservices.cortex.com"
xsi:type="ns2:LoadVerificationRspsInfo">
<maxLoad xsi:type="xsd:double">0.0</maxLoad>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

9. Card Transfer
The Card Transfer message enables the transfer of a specific amount, or the full balance, from one card onto another. Can principally occur when a card has been damaged or lost
and a replacement is required. A separate transaction type exists which will modify the status to lost/stolen/damaged and subsequently transfer the balance to a new, whilst also
activating the new card.
This message merely performs the transfer.
Note: Transfers can be performed from a card which has been marked as lost/stolen but only if configured to do so.
Note: Transfers are subject to load limit checking if this is configured. Load limit checking is set at institution level.

Card Transfer Message
date.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


response.

<newCardID> AN 16 19 Unique internal card identification number. C C


<DOB> YYYY-MM- 10 10 Date of Birth. Mandatory if the value of <authMethod> is ‘2’ C Om

DD

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




DD
<newPAN> AN 16 19 The new card number to where funds should be transferred. C C

The newPAN can be configured at institution code level to be masked in the
response.
customer logins.
<amtTransfer> D 1 20 The requested amount to transfer. If not present, it is assumed the full card O M
balance is requested to be transferred.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


If the amount is specified, this amount will be returned in the response.
Otherwise, the actual amount transferred (net of fees) is returned.
<currCode> AN 3 3 The Currency Code of the amtTransfer. C M

Must also be supplied in the request if an <amtTransfer> is specified
<loadSrc> AN 1 3 The source of the transfer request O Om

0 – Unknown
3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
8 – Agent
9 – Head Office
10 – Call Centre
server Item
Defined options:
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

<avlBal> D 1 20 The current balance on the card account. This includes all financial Om M
transactions, but excludes authorisations
DD
<itemId> N 1 10 The unique item ID for this Card Transfer. The ID returned is the ID relating to Om M
the ‘unload’ leg of the transfer, that is, the unload from the source card
<srcWalletRef> AN 1 32 The source wallet reference. O O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


This is used as an alternative to <srcWalletID> for wallet to wallet transfers.
<srcWalletID> N 1 10 Source wallet ID. O O

This is used as an alternative to <srcWalletRef> for wallet to wallet transfers.
<destWalletID> N 1 10 Destination wallet ID. O O

This is used as an alternative to <destWalletRef> for wallet to wallet transfers.
<destWalletRef> AN 1 32 The destination wallet reference. O O

This is used as an alternative to <destWalletID> for wallet to wallet transfers.
<destAmtTransfer> D 1 20 If present, this fixed amount is transferred to the destination account with out O Om
any forex ( if source and destination currency is different) and checks.
Requires destCurrCode.
<destCurrCode> AN 3 3 The Currency Code of the destAmtTransfer. O Om

Must also be supplied in the request if an <destAmtTransfer > is specified
If specified without destAmtTransfer, the amtTransfer is converted to
destCurrCode using forex and transferred for multi currency accounts.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
9.2. Example
9.2.1.Request
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<soapenv:Body>
<ns1:cardTransfer xmlns:ns1="urn:CardTransfer" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<pobjCardTransferRqstInfo href="#id0" />
</ns1:cardTransfer>
<multiRef xmlns:ns2="http://wsvalueobj.CardTransfer.prepaid.webservices.cortex.com"
xsi:type="ns2:CardTransferRqstInfo">
<newPAN xsi:type="soapenc:string">2222222222222222</newPAN>
<amtTransfer href="#id3" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</multiRef>
</soapenv:Body>
</soapenv:Envelope>
9.2.2.Response
<soapenv:Body>
<ns1:cardTransferResponse xmlns:ns1="urn:CardTransfer"
<cardTransferReturn href="#id0" />
</ns1:cardTransferResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardTransfer.prepaid.webservices.cortex.com"
xsi:type="ns2:CardTransferRspsInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<newPAN xsi:type="soapenc:string">222222******2222</newPAN>
<amtTransfer xsi:type="xsd:double">3.0</amtTransfer>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

10.Card Unload
A Card Unload enables the cardholder to redeem a specified value or the remaining balance on their card. It may be necessary and useful to cancel the card with a ‘Customer
Closed’ status. This is not possible in this transaction type, but can be performed in a transaction type described in section 4.
Note: The maximum amount that is available for unload is Available Balance minus Blocked Amount. Attempts to unload a higher amount are rejected.

Card Unload Message
date.

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Unload Message


<DOB> YYYY-MM- 10 10 Date of Birth. Mandatory if the value of <authMethod> is ‘2’ C Om

DD



This is used as an alternative to <walletID> if unloading wallets.
<walletID> N 1 10 Wallet ID. O O

This is used as an alternative to <walletRef> if unloading wallets.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Unload Message




DD
<amtUnload> D 1 20 The requested amount to unload. If not specified it is assumed the whole O M
amount remaining on the card has been requested.
Otherwise, the actual amount unloaded (net of fees) will be returned.
<currCode> AN 1 3 The card’s currency. Must be specified for multi-currency cards. Optional for C Om
single currency cards, if not provided the card currency will be used.
<loadSrc> AN 1 3 The source of the unload request O Om

0 – Unknown
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Unload Message

3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
8 – Agent
9 – Head Office
10 – Call Centre
<loadFundsType> AN 1 3 Payment method of funds for the unload: O Om

0 – Unknown
1 – Cash
2 – Debit card
3 – Credit card
12 – Wallet
customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Unload Message

server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<currCode> AN 3 3 The currency of the balance returned Om M
DD
<itemId> N 1 10 The unique item ID Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Card Unload Message

must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

10.2. Example
10.2.1. Request
<soapenv:Body>
<ns1:cardUnload xmlns:ns1="urn:CardUnload" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<in0 href="#id0" />
</ns1:cardUnload>
<multiRef xmlns:ns2="http://wsvalueobj.CardUnload.prepaid.webservices.cortex.com"
xsi:type="ns2:CardUnloadRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<amtUnload href="#id3" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
10.2.2. Response
<soapenv:Body>
<ns1:cardUnloadResponse xmlns:ns1="urn:CardUnload" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<cardUnloadReturn href="#id0" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</ns1:cardUnloadResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardUnload.prepaid.webservices.cortex.com"
xsi:type="ns2:CardUnloadRspsInfo">
<amtUnload xsi:type="xsd:double">10.0</amtUnload>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
Note: This will reverse a previous load message only and will not simply reverse a given amount.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

11.Card Activate/Card Load

Note that in case that <actMethod> = 5 and <authMethod> = 7, only one set of security details must be provided, this set will satisfy both the activation and the authentication.

Card Activate/Card Load Message
date.
<title> AN 1 4 Customer’s Title O Om

Mandatory if the value of <authMethod> = ‘6’
<firstName> AN 1 20 Customer’s Last Name C Om

Mandatory if <lastName> is present and the value of <authMethod> is not ‘6’.
<DOB> YYYY-MM- 10 10 Date of Birth. Mandatory if the value of <actMethod> is ‘1’ or <authMethod> is C Om
DD ‘2’ or ‘6’. Otherwise, will be updated as part of cardholder registration.
description in the Cardholder Update message for the impact of this change.
<addrl1> AN 1 35 Address Line 1 C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<city> AN 1 20 Home city C Om

<postCode> AN 1 10 Post Code C Om

Mandatory if <addrL1> is present, and <city> is not present.
<country> AN 1 12 Country of Residence. This is represented as an ISO country code: C Om

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<actMethod> AN 1 1 Method used for card activation - refer to Appendix D. M Om


response.

<CVV> AN 3 3 CVC2. Mandatory if the value of <actMethod> is ‘2’ or <authMethod> is ‘3’ C Om
<track2> AN 1 40 The Track 2. Can be used to activate the card. C C

or when the value of <actMethod> is ‘4’ or if <authMethod> is ‘7’.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<accessCode> AN 1 12 Access code. C Om

When used for activation: if <actMethod> is ‘3’, the provided access code is
used for activation only; the FIS stored value will not be updated.
When used for authentication, the provided access code cannot be used to
update the FIS stored value.
Mandatory if the value of <actMethod> is ‘3’ or <authMethod> is ‘4’.
<expDate> YYYY-MM- 10 10 Expiry Date. If not passed in the expiry date used from when the card was O Om
DD requested will be used

DD
<amtLoad> D 1 20 The amount to load onto the card. M M
<currCode> AN 3 3 Currency of the amount to load. This must match the card’s currency or the M Om
action will fail
customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



0 – Unknown
1 – Cash
2 – Debit card
3 – Credit card
12 – Wallet
<loadSrc> AN 1 3 The source of the load request O Om

0 – Unknown
3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
8 – Agent
9 – Head Office
10 – Call Centre
<reason> AN 1 60 Reason for card status change. O Om

Overrides default of ‘Card Activated’ that will be shown in Panorama.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<termCode> AN 1 16 Identification code of acquiring terminal. O Om
<designRef> AN 1 8 Sets the design associated with the card. O Om
<userdata> AN 1 30 Sets a member defined cardholder information field, which is stored at card O Om
level. This is a free text field.


+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100





configured, telephone numbers are stored as received.
e.g. 020 7292 2400 to +442072922400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400

If this is not present for wallet loads, the wallet is created with an empty
reference.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<effectiveDate> YYYY-MM- 10 10 Effective date for the wallet. O Om

DD
If this is left blank for a wallet load, the current date is used.
<effectiveTime> HHMMSS 6 6 Effective time for the wallet. O Om

If this is left blank for a wallet load, the current time is used.
<expiryDate> YYYY-MM- 10 10 Expiry date for the wallet. O Om

DD
<expiryTime> HHMMSS 6 6 Expiry time for the wallet O Om
<newCurrCode> N 1 1 Flag to indicate if a new currency code is to be used. Possible values are: O Om
0 – default value if not present. Existing currency in currCode field is used for
the account
1 – the account is updated to the currency code in currCode field
<walletProfileRef> AN 1 32 Wallet profile reference. C Om

This is mandatory for wallet loads when new wallet is created.
<walletID> N 1 10 Wallet ID. This can be used as an alternative to <walletRef> when reloading O O
wallets.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Mandatory if the value of <actMethod> is ‘5’ or if <authMethod> is ‘8’.
DD
<billConvRate> D 1 8 The conversion rate used to calculate the billing amount amtBill from the Om M
billConvRate = amtTxn/amtLoad
A default value of 1 will be sent in response when curBill is same as curTxn or if
curTxn not provided.
<amtTxn> D 1 20 The transaction amount, given in the transaction currency. O C

<curTxn> AN 1 3 The alpha transaction currency code. O C

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

11.2. Example
11.2.1. Request
<soapenv:Body>
<ns1:cardActivationLoad xmlns:ns1="urn:CardActivationLoad"
<pobjCardActivationLoadRqstInfo href="#id0" />
</ns1:cardActivationLoad>
<multiRef xmlns:ns2="http://wsvalueobj.CardActivationLoad.prepaid.webservices.cortex.com"
xsi:type="ns2:CardActivationLoadRqstInfo">
<title xsi:nil="true" xsi:type="soapenc:string" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<postCode xsi:nil="true" xsi:type="soapenc:string" />
<actMethod xsi:type="soapenc:string">2</actMethod>
<CVV xsi:type="soapenc:string">999</CVV>
<expDate xsi:nil="true" xsi:type="xsd:date" />
<amtLoad href="#id3" />
<loadFundsType xsi:type="soapenc:string">0</loadFundsType>
<loadSrc xsi:type="soapenc:string">0</loadSrc>
</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</soapenv:Body>
</soapenv:Envelope>
11.2.2. Response
<soapenv:Body>
<ns1:cardActivationLoadResponse xmlns:ns1="urn:CardActivationLoad"
<cardActivationLoadReturn href="#id0" />
</ns1:cardActivationLoadResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardActivationLoad.prepaid.webservices.cortex.com"
xsi:type="ns2:CardActivationLoadRspsInfo">
<amtLoad xsi:type="xsd:double">10.0</amtLoad>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

12.Card Unload/Status Change

This only differs to the ‘Card Unload’ message due to the inclusion of the <statCode> field as the card will be deactivated with a given Card Status (see Appendix A).

Card Unload/Status Change Message
date.

response.
If not present <cardID>or <track2> must be provided

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




DD
Mandatory if the value of <authMethod> is ‘2’ or ‘6’
<CVV> AN 3 3 CVC2. C Om
Mandatory if value of <authMethod> is ‘3’



DD
<amtUnload> D 1 20 The requested amount to unload. If not specified it is assumed the whole O M
amount remaining on the card has been requested.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Otherwise, the actual amount unloaded (net of fees) will be returned.
<currCode> AN 3 3 The currency of the balance returned Om M
<statCode> AN 2 2 The Card Status to set the card to. (Lost / Stolen / Customer Closed) M Om
<loadSrc> AN 1 3 The source of the unload request O Om

0 – Unknown
3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
8 – Agent
9 – Head Office
10 – Call Centre
<loadFundsType> AN 1 3 Payment method of funds for the unload: O Om

0 – Unknown
1 – Cash
2 – Debit card
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


3 – Credit card
12 – Wallet
customer logins.
<reason> AN 1 60 Reason for Status Change. O Om

Overrides default of ‘Card Status Change’ that will be shown in Panorama.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100





<currCode> AN 1 3 The card’s currency. Must be specified if an amount is requested. C Om
DD

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

12.2. Example
12.2.1. Request
<soapenv:Body>
<ns1:cardUnloadStatusChange xmlns:ns1="urn:CardUnloadStatusChange"
<pobjCardUnloadStatusChangeRqstInfo href="#id0" />
</ns1:cardUnloadStatusChange>
<multiRef xmlns:ns2="http://wsvalueobj.CardUnloadStatusChange.prepaid.webservices.cortex.com"
xsi:type="ns2:CardUnloadStatusChangeRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<amtUnload href="#id3" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
12.2.2. Response
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<soapenv:Body>
<ns1:cardUnloadStatusChangeResponse xmlns:ns1="urn:CardUnloadStatusChange"
<cardUnloadStatusChangeReturn href="#id0" />
</ns1:cardUnloadStatusChangeResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardUnloadStatusChange.prepaid.webservices.cortex.com"
xsi:type="ns2:CardUnloadStatusChangeRspsInfo">
<amtUnload xsi:type="xsd:double">10.0</amtUnload>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

13.Void Transaction
The following are the fields required by FIS Web Services to void a previous financial transaction; all changes to the account balance as a result of the original transaction will be
undone. The Void Transaction WS may be used to void the following Web Services: Card Load, Card Unload, Card Transfer, and Balance Adjustment. Note that it is not possible to
use this message to void a previous void.
Note: To void a card transfer, it is enough to do a single void transaction supplying the card number of the source card, that is, the card from which the funds were originally
transferred.

Void Transaction Message
date.

customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




response.
If not present <cardID> or <track2> must be provided.

DD

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



DD

server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<orgItemId> N 1 10 The unique item ID of the transaction to void. This corresponds to the M M
<itemId> returned by other messages
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


DD
<itemId> N 1 10 The unique item ID returned for this Void Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
13.2. Example
13.2.1. Request
<soapenv:Body>
<ns1:voidTransaction xmlns:ns1="urn:VoidTransaction"
<pobjVoidTransactionRqstInfo href="#id0" />
</ns1:voidTransaction>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<multiRef xmlns:ns2="http://wsvalueobj.VoidTransaction.prepaid.webservices.cortex.com"
xsi:type="ns2:VoidTransactionRqstInfo">
<orgItemId xsi:type="soapenc:string">63451</orgItemId>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

13.2.2. Response
<soapenv:Body>
<ns1:voidTransactionResponse xmlns:ns1="urn:VoidTransaction"
<voidTransactionReturn href="#id0" />
</ns1:voidTransactionResponse>
<multiRef xmlns:ns2="http://wsvalueobj.VoidTransaction.prepaid.webservices.cortex.com"
xsi:type="ns2:VoidTransactionRspsInfo">
<orgItemId xsi:type="soapenc:string">63451</orgItemId>
</multiRef>
</soapenv:Body>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

14.Cardholder Update
The following are the fields required by FIS Web Service to update the details of a cardholder.
Note: The dlvXXX fields, with the exception of dlvMethod, should only be used when a delivery (temporary) name and/or address will be associated with the cardholder. For the
specified validity period, this name and/or address will be used in place of the standard name and address.
Note: Additional cards can share the same customer record as the primary card or they can have their own customer record. An additional card can update all the values in its
own customer record. However, if the additional card shares the the primary card’s customer record, then only the primary card can update all the cardholder details - an
additional card can only update a subset of the information. See individual fields for whether or not an additional card can update them in this situation.

Cardholder Update Message
date.

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



response.
If not present <cardID> or <track2> must be provided



DD
description for the impact of this change.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



Note, this value is only used for authentication and not for update. For update,
use newAccessCode.
<newAccessCode> AN 1 12 The new access code for the card. O Om

This can be updated by the primary card and by additional cards that share the
same customer record.
customer logins.
<lastName> AN 1 20 Cardholder’s last name. C Om

If lastName is set to <space>, firstName is also cleared.
<title> AN 1 4 Cardholder’s title. O Om

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<firstName> AN 1 20 Cardholder’s first name. C Om

If firstName is set to <space>, lastName is also cleared.
Mandatory if <lastName> is present and the value of <authMethod> is not ‘6’.
<addrL1> AN 1 35 Address Line 1 C Om

If set to ‘space’, <addrL1>, <addrL2>, <addrL3>, <city>, <county>, <postcode>,
<country> and <tel> are also cleared.
<addrL2> AN 1 35 Address Line 2 O Om

<addrL3> AN 1 35 Address Line 3 O Om

<city> AN 1 20 City C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<postcode> AN 1 10 Post Code C Om

Mandatory if <addrL1> is present, and <city> is not present.
<country> AN 1 3 Country code. C Om

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada

Can be changed but cannot be cleared (unless addrL1 is cleared, in which case
all address fields will be cleared).
Can be cleared by sending a space.
<workAddrL1> AN 1 35 Work Address Line 1 C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


If set to <space>, workAddL1, workAddL2, workAddL3, workCity, workCounty,
workPostcode, workCountry and workTel are also cleared.
Mandatory if ‘Work Address’ fields are being specified.
<workAddrL2> AN 1 35 Work Address Line 2 O Om

<workAddrL3> AN 1 35 Work Address Line 3 O Om

<workCity> AN 1 20 Work City C Om

Mandatory if <workAddrL1> is present, and <workPostcode> is not present.
This field can be cleared by sending a space but see above restrictions.
<workPostcode> AN 1 10 Work Post Code C Om

Mandatory if <addrL1> is present, and <workCity> is not present.
This field can be cleared by sending a space but see above restrictions.
<workTel> AN 1 20 Work telephone number. O Om

Cortex can be configured to process telephone numbers as follows.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<workCounty> AN 1 20 Work County O Om

This field can be cleared by sending a space
<workCountry> AN 1 3 Work Country code. C Om

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
Can be changed but cannot be cleared (unless <addrL1> is cleared, in which
case all address fields will be cleared).
<pobox> AN 1 8 Post office box number. O Om

Sending a space clears the field.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


is.
<email> AN 1 64 Email address O Om

<fax> AN 1 20 Fax no O Om

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
<dlvTitle> AN 4 16 Delivery Title O Om

This field can be changed, or cleared by sending a space, but only if
<dlvLastName> is present and not empty.
<dlvFirstName> AN 1 20 Delivery First name C Om

Mandatory if <dlvLastName> is present.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<dlvLastName> AN 1 20 Delivery Last name C Om

Mandatory if ‘Delivery Name’ fields are being specified.
If is empty or contains a space, <dlvTitle> and <dlvFirstName> are ignored,
even if they contain values.
Cannot be cleared once it is set.
<dlvAddrL1> AN 1 35 Delivery Address Line 1 C Om

Mandatory if ‘Delivery Address’ fields are being specified.
If < dlvAddrL1> is empty or contains a space, <dlvAddrL2>, <dlvAddrL3>,
<dlvCity>, <dlvCounty>, <dlvPostcode>, <dlvCountry>, <dlvTel>are ignored,
even if they contain values.
Cannot be cleared once it is set.
<dlvAddrL2> AN 1 35 Delivery Address Line 2 O Om

<dlvAddrL1> is not ‘space’ and not empty.
<dlvAddrL3> AN 1 35 Delivery Address Line 3 O Om

<dlvAddrL1> is not ‘space’ and not empty.
<dlvCity> AN 1 20 Delivery City C Om

Mandatory if <dlvAddrL1> is present, and <dlvPostcode> is not present.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


This field can be cleared by sending a space, but see above restrictions.
<dlvPostcode> AN 1 10 Delivery Post code C Om

Mandatory if <dlvAddrL1> is present, and <dlvCity> is not present.
This field can be cleared by sending a space, but see above restrictions
<dlvCountry> AN 1 3 Delivery Country code. C Om

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
Mandatory if <dlvAddrL1> is present.
Can be changed but cannot be cleared.
<dlvCounty> AN 1 20 Delivery County O Om

This field can be changed, or cleared by sending a space, but only if <
dlvAddrL1> is not ‘space’ and not empty.
<dlvTel> AN 1 20 Delivery Telephone number. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


0044 (0) 20 7292 2400 to +442072722400
is.
This field can be changed, or cleared by sending a space, but only if <
dlvAddrL1> is not ‘space’ and not empty.
<dlvEffDate> YYYY-MM- 10 10 Date from which delivery name and/or address become effective, inclusive. O Om
DD
If field not present, the current date becomes the effective date.
<dlvDaysValid> N 1 3 The number of calendar days from the effective date for which the delivery C Om
name and/or address is valid.
Mandatory if ‘Delivery Name and Address’ details are being specified and
there is no current active delivery name and/or address.
<maritalStatus> AN 1 1 S: Single O Om
M: Married
D: Divorced
W: Widowed
space: Not specified
Sending a space also clears the field.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<sex> AN 1 1 M: Male O Om
F: Female
Sending a space also clears the field.
<crdproduct> AN 4 4 The new Product of the card. O C

Changing the card product means that the existing cycle and limit counters
associated with this card will be reset. The cycle and limits of the new product
will now apply.
Changing the card product may also affect the fee tier. If the fee tier of the old
card product is not defined in the new card product, the default value of 0 is
used. Even if the same fee tier value is defined for the old and new card
product, it may not have the same meaning in both. Therefore, it is advisable
to change the fee tier when the card product is changed.
Age-verification as described in the <DOB> field description does not apply if a
new <crdproduct> is explicitly specified in this message.
If the new card product does not have the same security checks as the product
being replaced, or does not have corresponding security check identifiers for
the same check as the previous product, the <modSecDet> field must be used
to correct the checks for the card now assigned to the new card product.
Mandatory in the response if present in the Request.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<embossName> AN 1 21 or 27 Name embossed on the card. Note that actual embossed name will not change O Om
until card is re-issued.
Note: The maximum length may vary depending on scheme regulations and
the card design. For example, for MasterCard no information can be embossed
over the MasterCard logo, which means a maximum length of 21 if the logo is
in the bottom right corner of the card design.
<refuseCheck> AN 1 1 Whether cheques should be refused. O Om

0: No
1: Yes
<mailShots> AN 1 1 Whether cardholder will accept mailshots or Member contact. O Om

0: No
1: Yes
<discret> AN 1 25 Discretionary data, for information only. O Om

<userdata> AN 1 30 Cardholder information stored at card level, free text field. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<userdata1> AN 1 12 Cardholder information stored at customer level, free text field. O Om




<dlvMethod> AN 1 1 To indicate the delivery method for the card: O Om

0 – Standard mail
1 – Registered mail
2 – Direct delivery
<pin> AN 1 1 To indicate whether the card should have a PIN. O Om

0: No
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1: Yes
Note that updating this value to reflect that the card has a PIN will not induce
a PIN-generation request. This must be initiated by another means. An update
from 0 to 1 means that a PIN may be requested.
<imageID> AN 1 16 ID of the image to be printed on the card. O Om

<renew> AN 1 1 To indicate whether the card should be renewed on expiry: O Om

0: No
1: Yes
This value may only be set to ‘1’ if the associated crdProduct is renewable.
This field can be changed but cannot be cleared.
<brncode> AN 8 8 Branch code (or Agent code) with which the card is associated. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<crdprogram> AN 1 6 Pre-defined program reference code associated with the card. O Om

<crddesign> AN 1 8 Pre-defined design reference code associated with the card. O Om

<denyMCC> AN 1 192 List of MCC’s (merchant category codes) that should be denied for the card. O Om
MCC’s can be comma-separated, specified as a range, or combinations of both.
Eg:
4546,5462,5667-5673,5957
These restrictions are in addition to MCC restrictions defined at the Card
Product level.
<denySvc> AN 1 64 Comma separated list of services (authorisation transaction types) that should O Om
be denied for the card:
0 – Sale (Goods & services)
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1 – Cash
9 – Sale with cashback
These restrictions are in addition to service code restrictions defined at the
Card Product level.
<accType> AN 2 2 Type code for the account associated with the card. O Om
<memo> AN 1 4096 Add a memo to the customer details that will be visible to CSR’s on the GUI O Om
application.
Existing memos cannot be changed or cleared.
<memoScope> N 1 3 Scope of visibility for the memo. O Om

0 – full visibility (any user logged in to the GUI application will be able to view
this memo).
To set more restrictive scopes, the Member and FIS must agree the value for
each level. This value may then be used here.
Defaulted to ‘full visibility’ if field is absent.
<memoUser> AN 1 15 The user that created the memo. O Om
server Item
Defined options:
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<feeTier> AN 1 3 The fee tier based on which fees are charged for the card. O Om
<isoLang> AN 2 2 The ISO Language code in ISO 639-1 format. O Om

This is used to customise the language in which certain fields are displayed in
Panorama and the Transaction Extract. It can also be used to customise pin
mailer salutations.
Note that <isoLang> does not translate Panorama field names, only the
contents, if applicable.
Default value: EN
<profileRef> AN 1 32 Profile Reference O Om
<additionalCrdDet> - - - See ADDITIONAL CARD DETAILS section below. O Om
<additionalCustDet> - - - See ADDITIONAL CUSTOMER DETAILS section below. O Om
<miscSvc> - - - See MISCELLANEOUS SERVICE section below. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<miscSvcLoadProfile> - - - See MISCELLANEOUS SERVICE LOAD PROFILE section below. O Om


<modSecDet> - - - See MODIFIED SECURITY DETAIL section below. O Om

DD
<formFactorID> AN 1 19 Form Factor ID. O Om
<accProfileRef> AN 1 32 Account Profile Reference O Om

If the tag is present with a blank (space) value, the profile will be unassigned.
<crdProfileRef> AN 1 32 Card Profile Reference O Om

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<custProfileRef> AN 1 32 Customer Profile Reference O Om

SOURCE-OF-FUNDS CARD DETAIL BEGINS HERE2
<fundCrdPAN> AN 13 19 PAN of source-of-funds card. O Om

This must be provided if the source-of-funds card is being updated otherwise
the record will be rejected.
If this is empty, there will be no change to any of the source-of-funds card
fields.
If this contains a space, all source-of-funds card field will be deleted.
<fundCrdEffDate> YYYY-MM- 10 10 Start Date of source-of-funds card. O Om

DD
<fundCrdExpDate> YYYY-MM- 10 10 Expiry Date of source-of-funds card. O Om

DD
2
Updating the source-of-funds card involves deleting the existing record and inserting the new one. Therefore all details must be provided even if they are the same as the ones in
the existing record. Any existing record details that are not provided for the new funding card will be deleted from the record.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<fundCrdType> AN 1 15 Card type of source-of-funds card: O Om

VISA – Visa
DELTA – Visa Debit/Delta
UKE – Visa Electron
MC – MasterCard
SWITCH – UK Maestro
MASTRO – International Maestro
SOLO – Solo
AMEX – American Express
DC – Diners Club
JCB - Japan Credit Bureau
<fundCrdIssNum> AN 1 2 Issuer number of source-of-funds card. O Om

Can be changed and can also be cleared by sending a space.
<fundCrdCVC> AN 3 4 Card verification code of source-of-funds card. O Om

Can be changed and can also be cleared by sending a space.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<value> AN 1 255 Additional data for the reference above. C Om
<valueDate> YYYY-MM- 10 10 Date value for the additional detail. C Om

DD
<valueTime> HHMMSS 6 6 Time value for the additional detail. C Om

Mandatory if the value of <valueDate> is provided.
<valueAmt> D 1 20 The amount to be updated. C Om
<valueCurrCode> AN 1 3 This is the currency. C Om

Mandatory if the value of <valueAmt> is provided.
<value> AN 1 255 Additional data for the reference above. C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<valueDate> YYYY-MM- 10 10 Date value for the additional detail. C Om

DD
<valueTime> HHMMSS 6 6 Time value for the additional detail. C Om

<valueAmt> D 1 20 The amount to be updated. C Om
<valueCurrCode> AN 1 3 This is the currency. C Om

MISCELLANEOUS SERVICE DETAIL BEGINS HERE
<svcSrc> N 1 2 Source of the service. Allowed value: M Om

4 - SMS
<svcType> N 1 3 The service type. Allowed values are: M Om

1 – Stop
2 – Stop All
10 – Lock Card
11 – Unlock Card
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


12 – Card to Card transfer
13 – Card Balance Enquiry
14 – Card Transaction History
15 – Activate Card
100 – Load Notifications
101 – Balance notification
102 – Minimum Balance Notification
<svcStatus> N 1 1 The service status associated with <svcType>. Allowed values are: M Om
1 – Enable
0 – Disable
<svcBalNotifyCycle> N 1 2 The cycle of balance notification if <svcType> is 101. M Om

Allowed values are:
1-79 – every 1 to 79 days
80 – Weekly
81 – Fortnightly
82 – Bimonthly
83 – Monthly
84 – Quarterly
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


85 – Biyearly
86 – Yearly
<svcMinBal> D 1 20 The minimum balance limit for minimum balance notification if <svcType> is M Om
102.
MISCELLANEOUS SERVICE DETAIL ENDS HERE
MISCELLANEOUS SERVICE LOAD PROFILE DETAIL BEGINS HERE
<svcMinLoad> D 1 20 Minimum load amount limit. M Om
<svcMaxLoad> D 1 20 Maximum load amount limit. M Om
<svcLoadFundsType> AN 1 3 Load type that the profile is for. If absent or empty, means the profile is for all M Om
load types.
<svcLoadSrc> AN 1 3 Load source that the profile is for. If absent or empty, means the profile is for M Om
all load sources.
MISCELLANEOUS SERVICE LOAD PROFILE DETAIL ENDS HERE
<charPos> N 1 2 Identifies the position in the stored security value to which secValue C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
<secChkID> N 1 8 Pre-defined security check identifier. C Om

Cannot be empty.
<secValue> AN 1 64 Value associated with security secChkID. Each secValue must immediately C Om
If <secValue> is ‘space’ and the security check type is “synchronized”, the
security data will be synchronized by card/customer data.
If <secValue> is ‘space’ and the security check type is normal, the security
value in the database will be ‘space’.
If <secValue> is empty when <action> is '6', the <secChkID>/ <secValue> pair
will be removed.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


MODIFIED SECURITY DETAIL BEGINS HERE
follow its associated id. If the secChkID is valid but not defined for the card,
the new check will be added. Existing checks will be updated. A null or empty
secValue will remove any pre-existing security check for the secChkID.
MODIFIED SECURITY DETAIL ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

14.2. Clearing field values

The following fields may have their values cleared by sending a <space>. In addition, some fields are cleared automatically if a related field is cleared. Such fields are indicated
below:
• title • workTel (also cleared if workAddrL1 contains space)
• lastName (cleared if either lastName or firstName contains space) • pobox
• firstName (cleared if either lastName or firstName contains space) • maritalStatus
• addrL1 • sex
• addrL2 (also cleared if addrL1 contains space) • userdata1
• addrL3 (also cleared if addrL1 contains space) • userdata2
• city (also cleared if addrL1 contains space) • userdata3
• county (also cleared if addrL1 contains space) • userdata4
• postcode (also cleared if addrL1 contains space) • mailshots
• country (also cleared if addrL1 contains space) • email
• tel (also cleared if addrL1 contains space) • fax
• userdata • mobTel
• workAddrL1 • newAccessCode
• workAddrL2 (also cleared if workAddrL1 contains space) • embossName
• workAddrL3 (also cleared if workAddrL1 contains space) • imageID
• workCity (also cleared if workAddrL1 contains space) • discret
• workCounty (also cleared if workAddrL1 contains space) • denyMCC
• workPostcode (also cleared if workAddrL1 contains space) • denySVC
• workCountry (also cleared if workAddrL1 contains space)
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

14.3. Example
14.3.1. Request
<soapenv:Body>
<ns1:cardHolderUpdate xmlns:ns1="urn:CardHolderUpdate"
<pobjCardHolderUpdateRqstInfo href="#id0" />
</ns1:cardHolderUpdate>
<multiRef xmlns:ns2="http://wsvalueobj.CardHolderUpdate.prepaid.webservices.cortex.com"
xsi:type="ns2:CardHolderUpdateRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<newAccessCode xsi:nil="true" xsi:type="soapenc:string" />
<title xsi:type="soapenc:string">Mrs</title>
<addrL1 xsi:nil="true" xsi:type="soapenc:string" />
<postcode xsi:nil="true" xsi:type="soapenc:string" />
<workAddrL1 xsi:nil="true" xsi:type="soapenc:string" />
<workCity xsi:nil="true" xsi:type="soapenc:string" />
<workPostcode xsi:nil="true" xsi:type="soapenc:string" />
<workTel xsi:nil="true" xsi:type="soapenc:string" />
<workCounty xsi:nil="true" xsi:type="soapenc:string" />
<workCountry xsi:nil="true" xsi:type="soapenc:string" />
<pobox xsi:nil="true" xsi:type="soapenc:string" />
<tel xsi:nil="true" xsi:type="soapenc:string" />
<email xsi:nil="true" xsi:type="soapenc:string" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<fax xsi:nil="true" xsi:type="soapenc:string" />

<mobTel xsi:nil="true" xsi:type="soapenc:string" />
<dlvTitle xsi:nil="true" xsi:type="soapenc:string" />
<dlvFirstName xsi:nil="true" xsi:type="soapenc:string" />
<dlvLastName xsi:nil="true" xsi:type="soapenc:string" />
<dlvAddrL1 xsi:nil="true" xsi:type="soapenc:string" />
<dlvCity xsi:nil="true" xsi:type="soapenc:string" />
<dlvPostcode xsi:nil="true" xsi:type="soapenc:string" />
<dlvCountry xsi:nil="true" xsi:type="soapenc:string" />
<dlvCounty xsi:nil="true" xsi:type="soapenc:string" />
<dlvTel xsi:nil="true" xsi:type="soapenc:string" />
<dlvEffDate xsi:nil="true" xsi:type="xsd:date" />
<dlvDaysValid xsi:nil="true" xsi:type="xsd:short" />
<maritalStatus xsi:nil="true" xsi:type="soapenc:string" />
<sex xsi:nil="true" xsi:type="soapenc:string" />
<crdproduct xsi:nil="true" xsi:type="soapenc:string" />
<embossName xsi:nil="true" xsi:type="soapenc:string" />
<refuseCheck xsi:nil="true" xsi:type="soapenc:string" />
<mailShots xsi:nil="true" xsi:type="soapenc:string" />
<discret xsi:nil="true" xsi:type="soapenc:string" />
<userdata xsi:nil="true" xsi:type="soapenc:string" />
<userdata1 xsi:nil="true" xsi:type="soapenc:string" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<dlvMethod xsi:nil="true" xsi:type="soapenc:string" />
<pin xsi:nil="true" xsi:type="soapenc:string" />
<renew xsi:nil="true" xsi:type="soapenc:string" />
<crdprogram xsi:nil="true" xsi:type="soapenc:string" />
<crddesign xsi:nil="true" xsi:type="soapenc:string" />
<denyMCC xsi:nil="true" xsi:type="soapenc:string" />
<denySvc xsi:nil="true" xsi:type="soapenc:string" />
<accType xsi:nil="true" xsi:type="soapenc:string" />
<imageID xsi:nil="true" xsi:type="soapenc:string" />
<brncode xsi:nil="true" xsi:type="soapenc:string" />
<memo xsi:nil="true" xsi:type="soapenc:string" />
<memoScope xsi:nil="true" xsi:type="soapenc:int" />
<memoUser xsi:nil="true" xsi:type="soapenc:string" />
<formFactorID xsi:type="soapenc:string" xsi:nil="true" />
<modSecDet xsi:nil="true" xsi:type="ns2:UpdateSecurityDetailsInfo" />
<miscSvc soapenc:arrayType="ns3:MiscellaneousServiceTypes[3]" xsi:type="soapenc:Array"
xmlns:ns3="http://wsvalueobj.CardHolderEnquiry.prepaid.webservices.cortex.com">
<miscSvc href="#id6" />
</miscSvc>
<miscSvcLoadProfile soapenc:arrayType="ns4:MiscellaneousServiceLoadProfile[1]" xsi:type="soapenc:Array"
<miscSvcLoadProfile href="#id9" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</miscSvcLoadProfile>
</multiRef>
<multiRef id="id8" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns6:MiscellaneousServiceTypes"
xmlns:ns6="http://wsvalueobj.CardHolderEnquiry.prepaid.webservices.cortex.com"
<svcSrc href="#id10" />
<svcType href="#id11" />
<svcStatus href="#id12" />
<svcMinBal xsi:type="xsd:double" xsi:nil="true" />
<svcBalNotifyCycle xsi:type="xsd:short" xsi:nil="true" />
</multiRef>
<svcMinBal href="#id17" />
</multiRef>
xsi:type="ns9:MiscellaneousServiceLoadProfile" xmlns:ns9="http://wsvalueobj.common.prepaid.webservices.cortex.com"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<svcMinLoad href="#id18" />

<svcMaxLoad href="#id19" />
<svcLoadSrc xsi:type="soapenc:string">1</svcLoadSrc>
<svcLoadFundsType xsi:type="soapenc:string">1</svcLoadFundsType>
</multiRef>
<svcBalNotifyCycle href="#id23" />
</multiRef>
xsi:type="xsd:double"
40.0
</multiRef>
xsi:type="xsd:short"
1
</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

675.0
</multiRef>
xsi:type="xsd:long"
1
</multiRef>
1
</multiRef>
1
</multiRef>
4
</multiRef>
4
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</multiRef>
101
</multiRef>
20.0
</multiRef>
4
</multiRef>
102
</multiRef>
1
</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


100
</multiRef>
<additionalCrdDet>
<reference>111111</reference>
<valueAmt>10.00</valueAmt>
<valueCurrCode>455</valueCurrCode>
</additionalCrdDet>
<additionalCustDet>
<reference>222222</reference>
<valueAmt>8.00</valueAmt>
<valueCurrCode>332</valueCurrCode>
</soapenv:Body>
</soapenv:Envelope>
14.3.2. Response
<soapenv:Body>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<ns1:cardHolderUpdateResponse xmlns:ns1="urn:CardHolderUpdate"
<cardHolderUpdateReturn href="#id0" />
</ns1:cardHolderUpdateResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardHolderUpdate.prepaid.webservices.cortex.com"
xsi:type="ns2:CardHolderUpdateRspsInfo">
<crdproduct xsi:nil="true" xsi:type="soapenc:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

15.Cardholder Enquiry
The Cardholder Enquiry message returns the details of a cardholder.
Note: The delivery name and/or address (dlvXXX) fields are only returned if they have not expired.

Cardholder Enquiry Message
date.
<localDate> YYYY-MM-DD 10 10 The current date M M

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


response.
<cardID> AN 16 19 Unique internal card identification number. C M


Mandatory in request and response if neither <cardID> nor <PAN> is present or
when the value of <authMethod> is ‘7’
<DOB> YYYY-MM-DD 10 10 Date of Birth. Mandatory if the value of <authMethod> is ‘2’ or ‘6’ C M

customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Returned in the response if present in the request, or if the customer has a
<loginID> defined.
<lastName> AN 1 20 Cardholder’s last name. Mandatory if the value of <authMethod> is ‘6’ C M
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
<profileRef> AN 1 32 Profile Reference Om O
<additionalCrdDet> - - - See ADDITIONAL CARD DETAILS section below. Om O
<additionalCustDet> - - - See ADDITIONAL CUSTOMER DETAILS section below. Om O
<miscSvc> - - - See MISCELLANEOUS SERVICE section below. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<miscSvcLoadProfile> - - - See MISCELLANEOUS SERVICE LOAD PROFILE section below. Om O

<secDet> - - - See SECURITY DETAIL section below. C C

Only present in response for configured customers
<statCode> AN 2 3 The status code of the card Om M
<title> AN 1 4 Cardholder’s title Om O
<firstName> AN 1 20 Cardholder’s first name Om O
<addrL1> AN 1 35 Address Line 1 Om O
<city> AN 1 20 City Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<postcode> AN 1 10 Post Code Om O
<county> AN 1 20 County Om O
<country> AN 1 3 Country code. Om O

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
<tel> AN 1 20 Telephone number. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2. Strip all leading non-numeric characters (except +). Non-leading non-numeric
characters are not removed.
3. Depending on the country (currently only UK), the international dialling prefix
(e.g. double zeros for UK) is converted to "+".
4. Depending on the country (currently only UK), the national dialling prefix (e.g.
single zero for UK) is dropped and "+" and the IDD number is prefixed.
e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
<workAddrL1> AN 1 35 Work Address Line 1 Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<workCity> AN 1 20 Work city Om O
<workPostcode> AN 1 10 Work Post Code Om O
<workCounty> AN 1 20 Work County Om O
<workCountry> AN 1 3 Work Country code. Om O

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
<workTel> AN 1 20 Work telephone number. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<email> AN 1 64 Email address Om O
<fax> AN 1 20 Fax no Om O
<pobox> AN 1 8 PO Box Om O
<mobTel> AN 1 20 Mobile telephone number. Om O

configured, telephone numbers are stored as received. However, this processing
is required for using SMS services.
2. Rejects any numbers containing non-numeric characters with the exception of
the prefix “+”.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
6. If there is no "+" prefix, international dialling prefix or national dialling prefix,
the number is rejected.
<maritalStatus> AN 1 1 S: Single Om O
M: Married
D: Divorced
W: Widowed
<sex> AN 1 1 M: Male Om O
F: Female
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<accno> AN 1 28 Account number of the card Om O
<crdproduct> AN 1 4 Card Product associated with the card. Om O
<embossName> AN 1 21 or 27 Name embossed on the card. Note that actual embossed name will not change Om O
until card is re-issued.
Note: The maximum length may vary depending on scheme regulations and the
card design. For example, for MasterCard no information can be embossed over
the MasterCard logo, which means a maximum length of 21 if the logo is in the
bottom right corner of the card design.
<refuseCheck> AN 1 1 Whether cheques should be refused. Om O

0: No
1: Yes
<mailShots> AN 1 1 Whether cardholder will accept mailshots or issuer contact. Om O

0: No
1: Yes
<discret> AN 1 25 Discretionary data, for information only. Om O
<userdata> AN 1 30 Cardholder information stored at card level, free text field. Om O
<userdata1> AN 1 12 Cardholder information stored at customer level, free text field. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<custCode> AN 1 8 Cardholder’s FIS customer code. Om O
<currCode> AN 1 3 Card currency code. Om O
<expDate> YYYY-MM-DD 10 10 Card expiry date. Om O
<effDate> YYYY-MM-DD 10 10 Card effective date. Om O
<svccode> AN 1 3 Card Service Code. Om O
<additionalNo> N 1 1 Number of additional card. Zero indicates the card is a primary card. Om O
<dateCreated> YYYY-MM-DD 10 10 Calendar date the card was created in the FIS system. Om O
<dateActivated> YYYY-MM-DD 10 10 Calendar date the card was activated in the FIS system. Om O
<crdprogram> AN 1 6 Pre-defined program reference code associated with the card. Om O
<crddesign> AN 1 8 Pre-defined design reference code associated with the card. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<pin> AN 1 1 To indicate whether the card should have a PIN. Om O

0: No
1: Yes
<dlvMethod> AN 1 1 To indicate the delivery method for the card: Om O

0 – Standard mail
<imageID> AN 1 16 ID of the image printed on the card Om O
<brncode> AN 8 8 Branch code (or Agent code) with which the card is associated. Om O
<renew> AN 1 1 To indicate whether the card will be renewed on expiry: Om O

0: No
1: Yes
<denyMCC> AN 1 192 List of MCC’s (merchant category codes) that should be denied for the card. Om O
Eg:
4546,5462,5667-5673,5957
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


These restrictions are in addition to MCC restrictions defined at the Card Product
level.
<denySvc> AN 1 64 Comma separated list of services (authorisation transaction types) that should be Om O
denied for the card:
1 – Cash
These restrictions are in addition to service code restrictions defined at the Card
Product level.
<accType> AN 2 2 Type code for the account associated with the card. Om O
<CVC2> AN 3 3 The 3-digit security number printed on the back of the card. Om M
<dlvTitle> AN 4 16 Delivery Title Om O
<dlvFirstName> AN 1 20 Delivery Firstname Om O
<dlvLastName> AN 1 20 Delivery Lastname Om O
<dlvAddrL1> AN 1 35 Delivery Address Line 1 Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<dlvCity> AN 1 20 Delivery City Om O
<dlvPostcode> AN 1 10 Delivery Post code Om O
<dlvCounty> AN 1 20 Delivery County Om O
<dlvCountry> AN 1 3 Delivery Country code. Om O

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
<dlvTel> AN 1 20 Delivery Telephone number. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<dlvEffDate> YYYY-MM-DD 10 10 Date from which the delivery name and/or address became effective, inclusive. Om C
Mandatory if name and/or address delivery fields are present.
<dlvExpDate> YYYY-MM-DD 10 10 Date after which the delivery name and/or address expires. Om C
<sysDate> YYYY-MM-DD 10 10 The Cortex processing system date. This date is used for reconciliation Om M
<feeTier> N 1 3 The fee tier based on which fees are charged for the card. Om O
<isoLang> AN 2 2 The ISO Language code in ISO 639-1 format. Om O

This is used to customise the language in which certain fields are displayed in
Panorama and the Transaction Extract. It can also be used to customise pin
mailer salutations.
Note that <isoLang> does not translate Panorama field names, only the contents,
if applicable.
Default value: EN
<fundCrdPAN> AN 16 19 PAN of source-of-funds card. Om O
<fundCrdEffDate> YYYY-MM-DD 10 10 Start Date of source-of-funds card. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<fundCrdExpDate> YYYY-MM-DD 10 10 Expiry Date of source-of-funds card. Om O

This must be provided if the source-of-funds card is being updated otherwise the
record will be rejected.
<fundCrdType> AN 1 15 Card type of source-of-funds card: Om O

VISA – Visa
DELTA – Visa Debit/Delta
UKE – Visa Electron
MC – MasterCard
SWITCH – UK Maestro
MASTRO – International Maestro
SOLO – Solo
AMEX – American Express
DC – Diners Club
JCB - Japan Credit Bureau
This must be provided if the source-of-funds card is being updated otherwise the
record will be rejected.
<fundCrdIssNum> AN 1 2 Issuer number of source-of-funds card Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<formFactorID> AN 1 19 Form Factor ID. Om O
<accProfileRef> AN 1 32 Account Profile Reference Om O
<crdProfileRef> AN 1 32 Card Profile Reference Om O
<custProfileRef> AN 1 32 Customer Profile Reference Om O
<prevStatCode> AN 2 3 The previous status code of the card Om O
< - - - See ADDITIONAL RECORD CARD DETAILS section below Om O

additionalRecCrdDet>
<reference> AN 1 32 Reference Code for additional data Om M
<value> AN 1 255 Additional data for the reference above. Om C
<valueDate> YYYY-MM-DD 10 10 Date value for the additional detail. Om C
<valueTime> HHMMSS 6 6 Time value for the additional detail. Om C

<valueAmt> D 1 20 This is the amount. Om C
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<valueCurrCode> AN 1 3 This is the currency. Om C



MISCELLANEOUS SERVICE DETAIL BEGINS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<svcSrc> N 1 2 Source of the service. Allowed value: Om M

4 - SMS
<svcType> N 1 3 The service type. Allowed values are: Om M

1 – Stop
2 – Stop All
10 – Lock Card
11 – Unlock Card
12 – Card to Card transfer
13 – Card Balance Enquiry
14 – Card Transaction History
15 – Activate Card
100 – Load Notifications
101 – Balance notification
102 – Minimum Balance Notification
<svcStatus> N 1 1 The service status associated with <svcType>. Allowed values are: Om M
1 – Enable
0 – Disable
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<svcBalNotifyCycle> N 1 2 The cycle of balance notification if <svcType> is 101. Om M

Allowed values are:
1-79 – every 1 to 79 days
80 – Weekly
81 – Fortnightly
82 – Bimonthly
83 – Monthly
84 – Quarterly
85 – Biyearly
86 – Yearly
NOTE: Every time the balance notification service is enabled from disabled
status, the cycle will be same as set at card product level unless
<svcBalNotifyCycle> is set.
<svcMinBal> D 1 20 The minimum balance limit for minimum balance notification if <svcType> is Om M
102.
NOTE: Every time the minimum balance notification service is enabled from
disabled status, the minimum balance limit will be the same as set at card
product level unless <svcMinBal> is set.
MISCELLANEOUS SERVICE DETAIL ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


MISCELLANEOUS SERVICE LOAD PROFILE DETAIL BEGINS HERE
<svcMinLoad> D 1 20 Minimum load amount limit. Om M
<svcMaxLoad> D 1 20 Maximum load amount limit. Om M
<svcLoadFundsType> AN 1 3 Load type that the profile is for. If absent or empty, means the profile is for all Om M
load types.
<svcLoadSrc> AN 1 3 Load source that the profile is for. If absent or empty, means the profile is for all Om M
load sources.
MISCELLANEOUS SERVICE LOAD PROFILE DETAIL ENDS HERE
must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Not present in the response.
ADDITIONAL RECORD CARD DETAILS STARTS HERE
<recReference> AN 1 64 Xml tag of rec-root for token data Om O
< additionalRecData> - - - See AdditionalRecData Definition Om O

Can occur multiple for within the message.
ADDITIONAL RECORD CARD DETAILS ENDS HERE
ADDITIONAL RECORD DATA DETAILS START HERE
<additionalRecData> - - - See Below for additional details definition for additionalRecData Om O

Can occur multiple times within the message
ADDITIONAL RECORD DATA DETAILS ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


ADDITIONAL DETAILS START HERE

Mandatory if the value of <valueDate> is provided

ADDITIONAL DETAILS ENDS HERE
15.2. Example
15.2.1. Request
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<soapenv:Body>
<ns1:cardHolderEnquiry xmlns:ns1="urn:CardHolderEnquiry"
<pobjCardHolderEnquiryRqstInfo href="#id0" />
</ns1:cardHolderEnquiry>
<multiRef xmlns:ns2="http://wsvalueobj.CardHolderEnquiry.prepaid.webservices.cortex.com"
xsi:type="ns2:CardHolderEnquiryRqstInfo">
<track2 xsi:type="soapenc:string">1111111111111111=22222222222222222222</track2>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</multiRef>
</soapenv:Body>
</soapenv:Envelope>
15.2.2. Response
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:cardHolderEnquiryResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:CardHolderEnquiry">
<cardHolderEnquiryReturn xsi:type="ns2:CardHolderEnquiryRspsInfo"
xmlns:ns2="http://wsvalueobj.CardHolderEnquiry.prepaid.webservices.cortex.com">
<instCode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">IDT</instCode>
<txnType xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</txnType>
<PAN xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">527442******8068
</PAN>
<cardID xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">52744200130
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</cardID>
<loginID xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">14808</loginID>
<lastName xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Gairola</lastName>
<title xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></title>
<firstName xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Aparna</firstName>
<addrL1 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">41</addrL1>
<addrL2 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></addrL2>
<addrL3 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></addrL3>
<city xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Watford</city>
<county xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Watford
</county>
<postcode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">WD17 1TB</postcode>
<country xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">826</country>
<workAddrL1 xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Mitre House</workAddrL1>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">177 Regent Street</workAddrL2>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></workAddrL3>
<workCity xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">London</workCity>
<workCounty xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Greater London</workCounty>
<workCountry xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">826</workCountry>
<workPostcode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">W1B 4JN</workPostcode>
<workTel xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">+07654322343</workTel>
<pobox xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></pobox>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<tel xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">213423423</tel>

<email xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></email>
<fax xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></fax>
<mobTel xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">066544322312
</mobTel>
<dlvTitle xsi:type="soapenc:string" xsi:nil="true"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<dlvFirstName xsi:type="soapenc:string" xsi:nil="true"
<dlvLastName xsi:type="soapenc:string" xsi:nil="true"
<dlvAddrL1 xsi:type="soapenc:string" xsi:nil="true"
<dlvCity xsi:type="soapenc:string" xsi:nil="true"
<dlvPostcode xsi:type="soapenc:string" xsi:nil="true"
<dlvCountry xsi:type="soapenc:string" xsi:nil="true"
<dlvCounty xsi:type="soapenc:string" xsi:nil="true"
<dlvTel xsi:type="soapenc:string" xsi:nil="true"
<dlvEffDate xsi:type="xsd:date" xsi:nil="true" />
<dlvExpDate xsi:type="xsd:date" xsi:nil="true" />
<maritalStatus xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></maritalStatus>
<sex xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0</sex>
<statCode xsi:type="soapenc:string"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">00</statCode>
<crdproduct xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">RWAH</crdproduct>
<custCode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">00003529</custCode>
<accno xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">DDEBIT999900
</accno>
<currCode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">GBP</currCode>
<effDate xsi:type="xsd:date">2009-10-13</effDate>
<svccode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">121</svccode>
<embossName xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">test</embossName>
<additionalNo xsi:type="xsd:int">0</additionalNo>
<dateCreated xsi:type="xsd:date">2007-02-20</dateCreated>
<crdprogram xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">BLISS</crdprogram>
<crddesign xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">UIDA</crddesign>
<pin xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</pin>
<refuseCheck xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></refuseCheck>
<mailShots xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0</mailShots>
<discret xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></discret>
<userdata xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></userdata>
<userdata1 xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></userdata1>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<dlvMethod xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</dlvMethod>
<dateActivated xsi:type="xsd:date">2007-06-01</dateActivated>
<imageID xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></imageID>
<renew xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</renew>
<brncode xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">DDEBIT</brncode>
<denyMCC xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0000-1</denyMCC>
<denySvc xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1,2,0000-1234</denySvc>
<accType xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">01</accType>
<CVC2 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">203</CVC2>
<feeTier xsi:type="xsd:short">0</feeTier>
<isoLang xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">RO</isoLang>
<fundCrdPAN xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">540400******0001</fundCrdPAN>
<fundCrdEffDate xsi:type="xsd:date" xsi:nil="true" />
<fundCrdExpDate xsi:type="xsd:date">2015-04-01</fundCrdExpDate>
<fundCrdType xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">MC</fundCrdType>
<fundCrdIssNum xsi:type="soapenc:string"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"></fundCrdIssNum>
<formFactorID xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</formFactorID>
<miscSvc soapenc:arrayType="ns2:MiscellaneousServiceTypes[13]"
xsi:type="soapenc:Array" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<miscSvc xsi:type="ns2:MiscellaneousServiceTypes">
<svcSrc xsi:type="xsd:short">4</svcSrc>
<svcType xsi:type="xsd:short">10</svcType>
<svcStatus xsi:type="xsd:short">0</svcStatus>
</miscSvc>
</miscSvc>
</miscSvc>
</miscSvc>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</miscSvc>
</miscSvc>
</miscSvc>
<svcBalNotifyCycle xsi:type="xsd:short">1
</svcBalNotifyCycle>
</miscSvc>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<svcMinBal xsi:type="xsd:double">1530.0</svcMinBal>
</miscSvc>
</miscSvc>
</miscSvc>
/miscSvc>
</miscSvc>
</miscSvc>
<miscSvcLoadProfile xsi:type="ns3:MiscellaneousServiceLoadProfile"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

xsi:nil="true" xmlns:ns3="http://wsvalueobj.common.prepaid.webservices.cortex.com" />

<profileRef xsi:type="soapenc:string" xsi:nil="true"
<additionalCrdDet xsi:type="ns4:AdditionalDetails"
<additionalCustDet soapenc:arrayType="ns5:AdditionalDetails[26]"
xsi:type="soapenc:Array" xmlns:ns5="http://wsvalueobj.common.prepaid.webservices.cortex.com"
<additionalDetails xsi:type="ns6:AdditionalDetails">
<reference xsi:type="soapenc:string">_CTX_REC_FWL_EXPDT</reference>
<valueDate xsi:type="xsd:date">2016-08-21</valueDate>
<valueTime xsi:type="xsd:long">114342</valueTime>
<valueAmt xsi:type="xsd:double" xsi:nil="true"/>
<valueCurrCode xsi:type="soapenc:string" xsi:nil="true"/>
</additionalDetails>
<reference xsi:type="soapenc:string">_CTX_REC_FWL_EFFDT</reference>
<valueDate xsi:type="xsd:date">2016-08-19</valueDate>
<valueTime xsi:type="xsd:long">114342</valueTime>
<reference xsi:type="soapenc:string">_CTX_REC_FWL_FLAG</reference>
<valueDate xsi:type="xsd:date" xsi:nil="true"/>
<valueTime xsi:type="xsd:long" xsi:nil="true"/>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<reference xsi:type="soapenc:string">_CTX_REC_FWLTXN_TLOGID</reference>
<reference xsi:type="soapenc:string">_CTX_REC_FWL_TEXT</reference>
<value xsi:type="soapenc:string"> Whitelist</value>
</additionalRecData>
</additionalRecData>
</additionalRecCrdDet>
</additionalRecCrdDet>
<secDet soapenc:arrayType="ns2:CurrentSecurityDetailsInfo[2]" xsi:type="soapenc:Array"
<secDet xsi:type="ns2:CurrentSecurityDetailsInfo">
<secChkID xsi:type="xsd:long">5</secChkID>
<secValue xsi:type="soapenc:string">Answer2</secValue>
</secDet>
<secDet xsi:type="ns2:CurrentSecurityDetailsInfo">
<secChkID xsi:type="xsd:long">6</secChkID>
<secValue xsi:type="soapenc:string">Answer3</secValue>
</secDet>
</secDet>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</cardHolderEnquiryReturn>
</ns1:cardHolderEnquiryResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

16.Balance Adjustment
The Balance Adjustment Web Service allows a card issuer to apply miscellaneous debits or credits to a cardholder account. Examples of use may include applying a miscellaneous
fee or charge, removal of a fee, or a credit to the card following a successful chargeback.
Amounts in this Web Service are not subjected to the full range of limit checking. Note that sufficient funds must exist on the card for a debit, and a credit cannot increase the card
balance beyond the defined maximum, where applicable.

Balance Adjustment Message
date.

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




<DOB> YYYY-MM- 10 10 Date of Birth C Om

DD
<CVV> AN 3 3 CVC2 C Om



DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
<amtAdjustment> D 1 20 The amount to debit or credit the card M Om
<currCode> AN 3 3 In Request: the currency alpha code of amtAdjustment. Must match the M M
currency of the card account
In Response: the currency alpha code of the avlBal (balance) returned. Will be
the currency of the card account.
<debOrCred> AN 1 1 Flag to indicate whether the adjustment is a debit or credit to the card: M Om
‘0’ – Debit
‘1’ – Credit
<description> AN 1 40 Description of balance adjustment. Will appear in Account Enquiry. M Om
<forcePost> N 1 1 Flag to indicate whether to force post the adjustment to the account: O Om
0 – Do not force posting
1 – Force posting
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


If <forcePost> value is 1, the adjustment will be posted to the account
regardless of restrictions such as insufficient funds or negative balance.
The exception to this is maximum balance limits and service deny. Force
posting will not override any maximum balance limits set for the card or
account and it will not apply adjustments if it not permitted by the card setup.
<extCode> AN 1 16 External code associated with the posting. O Om
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



0 – Unknown
3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
7 - Post Office
8 – Agent
9 – Head Office
10 – Call Centre
11 – In-store
12 - EPAY

0 – Unknown
1 – Cash
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


2 – Debit card
3 – Credit card
4 – Import
5 – Saving stamps
6 – Cheque
12 – Wallet

<avlBal> D 1 20 The balance on the card following the adjustment. This includes all the Om M
financials received but excludes pending authorisations
DD
<itemId> N 1 10 The unique item ID returned for the adjustment Om M

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
16.2. Example
16.2.1. Request
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<soapenv:Body>
<ns1:balanceAdjustment xmlns:ns1="urn:BalanceAdjustment"
<pobjBalanceAdjustmentRqstInfo href="#id0" />
</ns1:balanceAdjustment>
<multiRef xmlns:ns2="http://wsvalueobj.BalanceAdjustment.prepaid.webservices.cortex.com"
xsi:type="ns2:BalanceAdjustmentRqstInfo">
<amtAdjustment href="#id3" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<debOrCred href="#id4" />

<description xsi:type="soapenc:string">adjustment test</description>
<forcePost xsi:nil="true" xsi:type="xsd:int" />
<extCode xsi:nil="true" xsi:type="soapenc:string" />
</multiRef>
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:short">0</multiRef>
</soapenv:Body>
</soapenv:Envelope>
16.2.2. Response
<soapenv:Body>
<ns1:balanceAdjustmentResponse xmlns:ns1="urn:BalanceAdjustment"
<balanceAdjustmentReturn href="#id0" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</ns1:balanceAdjustmentResponse>
<multiRef xmlns:ns2="http://wsvalueobj.BalanceAdjustment.prepaid.webservices.cortex.com"
xsi:type="ns2:BalanceAdjustmentRspsInfo">
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

17.Card Application
The Card Application message may be used to request one or more cards. Anonymous (un‐personalised) cards will be generated based on the information provided in the
message. Multiple cards can be requested using this method.
For a personalised card, in addition to the information in the message, an XML file containing details of the personalised card must be attached to the Web Service call. The format
of the file must correspond with the version of the “Card Request Interface Specification” currently in production. Note that this method can be used only for a single new card
application; multiple cards, replacement cards or other actions are not supported.
If in doubt, confirm with the FIS Application Support Department.
Details of all cards produced will be returned in a list.

Card Application Message
date.
<authMethod> AN 1 1 Method used for cardholder authentication - refer to Appendix E. O Om

This field is not suitable for new card applications where no account exists. It
would be suitable where there is already a relationship with a cardholder e.g.
existing cardholder requesting an additional card.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



Required in request and response if <cardID> is not present and
<authMethod> is ‘1’, ‘2’, ‘3’, ‘4’ or ‘6’.
response.

Required in request and response if <PAN> is not present and <authMethod>
is ‘1’, ‘2’, ‘3’, ‘4’ or ‘6’.
not in request and cannot be derived from the PAN/track2.

DD

Applicable only if Track 2 on an existing card is used to authenticate a
cardholder requesting an additional card.
Mandatory in request and response if <authMethod> is ‘7’
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<accessCode> AN 1 12 Access Code C Om



DD
customer logins.
<crdprogram> AN 1 6 Card Program to be associated with the new card application. C Om

Mandatory for anonymous card applications, otherwise ignored.
<crddesign> AN 1 8 Pre-defined design reference code associated with the new card application. C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<carrierPAN> AN 1 19 Indicates whether a Carrier PAN should be associated with each new card: O Om
Y - Yes
N – No
Used only for anonymous card applications.
<stockNoStart> N 1 10 Indicates the starting stock number to be assigned to each card request. If O Om
value is 0, the stock number will start from 1.
If field not provided, no stock number will be generated.
Used only for anonymous card applications.
<currCode> AN 1 3 Currency code of cards requested. C Om

<crdproduct> AN 1 4 Card Product to be associated with the new card applications. C Om

<amtLoad> D 1 20 The amount to be loaded onto the new card. O Om

Optional for anonymous card applications, otherwise ignored.
<expDate> YYYY-MM- 10 10 Card expiry date. C Om

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<lang> AN 1 1 Cardholder language. Valid values are: C Om

1 – English
2 - French
3 – German
4 – Spanish
5 – Italian
6 – Portuguese
<pin> AN 1 1 Whether a PIN is required: C Om

0 – False
1 - True
<cardName> AN 1 21 or 27 Embossing name for the card. C Om

Optional for anonymous card applications, otherwise ignored.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<noOfCards> N 1 10 Number of cards to be generated. C C

Mandatory for anonymous card applications, otherwise informational only.
Note that for anonymous card applications, the maximum value for this field is
10. The purpose of <noOfCards> for anonymous cards is to allow buffering on
the client side, not for mass card production. Numbers greater than 10 will be
reduced to 10.
Returned in response if present in request.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<crdDet> - - - See Card Details section below Om M
<noOfCardsProduced> N 1 10 Number of cards successfully produced Om C
DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
CARD DETAIL BEGINS HERE
<result> AN 3 3 The action code of each card application Om C
<PAN> AN 16 19 Card Number generated by the application. Om C

response.
<DOB> YYYY-MM- 10 10 Date of Birth of the new card applicant. Om M

DD
<lastName> AN 1 20 Last name of the new card applicant. Om M
<title> AN 1 4 Title of the new card applicant. Om O
<firstName> AN 1 20 First name of the new card applicant. Om O
<addrL1> AN 1 35 Address Line 1 of the new card applicant. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<city> AN 1 20 City of the new card applicant. Om O
<county> AN 1 20 County of the new card applicant. Om O
<postcode> AN 1 10 Post Code of the new card applicant. Om O
<country> AN 1 3 Country code. of the new card applicant. Om O

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
<workAddrL1> AN 1 35 Work Address Line 1 of the new card applicant. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<workCity> AN 1 20 Work city of the new card applicant. Om O
<workCounty> AN 1 20 Work County of the new card applicant. Om O
<workCountry> AN 1 3 Work Country code. of the new card applicant. Om O

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
<workPostcode> AN 1 10 Work Post Code of the new card applicant. Om O
<workTel> AN 1 20 Work telephone no of the new card applicant. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<pobox> AN 1 8 PO Box of the new card applicant. Om O
<tel> AN 1 20 Telephone no of the new card applicant. Om O

e.g. 020 7292 2400 to +442072922400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
<email> AN 1 64 Email address of the new card applicant. Om O
<fax> AN 1 20 Fax no of the new card applicant. Om O
<mobTel> AN 1 20 Mobile telephone no of the new card applicant. Om O

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
<dlvTitle> AN 4 16 Delivery Title Om O
<dlvFirstName> AN 1 20 Delivery Firstname Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<dlvLastName> AN 1 20 Delivery Lastname Om O
<dlvCity> AN 1 20 Delivery City Om O
<dlvPostcode> AN 1 10 Delivery Post code Om O
<dlvCounty> AN 1 20 Delivery County Om O
<dlvCountry> AN 1 3 Delivery Country code. Om O

E.g.
826: UK
840: US
250: France
276: Germany
724: Spain
124: Canada
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<dlvTel> AN 1 20 Delivery Telephone number. Om O

e.g. 020 7292 2400 to +442072922400
e.g. +33 020 7292 2400 to +3302072922400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
is.
<dlvEffDate> YYYY-MM- 10 10 Date from which the delivery name and/or address became effective, Om C
DD inclusive.
<dlvExpDate> YYYY-MM- 10 10 Date after which the delivery name and/or address expires. Om C
DD
<maritalStatus> AN 1 1 S: Single Om O
M: Married
D: Divorced
W: Widowed
<sex> AN 1 1 M: Male Om O
F: Female
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<statCode> AN 2 3 The status code of the card Om M
<crdproduct> AN 1 4 Card product of the new card Om O
<custCode> AN 1 8 Cardholder’s FIS customer code. Om O
<accno> AN 1 28 Account number of the card Om O
<currCode> AN 1 3 Request : required if cardDetails are not supplied Om O

Response : Card currency code.
<expDate> YYYY-MM- 10 10 Request : required if cardDetails are not supplied Om O

DD
Response : card expiry date.
<effDate> YYYY-MM- 10 10 Card effective date. Om O

DD
<svccode> AN 1 3 Card Service Code. Om O
<embossName> AN 1 21 or 27 Name embossed on the card. Note that actual embossed name will not Om O
change until card is re-issued.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<additionalNo> N 1 1 Number of additional card. Zero indicates the card is a primary card. Om O
<dateCreated> YYYY-MM- 10 10 Calendar date the card was created in the FIS system. Om O
DD
<crdprogram> AN 1 6 Pre-defined program reference code associated with the card. Om O
<crddesign> AN 1 8 Pre-defined design reference code associated with the card. Om O
<pin> AN 1 1 To indicate whether the card should have a PIN: Om O

0: False
1: True
<refuseCheck> AN 1 1 Whether cheques should be refused. Om O

0: No
1: Yes
<mailShots> AN 1 1 Whether cardholder will accept mailshots or issuer contact. Om O

0: No
1: Yes
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<discret> AN 1 25 Discretionary data, for information only. Om O
<userdata> AN 1 30 Cardholder information stored at card level, free text field. Om O
<dlvMethod> AN 1 1 To indicate the delivery method for the card: Om O

0 – Standard mail
<dateActivated> YYYY-MM- 10 10 Calendar date the card was activated in the FIS system. Om O
DD
<loginID> AN 1 64 Login ID of the customer. Only applicable to systems using customer logins. C C
Returned in the response if a loginID is defined for this customer.
<imageID> AN 1 16 ID of the image to be printed on the card Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<renew> AN 1 1 To indicate whether the card will be renewed on expiry: Om O

0: No
1: Yes
<brncode> AN 8 8 Branch code (or Agent code) with which the card is associated. Om O
<denyMCC> AN 1 192 List of MCC’s (merchant category codes) that should be denied for the card. Om O
Eg:
4546,5462,5667-5673,5957
These restrictions are in addition to MCC restrictions defined at the Card
Product level.
<denySvc> AN 1 64 Comma separated list of services (authorisation transaction types) that should Om O
be denied for the card:
1 – Cash
These restrictions are in addition to service code restrictions defined at the
Card Product level.
<accType> AN 2 2 Type code for the account associated with the card. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<CVC2> AN 3 3 The 3-digit security number printed on the back of the card. Om C
CARD DETAIL ENDS HERE
17.2. Example
17.2.1. Request
------=_Part_0_6848169.1226074666616
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-Id: <DBB1BF6A478B36C63711984F04396D8A>

<soapenv:Body>
<ns1:cardApplication soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:CardApplication">
<pobjCardApplicationInfo xsi:type="ns2:CardApplicationRqstInfo"
xmlns:ns2="http://wsvalueobj.CardApplication.prepaid.webservices.cortex.com">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<instCode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">TEST</instCode>
<authMethod xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<PAN xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<DOB xsi:type="xsd:date" xsi:nil="true" />
<CVV xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<track2 xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<accessCode xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<lastName xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<loginID xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<crdprogram xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<crddesign xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<carrierPAN xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<stockNoStart xsi:type="xsd:int" xsi:nil="true" />
<currCode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">GBP</currCode>
<crdproduct xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">AAAA</crdproduct>
<amtLoad xsi:type="xsd:double" xsi:nil="true" />
<lang xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</lang>
<pin xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0</pin>
<cardName xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<noOfCards xsi:type="xsd:int">1</noOfCards>
<itemSrc xsi:type="xsd:short" xsi:nil="true" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<secDet xsi:type="ns3:SecurityDetailsInfo" xsi:nil="true"

xmlns:ns3="http://wsvalueobj.common.prepaid.webservices.cortex.com" />
</pobjCardApplicationInfo>
<cardDetails href="cid:4405CF00678BB1FAC026A9D5F1B12EBA" xsi:type="ns4:Source" xmlns:ns4="http://xml.apache.org/xml-
soap" />
</ns1:cardApplication>
</soapenv:Body>
</soapenv:Envelope>
------=_Part_0_6848169.1226074666616
Content-Type: text/xml
Content-Transfer-Encoding: binary
Content-Id: <4405CF00678BB1FAC026A9D5F1B12EBA>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<CRDREQ>
<CARD>
<RECID>1</RECID>
<INSTCODE>TEST</INSTCODE>
<PARTICIPANTID>0580</PARTICIPANTID>
<PROGRAMID>TTTTTT</PROGRAMID>
<CURRCODE>GBP</CURRCODE>
<CRDPRODUCT>AAAA</CRDPRODUCT>
<DESIGNREF>UAEA</DESIGNREF>
<TITLE>MR</TITLE>
<LASTNAME>MARTINTEST</LASTNAME>
<FIRSTNAME>MARTINTEST</FIRSTNAME>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<ADDRL1>1 TOWN STREET</ADDRL1>

<POSTCODE>W1 7JT</POSTCODE>
<DOB>1968-01-05</DOB>
<COUNTRY>826</COUNTRY>
<LANG>1</LANG>
<STATCODE>00</STATCODE>
<PRODUCEPIN>1</PRODUCEPIN>
<AWARDTEXT>CRI has Created your Card</AWARDTEXT>
<ACTION>1</ACTION>
</CARD>
</CRDREQ>
------=_Part_0_6848169.1226074666616--
17.2.2. Response
<soapenv:Body>
<ns1:cardApplicationResponse xmlns:ns1="urn:CardApplication"
<cardApplicationReturn xmlns:ns2="http://wsvalueobj.CardApplication.prepaid.webservices.cortex.com"
xsi:type="ns2:CardApplicationRspsInfo">
<instCode xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="soapenc:string">TEST</instCode>
<txnType xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="soapenc:string">17</txnType>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<loginID xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xsi:nil="true" xsi:type="soapenc:string" />
<crdDet xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" soapenc:arrayType="ns2:CardDetailsInfo[1]"
xsi:type="soapenc:Array">
<crdDet xsi:type="ns2:CardDetailsInfo">
<result xsi:type="soapenc:string">000</result>
<lastName xsi:type="soapenc:string">MARTINTEST</lastName>
<title xsi:type="soapenc:string">MR</title>
<firstName xsi:type="soapenc:string">MARTINTEST</firstName>
<addrL1 xsi:type="soapenc:string">1 ST STREET</addrL1>
<addrL2 xsi:type="soapenc:string" />
<addrL3 xsi:type="soapenc:string" />
<city xsi:type="soapenc:string">LONDON</city>
<county xsi:type="soapenc:string">LONDON</county>
<postcode xsi:type="soapenc:string">W1 7JT</postcode>
<country xsi:type="soapenc:string">826</country>
<workAddrL1 xsi:type="soapenc:string">1 Work Street</workAddrL1>
<workAddrL2 xsi:type="soapenc:string">Work place</workAddrL2>
<workAddrL3 xsi:type="soapenc:string" />
<workCity xsi:type="soapenc:string">LANDAN</workCity>
<workCounty xsi:type="soapenc:string">KENT</workCounty>
<workCountry xsi:type="soapenc:string">826</workCountry>
<workPostcode xsi:type="soapenc:string">SE16 4RT</workPostcode>
<workTel xsi:type="soapenc:string" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<pobox xsi:type="soapenc:string" />

<tel xsi:type="soapenc:string">020729210000</tel>
<email xsi:type="soapenc:string">J.SAMUEL@FSNET.CO.UK</email>
<fax xsi:type="soapenc:string" />
<mobTel xsi:type="soapenc:string">078001234512</mobTel>
<dlvTitle xsi:nil="true" xsi:type="soapenc:string" />
<dlvFirstName xsi:nil="true" xsi:type="soapenc:string" />
<dlvLastName xsi:nil="true" xsi:type="soapenc:string" />
<dlvCity xsi:nil="true" xsi:type="soapenc:string" />
<dlvPostcode xsi:nil="true" xsi:type="soapenc:string" />
<dlvCountry xsi:nil="true" xsi:type="soapenc:string" />
<dlvCounty xsi:nil="true" xsi:type="soapenc:string" />
<dlvTel xsi:nil="true" xsi:type="soapenc:string" />
<dlvEffDate xsi:nil="true" xsi:type="xsd:date" />
<dlvExpDate xsi:nil="true" xsi:type="xsd:date" />
<maritalStatus xsi:type="soapenc:string" />
<sex xsi:type="soapenc:string">M</sex>
<crdproduct xsi:type="soapenc:string">AAAA</crdproduct>
<custCode xsi:type="soapenc:string">55555555</custCode>
<accno xsi:type="soapenc:string">TTTTTT1111111</accno>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<effDate xsi:type="xsd:date">2008-11-07</effDate>
<svccode xsi:type="soapenc:string">221</svccode>
<embossName xsi:type="soapenc:string" />
<additionalNo xsi:type="xsd:int">23</additionalNo>
<dateCreated xsi:type="xsd:date">2008-11-07</dateCreated>
<crdprogram xsi:type="soapenc:string">TTTTTT</crdprogram>
<crddesign xsi:type="soapenc:string">UAEA</crddesign>
<pin xsi:type="soapenc:string">1</pin>
<refuseCheck xsi:type="soapenc:string" />
<mailShots xsi:type="soapenc:string">0</mailShots>
<discret xsi:type="soapenc:string" />
<userdata xsi:type="soapenc:string" />
<userdata1 xsi:type="soapenc:string" />
<dlvMethod xsi:type="soapenc:string">0</dlvMethod>
<dateActivated xsi:type="xsd:date">2008-11-07</dateActivated>
<imageID xsi:type="soapenc:string" />
<renew xsi:type="soapenc:string">1</renew>
<brncode xsi:type="soapenc:string">TTTTTT</brncode>
<denyMCC xsi:nil="true" xsi:type="soapenc:string" />
<denySvc xsi:nil="true" xsi:type="soapenc:string" />
<accType xsi:type="soapenc:string">00</accType>
<CVC2 xsi:type="soapenc:string">111</CVC2>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</crdDet>
</crdDet>
<noOfCardsProduced xsi:type="xsd:int">1</noOfCardsProduced>
<noOfCards xsi:type="xsd:int">1</noOfCards>
<actionCode xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="soapenc:string">000</actionCode>
</cardApplicationReturn>
</ns1:cardApplicationResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

18.Manage PIN
The Manage PIN message may be used to set, change or retrieve the PIN associated with the card. To use the functions supporting real-time PIN exchange, the communicating
systems must have the ability to:
• encrypt and decrypt an ANSI PIN block under a shared 3DES (double length) ‘zone PIN key’ (ZPK), also referred to as a ‘PIN key’ or ‘working key’
• encrypt and decrypt the shared ZPK under a shared 3DES (double length) ‘zone master key’ (ZMK), also referred to as a ‘key encrypting key’ or ‘transport key’, under which
the ZPK will be transported.
This system of encryption/decryption should be hardware-based (e.g. Thales HSM), conformant with security standards imposed by the payment network under which the card is
issued.
The mechanism for generating and communicating the keys between parties will be in accordance with standard FIS procedures.
Note: It is recommended that when using this Web Service to set or change PINs on EMV cards, that the Issuer informs the cardholder that they must then go to an ATM to
‘unblock’ or ‘unlock’ the PIN. This synchronises the PIN on the chip with the new PIN stored on FIS. If this action does not take place, transactions made using POS
terminals in the UK will be rejected, as all UK POS terminals perform offline PIN checking (the cardholder will expect to use their new PIN, but the chip will contain the old
PIN). ATM’s always perform online PIN checking so this problem is avoided. Note that as soon as a cardholder uses an EMV-enabled ATM or performs an online transaction
on an EMV-enabled POS terminal, the PIN on the chip will be automatically synchronised with the PIN on FIS.

Manage PIN Message
date.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage PIN Message


Required in request and response if <cardID> is absent and <authMethod> is
‘1’, ‘2’, ‘3’, ‘4’ or ‘6’.
response.

Required in request and response if <PAN> is absent and <authMethod> is ‘1’,
‘2’, ‘3’, ‘4’ or ‘6’.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage PIN Message


DD

customer logins.


DD
<function> AN 1 2 PIN function requested: M Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage PIN Message

00 – Set PIN
01 – Get PIN
02 – Change PIN
03 – Generate and Get PIN
04 – Request New PIN
05 – Request PIN Reminder
Note: <function> values 00 – 03 are effected real-time, whereas values 04 – 05
are batched for production and delivery by the PIN production bureau, in
accordance with the delivery method assigned to the cardholder.
<currentPIN> AN 16 16 Current PIN. C C

Represented as an ANSI PIN block encrypted under the ZPK indicated by
<keyRef>.
Note: The PIN block is based on the PAN. However, if the CardID is present, the
PIN block will be based on the CardID instead.
Usage dependent upon Request, Response, and <function>.
In Request, field is Mandatory for function 02. For all other functions, this field
will be ignored. In Response, this field is Mandatory for function 01. For all
other functions, this field will be omitted.
<newPIN> AN 16 16 New PIN. C C
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage PIN Message

<keyRef>.
In Request, field is Mandatory for functions 00 and 02. For all other functions,
this field will be ignored.
In Response, this field is Mandatory for function 03. For all other functions, this
field will be omitted.
<confirmPIN> AN 16 16 Confirmation of new PIN. C Om

<keyRef>.
In Request, field is Mandatory for functions 00 and 02. For all other functions,
this field will be ignored.
In Response, this field will be omitted.
<keyRef> AN 1 16 ZPK reference code for ANSI PIN block PIN encryption. C C
Mandatory for functions 00, 01, 02, 03.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage PIN Message

server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage PIN Message

must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

18.2. PIN field usage

The table below displays the conditions under which each of the xxxPIN fields must be present in the Request and Response for each <function>. ‘Y’ indicates field must be present.
Field
currentPIN newPIN confirmPIN
Function Request Response Request Response Request Response
00 – Set PIN Y Y
01 – Get PIN Y
02 – Change PIN Y Y Y
03 – Generate and Get PIN Y
04 - Request New PIN
05 - Request PIN Reminder
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

18.3. Example
18.3.1. Request
<soapenv:Body>
<ns1:managePIN soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:ManagePIN">
<pobjManagePINRqstInfo xsi:type="ns2:ManagePINRqstInfo"
xmlns:ns2="http://wsvalueobj.ManagePIN.prepaid.webservices.cortex.com">
<authMethod xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</authMethod>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">5274420063810855
</PAN>
<cardID xsi:type="soapenc:string" xsi:nil="true"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<track2 xsi:type="soapenc:string" xsi:nil="true"

<CVV xsi:type="soapenc:string" xsi:nil="true"
<accessCode xsi:type="soapenc:string" xsi:nil="true"
<loginID xsi:type="soapenc:string" xsi:nil="true"
<lastName xsi:type="soapenc:string" xsi:nil="true"
<function xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">01</function>
<currentPIN xsi:type="soapenc:string" xsi:nil="true"
<newPIN xsi:type="soapenc:string" xsi:nil="true"
<confirmPIN xsi:type="soapenc:string" xsi:nil="true"
<keyRef xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">OBERTHUR
</keyRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<ipAddress xsi:type="soapenc:string" xsi:nil="true"
</pobjManagePINRqstInfo>
</ns1:managePIN>
</soapenv:Body>
</soapenv:Envelope>
18.3.2. Response
<soapenv:Body>
<ns1:managePINResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:ManagePIN">
<managePINReturn xsi:type="ns2:ManagePINRspsInfo"
xmlns:ns2="http://wsvalueobj.ManagePIN.prepaid.webservices.cortex.com">
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">527442******0855
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</PAN>
<cardID xsi:type="soapenc:string"
</cardID>
<currentPIN xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">5C9C539E0B9E9156</currentPIN>
<newPIN xsi:type="soapenc:string" xsi:nil="true"
<keyRef xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">OBERTHUR
</keyRef>
</managePINReturn>
</ns1:managePINResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

19.Outgoing Transaction
This message is generated from FIS and sent to a member Web Service. The message will be used to send a transaction from the payment scheme3 onto another system e.g. for
approval or as a posting.
Note: The total amount of funds blocked on a cardholder’s account as a result of an authorisation is <billAmt> + <amtCom> + <amtPad>
Note: <amtPad> is applied only to the authorisation. To generate an indicative financial amount from the authorisation, use <billAmt> + <amtCom>

Outgoing Transaction Message
date.
<instCode> AN 1 4 Name of the issuing financial institution. M M
<txnType> AN 1 2 The Transaction Type. See Appendix C. M M
<msgType> N 3 3 Message type. Possible values are: M Om

100 – authorisation request
120 – authorisation advice
3
MasterCard or Visa
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


420 – reversal advice
<tlogId> N 1 10 Transaction unique identifier as defined by FIS CORTEX. M Om
<orgTlogID> N 1 10 The <tlogID> of the original transaction. C Om

Applies only to AUTHREV messages.
<repeat> AN 1 1 Indicates whether the message is a repeat of a message already received from C Om
the payment network:
0: False
1: True
Default is 0.
<timeout> 1 1 Indicates whether the message is for a timed-out original transaction i.e. C Om
where the payment network timed out:
0: False
1: True
Default is 0.
Applies only to reversal messages.
<PAN> AN 16 19 Card Number. C C

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


response.
If not present <cardID> must be provided.

<accNo> AN 1 24 Account Number. M Om
<curBill> AN 1 3 Account currency, expressed in ISO alpha format. M O
<avlBal> D 1 20 Balance of the card account. This includes all financials but ignores outstanding C C
authorisations.
Reserved for future use.
<blkAmt> D 1 20 Amount of funds blocked on the card account as a result of all outstanding C C
authorisations.
Reserved for future use.
<localDate> YYYY-MM- 10 10 The current date. M M

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<localTime> HHMMSS 6 6 The current time. M M
<amtTxn> D 1 20 Transaction amount, expressed in the transaction currency <curTxn>. M Om
<curTxn> AN 1 3 Transaction currency, expressed in ISO alpha format. M Om
<billAmt> D 1 20 Billing Amount. The transaction amount expressed in the account currency M Om
<accCur>.
<billConvRate> D 1 8 The conversion rate used to calculate the billing amount <billAmt> from the M Om
transaction amount <amtTxn>.
<amtCom> D 1 20 The total amount of all commissions added to the authorisation, except M Om
authorisation padding – see <amtPad>.
Expressed in the account currency <accCur>.
<amtPad> D 1 20 This field will show a combination of amtBill + amtPad. M Om

Expressed in the account currency <accCur>.
The amount of padding applied to the authorisation is not included within
<amtCom> as the padding is applied only to the authorisation, not to the
corresponding financial.
<txnCode> N 1 2 ISO transaction code of the authorisation: M Om

00: Sale/Purchase
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


01: Cash
09: Sale with cashback
11: Quasi cash
20: Redund
26: Cardholder funds transfer
28: Cash deposit
30: Balance enquiry (VISA)
31: Balance enquiry (MasterCard, LINK)
90: PIN change
94: PIN unblock
95: Application unblock
98: Account verification
<termCode> ANS 1 16 Terminal code. C Om

Mandatory if provided by the payment network.
<crdAcptID> ANS 1 15 Card Acceptor Identifier. C Om

<crdAcptLoc> ANS 1 64 Card Acceptor Location. C Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<MCC> N 4 4 Merchant Category Code. C Om

<poschp> AN 1 1 POS cardholder presence indicator: C Om

0: present
1: not present, unspecified
2: not present, mail order
3: not present, telephone order
4: not present, standing order
5: not present, electronic order
6: present, standing order
<poscdim> AN 1 1 POS card data input method: C Om

0: unspecified
1: manual, no terminal
2: mag stripe read
3: bar code read
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


4: OCR
5: ICC read
6: manually keyed
7: contactless ICC
8: ICC, data not reliable
9: Full track read
A: As S and chip cryptogram used
B: As T and chip cryptogram used
C: As V and chip cryptogram used
D: As V but merchant is capable of supporting SET
E: Contactless mag stripe
S: Merchant supports 3D secure
T: Full 3D secure transaction
U: E-Commerce no security
V: E-Commerce with channel encryption
<poscham> AN 1 1 POS cardholder authentication method: C Om

0: not authenticated
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1: PIN
2: electronic signature analysis
3: biometrics
4: biographic
5: manual signature verification
6: manual (other)
8: unknown
9: e-commerce transaction
<poscp> AN 1 1 POS card presence indicator: C Om

0: present
1: not present
<approvalCode> AN 4 6 Approval Code for authorisation. C C

Mandatory for approved transactions:
Mandatory in the Request if FIS is approving the authorisation.
Mandatory in the Response if the communicating system is approving the
authorisation.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Applies only to <AUTHADV>, <AUTHREQ> and <AUTHREV> messages.
<sysDate> YYYY-MM- 10 10 The Cortex processing system date. This date is used for reconciliation. M M
DD
<rev> AN 1 1 Indicates if this message is to reverse an earlier transaction. Possible values: O C

0 – False
1 – True
If the value is 1, the Item ID of the original transaction is specified in
<orgItemId>.
Mandatory in response if present in request.
<orgItemId> N 1 10 The item ID of the transaction to be reversed. C C

Mandatory in request for reversal messages i.e. where <rev>=1. Mandatory in
response if present in request.
<itemSrc> AN 1 2 Source field to define alternate fees. It is used in conjunction with existing fee O O
server Item
Defined options:
2 - Website
3 - IVR
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


4 - SMS
5 – mbanking
6 - SecureCode
<amtFee> D 1 20 Fee amount, expressed in the account currency <curBill>. M Om
<ctxLocalDate> YYYY-MM- 10 10 UK local date O Om

DD
<ctxLocalTime> HHMMSS 6 6 UK Local Time O Om
<aVSChkRs> AN 1 1 AVS check result. Refer to Appendix K: AVS Check Results. O Om
<threeDSecChkRs> AN 1 1 SecureCode check result. O Om

Possible values:
Y – 3D-secure data checked and correct
N – 3D-secure data checked and wrong
U – 3D-secure data not checked
<actionCode> AN 3 3 The action code for the response. O M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<amtCashback> D 1 20 Amount of cash included in amtTxn field. O Om
<trn> AN 1 25 Transaction ID (for VISA) or O Om

Trace ID (for MasterCard)
<txnsubcode> N 1 1 Transaction Sub Code. Possible values: O Om

0 = Unknown
1 = MasterCard rePower (this value is no longer used and future rePower
transactions will use a value of 4)
2 = Visa Mobile Gateway Transaction
3 = Offline Transaction
4 = Immediate Payment Transaction
5 = Incremental Auth
6 = Visa Fast Funds
19.2. Example
19.2.1. Request
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<soapenv:Body>
<ns1:outgoingTransaction soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:OutgoingTransaction">
<pobjWSOutgoingTransactionRqstInfo href="#id0" />
</ns1:outgoingTransaction>
xsi:type="ns2:OutgoingTransactionRqstInfo" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns2="http://wsvalueobj.OutgoingTransaction.prepaid.webservices.cortex.com">
<tlogId xsi:type="soapenc:string">477627</tlogId>
<amtTxn href="#id3" />
<curTxn xsi:type="soapenc:string">EUR</curTxn>
<txnCode href="#id4" />
<termCode xsi:type="soapenc:string">Term0004</termCode>
<crdAcptID xsi:type="soapenc:string">ID-Code06</crdAcptID>
<crdAcptLoc xsi:type="soapenc:string">Offsite ATM01~~St. Louis~90210 MO 840</crdAcptLoc>
<MCC href="#id5" />
<poschp xsi:type="soapenc:string">0</poschp>
<poscdim xsi:type="soapenc:string">9</poscdim>
<poscham xsi:type="soapenc:string">1</poscham>
<poscp xsi:type="soapenc:string">1</poscp>
<billAmt href="#id6" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<billConvRate href="#id7" />

<msgType xsi:type="soapenc:string">100</msgType>
<repeat href="#id8" />
<timeout href="#id9" />
<orgTlogID xsi:type="soapenc:string" xsi:nil="true" />
<accNo xsi:type="soapenc:string">12345678</accNo>
<amtPad href="#id10" />
<approvalCode xsi:type="soapenc:string">057184</approvalCode>
<amtFee href="#id11" />
<amtCom href="#id12" />
<amtPad href="#id13" />
<blkAmt href="#id14" />
</multiRef>
xsi:type="xsd:int"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0</multiRef>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">80.09</multiRef>
xsi:type="xsd:int"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


xsi:type="soapenc:double"
xsi:type="xsd:int"
xsi:type="xsd:int"
xsi:type="xsd:int"
xsi:type="xsd:long"
</soapenv:Body>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</soapenv:Envelope>
19.2.2. Response
<soapenv:Body>
<ns1:outgoingTransactionResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:OutgoingTransaction">
<outgoingTransactionReturn href="#id0" />
</ns1:outgoingTransactionResponse>
xsi:type="ns2:OutgoingTransactionResponse" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns2="http://wsvalueobj.OutgoingTransaction.prepaid.webservices.cortex.com">
<approvalCode xsi:type="soapenc:string" xsi:nil="true" />
<avlBal xsi:type="soapenc:double" xsi:nil="true" />
<blkAmt xsi:type="soapenc:double" xsi:nil="true" />
<localDate xsi:type="xsd:dateTime">2009-08-13T22:00:00.000Z</localDate>
<sysDate xsi:type="xsd:dateTime">2009-08-14T08:56:22.022Z</sysDate>
</multiRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


xsi:type="xsd:int"
xsi:type="xsd:long"
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

20.Manage Connection
The Manage Connection message provides an incoming and an outgoing service updating status of the host.

Manage Connection Message
date.

DD
<function> AN 2 2 Function which can have different values: M M

00 – ping
01 – sign on
02 – sign off
03 – advice recovery
04 –exception state
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Manage Connection Message

<hostName> AN 1 4 Name of the host M M
<sysDate> YYYY-MM- 10 10 The Cortex processing system date. This date is used for reconciliation. Om M
DD
<actionCode> AN 3 3 The action code for the response. Om M
20.2. Example
20.2.1. Request
<soapenv:Body>
<ns1:manageConnection soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:ManageConnection">
<pobjManageConnectionRqstInfo href="#id0" />
</ns1:manageConnection>
xsi:type="ns2:ManageConnectionRqstInfo" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns2="http://wsvalueobj.ManageConnection.prepaid.webservices.cortex.com">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<function xsi:type="soapenc:string">01</function>
<hostName xsi:type="soapenc:string">IDT</hostName>
</multiRef>
xsi:type="xsd:long" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">115800</multiRef>
xsi:type="xsd:int" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">21462</multiRef>
</soapenv:Body>
</soapenv:Envelope>
20.2.2. Response
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Body>
<ns1:manageConnectionResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:ManageConnection">
<manageConnectionReturn href="#id0" />
</ns1:manageConnectionResponse>
xsi:type="ns2:ManageConnectionRspsInfo" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns2="http://wsvalueobj.ManageConnection.prepaid.webservices.cortex.com">
<instCode xsi:type="soapenc:string">IDT</instCode>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<function xsi:type="soapenc:string">01</function>
<hostName xsi:type="soapenc:string">IDT</hostName>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

21.Validate Card
The Validate Card service verifies card details. The card details that can be verified are track2 and card PIN.

Validate Card Message
date.

Required in request and response if <authMethod> is ‘1’, ‘2’, ‘3’, ‘4’ or ‘6’
response.

Mandatory in request and response if either <authMethod> is ‘7’ or if neither
<cardID> nor <PAN> is provided.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



DD

customer logins.


DD
<PIN> AN 16 16 Current PIN. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Represented as an ANSI PIN block encrypted under the ZPK or TPK indicated by
<keyType and <keyRef>.
<EMVData> AN 1 1024 Card EMV data sent for verification. O Om

The EMV data is in binary format.
Customer should generate the EMV data in the above format (see Appendix I)
and then convert the entire string to HEX. The HEX data must be sent in this
tag.
<keyRef> AN 1 16 ZPK or TPK reference code for ANSI PIN block PIN encryption. C Om
server item. Possible options are:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



<sysDate> YYYY-MM- 10 10 The Cortex processing system date. It is used for reconciliation Om M
DD
<rejectReason> N 1 1 The Validate Card web service invokes the CRDCHK service. rejectReason is returned Om O
only when returned by the CRDCHK service. Possible values are as follows. One reject
reason can be shared by multiple failure scenarios.
34 Unable to begin SQL
35 Unable to commit SQL
600
PIN transaction and PIN tries exceeded has been set on card status
Card status is not approved
602 CVV validation failed
606 No expiry date with track data
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


610
Expiry date set in card has expired
Supplied expiry date in message has expired
613
Unable to get Fielded Buffer
Unable to set fielded buffer
614 No PIN block record for card
615
PVV validation failed for old card
PVV validation failed for new card
PVV value not in track or database
PVKI value not in track or database
616
Failed to verify PIN block
Failed to convert PIN block
617 Incorrect PIN entered
618 Update PIN try failed
619 Maximum PIN tries reached
623 Can't read card format record
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


624 Can't read card detail record
625
Failed to get card status
Failed to get PIN try card status [01]
626:
Can't get PAN or card sequence number or cardid from FB
Can't set PAN or card sequence number or cardid from FB
630 Can't read card PIN record
634 No PAN found in track data
693 Can't read crdproduct record
695 Card not yet effective
698 CVC validation failed
700 Invalid expiry date
703 Missing CVV / mandatory
705
Track 2 expiry date not same as in message and passed
Passed expiry date not same as card expiry date
709
Corrupted PVKI in T2
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Corrupted PVV in T2
714
CVV generation failed
iCVV generation failed
716 No service code found in track data
722 PAN in track not same in message
723 Track 2 expiry date not same as in message and also both expired
724 Can’t update card for PIN retry
753 Could not add card status history
763 Failed to generate CVC
767 Old card not expired
873 Other EMV error
1109 Mandatory data missing
1110
Invalid PIN key type
EMV data is invalid hex-string
1112 Failed to get system date
1121 Card not exists
1133 Date of birth not same
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1134 Access code not same
1141 Different institution
1142 Different card ID
corresponds. charPos 0 is the first character of the security value.
must be omitted.
21.2. Example
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

21.2.1. Request
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
<soapenv:Body>
<ns1:validateCard
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:ValidateCard">
<pobjValidateCardRqstInfo href="#id0" />
</ns1:validateCard>
xsi:type="ns2:ValidateCardRqstInfo" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns2="http://wsvalueobj.ValidateCard.prepaid.webservices.cortex.com">
<track2 xsi:type="soapenc:string" xsi:nil="true" />
<cardID xsi:type="soapenc:string" xsi:nil="true" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<accessCode xsi:type="soapenc:string">111</accessCode>
<loginID xsi:type="soapenc:string" xsi:nil="true" />
<lastName xsi:type="soapenc:string" xsi:nil="true" />
<PIN xsi:type="soapenc:string">D71822524FE51D94</PIN>
<EMVData xsi:type="soapenc:string">
82025800950580000400009a030905279c01315f2a0208269f02060000000000009f03060000000000009f1a0208269f1e0841544d30303030329f2608
f39d4eb8f402a71c9f2701809f33036040209f34030203009f3501149f360201519f37044f461ba59f53015a
</EMVData>
<keyRef xsi:type="soapenc:string">OBERTHUR</keyRef>
<secDet
xsi:type="ns3:SecurityDetailsInfo"
</multiRef>
xsi:type="xsd:int"
</multiRef>
xsi:type="xsd:long"
122300
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

21.2.2. Response
<soapenv:Envelope
<soapenv:Body>
<ns1:validateCardResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:ValidateCard">
<validateCardReturn href="#id0" />
</ns1:validateCardResponse>
xsi:type="ns2:ValidateCardRspsInfo" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns2="http://wsvalueobj.ValidateCard.prepaid.webservices.cortex.com">
<track2 xsi:type="soapenc:string" xsi:nil="true" />
<cardID xsi:type="soapenc:string"></cardID>
<loginID xsi:type="soapenc:string" xsi:nil="true" />
</multiRef>
</soapenv:Body>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

22.Wallet Enquiry
This is an enquiry service that provides details of all unexpired wallets. The service provides details of their effective/expiry dates as well as amount remaining and spend history.

Wallet Enquiry Message
date.
<txnType> AN 1 2 The transaction type. See Appendix C. M M
<authMethod> AN 1 1 Method used for cardholder authentication. See Appendix E. M Om

Mandatory if neither <track2> or <cardID> are provided.
response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



Mandatory in request and response if neither <cardID> nor <PAN> are present
<accno> AN 1 28 Account number of the card C C

If present will take priority in the enquiry process. If not present, account
associated with the PAN will be used.
<currCode> AN 3 3 The card currency alphabetic ISO code. C C

Mandatory if <accno> is provided.
DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




DD
<startDate> YYYY-MM- 10 10 Start date for the Enquiry. Only wallets which have not expired between O C
DD <startDate> and <endDate> will be returned as part of the enquiry.
If not present, ALL unexpired will be returned.
Must be present if <endDate> is present.
<endDate> YYYY-MM- 10 10 End date for the Enquiry. Only wallets which have not expired between O C
DD <startDate> and <endDate> will be returned as part of the enquiry.
If not present, ALL unexpired will be returned.
Must be present if <startDate> is present.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

<walletDetails> - - - See WALLET DETAILS definition below. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


DD
must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


WALLET DETAILS BEGINS HERE
<walletRef> AN 1 32 Wallet reference. Om M

This is used as an alternative to <walletID>
<walletID> N 1 10 Wallet ID. Om M

This is used as an alternative to <walletRef>.
<effectiveDate> YYYY-MM- 10 10 Effective date for the wallet. Om O

DD
<effectiveTime> HHMMSS 6 6 Effective time for the wallet. Om O
<expiryDate> YYYY-MM- 10 10 Expiry date for the wallet. Om O

DD
<expiryTime> HHMMSS 6 6 Expiry time for the wallet Om O
<currentBalance> D 1 20 The current balance of the wallet, expressed in the wallet currency. Om O
<curBill> AN 1 3 Wallet currency, represented in the alphabetic ISO code. Om O
<walletProfileRef> AN 1 32 Wallet profile reference. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<walletTxns> - - - See WALLET TRANSACTIONS definition below. Om O

WALLET DETAILS ENDS HERE
WALLET TRANSACTIONS BEGINS HERE
<txnID> N 1 10 The transaction ID. Om M
<amtSpent> D 1 20 The amount of the wallet transaction. Om O
<txnDate> YYYY-MM- 10 10 Calendar date on which CORTEX processed the transaction. Om O

DD
<txnTime> N 6 6 Time at which CORTEX processed the transaction. Om O
<localDate> YYYY-MM- 10 10 Calendar date the transaction was generated by the terminal (POS/ATM) or Om C
DD acquirer.
Applicable to network-received transactions only.
<amtTxn> D 1 20 The transaction amount, expressed in the transaction currency Om O
<curTxn> AN 1 3 Transaction currency, represented in the alphabetic ISO code. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<amtBill> D 1 20 The amount of the transaction billed (for financials) or blocked (for Om M
authorisations) to the cardholder account, expressed in the wallet currency
<curBill>
<debOrCred> AN 1 1 ‘0’ – Debit Om M

‘1’ – Credit
<crdAcptID> AN 1 15 Card Acceptor Identification Om C
<RRN> AN 1 12 Reference Number Om O
<description> AN 1 40 Transaction description Om M
<itemId> N 1 10 The item ID. Present in all returned items that impact the funds on the Om C
account.
<itemType> AN 1 2 The type of the item: Om C

0 – Load
1 – Unload
2 – Financial transaction
3 – Authorisation transaction, pending (currently blocking funds)
4 – Authorisation unblock (no longer blocking funds)
5 – Fee (financial)
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


6 – Balance Adjustment
7 – Fee (on pending authorisation, currently blocking funds)
8 – Account status change
<tlogID> N 1 10 The unique CORTEX-identifier of all network-received transactions. Om C

Applicable to net-work-received transactions only.
<messageID> N 1 10 Member identifier for all Web Service-received transactions. Om O

Applicable to Web Service-received transactions only.
<PAN> AN 16 19 Card Number Om M

response.
<CardID> AN 16 19 Unique internal card identification number. Om O
WALLET TRANSACTIONS ENDS HERE
22.2. Example
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

22.2.1. Request
<soapenv:Envelope
<soapenv:Body>
<ns1:walletEnquiry
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:WalletEnquiry">
<pobjWalletEnquiryRqstInfo xsi:type="ns2:WalletEnquiryRqstInfo" xmlns:ns2
="http://wsvalueobj.WalletEnquiry.prepaid.webservices.cortex.com"/>
<txnType xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">>22</txnType>
<authMethod xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</authMethod>
<PAN xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">5274420005774326</PAN>
<cardID xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<accessCode xsi:type ="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<lastName xsi:type ="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<localDate xsi:type ="xsd:date">2006-12-06</localDate>
<localTime xsi:type ="xsd:long">122300</localTime>
<startDate xsi:type ="xsd:date">2010-10-24</startDate>
<endDate xsi:type ="xsd:date">2010-10-24</endDate>
<loginID xsi:type ="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<itemSrc xsi:type ="xsd:short" xsi:nil="true" />

<secDet soapenc:arrayType="ns3:SecurityDetailsInfo[1]" xsi:type="soapenc:Array"
xmlns:ns3="http://wsvalueobj.common.prepaid.webservices.cortex.com"
<secDet xsi:type="ns3:SecurityDetailsInfo">
<charPos xsi:type ="xsd:int" xsi:nil="true" />
<secChkID xsi:type ="xsd:long">1</secChkID>
<secValue xsi:type ="soapenc:string">test12</secValue>
</secDet>
</secDet>
</pobjWalletEnquiryRqstInfo>
</ns1:walletEnquiry>
</soapenv:Body>
</soapenv:Envelope>
22.2.2. Response
<soapenv:Envelope
<soapenv:Body>
<ns1:walletEnquiryResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:WalletEnquiry">
<walletEnquiryReturn xsi:type="ns2:WalletEnquiryRspsInfo"
xmlns:ns2="http://wsvalueobj.WalletEnquiry.prepaid.webservices.cortex.com">
<PAN xsi:type="xsd:string">527442******4326</PAN>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<actionCode xsi:type="xsd:string">000</actionCode>
<cardID xsi:type="xsd:string">13467543678</cardID>
<endDate xsi:type="xsd:date">2010-10-24</endDate>
<instCode xsi:type="xsd:string">IDT</instCode>
<loginID xsi:type="xsd:string" xsi:nil="true" />
<startDate xsi:type="xsd:date">2010-10-24</startDate>
<txnType xsi:type="xsd:string">22</txnType>
<walletDet soapenc:arrayType="ns2:WalletDetailsInfo[1]" xsi:type="soapenc:Array"
<walletDet xsi:type="ns2:WalletDetailsInfo">
<curBill xsi:type="xsd:string">GBP</curBill>
<currentBalance xsi:type="xsd:double">156.5</currentBalance>
<effectiveDate xsi:type="xsd:date">2010-10-23</effectiveDate>
<effectiveTime xsi:type="xsd:long">0</effectiveTime>
<expiryDate xsi:type="xsd:dateTime" xsi:nil="true" />
<expiryTime xsi:type="xsd:long">0</expiryTime>
<walletID xsi:type="xsd:long">1</walletID>
<walletProfileRef xsi:type="xsd:string">TESTWALPROF</walletProfileRef>
<walletRef xsi:type="xsd:string">TESTWALREF</walletRef>
<walletTxns soapenc:arrayType="ns2:WalletTransactionsInfo[2]" xsi:type="soapenc:Array">
<walletTxns xsi:type="ns2:WalletTransactionsInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<RRN xsi:type="xsd:string">561234018222</RRN>
<amtSpent xsi:type="xsd:double">0.5</amtSpent>
<crdAcptID xsi:type="xsd:string">000000000MANSIG</crdAcptID>
<curTxn xsi:type="xsd:string">EUR</curTxn>
<debOrCred xsi:type="xsd:string">0</debOrCred>
<description xsi:type="xsd:string">Fin: PRIMARK, HARROW ON THE HILL LONDON </description>
<itemId xsi:type="xsd:string">54915</itemId>
<itemType xsi:type="xsd:string">2</itemType>
<txnID xsi:type="xsd:long">8</txnID>
</walletTxns>
<walletTxns xsi:type="ns2:WalletTransactionsInfo">
<RRN xsi:type="xsd:string" xsi:nil="true" />
<amtSpent xsi:type="xsd:double">10.0</amtSpent>
<crdAcptID xsi:type="xsd:string"> </crdAcptID>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<curTxn xsi:type="xsd:string" xsi:nil="true" />

<debOrCred xsi:type="xsd:string">0</debOrCred>
<description xsi:type="xsd:string">test wallet adjustment</description>
<itemId xsi:type="xsd:string">70556</itemId>
<itemType xsi:type="xsd:string">6</itemType>
<localDate xsi:type="xsd:dateTime" xsi:nil="true" />
<txnID xsi:type="xsd:long">1</txnID>
</walletTxns>
</walletTxns>
</walletDet>
</walletDet>
</walletEnquiryReturn>
</ns1:walletEnquiryResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

23.Balance Update
This web service allows the card issuer to apply an update to the balance of a cardholder account.

Balance Update Message
date.

response.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



Mandatory in request and response when the value of <authMethod> is ‘7’ or
if neither <cardID> nor <PAN> is present.
<accno> AN 1 28 Account number of the card whose balance will be updated. If not present, the C C
primary account of the <PAN>/<cardID>/ <track2> is used.
If <PAN>/< cardID >/< track2> and <ACCNO> are both present, <ACCNO> must
be associated with the <PAN>/<cardID>/ <track2>.
Mandatory in request and response if neither <cardID> nor <PAN> nor
<track2> is present or when the value of <authMethod> is ‘9’.

DD
Mandatory if the value of <authMethod> is ‘2’ or ‘6’.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<localDate> YYYY-MM- 10 10 The current date. M M

DD
customer logins.
<amtUpdate> D 1 20 The new available balance to set for the card account M Om
<currCode> AN 3 3 In Request: the currency alpha code of amtUpdate. Must match the currency M M
of the card account.
In Response: the currency alpha code of the avlBal (balance) returned. Will be
the currency of the card account.
<function> AN 1 2 Balance update function requested: O Om

00 – Balance overwrite (default)
<description> AN 1 40 Description of balance update. O Om
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<extCode> AN 1 16 External code associated with the posting. O Om
server Item.
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

0 – Unknown
3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


7 - Post Office
8 – Agent
9 – Head Office
10 – Call Centre
11 – In-store
12 - EPAY

0 – Unknown
1 – Cash
2 – Debit card
3 – Credit card
4 – Import
5 – Saving stamps
6 – Cheque
12 – Wallet
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<avlBal> D 1 20 The balance on the card following the Update. This includes all the financials Om M
received but excludes pending authorisations.
authorisations.
<sysDate> YYYY-MM- 10 10 The Cortex processing system date. This date is used for reconciliation. Om M
DD
<itemId> N 1 10 The unique item ID returned for the Update. Om M
<actionCode> AN 3 3 The action code for the response. Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
23.2. Example
23.2.1. Request
<soapenv:Body>
<ns1:balanceUpdate soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:BalanceUpdate">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<pobjBalanceUpdateRqstInfo xsi:type="ns2:BalanceUpdateRqstInfo"
xmlns:ns2="http://wsvalueobj.BalanceUpdate.prepaid.webservices.cortex.com">
<instCode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">IDT</instCode>
<amtUpdate xsi:type="xsd:double">1056.0</amtUpdate>
<accno xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">DDEBIT999900</accno>
<description xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">test balance
update</description>
<extCode xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<loadFundsType xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">12</loadFundsType>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<loadSrc xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />

<function xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">02</function>
<ipAddress xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
</pobjBalanceUpdateRqstInfo>
</ns1:balanceUpdate>
</soapenv:Body>
</soapenv:Envelope>
23.2.2. Response
<soapenv:Body>
<ns1:balanceUpdateResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:BalanceUpdate">
<balanceUpdateReturn xsi:type="ns2:BalanceUpdateRspsInfo"
xmlns:ns2="http://wsvalueobj.BalanceUpdate.prepaid.webservices.cortex.com">
<accno xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">DDEBIT999900</accno>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<itemId xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0</itemId>
<actionCode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">000</actionCode>
</balanceUpdateReturn>
</ns1:balanceUpdateResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

24.SMS Reminders
This web service allows a card issuer to send SMS reminders to the cardholder.

SMS Reminders Message
date.
<instCode> AN 1 4 Name of the issuing financial institution. M M

Required in request and response if <cardID> is absent and <authMethod> is
‘1’, ‘2’, ‘3’, ‘4’ or ‘6’.
response.
If not present, <cardID> or <track2> must be provided.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Required in request and response if <PAN> is absent and <authMethod> is ‘1’,
‘2’, ‘3’, ‘4’ or ‘6’.


DD
Mandatory if the value of <authMethod> is ‘2’ or ‘6’.
Mandatory if value of <authMethod> is ‘3’.

customer logins.
Mandatory if the value of <authMethod> = ‘5’.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




DD
<function> AN 1 2 SMS reminder function requested: O Om

00 – PIN reminder (default)
114 – CVV Pan Reminder
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
24.2. Example
24.2.1. Request
<soapenv:Body>
<ns1:smsReminders soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:SMSReminders">
<pobjSMSRemindersRqstInfo xsi:type="ns2:SMSRemindersRqstInfo"
xmlns:ns2="http://wsvalueobj.SMSReminders.prepaid.webservices.cortex.com">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<function xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">00</function>
</pobjSMSRemindersRqstInfo>
</ns1:smsReminders>
</soapenv:Body>
</soapenv:Envelope>
24.2.2. Response
<soapenv:Body>
<ns1:smsRemindersResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:SMSReminders">
<smsRemindersReturn xsi:type="ns2:SMSRemindersRspsInfo"
xmlns:ns2="http://wsvalueobj.SMSReminders.prepaid.webservices.cortex.com">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</smsRemindersReturn>
</ns1:smsRemindersResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

25.Reset Fraud Status

This web service should be used to change the status of a card from fraud monitoring status (status 14) to its previous status.

Reset Fraud Status Message
date.

response.

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100




Note that method 5 (loginID) is not possible in this message.
DD



DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
<reason> AN 1 60 Reason for Reset Fraud Status. M Om

Overrides default of ‘Card Reset Fraud Status’ that will be shown in Panorama.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


DD
must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

25.2. Example
25.2.1. Request
<soapenv:Body>
<ns1:resetFraudStatus soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:ResetFraudStatus">
<pobjResetFraudStatusRqstInfo xsi:type="ns2:ResetFraudStatusRqstInfo"
xmlns:ns2="http://wsvalueobj.ResetFraudStatus.prepaid.webservices.cortex.com">
<CVV xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
</CVV>
<accessCode xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
</accessCode>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<lastName xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">

</lastName>
<crdAcptID xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
</crdAcptID>
<loginID xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
</loginID>
<reason xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">testing changing
status </reason>
</pobjResetFraudStatusRqstInfo>
</ns1:resetFraudStatus>
</soapenv:Body>
</soapenv:Envelope>
25.2.2. Response
<soapenv:Body>
<ns1:resetFraudStatusResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<resetFraudStatusReturn xsi:type="ns2:ResetFraudStatusRspsInfo"
xmlns:ns2="http://wsvalueobj.ResetFraudStatus.prepaid.webservices.cortex.com">
<PAN xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">123456******1234</PAN>
26.Outgoing Notification
This message is generated from FIS and sent to a client’s Web Service. The message will be used to send a notification to the client for the card holder.
FIS will send an appropriate notification content, based on notification type, which can be processed by the client.
For those fields that are present in the request and in the response, the value in the response must be returned unchanged from that in the request.
The current available <actionCode> value for this message is 000. Refer to Appendix B for the meaning of this value.

Outgoing Notification Message
Tag Type Min Len. Max Len. Description Req Rsp
<messageID> N 1 10 Message ID. Should be unique for every message request sent M M
<PAN> AN 4 4 The last 4 digits of the Card Number. C C

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


If not present <cardID> must be provided.


DD
<crdProfileRef> AN 1 32 Card Profile Reference O Om
<notifType> N 1 2 The notification type. Valid values are M M

100 - Load notification
101 - Balance notification
102 - Minimum balance notification
103 - EMS fraud notification
104 - Access code notification
105 - Security question notification
106 - Card PIN notification
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


107 - Transaction notification
108 - Card Upgrade notification
109 - Reversal transaction notification
110 - KYC pass for upgrade when load limit exceeded notification
111 - KYC fail for upgrade when load limit exceeded notification
112 - KYC pass for upgrade when customer duplicated notification
113 - KYC fail for upgrade when customer duplicated notification
114 - Card information notification
115 - Monthly fee failure notification
116 - Card product update notification
117 - Card blocking (when customer duplicate) notification
118 - Card request pended (when customer duplicate) notification
<notifContent> AN 1 1024 The content containing details of the notification. M Om
Note: This element value could be encrypted for some notification types:
When <notifType> is 106, contains encrypted content as hex-string.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


configured, telephone numbers are stored as received. However, this processing is
required for using SMS services.
1. Strips all special characters, including spaces, left parenthesis, right parenthesis,
and hyphen (-).
2. Rejects any numbers containing non-numeric characters with the exception of
the prefix “+”.
e.g. 020 7292 2400 to +442072922400
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


e.g. +33 020 7292 2400 to +3302072922400
+44 (0) 20 7292 2400 to +442072722400
+44 20 7292 2400 to +442072722400
0044 (0) 20 7292 2400 to +442072722400
6. If there is no "+" prefix, international dialling prefix or national dialling prefix,
the number is rejected.
<email> AN 1 64 Email address O Om
26.2. Example
26.2.1. Request
<soapenv:Body>
<ns1:outgoingNotification xmlns:ns1="urn:OutgoingNotification"
<pobjWSOutgoingNotificationRqstInfo xmlns:ns2="http://wsvalueobj.OutgoingNotification.prepaid.webservices.cortex.com"
xsi:type="ns2:OutgoingNotificationRqstInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<crdProfileRef xsi:type="soapenc:string">19136</crdProfileRef>
<notifType xsi:type="xsd:int">106</notifType>
<notifContent
xsi:type="soapenc:string">382B82663993FD0EE591F0CE6B085989781A78EF3699A1C0FA542FB23AE52CD7D903994216D8A3CE3E073DBFCC09C4D9
634019523B5CE37E39A9256661918CBF966C09EAFB11D240</notifContent>
<mobTel xsi:type="soapenc:string">+447891234567</mobTel>
<email xsi:type="soapenc:string">someone@fisglobal.com</email>
</pobjWSOutgoingNotificationRqstInfo>
</ns1:outgoingNotification>
</soapenv:Body>
</soapenv:Envelope>
26.2.2. Response
<soapenv:Body>
<ns1: outgoingNotificationResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<outgoingNotificationReturn xsi:type="ns2:OutgoingNotificationResponse"
xmlns:ns2="http://wsvalueobj.OutgoingNotification.prepaid.webservices.cortex.com">
<notifType xsi:type="xsd:int">106</notifType>
</outgoingNotificationReturn>
</ns1:outgoingNotificationResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

27.Card Activation Reversal

This web service will reverse the card activation process and also void the load if any was assocated with the activation. This process will be rejected if there is usage detected on
the card.

Card Activation Reversal Message
date.

Note that method 5 (loginID) and method 9 (Account number and currency
code) is not possible in this message.

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



<DOB> YYYY-MM- 10 10 Date of Birth. Mandatory if the value of <authMethod> is ‘2’ or ‘6’. C C
DD
Conditional in request: needs to be present if the associated authmethod
used.
<track2> AN 1 40 The Track 2. C Om

<accessCode> AN 1 12 Access code. C Om



DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<sysDate> YYYY-MM- 10 10 The Cortex processing system date. This date is used for reconciliation Om O
DD
must be omitted.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

27.2. Example
27.2.1. Request
<soapenv:Body>
<ns1:cardActivationReversal xmlns:ns1="urn:CardActivationReversal"
<pobjCardActivationReversalRqstInfo href="#id0" />
</ns1:cardActivationReversal>
<multiRef xmlns:ns2="http://wsvalueobj.CardActivationReversal.prepaid.webservices.cortex.com"
xsi:type="ns2:CardActivationReversalRqstInfo">
<cardID xsi:type ="soapenc:string" xsi:nil ="true" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</multiRef>
</soapenv:Body>
</soapenv:Envelope>
27.2.2. Response
<soapenv:Body>
<ns1:cardActivationReversalResponse xmlns:ns1="urn:CardActivationReversal"
<cardActivationReversalReturn href="#id0" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</ns1:cardActivationReversalResponse>
<multiRef xmlns:ns2="http://wsvalueobj.CardActivationReversal.prepaid.webservices.cortex.com"
xsi:type="ns2:CardActivationReversalRspsInfo">
<cardID xsi:type="soapenc:string"></cardID>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

28.Limit Enquiry
This is an enquiry service that provides details for card, account and customer limits.

Limit Enquiry Message
date.

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<track2> AN 1 40 The card’s Track 2. C Om

DD



DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


customer logins.
server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

<cardLimDet> - - - See CARD LIMIT DETAILS definition below. Om O
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<accLimDet> - - - See ACCOUNT LIMIT DETAILS definition below. Om O

<custLimDet> - - - See CUSTOMER LIMIT DETAILS definition below. Om O

<indCardLimDet> - - - See CARD LIMIT DETAILS definition below. Om O

<indAccLimDet> - - - See ACCOUNT LIMIT DETAILS definition below. Om O

<indCustLimDet> - - - See CUSTOMER LIMIT DETAILS definition below. Om O

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
CARD LIMIT DETAILS BEGINS HERE

Card Number
<PAN> AN 16 19 Om M
response.
Unique internal card identification number.
<cardID> AN 16 19 Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<limits> - - - See LIMITS definition below. Om O

CARD LIMIT DETAILS ENDS HERE
ACCOUNT LIMIT DETAILS BEGINS HERE

Card Account Number
<accno> AN 1 28 Om M
Limit currency, represented in the alphabetic ISO code.
<currCode> AN 3 3 Om M

ACCOUNT LIMIT DETAILS ENDS HERE
CUSTOMER LIMIT DETAILS BEGINS HERE

Cardholder’s FIS customer code.
<custCode> AN 1 8 Om M

CUSTOMER LIMIT DETAILS ENDS HERE
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


LIMITS DEFINITION BEGINS HERE
<limDet> - - - See LIMIT DETAILS definition below. Om M

LIMITS DEFINITION ENDS HERE
LIMIT DETAILS DEFINITION BEGINS HERE
<limType> N 1 3 Limit type: Om M

0 - load limit
1 - cash transaction limit
2 - purchase transaction limit
3 - debit transaction limit
4 - credit transaction limit
100 - balance limit
<cycleProfRef> AN 0 32 The cycle profile reference code. Not Returened for Indivdual Limits. Om O
<cycleLen> N 1 5 The cycle length: Om M

0 - per transaction
1 - daily
2-999 - 2-999 daily
1000 - weekly (from any day of week)
1001 - weekly and begin from Monday
1002 - weekly and begin from Tuesday
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1003 - weekly and begin from Wednesday
1004 - weekly and begin from Thursday
1005 - weekly and begin from Friday
1006 - weekly and begin from Saturday
1007 - weekly and begin from Sunday 1100 - fortnightly (from any day of
week)
1101 - fortnightly and begin from Monday
1102 - fortnightly and begin from Tuesday
1103 - fortnightly and begin from Wednesday
1104 - fortnightly and begin from Thursday
1105 - fortnightly and begin from Friday
1106 - fortnightly and begin from Saturday
1107 - fortnightly and begin from Sunday
1200 - bimonthly (half month)
1300 - monthly (from any day of month)
1301-1331 - monthly and begin from 1st to 31st (is available)
1400 - quarterly
1401 - quarterly and begin from 1st of Jan/Apr/Jul/Oct
1500 - biyearly (half year)
1501 - biyearly (half year) and begin from 1st of Jan and Jul
1600 - yearly
1601 - yearly and begin from 1st of Jan
2000 - life
<currCode> AN 3 3 Cycle profile currency or limit profile currency, represented in the alphabetic Om M
ISO code.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<allCurr> N 1 5 Whether for all currencies: Om M

0 - no
1 - yes
<cycBeginDate> YYYY-MM- 10 10 Cycle begin date Om M

DD
<cycEndDate> YYYY-MM- 10 10 Next cycle beginning date Om M

DD
<cycAmt> D 1 20 Total amount in the cycle. Om M
<cycNum> N 1 10 Total number in the cycle. Om M
<limRef> AN 1 32 Limit reference code. Om M
<limDesc> AN 1 255 Limit description Om M
<maxAmt> D 1 20 Maximum amount limit. If limit type is 100, it is maximum balance limit. Om M
0 means no limit.
<minAmt> D 1 20 Minimum amount limit. Used only for limit per transaction (i.e. cycle length is Om M
0).
0 means no limit
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<maxNum> N 1 20 Maximum number limit. Not used for limit type 100, or limit per transaction Om M
(i.e. cycle length is 0).
0 means no limit.
Placeholder for future use. Currently fixed to 2263-08-31
<lastExcDate> YYYY-MM- 10 10 Om M
DD
LIMIT DETAILS DEFINITION ENDS HERE
28.2. Example
28.2.1. Request

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:LimitEnquiry"
<soapenv:Header/>
<soapenv:Body>
<urn:limitEnquiry soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<pobjLimitEnquiryRqstInfo xsi:type="wsv:LimitEnquiryRqstInfo"
xmlns:wsv="http://wsvalueobj.LimitEnquiry.prepaid.webservices.cortex.com">
<instCode xsi:type="soapenc:string">IDT</instCode>
<secDet xsi:type="urn:ArrayOf_tns3_SecurityDetailsInfo" soapenc:arrayType="wsv1:SecurityDetailsInfo[]"
xmlns:wsv1="http://wsvalueobj.common.prepaid.webservices.cortex.com"/>
</pobjLimitEnquiryRqstInfo>
</urn:limitEnquiry>
</soapenv:Body>
</soapenv:Envelope>
28.2.2. Response
?xml version="1.0" encoding="UTF-8"?>
<soapenv:Body>
<ns1:limitEnquiryResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:LimitEnquiry">
<limitEnquiryReturn xsi:type="ns2:LimitEnquiryRspsInfo"
xmlns:ns2="http://wsvalueobj.LimitEnquiry.prepaid.webservices.cortex.com">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</PAN>
</cardID>
<cardLimDet xsi:type="ns2:CardLimitInfo" xsi:nil="true" />
<accLimDet xsi:type="ns2:AccountLimitInfo" xsi:nil="true" />
<custLimDet soapenc:arrayType="ns2:CustomerLimitInfo[1]"
<custLimDet xsi:type="ns2:CustomerLimitInfo">
<custCode xsi:type="soapenc:string">00003529</custCode>
<limits soapenc:arrayType="ns2:LimitsInfo[1]" xsi:type="soapenc:Array">
<limits xsi:type="ns2:LimitsInfo">
<limDet soapenc:arrayType="ns2:LimitInfo[3]" xsi:type="soapenc:Array">
<limDet xsi:type="ns2:LimitInfo">
<limType xsi:type="xsd:int">0</limType>
<cycProfRef xsi:type="soapenc:string"></cycProfRef>
<cycLen xsi:type="xsd:int">1001</cycLen>
<currCode xsi:type="soapenc:string">826</currCode>
<allCurr xsi:type="soapenc:string">0</allCurr>
<cycBeginDate xsi:type="xsd:date">2263-08-31</cycBeginDate>
<cycEndDate xsi:type="xsd:date">2263-08-30</cycEndDate>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<cycAmt xsi:type="xsd:double">0.0</cycAmt>
<cycNum xsi:type="xsd:int">0</cycNum>
<limRef xsi:type="soapenc:string">
</limRef>
<limDesc xsi:type="soapenc:string">test</limDesc>
<maxAmt xsi:type="xsd:double">10.0</maxAmt>
<minAmt xsi:type="xsd:double">100.0</minAmt>
<maxNum xsi:type="xsd:int">20</maxNum>
<lastExcDate xsi:type="xsd:date">2263-08-31</lastExcDate>
</limDet>
</limRef>
<limDesc xsi:type="soapenc:string">another test</limDesc>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</limDet>
</limRef>
<limDesc xsi:type="soapenc:string">Limit detail 6</limDesc>
</limDet>
</limDet>
</limits>
</limits>
</custLimDet>
</custLimDet>
<indCardLimDet soapenc:arrayType="ns2:CardLimitInfo[1]"
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<indCardLimDet xsi:type="ns2:CardLimitInfo">
<limits soapenc:arrayType="ns2:LimitsInfo[1]" xsi:type="soapenc:Array">
<limits xsi:type="ns2:LimitsInfo">
<limDet soapenc:arrayType="ns2:LimitInfo[1]" xsi:type="soapenc:Array">
<cycProfRef xsi:type="soapenc:string" xsi:nil="true" />
<currCode xsi:type="soapenc:string">USD</currCode>
<limRef xsi:type="soapenc:string">test1</limRef>
<limDesc xsi:type="soapenc:string"></limDesc>
</limDet>
</limDet>
</limits>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</limits>
</indCardLimDet>
</indCardLimDet>
<indAccLimDet xsi:type="ns2:AccountLimitInfo" xsi:nil="true" />
<indCustLimDet xsi:type="ns2:CustomerLimitInfo" xsi:nil="true" />
</limitEnquiryReturn>
</ns1:limitEnquiryResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

29.Remove Authorisation
The Remove Authorisation removes the pending authorization.

Remove Authorisation Message
Tag Type Min Max Length Description Request Response
Length
<messageID> N 1 10 Message ID. Should be unique for every message request sent on a M M
particular date.

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Length
Present in response if present in the request. Cannot be sent in response
when not in request and cannot be derived from the PAN/Track2.
<tlogId> N 1 10 Transaction unique identifier as defined by FIS CORTEX. M M
<reason> AN 1 60 Reason for remove Authorisation O Om

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Length
<itemSrc> N 1 5 Source field to define alternate fees. It is used in conjunction with existing O Om
fee server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 – SecureCode
DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Length

DD
Mandatory if value of <actMethod> is ‘1’. In this case it will be used for
authentication only.
Otherwise, if <actMethod> is not ‘1’ and <lastName> has been provided,
this sets the cardholder’s date of birth.
description in the Cardholder Update message for the impact of this
change.

Mandatory in request and response if neither <PAN> nor <cardID> is
present or when <actMethod> is ‘4’
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Length
<CVV> AN 3 3 Card Verification Value, the 3-digit code printed on the back of the card. C Om
Mandatory if the value of <actMethod> is ‘2’
<lastName> AN 1 20 Customer’s last name. O Om

This must be present in order to update personal details such as address
and telephone number.
Sending a ‘space’ will clear this field. If <lastName> is cleared, <firstName>
will automatically be cleared.
customer logins.


+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Length
<charPos> N 1 2 Identifies the position in the stored security value to which - -

secValue corresponds. charPos 0 maps to the first character of
the security value.
Used when the security check associated with the secChkID is for
matching character based verification in a security value, rather
than the whole value. secChkID is normally mentioned in your
member profile, so refer to this if you would like to know if you
are using full value or character based verification.
Mandatory if secChkID indicates character based verification,
otherwise field must be omitted.
<secValue> AN 1 64 Value associated with security secChkID. Each secValue must - -

immediately follow its associated secChkID.
29.2. Example
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

29.2.1 Request

<soapenv:Body>
<ns1:RemoveAuthorisation soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:RemoveAuthorisation">
<pobjRemoveAuthorisationRqstInfo xsi:type="ns2:RemoveAuthorisationRqstInfo"
xmlns:ns2="http://wsvalueobj.RemoveAuthorisation.prepaid.webservices.cortex.com">
<tlogId xsi:type="xsd:int">213</tlogId>
<reason xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">any</reason>
<accessCode xsi:type="soapenc:string" xsi:nil="true"
<itemSrc xsi:type="xsd:short">1</itemSrc>
<crdAcptID xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


</pobjRemoveAuthorisationRqstInfo>
</ns1:RemoveAuthorisation>
</soapenv:Body>
</soapenv:Envelope>
29.2.2 Response

<soapenv:Body>
<ns1:RemoveAuthorisationResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:RemoveAuthorisation">
<removeAuthorisationReturn xsi:type="ns2:RemoveAuthorisationRspsInfo"
xmlns:ns2="http://wsvalueobj.RemoveAuthorisation.prepaid.webservices.cortex.com">
</PAN>
</cardID>
<tlogId xsi:type="soapenc:int" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">213</tlogId>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</removeAuthorisationReturn>
</ns1:RemoveAuthorisationResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

30.Limit Update
This is an update service that sets bespoke limits at an individual card, account and customer level.
Note Cortex takes into account all limits wherever set e.g. product level, account type level, profile level or individual card/account/customer level (the latter as set by the Limit
Update web service) when deciding to approve or decline a transaction authorisation request.

date.

response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100



<track2> AN 1 40 The card’s Track 2. C Om

<limAction> AN 1 1 Action:
A - Add new limit
M - Modify limit
D - Delete limit
R - Reset counter
<limOwner> N 1 1 Owner code:

1 - customer
2 - card
3 - account
<limRef> AN 1 32 Limit reference code. Om M

<currCode> AN 3 3 Om M
Limit id
<limID> N 1 11 Om M
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


modLimit - - - See MOD LIMIT DETAILS definition below
addLimit - - - See ADD LIMIT DETAILS definition below
resetLimit - - - See RESET LIMIT DETAILS definition below
DD



DD
customer logins.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


server Item
Defined options:
2 - Website
3 - IVR
4 - SMS
5 – mbanking
6 - SecureCode

DD
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


must be omitted.
MOD LIMIT DETAILS BEGINS HERE
0 means no limit.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


0).
0 means no limit
0 means no limit.
MOD LIMIT DETAILS BEGINS HERE
ADD LIMIT DETAILS BEGINS HERE
<limType> N 1 3 Limit type: Om M

0 - load limit
1 - cash transaction limit
2 - purchase transaction limit
3 - debit transaction limit
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


4 - credit transaction limit
100 - balance limit
<curBill> AN 3 3 Om M

0 – Unknown
1 – Cash
2 – Debit card
3 – Credit card
4 – Import
5 – Saving stamps
6 – Cheque
12 – Wallet
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


<loadSrc> AN 1 3 The source of the request O Om

0 – Unknown
3 – IVR
4 – Website
5 – Paypoint
6 – Payzone
8 – Agent
9 – Head Office
10 – Call Centre
<allCurr> N 1 5 Whether for all currencies: Om M

0 - no
1 - yes
0 means no limit.
0).
0 means no limit
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


0 means no limit.
<cycleLen> N 1 5 The cycle length: Om M

0 - per transaction
1 - daily
2-999 - 2-999 daily
1000 - weekly (from any day of week)
1001 - weekly and begin from Monday
1002 - weekly and begin from Tuesday
1003 - weekly and begin from Wednesday
1004 - weekly and begin from Thursday
1005 - weekly and begin from Friday
1006 - weekly and begin from Saturday
1007 - weekly and begin from Sunday 1100 - fortnightly (from any day of
week)
1101 - fortnightly and begin from Monday
1102 - fortnightly and begin from Tuesday
1103 - fortnightly and begin from Wednesday
1104 - fortnightly and begin from Thursday
1105 - fortnightly and begin from Friday
1106 - fortnightly and begin from Saturday
1107 - fortnightly and begin from Sunday
1200 - bimonthly (half month)
1300 - monthly (from any day of month)
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


1301-1331 - monthly and begin from 1st to 31st (is available)
1400 - quarterly
1401 - quarterly and begin from 1st of Jan/Apr/Jul/Oct
1500 - biyearly (half year)
1501 - biyearly (half year) and begin from 1st of Jan and Jul
1600 - yearly
1601 - yearly and begin from 1st of Jan
2000 - life
cycBeginType N 1 5 Cycle beginning type: Om M

0 - first transaction/load date
2 - activation date
3 - creation date
ADD LIMIT DETAILS ENDS HERE
RESET LIMIT DETAILS BEGINS HERE

Reason to reset
<whyReset> AN 1 255 Om M
RESET LIMIT DETAILS ENDS HERE
30.2. Example
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

30.2.1 Request

<soapenv:Body>
<ns1:limitUpdate soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:LimitUpdate">
<pobjLimitUpdateRqstInfo xsi:type="ns2:LimitUpdateRqstInfo"
xmlns:ns2="http://wsvalueobj.LimitUpdate.prepaid.webservices.cortex.com">
<limAction xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">A</limAction>
<limOwner xsi:type="xsd:short">2</limOwner>
<limRef xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">test1</limRef>
<limID xsi:type="xsd:int" xsi:nil="true" />
<currCode xsi:type="soapenc:string" xsi:nil="true"
<modLimit xsi:type="ns2:UpdateLimitDetailsInfo">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<limDesc xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">testing modify lim
id2</limDesc>
</modLimit>
<addLimit xsi:type="ns2:AddLimitDetailsInfo">
<limType xsi:type="xsd:short">1</limType>
<curBill xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">USD</curBill>
<loadFundsType xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<loadSrc xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1</loadSrc>
<allCurr xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
<cycLen xsi:type="xsd:short">0</cycLen>
<cycBeginType xsi:type="xsd:short" xsi:nil="true" />
<limDesc xsi:type="soapenc:string" xsi:nil="true" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
</addLimit>
<resetLimit xsi:type="ns2:ResetLimitDetailsInfo">
<whyReset xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"> to reset</whyReset>
</resetLimit>
<itemSrc xsi:type="xsd:short">1</itemSrc>
</pobjLimitUpdateRqstInfo>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</ns1:limitUpdate>
</soapenv:Body>
</soapenv:Envelope>
30.2.2 Response

<soapenv:Body>
<ns1:limitUpdateResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:LimitUpdate">
<limitUpdateReturn xsi:type="ns2:LimitUpdateRspsInfo"
xmlns:ns2="http://wsvalueobj.LimitUpdate.prepaid.webservices.cortex.com">
</PAN>
</cardID>
<limAction xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">A</limAction>
<limOwner xsi:type="xsd:int" xsi:nil="true" />
<limID xsi:type="xsd:int">8</limID>
<limRef xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">test1
</limRef>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</limitUpdateReturn>
</ns1:limitUpdateResponse>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix A: Card Status Codes

The codes defined in the table below are the card status codes available for use in FIS. These codes are either set
internally within FIS dependent upon specific actions, or may be assigned manually by Call Centre staff via the GUI
interface. The associated Action Codes correspond with ISO response codes.
Status Code Description Response Action Code
00 Normal Approve 000
01 PIN tries exceeded Deny 106
02 Inactive Deny 125
03 Card expired Deny 101
04 Lost Deny and pick up card 208
05 Stolen Deny and pick up card 209
06 Cardholder closed Deny 100
07 Issuer cancelled Deny 100
08 Fraudulent use Deny and pick up card 202
09 Dormant Deny 125

A status used for anonymous cards that are with a
retailer waiting to be sold.
10 Pending Breakage Deny and pick up card 200
11 Pending Closure Deny 125
14 Fraud Status Deny 104
15 Duplicate Card Deny 104
60 Suspend Deny 107
61 Card Returned Deny 100
62 Watch Approve 000
63 Other Returned Deny 100
64 Fraud Deny and pick up card 202
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Version V2.45.1 20/09/2016 Confidential
Status Code Description Response Action Code
65 Bankrupt Deny 100
66 Cancelled Deny 100
67 No Renewal Approve 000
68 Deceased Deny 100
74 Pending Investigation Deny 100
77 Block Deny 100
78 Refer to issuer Deny 107

Merchants may receive a “Refer to Issuer” message
(depending on the capabilities of the POS terminal)
when using a card with this status. The merchant or
cardholder may then contact the issuer bank.
84 Delinquent Deny 116
86 Restricted card Deny 104
89 Pick up Deny and pick up card 200
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix B: Action Codes

The codes defined in the table below are the action codes that may be returned in Web Service responses. These
Action Codes correspond with ISO response codes, and may be generated by the Web Services dependent upon specific
actions, or may be associated with a specific card status, as described in Appendix A. Action codes with a ‘2’ prefix
indicate that the card should be retained. This generally will not be an option for the Web Service calling application, so
‘deny & pickup’ effectively means ‘deny’.
Action Code Description/Response Usage
000 Normal, approve Indicates Success of the WS Transaction
006 Partial approval Indicates Partial Success of the WS transaction

e.g. Bulk card application
100 Do not Honour, deny As required by Issuer. Also used for example in
Card Load when the currency in the request does
not match the card currency
101 Card expired, deny
104 Restricted card, deny As required by Issuer
105 Call acquirer security, deny As required by Issuer
106 PIN tries exceeded, deny As required by Issuer
107 Refer to issuer, deny As required by Issuer
116 Insufficient funds, deny Used to indicate lack of funds to the account eg to
cover the fee associated with the request
118 No card record, deny Used to indicate the PAN in the request has no
associated card record in the database
119 Transaction not allowed to cardholder, deny Used to indicate that the cardholder is not allowed
to perform that particular transaction type
121 Amount limits exceeded or outside valid load Used when any of the card or account amount
range, deny limits are exceeded or a load amount falls outside
the valid range
123 Frequency limits exceeded, deny Used when any of the card or account frequency
limits are exceeded
125 Card not effective, deny Used when the card has not yet been activated.
126 Invalid PIN, deny
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

167 No PIN assigned, deny Used when trying to retrieve a PIN from a card
that has no PIN assigned
168 PIN already present, deny Used when trying to set a PIN on a card that
already has a PIN assigned
169 No-PIN card, deny Used when requesting a PIN on a card that is
marked as a ‘no-PIN’ card
184 PIN confirmation failed, deny Used when the PIN confirmation does not match
the new PIN when attempting to change the PIN
200 Card closed, deny & pickup As required by Issuer
202 Fraudulent use, deny & pickup As required by Issuer
204 Restricted card, deny & pickup As required by Issuer
205 Call acquirer security, deny & pickup As required by Issuer
206 PIN tries exceeded, deny & pickup As required by Issuer
207 Special conditions, deny & pickup As required by Issuer
208 Card lost, deny & pickup
209 Card stolen, deny & pickup
903 Re-enter transaction
904 Format error, deny Generic format error condition eg used by

Account Enquiry to indicate invalid format in
‘txnfilter’ value received in request or when the
security details do not match with the selected
authMethod
908 System malfunction, deny System error during ping/sign on or sign off
909 System malfunction, deny Generic ‘catch-all’ error condition
913 Duplicate transaction, deny To indicate the received request is a duplicate of a

previous request. The ID of the original request
(that this request duplicates) is also returned in
the response.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Applies to financial messages, like Card Load, Card
Unload, Card Transfer, Card Activation Load and
Card Unload Status Change
914 Unable to trace original transaction, deny Used to indicate that the item a Void transaction
seeks to cancel cannot be found
920 Security error – authentication failed, deny Failed to authenticate the cardholder
921 Security error – security answer not defined Failed to authenticate cardholder because one or
more of the security details have not been setup
for the cardholder
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix C: Transaction Types
Code Description
0 Card Activation
1 Card Load
2 Status Change
3 Balance Enquiry
4 Account Enquiry
5 Card List Enquiry
6 Load Verification
7 Card Transfer
8 Card Unload
10 Activate/Load
11 Card Unload/Status Change
12 Void Transaction
13 Cardholder Update
14 Cardholder Enquiry
16 Balance Adjustment
17 Card Application
18 Manage PIN
19 Outgoing Transaction
20 Manage Connection
21 Validate Card
22 Wallet Enquiry
23 Balance Update
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Code Description
24 SMS Reminders
25 Reset Fraud Status
26 Outgoing Notification
27 Card Activation Reversal
28 Limit Enquiry
29 Remove Authorisation
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix D: Activation Methods

The table below lists the activation methods available to the Web Services to be used during card activation.
Method Description
1 Card identifier & cardholder’s date of birth
2 Card identifier & CVC2
3 Card identifier & access code
4 Full Track 2
5 Card identifier & security data
6 Card identifier only
Note: Card identifier can be either the PAN or the Card ID.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix E: Authentication Methods

The table below lists the authentication methods available to the Web Services. Each individual Web Service lists any
restrictions that apply to that particular Web Service.
Method Description
1 Card number or Card ID only
2 Card number or Card ID

AND
Cardholder’s date of birth

AND
CVC2

AND
Access code
5 Login ID

AND
Cardholder’s date of birth & cardholder’s last name
7 Full Track2

AND
Security data
9 Account number and currency code if present in the request interface of the webservice.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix F: Fee Identifiers

The table below provides a list of fee identifiers associated with the <feeID> field in the Account Enquiry service.
Fee ID Description
1000 Cash
1010 Sale/sale with tip
1020 Sale with cashback
1030 Declined transaction
1040 Other transaction (e.g.: PIN change)
1060 Currency exchange mark-up percentage
1061 Foreign exchange due to markup on network rate
1062 Currency exchange rate mark-up percentage for authorisation padding
1064 Foreign exchange due to mark-up on network rate (billing currency based)
1065 Currency exchange rate mark-up percentage for authorisation padding (billing currency based)
1100 Retail club out-of-club fee
2000 Card application approval
2010 Card issue
2011 Card reissue (renewal)
2012 Damaged card replacement
2013 Lost/stolen card replacement
2014 Card restriction
2015 Changing card limit
2016 Authorisation override
2020 Card product change
2110 PIN issue
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Fee ID Description
2111 PIN reissue (new PIN)
2112 PIN reminder (same PIN)
2300 Card value load
2301 Card activation
2302 Status change
2303 Balance enquiry
2304 Account enquiry
2306 Card transfer
2307 Card value unload
2308 Cardholder registration
2309 Card value unload and status change
2310 Cardholder details update
2311 Set PIN real-time
2312 Get PIN real-time
2313 Change PIN real-time
2314 Generate and Get PIN real-time
2315 Archive account enquiry
2320 SMS miscellaneous service fee
2321 Validate card
2323 Redemption fee
2324 Wallet enquiry
2325 SMS reminders
2326 Balance update
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Fee ID Description
2327 Call centre fee
2328 Dispute fee
2329 PIN reminder reversal fee
2401 Card dormancy
2402 Card management
2403 Account manual breakage
2404 Card management fee (in advice)
2405 Card dormancy fee (by last load date)
2441 Card expiry breakage
2442 Card lost/stolen breakage
2443 Account end-of-life breakage
2444 Account closure breakage
2450 Account wallet expiry breakage
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix G: Security Configuration

To protect messages transferred between the customer and FIS, a secure channel of communication is established.
Creating a secure channel comprises:
• Ensuring only FIS can decrypt the message (HTTPS)
• Authenticating that the customer is the message source (VPN or WS Security)
A combination of HTTPS + VPN or HTTPS + WS Security forms a secure communication channel.
HTTPS
The HTTPS protocol uses a FIS-generated SSL key pair (public-private) to ensure message security. The customer gets
the public key from FIS via Internet Explorer and stores it as a Trusted CA Certificate. This makes sure that only FIS can
decrypt messages from the customer. However, it does not authenticate the member as the source of the message.
VPN and WS Security

FIS uses one of two protocols to authenticate that the message has come from the customer:
• VPN: FIS uses VPNs to encrypt traffic and authenticate message source. The customer IP gateway address plus
range of connecting hosts (or a single translated - NATted - IP) are specified during VPN setup and only
messages from these are accepted as genuine.
• WS Security: FIS uses a message signature to uniquely authenticate a customer and validate that the contents
of the message have not been tampered with. To implement this, the customer needs to generate a
public/private SSL keypair and send FIS a certificate request for signing in PEM format. The certificate(s)
representing the SSL pair will be signed by FIS’s Certificate Authority. The customer then imports the signed
certificate into their keystore. All messages sent after this must be signed using the private SSL key to allow FIS
to validate the signatures and authenticate the source of the message.
For implementation details on WS-Security, refer to the appropriate specification at:
http://www.oasis-open.org/committees/download.php/15251/oasis-wss-soap-message-security-1.1.pdf
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix H: WS Security Messages

If the member has opted for WS Security, the request web service has an extra section called the Header. This is located between the start of the Envelope and the Body. The
Header section would look like the following:
<soapenv:Header>
<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-secext-1.0.xsd">
<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd">
<wsu:Created>2006-02-21T16:58:30.042Z</wsu:Created>
<wsu:Expires>2006-02-21T17:08:30.042Z</wsu:Expires>
</wsu:Timestamp>
<wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-
wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-
profile-1.0#X509v3" wsu:Id="CertId-3091716" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
utility-1.0.xsd">
MIIDGDCCAtYCBEP7OhwwCwYHKoZIzjgEAwUAMHIxCzAJBgNVBAYTAkdCMQ8wDQYDVQQIEwZMb25k
b24xDzANBgNVBAcTBkxvbmRvbjEbMBkGA1UEChMSTm9tYWQgU29mdHdhcmUgTHRkMQwwCgYDVQQL
EwNOUFMxFjAUBgNVBAMTDU5QU0FDTFRlc3REU0EwHhcNMDYwMjIxMTYwNDQ0WhcNMDYwNTIyMTYw
NDQ0WjByMQswCQYDVQQGEwJHQjEPMA0GA1UECBMGTG9uZG9uMQ8wDQYDVQQHEwZMb25kb24xGzAZ
BgNVBAoTEk5vbWFkIFNvZnR3YXJlIEx0ZDEMMAoGA1UECxMDTlBTMRYwFAYDVQQDEw1OUFNBQ0xU
ZXN0RFNBMIIBtzCCASwGByqGSM44BAEwggEfAoGBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9EAMMe
P4C2USZpRV1AIlH7WT2NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f6AR7ECLCT7up1/63
xhv4O1fnxqimFQ8E+4P208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RSAHHAhUAl2BQjxUjC8yy
krmCouuEC/BYHPUCgYEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+Zx
BxCBgLRJFnEj6EwoFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTx
vqhRkImog9/hWuWfBpKLZl6Ae1UlZAFMO/7PSSoDgYQAAoGAUP8bhnOFHzOR50LVS5FCW3YV+xOB
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

sbgEeVNLUAXFIYESUlBXrE+7Jul74+d6Amfj9DZ0DFo68p3KZE0tV+bewxTUnQY/DRkN5Ef4N3G7
dxu6K+gb3YUS0q5SEp4gGGqvy7kUkn4PxIVvnFXdLdTHMoK4ZfrrIML0kgM+mwUm+iEwCwYHKoZI
zjgEAwUAAy8AMCwCFAZ+bH1CNUdd8Gy6ZeflYj0t3zMAAhRWTTtTKqW3amfKnWeJZGskSMw7Eg==
</wsse:BinarySecurityToken>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
<ds:Reference URI="#id-27921979">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>OpdZfCR20pt2wYLByZV7+JHq+/c=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>fw7qY1jDf8fRP/Fxa/lFRbTI5kxK4bEM0HdI8jObNm3tobTYoue93g==</ds:SignatureValue>
<ds:KeyInfo Id="KeyId-11363603">
<wsse:SecurityTokenReference wsu:Id="STRId-4365337" xmlns:wsu="http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Reference URI="#CertId-3091716" ValueType="http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

</soapenv:Header>
Note: The BinarySecurityToken (i.e. certificate) will be different for different members and the SignatureValue will be different for every message.
Note: The Timestamp section is optional and is present only if the member has requested it during configuration. The response web service remains the same unless a timestamp
is requested by the member.
Request messages that contain WS security would therefore look similar to the following. All WS messages in this specification can have a WS Security Header section added to
them. The following example is of a Cardholder Enquiry message with WS Security:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<soapenv:Header>
<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd">
<wsu:Created>2006-02-21T16:58:30.042Z</wsu:Created>
<wsu:Expires>2006-02-21T17:08:30.042Z</wsu:Expires>
</wsu:Timestamp>
<wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-
wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-
profile-1.0#X509v3" wsu:Id="CertId-3091716" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
utility-1.0.xsd">
MIIDGDCCAtYCBEP7OhwwCwYHKoZIzjgEAwUAMHIxCzAJBgNVBAYTAkdCMQ8wDQYDVQQIEwZMb25k
b24xDzANBgNVBAcTBkxvbmRvbjEbMBkGA1UEChMSTm9tYWQgU29mdHdhcmUgTHRkMQwwCgYDVQQL
EwNOUFMxFjAUBgNVBAMTDU5QU0FDTFRlc3REU0EwHhcNMDYwMjIxMTYwNDQ0WhcNMDYwNTIyMTYw
NDQ0WjByMQswCQYDVQQGEwJHQjEPMA0GA1UECBMGTG9uZG9uMQ8wDQYDVQQHEwZMb25kb24xGzAZ
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

BgNVBAoTEk5vbWFkIFNvZnR3YXJlIEx0ZDEMMAoGA1UECxMDTlBTMRYwFAYDVQQDEw1OUFNBQ0xU
ZXN0RFNBMIIBtzCCASwGByqGSM44BAEwggEfAoGBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9EAMMe
P4C2USZpRV1AIlH7WT2NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f6AR7ECLCT7up1/63
xhv4O1fnxqimFQ8E+4P208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RSAHHAhUAl2BQjxUjC8yy
krmCouuEC/BYHPUCgYEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+Zx
BxCBgLRJFnEj6EwoFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTx
vqhRkImog9/hWuWfBpKLZl6Ae1UlZAFMO/7PSSoDgYQAAoGAUP8bhnOFHzOR50LVS5FCW3YV+xOB
sbgEeVNLUAXFIYESUlBXrE+7Jul74+d6Amfj9DZ0DFo68p3KZE0tV+bewxTUnQY/DRkN5Ef4N3G7
dxu6K+gb3YUS0q5SEp4gGGqvy7kUkn4PxIVvnFXdLdTHMoK4ZfrrIML0kgM+mwUm+iEwCwYHKoZI
zjgEAwUAAy8AMCwCFAZ+bH1CNUdd8Gy6ZeflYj0t3zMAAhRWTTtTKqW3amfKnWeJZGskSMw7Eg==
</wsse:BinarySecurityToken>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
<ds:Reference URI="#id-27921979">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>OpdZfCR20pt2wYLByZV7+JHq+/c=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>fw7qY1jDf8fRP/Fxa/lFRbTI5kxK4bEM0HdI8jObNm3tobTY
oue93g==</ds:SignatureValue>
<ds:KeyInfo Id="KeyId-11363603">
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<wsse:SecurityTokenReference wsu:Id="STRId-4365337"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Reference URI="#CertId-3091716" ValueType="http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<ns1:cardHolderEnquiry xmlns:ns1="urn:CardHolderEnquiry"
<pobjCardHolderEnquiryRqstInfo href="#id0"/>
</ns1:cardHolderEnquiry>
<multiRef xmlns:ns2="http://wsvalueobj.CardHolderEnquiry.prepaid.webservices.cortex.com"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id0" soapenc:root="0"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:CardHolderEnquiryRqstInfo">
<messageID href="#id1"/>
<localTime href="#id2"/>
<PAN xsi:type="soapenc:string">6759************</PAN>
<track2
xsi:type="soapenc:string">6759******************************************</track2>
<DOB xsi:nil="true" xsi:type="xsd:date"/>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

<CVV xsi:type="soapenc:string">***</CVV>
<accessCode xsi:nil="true" xsi:type="soapenc:string"/>
<loginID xsi:nil="true" xsi:type="soapenc:string"/>
<lastName xsi:nil="true" xsi:type="soapenc:string"/>
<secDet xmlns:ns3="http://wsvalueobj.common.prepaid.webservices.cortex.com"
xsi:nil="true" xsi:type="ns3:SecurityDetailsInfo"/>
</multiRef>
<multiRef xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id1"
soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:int">1</multiRef>
<multiRef xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id2"
soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:long">125409</multiRef>
</soapenv:Body>
</soapenv:Envelope>
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix I: EMV Data Format

This information is an extract from the CORTEX ISO8583:1993 External Interface Functional Specification document.
Note: The total length of all EMV data should not be in the HEX string; only BER-TLV data (actual EMV data) should be
in the HEX as <EMVDATA>.
Field 55 Integrated Circuit Card (ICC) System Related Data
Representation: b..999 (LLLVAR)
Description: ICC System Related Data is used to transport chip-specific data over the payment network. It
contains various data – in the form of Private Data Sub-elements (PDSs) – captured by the chip
terminal as part of a chip transaction. This field is used only for EMV transactions.
Requirements: This field is only used by an EMV transaction.

This field is logically subdivided into the following subfields using the Basic Encoding Rules - Tag
Length Value (BER-TLV) method. The lengths shown are the number of bytes of data.
For approved PIN Change on EMV cards, PIN unblock and Application Unblocks, it is the issuer’s
responsibility to load any required issuer scripts into tag 71 and/or tag 72.
PDS 5F2A Transaction Currency Code
Tag: 5F2A
Length: 2
Format: b 2 (n 3)
Description: This field contains the code of the currency in which the authorised transaction amount (Field 55
tag 9F02) is expressed. This field is used in the generation of the cryptogram.
The currency code, which must comply with ISO 4217, is carried as three hexadecimal digits,
over two bytes.
PDS 71 Issuer Script Template 1
Tag: 71
Length: Variable (up to 999)
Format: b..999
Description: This field contains proprietary issuer data to be transmitted to the ICC before the second
cryptogram is generated by the ICC.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

PDS 72 Issuer Script Template 2
Tag: 72
Format: b..999
Description: This field contains proprietary issuer data to be transmitted to the ICC after the second
cryptogram is generated by the ICC.
PDS 82 Application Interchange Profile
Tag: 82
Length: 2
Format: b2
Description: This field indicates the capabilities of the ICC to support specific functions.
This field is a 16 bit string:
Byte Bit Values Description
1 1 Unused
2 1 Static Data Authentication supported
0 Static Data Authentication not supported
3 Unused
4 1 Cardholder Verification supported
0 Cardholder Verification not supported
5 1 Terminal Risk Management performed
0 Terminal Risk Management not performed
6 1 Issuer Authentication supported
0 Issuer Authentication not supported
7-8 Unused
2 1-8 Unused
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

PDS 84 Dedicated File Name
Tag: 84
Format: b..16
Description: This field contains the name of the Dedicated File as described in the ISO/IEC 7816-4. This is
normally the same as the Application Identifier.
Not used in Visa EMV transactions.
PDS 91 Issuer Authentication Data
Tag: 91
Format: b..16
Description: This field contains the data sent to the ICC for online issuer authentication.
For current VSDC cards, this field is divided into subfields as follows:
Subfield Position Format Values / Description
Authorisation Response Code 1-8 b8 This subfield contains an ARPC used to

(ARPC) authenticate the issuer host system.
ARPC Response 9-10 an 2 This subfield contains the response

code used by the issuer to calculate the
ARPC.
Unused 11-16
For non-VSDC cards, the break out above does not apply, though the field is still used and
transmitted.
PDS 95 Terminal Verification Results (TVR)
Tag: 95
Length: 5
Format: b5
Description: This field contains the status of the terminal functions from the perspective of the ICC-capable
terminal. The terminal records the results of offline and online processing by setting a series of
indicators in this field. This field is a 40 bit string:
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Byte Bit Value Description
1 1 1 Static Data Authentication not performed
0 Static Data Authentication performed
2 1 Static Data Authentication failed
0 Static Data Authentication passed
3 1 Chip Data Missing – Yes
0 Chip Data Missing - No
4 1 PAN on terminal exception file – Yes
0 PAN on terminal exception file – No
5-8 Unused
2 1 1 Chip and terminal are different versions – Yes
0 Chip and terminal are different versions –No
2 1 Expired Application – Yes
0 Expired Application - No
3 1 Application Active – No
0 Application Active – Yes
4 1 Service allowed for card product – No
0 Service allowed for card product – Yes
5 1 New Card – Yes
0 New Card – No
6-8 Unused
3 1 1 Cardholder Verification – Failed
0 Cardholder Verification – Passed
2 1 1 – Unrecognised CVM
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

0 0 – Other
3 1 PIN try limit exceeded – Yes
0 PIN try limit exceeded – No
4 1 PIN entry required and PIN pad not working or not present
0 Other
5 1 PIN entry required, PIN pad not present, but PIN not entered
0 Other
6 1 Online PIN entered
0 Online PIN not entered
7-8 Unused
4 1 1 Transaction exceeds floor limit – Yes
0 Transaction exceeds floor limit – No
2 1 Lower offline limit exceeded – Yes
0 Lower offline limit exceeded – No
3 1 Upper offline limit exceeded – Yes
0 Upper offline limit exceeded – No
4 1 Transaction selected randomly for online transmission – Yes
0 Transaction selected randomly for online transmission – No
5 1 Merchant forced transaction online – Yes
0 Merchant forced transaction online – No
6-8 Unused
5 1 Unused
2 1 Issuer Authentication Failed – Yes
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

0 Issuer Authentication Failed – No
3 1 Script processing failed prior to generating final cryptogram – Yes
0 Script processing failed prior to generating final cryptogram – No
4 1 Script processing failed after generating final cryptogram – Yes
0 Script processing failed after generating final cryptogram – No
5-8 Unused
PDS 9A Transaction Date
Tag: 9A
Length: 3
Format: b 3 (n 6): YYMMDD
Description: This field contains the date on which the transaction was authorised, in the form of six
hexadecimal digits over three bytes. This field is used in the generation of the cryptogram.
PDS 9C Transaction Type
Tag: 9C
Length: 1
Format: b 1 (n 2)
Description: This field gives the type of transaction indicated to the ICC at authorisation time. This field is
used in the generation of the cryptogram.
PDS 9F02 Amount, Authorised
Tag: 9F02
Length: 6
Format: b 6 (n 12)
Description: This field contains the authorised amount of the transaction. This field is used in the generation
of the cryptogram.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

PDS 9F03 Amount, Other
Tag: 9F03
Length: 6
Format: b 6 (n 12)
Description: This field contains a cashback amount associated with a transaction. This field is used in the
generation of the cryptogram.
PDS 9F09 Application Version Number
Tag: 9F09
Length: 2
Format: b2
Description: This field contains the version number assigned by the payment system to the application.
PDS 9F10 Issuer Application Data
Tag: 9F10
Format: b..32
Description: This field contains proprietary application data to be transmitted to the issuer in an online
message.
For non-Visa transactions, this field may be present and transmitted, though the content is not
described here.
For Visa VSDC card transactions, this field is divided into 2 subfields:
Subfield Format Values / Description
VISA Discretionary Data b..16 This subfield contains the Visa discretionary part of the
issuer application data. This subfield is variable length to
16 bytes, the first byte is the length and remaining 15
bytes are divided into 4 subfields, see below.
Issuer Discretionary b..16 This subfield contains data defined by the issuer on the
Data card. This subfield is variable length to 16 bytes, the first
byte is the length.
VISA Discretionary Data is divided to 3 subfields:
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Subfield Position Format Values / Description
Derivation key index 1 b1 This subfield contains an index into the

issuer’s list of keys for use in online card
authentication, issuer authentication, and
validation of the clearing cryptogram.
Cryptogram version 2 b1 This subfield indicates which version of the

cryptogram algorithm was used for ARQC, TC
or AAC generation.
Card Verification Results 3 up to 6 b..4 The CVR is an up to 24 bit string, and the first
(CVR) byte is the length. See below table.
Other VISA Others Unused

Discretionary Data
The [Visa] CVR is an up to 24 bit string:
1 CVR length
2 1-2 00 2nd cryptogram is AAC
01 2nd cryptogram is TC
10 not requested
3-4 00 1st cryptogram is AAC
01 1st cryptogram is TC
10 1st cryptogram is ARQC
11 1st cryptogram is AAR
5 1 Issuer Authentication failed
0 Issuer Authentication passed
6 1 Offline PIN verification performed
0 Offline PIN verification not performed
7 1 Offline PIN verification failed
0 Offline PIN verification passed
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

8 1 Not able to go online
0 Able to go online
3 1 1 Last online transaction incomplete
0 Last online transaction complete
2 1 PIN try limit exceeded
0 PIN try limit not exceeded
3 1 Velocity checking counters exceeded
0 Velocity checking counters not exceeded
4 1 New card
0 Not a new card
5 1 Issuer Authentication on last online transaction failed
0 Issuer Authentication on last online transaction passed
6 1 Issuer Authentication on last online transaction performed
0 Issuer Authentication on last online transaction not performed
7 1 PIN try limit exceeded and application blocked
0 PIN try limit not exceeded
8 1 Static Data Authentication on last transaction failed and terminal was

not able to go online
0 Static Data Authentication on last transaction OK, not performed, or

failed , but terminal was able to go online
4 1-4 Number of issuer script commands containing secure messaging

processed on last transaction.
5 1 Issuer script processing failed on last transaction
0 No script failure on last transaction
6-8 Unused
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

PDS 9F1A Terminal Country Code
Tag: 9F1A
Length: 2
Format: b 2 (n 3)
Description: This field contains the numeric code for the country where the terminal is located.
The country code, which must comply with ISO 3166, is carried as three hexadecimal digits, over
two bytes.
PDS 9F1E Interface Device (IFD) Serial Number
Tag: 9F1E
Length: 8
Format: b 8 (an 8)
Description: This contains a unique, permanent serial number assigned to the IFD (terminal) by the
manufacturer. This serial number is encoded as eight alphanumeric characters, over eight bytes.
PDS 9F26 Application Cryptogram
Tag: 9F26
Length: 8
Format: b8
Description: This field contains the Application Cryptogram (AC) computed by the ICC. It may contain an
Authorisation Request Cryptogram (ARQC), Transaction Certificate (TC), Application
Authentication Cryptogram (AAC) or Application Authorisation Referral Cryptogram (AAR.)
PDS 9F27 Cryptogram Information Data
Tag: 9F27
Length: 1
Format: b1
Description: This field indicates the type of cryptogram and the actions to be performed by the terminal.
The two leftmost bits indicate the type of cryptogram. The default value for the remaining bits is
zero if the data is not available.
Not used by Visa EMV transactions.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

PDS 9F33 Terminal Capability
Tag: 9F33
Length: 3
Format: b3
Description: This field indicates the card data input, Card Verification Method (CVM) and security capabilities
supported of the terminal.
This field is a 24 bit string:
1 1 1 Card Data Input Capability - Manual key enter
0 Card Data Input Capability - No manual key enter
2 1 Card Data Input Capability - Magnetic stripe read
0 Card Data Input Capability – No magnetic stripe read
3 1 Card Data Input Capability – Chip read
0 Card Data Input Capability – No chip read
4-8 Unused
2 1 1 CVM Capability – Online PIN allowed
0 CVM Capability – Online PIN not allowed
2 1 CVM Capability – Online PIN allowed
0 CVM Capability - Online PIN not allowed
3 1 CVM Capability – Signature allowed
0 CVM Capability – Signature not allowed
4-8 Unused
3 1 1 Security Capability – Static Data Authentication supported
0 Security Capability – Static Data Authentication not supported
2 1 Unused
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

3 1 Security Capability – Card capture
0 Security Capability – No card capture
4-8 Unused
PDS 9F34 Cardholder Verification Method (CVM) Results
Tag: 9F34
Length: 3
Format: b3
Description: This field indicates the result of the last cardholder verification performed.
PDS 9F35 Terminal Type
Tag: 9F35
Length: 1
Format: b 1 (n 2)
Description: This field indicates the environment of the terminal, its communications capability and its
operational control. This type consists of two hexadecimal digits, carried in one byte.
PDS 9F36 Application Transaction Counter (ATC)
Tag: 9F36
Length: 2
Format: b2
Description: This field contains the value of a counter maintained by the ICC, which is used in the generation
of the cryptogram
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

PDS 9F37 Unpredictable Number
Tag: 9F37
Length: 4
Format: b4
Description: This field contains the number used in the generation of the cryptogram to provide variability
and uniqueness.
PDS 9F41 Transaction Sequence Counter
Tag: 9F41
Format: b..4 (n..8)
Description: This field is a counter maintained by the terminal, which is incremented by one for each
transaction. The value of the counter is carried as up to eight hexadecimal digits, in up to four
bytes (in Latin 1 and ASCII sharacter sets).
PDS 9F53 Transaction Category Code
Tag: 9F53
Length: 1
Format: b 1 (an 1)
Description: This is a proprietary Mastercard & Europay field, containing a code defining the industry sector in
which the merchant operates. This code consists of a single alphanumeric character, carried in
one byte (in Latin 1 and ASCII sharacter sets)..
Only used in Europay & Mastercard EMV transactions.
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Example
<EMVdata>82025800950580000400009a030905279c01315f2a0208269f02060000000000009f0306
0000000000009f1a0208269f1e0841544d30303030329f2608f39d4eb8f402a71c9f2701809f33036
040209f34030203009f3501149f360201519f37044f461ba59f53015a<EMVdata>
Details of the contents of EMVdata
Tag - Value pairs

82 - 025800
95 - 058000040000
9a - 03090527
9c - 0131
5f2a - 020826
9f02 - 06000000000000
9f03 - 06000000000000
9f1a - 020826
9f1e - 0841544d3030303032
9f26 - 08f39d4eb8f402a71c
9f27 - 0180
9f33 - 03604020
9f34 - 03020300
9f35 - 0114
9f36 - 020151
9f37 - 044f461ba5
9f53 - 015a
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix J: Card Status and Card Expiry Check by Web Service

The following table lists card statuses in which a card should be in order to perform a web service action and whether a
card expiry check is done on the card. Please note that checks on the card are not limited to those included in this table.
No Web Service Card needs to be in status Card Expiry check
1 Card Activation 02 Yes
2 Card Load 00 or 02 or any status that has an action/response Yes

code of 000 *
3 Status Change Current Status New Status No
Non cancelled** 14
02 09
Non cancelled 00
If not activated then
current status needs to be
02
Non cancelled and not 02

activated
Any Cancelled
Non cancelled Non cancelled and other

than 14, 09, 00 and 02
4 Balance Enquiry No restriction No
5 Account Enquiry No restriction No
6 Card List Enquiry No restriction No
7 Load Verification Same as Card Load Yes
8 Card Transfer Source Card Destination card Expiry checked for

destination card
Non cancelled** 00 or 02 or any status
that has action/response
code 000
Cancelled status 04 or 05 00 or 02
and configuration set to
allow these transfers
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

9 Card Unload Non cancelled** Yes
10 Activate/Load 02 Yes
11 Card Unload/Status Non cancelled** Yes

Change
12 Void Transaction Same as Card Load Yes
13 Cardholder Update No restriction Yes
14 Cardholder Enquiry No restriction No
15 Outgoing Loads Transaction Type Status Yes
Debit any status that has

action/response code
000 excluding 02
Online Load Any status that has

action/response code
000
16 Balance Adjustment If not a ForcePost then should be in 00 or 02 or any If ForcePost, then no expiry
status that has action/response code 000 check. Checked if not a
ForcePost request
No restriction if ForcePost is 1
17 Card Application No restriction Not applicable
18 Manage PIN Non cancelled** Yes
19 Outgoing Transaction Transaction Type Status Yes
Debit any status that has

action/response code 000
excluding 02
Online Load from ISO93 Any status that has

interface action/response code
000
Credit ( exclude Online No restriction

Load)
20 Manage Connection No restriction No
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

21 Validate Card Any status that has action/response code 000 or if the Yes
card status 01 then there should be no pin in the
service request. Latter can be overridden by the
customer.
22 Wallet Enquiry No restriction No
23 Balance Update No restriction No
24 SMS Reminders Non cancelled Yes
25 Reset Fraud Status 14 or 15 but any status can be configured as a fraud No

status.
26 Outgoing Notification No restriction No
27 Card Activation 00 No
Reversal
28 Limit Enquiry No restriction No
* Acceptable status codes for this service can be overridden by client configuration.
** Non cancelled statuses – please refer to table below.
Note: This list is the system list. New statuses can be added by the client.
Status Code Description Cancelled
00 Normal False
01 Pin Tries Exceeded False
02 Not Yet Issued False
03 Card Expired True
04 Lost True
05 Stolen True
06 Customer Closed True
07 Bank Cancelled True
08 Fraudulent Use True
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

09 Dormant False
10 Pending Breakage True
11 Pending Closure False
12 Card Overflow False
13 Pending Reset False
14 Fraud Investigation False
15 Fraud Invest(As Dup) False
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Appendix K: AVS Check Results

The invalid values of <aVSChkRs> are (all uppercases value and digit 1 and 2):
Value Meaning VISA (F44.2) VISA (F44.2) VISA (F44.2) MasterCard

mapping in mapping in mapping in (DE123.13)
request response response mapping
(international) (domestic)
A Postcode does not match A A A A
B Postcode format is incompatible B B B A
C Address and postcode formats are C N N N

both incompatible
D Address and postcode both match D D Y X

but acquirer has no representment
right
F Address not in database Z Z W
G AVS data not checked and acquirer G G U U

has no representment right
I AVS data not checked (either I, S or U G U U

Address and postcode both not in
database or AVS currently not
supported
M Postcode not in request message A A A
N Address and postcode both not N N N N

match
P Address format is incompatible P P P W
R Retry - system unable to process R I R R
S AVS currently not supported G U S
U Address and postcode both not in G U U

database
W Address does not match W or Z Z Z W
X Postcode not in database A A A
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100

Value Meaning VISA (F44.2) VISA (F44.2) VISA (F44.2) MasterCard

mapping in mapping in mapping in (DE123.13)
request response response mapping
(international) (domestic)
Y Address and postcode both match F, M, X or Y M Y X
Z Address not in request message Z Z W
1 Address does not match and N N N

postcode not checked
2 Postcode does not match and N N N

address not checked
+44.1923.471850 +65.6225.5926 +61.3.8615.1100 +1.501.220.5100


Web Services Interface Specification V2.46.0

Uploaded by

Copyright:

Available Formats

You might also like

Web Services Interface Specification V2.46.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Web Services Interface Specification V2.46.0

Uploaded by

Copyright:

Available Formats

Web Services

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 2

1 Debit and Prepaid Document Library

Version Date Detail of Change

0.3 Draft 21/01/05 Further message types added

1.0 05/03/05 First Version

1.1 12/03/05 Enhancing messages with further functionality

1.2 23/04/05 Adding further fields and adding in ACTIONCODE appendix

1.3 08/08/05 Corrections to typos and adding more description in

1.5 09/12/05 New messages CardListEnquiry and LoadVerification.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 3

Version Date Detail of Change

1.6 08/02/06 Clarification of the description of Combination Messages

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 4

Version Date Detail of Change

2.5 13/09/06 Moved <actMethod> values & descriptions to Appendix D.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 5

Version Date Detail of Change

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 6

Version Date Detail of Change

2.6 25/10/06 Added new ‘Manage PIN’ Web Service.

2.6.1 DRAFT 14/12/06 Added new ‘Outgoing Transaction’ Web Service.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 7

Version Date Detail of Change

2.8 03/08/07 Added usage notes on Manage PIN.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 8

Version Date Detail of Change

2.9.1 28/02/08 Changed branding from Nomad Payments to Metavante.

2.9.2 21/05/08 Card Transfer: Corrected data type of CURRCODE.

2.9.3 15/07/08 Corrected description of security options in Appendix G and of <forcepost> in

2.9.4 16/08/08 Corrected data type of <messageID> in all messages.

2.10.1 09/08/08 Clarified sorting of transactions in Account Enquiry.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 9

Version Date Detail of Change

2.11.1 12/12/08 Updated list of card statuses (Appendix A).

2.11.2 19/01/09 Added rules used to store telephone numbers.

2.12.1 19/02/09 Added note on voiding card transfers

2.13.1 26/03/09 Added note on card to card transfer.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 10

Version Date Detail of Change

2.15 24/07/09 Added <txnSubCode> to Account Enquiry web service.

2.16 14/09/09 Updated in CardHolderUpdate web service:

2.16.2 02/11/09 Corrected description of <cardID>.

2.17 27/11/09 Added <description> to CardLoad web service.

2.17.1 21/07/10 Corrected example for Card Application web service.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 11

Version Date Detail of Change

2.19 28/10/10 Added <profileRef>, <additionalCrdDet> and <additionalCustDet> to

2.19.1 08/11/10 Modified <walletRef> description in CardLoad, CardUnload, CardActivationLoad,

2.20 08/03/11 Added Wallet Enquiry web service.

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 12

Version Date Detail of Change

2.20.2 03/06/11 Corrected description of Card Application web service.

2.21 03/08/11 Added <newCurrCode> to Card Activation/ Load web service.

2.23.1 06/10/11 Clarified use of Card Application web service.

2.23.4 13/08/12 Applied FIS corporate template

2.27.1 23/01/13 Updated Card Unload message – add to description of <currCode>

© 2005-2016 FIS and/or its subsidiaries. All Rights Reserved. 13

Version Date Detail of Change