The Request Message for the Tender Type Lookup Operation
The Reply Message for the Tender Type Lookup Operation
Either a raw PAN or a token representing a PAN.
The type includes an attribute, isToken, to indicate if the PAN is tokenized.
Allowable Values: Text string
Required: No
Length: TBD
Default Value: blank
Restrictions: N/A
Aliases: N/A
Either a raw PAN or a token representing a PAN.
The type includes an attribute, isToken, to indicate if the PAN is tokenized.
Payment tender class enum
Allowable Values: Text string
Required: No
Length: TBD
Default Value: blank
Restrictions: N/A
Aliases: N/A
ISO currency code
Allowable Values: Text string
Required: No
Length: 3
Default Value: blank
Restrictions: N/A
Aliases: N/A
Matching Tender Type. Element is not displayed in the xml if the value is null. This element identifies the tender type.
Example values: Credit card: VC (Visa), MC (Master Card), AM (American Express) Stred Value: Stored Value tender type codes are provider specific (i.e Blackhawk, SVS, etc.) Example: BH (Blackhawk), SP (SVS), OGC (GSI Online Gift Certificate)
Allowable Values: Text string
Required: No
Length: 4
Default Value: blank
Restrictions: N/A
Aliases: N/A
This element can have the values listed below:
Allowable Values: Text string
TENDER_TYPE_FOUND -
A matching tender type is found by account number, tender class, currency code and store id.
PAN_FAILS_LUHN_CHECK - The account number fails to pass Luhn check. http://en.wikipedia.org/wiki/Luhn_algorithm
NO_TENDER_TYPE_FOUND - No tender type matches the account number, tender class, currency code and store id
PAN_NOT_CONFIGURED_TO_STORE - Tender type matches the account number, tender class and currency code but not the store id
UNKNOWN_FAILURE - Failed to find a tender type for unknown cause/s
Required: No
Length: TBD
Default Value: blank
Restrictions: N/A
Aliases: N/A
A matching tender type is found by account number,
tender class, currency code and store id.
The account number fails to pass Luhn check.
http://en.wikipedia.org/wiki/Luhn_algorithm
No tender type matches the account number, tender class,
currency code and store id
Tender type matches the account number, tender class
and currency code but not the store id
Failed to find a tender type for unknown cause/s
This xsd:any element indicates that future optional elements may show up in this location of the XML document in the responses returned from the service.
The purpose of this xsd:any element is to define a more robust service interface that allows for new, optional elements to be added to the service's responses without the service clients' code throwing exceptions.
The client code for this service call should be written to not break if new optional XML elements show up in this part of the service response. Modern XML marshalling frameworks often process xsd:any elements properly out-of-the-box (for example, in Java, JAXB and JibX XML marshalling frameworks both honor xsd:any elements and don't throw exceptions if new optional elements appear within the xsd:any section of the XML document).
Developers' unit tests of their service client code should include a test case where this reply message contains one or more new elements in this location of the XML document.
If new optional elements are added to this interface, a new schema will be created, communications will be sent out, and you will have the option to modify your service client code to process and use the new elements.
If there is no need/desire to process the new optional elements, your service client should continue to run uninterrupted as long as it is built to honor this xsd:any element.