Cashier-Profil für die Kassette für SET - Wallet (Elektronische Brieftasche)

Der folgende XML-Code ist das Standard-Cashier-Profil, das in WebSphere Commerce für die Verwendung mit der Kassette für SET bereitgestellt wird.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Profile SYSTEM "../../../../xml/PaymentManager/profile.dtd">

<!--
//*==================================================================
//* Licensed Materials - Property of IBM
//*
//* 5724-A18
//*
//* (c) Copyright IBM Corp. 2001
//*
//* US Government Users Restricted Rights - Use, duplication or
//* disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
//*
//*================================================================== -->

<!-- ==================================================================
This is the Standard WC 5.1 cashier profile for the Payment Manager 
Cassette for SET 
================================================================== -->

<Profile useWallet="true" enableTrace="true" >

<CollectPayment>

<!-- ==================================================================
Parameters required by Payment Manager for order creation
================================================================== -->
<Parameter name="PAYMENTTYPE"><CharacterText>SET</CharacterText></Parameter>
<Parameter name="MERCHANTNUMBER"><CharacterText>{storeId}</CharacterText></Parameter>
<Parameter name="ORDERNUMBER"><CharacterText>{orderId}</CharacterText></Parameter>
<Parameter name="CURRENCY"><CharacterText>{CURRENCY}</CharacterText></Parameter>
<Parameter name="AMOUNT"><CharacterText>{AMOUNT}</CharacterText></Parameter>
<Parameter name="AMOUNTEXP10"><CharacterText>{AMOUNTEXP10}</CharacterText></Parameter>

<!-- ==================================================================
Optional parameters for Payment Manager
================================================================== -->

<!-- Indicates how automatic approval of the order should be attempted
Supported values are: 
0 - no automatic approval
1 - synchronous automatic approval - Payment Manager attempts approval as
part of order creation operation
2 - asynchronous automatic approval - Payment Manager schedules an approval
operations after order is created
The default value is 0.

Since a Wallet application is used, the Payment Manager has to return a wakeup
message to WC to send to the shopper. This completes the DoPayment command.
Specifying an APPROVEFLAG of 1 means the Wallet application would receive the 
Purchase Response from the Payment Manager after the Authorization response is 
received from the Payment Gateway.
-->
<Parameter name="APPROVEFLAG"><CharacterText>1</CharacterText></Parameter>

<!-- The amount which should be used when approving an order. Usually
this will be the same as the order amount. This field is required
if the APPROVEFLAG is set to 1 or 2. -->
<Parameter name="PAYMENTAMOUNT"><CharacterText>{approval_amount}</CharacterText></Parameter>

<!-- The payment number which should be used when approving an order.
Usually this will be 1. This field is required if the APPROVEFLAG
is set to 1 or 2. -->
<Parameter name="PAYMENTNUMBER"><CharacterText>1</CharacterText></Parameter>

<!-- Indicates whether the deposit should be attempted automatically. 
This flag is only valid if APPROVEFLAG is set to 1 or 2.
Supported values are:
0 - Funds should not be automatically deposited. 
1 - Funds should be automatically deposited. 
The default value is 0.
-->
<Parameter name="DEPOSITFLAG"><CharacterText></CharacterText></Parameter>

<!-- The following two parameters are optional. Either one could be used to pass the 
Buyer Purchase Order number to the Payment Manager. The first Parameter takes only 
ASCII Text. If Buyer Purchase Order numbers on your system may contain non-ASCII 
Strings, use parameter ORDERDATA2 instead. 
-->
<Parameter name="TRANSACTIONID" maxBytes="128" encoding="ASCII"><CharacterText>{PONumber}</CharacterText></Parameter>
<Parameter name="ORDERDATA2"><CharacterText></CharacterText></Parameter>


<!-- ==================================================================
Parameters required by the cassette
================================================================== -->
<Parameter name="$SUCCESSURL"><CharacterText>http://{WCHostName}{WebPath}/PaySuccessView?storeId={storeId}&amp;orderId={orderId}&amp;langId={buyer_language_id}</CharacterText></Parameter>
<Parameter name="$FAILUREURL"><CharacterText>http://{WCHostName}{WebPath}/PayResetPM?storeId={storeId}&amp;orderId={orderId}&amp;fail=1&amp;langId={buyer_language_id}&amp;URL=PayFailureView</CharacterText></Parameter>
<Parameter name="$CANCELURL" ><CharacterText>http://{WCHostName}{WebPath}/PayResetPM?storeId={storeId}&amp;orderId={orderId}&amp;cancel=1&amp;langId={buyer_language_id}&amp;URL=PayCancelView</CharacterText></Parameter>
<Parameter name="$SERVICEURL"><CharacterText>http://{WCHostName}{WebPath}/PayServiceView?storeId={storeId}&amp;orderId={orderId}&amp;langId={buyer_language_id}</CharacterText></Parameter>

<!-- The encoding attribute indicates to the Cashier that the bytes for the 
OrderDescription can be obtained from the returned String using the 8859_1 
character encoding because that was how the GenericExtension class encodes 
the bytes. The resulting bytes are in the language of the requester. -->
<Parameter name="$ORDERDESCRIPTION" encoding="8859_1" >
<ExtensionValue name="com.ibm.commerce.payment.extensions.GenericExtension" />
</Parameter>


<!-- ==================================================================
Optional parameters for the cassette
================================================================== -->

<!-- The cardholder's street address. 1 to 128 ASCII characters. -->
<Parameter name="$AVS.STREETADDRESS" maxBytes="128" encoding="ASCII"><CharacterText>{billto_address1}</CharacterText></Parameter>

<!-- The cardholder's city. 1 to 50 ASCII characters. -->
<Parameter name="$AVS.CITY" maxBytes="50" encoding="ASCII"><CharacterText>{billto_city}</CharacterText></Parameter>

<!-- The cardholder's state or province. 1 to 50 ASCII characters. -->
<Parameter name="$AVS.STATEPROVINCE" maxBytes="50" encoding="ASCII"><CharacterText>{billto_state}</CharacterText></Parameter>

<!-- The cardholder's postal/zip code. 1 to 14 ASCII characters. -->
<Parameter name="$AVS.POSTALCODE" maxBytes="14" encoding="ASCII"><CharacterText>{billto_zipcode}</CharacterText></Parameter>

<!-- The cardholder's ISO 3166 (3 digits) country code. This field is
required if any other AVS data is passed. -->
<Parameter name="$AVS.COUNTRYCODE"><CharacterText>{billto_country_code}</CharacterText></Parameter>

<!-- An identifier that the merchant uses to specify one of its locations. 
The value is specified as a String. 1 to 10 ASCII characters. -->
<Parameter name="$AVS.LOCATIONID" maxBytes="10" encoding="ASCII"><CharacterText></CharacterText></Parameter>


<!-- Indicates the content type and character set of the $ORDERDESCRIPTION 
parameter. Some wallet may require the Content-Type Header of the 
Payment Initiation message to include the charset specification. 
In that case, specify "text/plain; charset={language_encoding}"
without the quotes as value for the $CHARSET parameter.
-->
<Parameter name="$CHARSET"><CharacterText></CharacterText></Parameter> 

<!-- One of two fields in the merchData structure; when specified, the 
Cassette will use it. Value must be a 4-character numeric string. 
Note: The requirement to use this field will come from the acquirer. -->
<Parameter name="$MERCHCATCODE"><CharacterText></CharacterText></Parameter> 

<!-- One of two fields in the merchData structure; when specified, 
the Cassette will use it. Value must be a numeric string between 
"1" and "8". Semantics for possible values are described in the SET
specification. Note: The requirement to use this field will come 
from the acquirer. -->
<Parameter name="$MERCHGROUP"><CharacterText></CharacterText></Parameter> 

<!-- The MerOrderNum field is in the SaleDetail structure of CapReq and 
AuthReq (with capture now) messages. Value must be a character string 
with a maximum length of 24 characters. -->
<Parameter name="$MERORDERNUM"><CharacterText></CharacterText></Parameter> 

<!-- Indicates whether or not a merchant may approve additional shipments. 
Supported values are: 
0-Indicates that this is the final payment for the order.
1-Indicates that the merchant may approve additional split 
payments for the order. -->
<Parameter name="$SPLITALLOWED"><CharacterText>1</CharacterText></Parameter> 

<!-- Used to indicate that an incoming purchase request from a Wallet must contain
a cardholder certificate. If this keyword is omitted, purchases without 
certificates are allowed. Valid values are: 
0: Indicates that cardholder certificates are not required. 
1: Indicates that cardholder certificate are required. 
-->
<Parameter name="$REQUIRECARDCERT"><CharacterText>1</CharacterText></Parameter>

</CollectPayment>

<Command name="DEPOSIT">
<!-- ==================================================================
Parameters required by Payment Manager for DEPOSIT Command
================================================================== -->
<Parameter name="MERCHANTNUMBER"><CharacterText>{storeId}</CharacterText></Parameter>
<Parameter name="ORDERNUMBER"><CharacterText>{orderId}</CharacterText></Parameter>
<Parameter name="PAYMENTNUMBER"><CharacterText>{payment_number}</CharacterText></Parameter>
<Parameter name="AMOUNT"><CharacterText>{AMOUNT}</CharacterText></Parameter>
</Command>


</Profile>

Die Datei WC51_SET_MIA.profile befindet sich in:
laufwerk:\WebSphere\CommerceServer\instances\exemplarname\xml\payment\
laufwerk:\Programme\WebSphere\CommerceServer\instances\exemplarname\xml\payment\
/usr/WebSphere/CommerceServer/instances/exemplarname/xml/payment/
/opt/WebSphere/CommerceServer/instances/exemplarname/xml/payment/
root_pfad_des_exemplars/xml/payment/

Hierbei ist root_pfad_des_exemplars der Pfad, den Sie während der Erstellung des Exemplars im Feld Root-Pfad des Exemplars auf der Seite Exemplar im Konfigurationsmanager angegeben haben. Der Standardpfad lautet: /QIBM/UserData/WebCommerce/instances/exemplarname/.

Der Parameter PAYMENTTYPE gibt den Namen der Kassette des Profils an. 

WebSphere Commerce verwendet das Element <BuyPageInformation> des Cashier-Profils nicht. Eine vergleichbare Funktionalität wird durch die Eigenschaft attrPageName der Zahlungsrichtlinie erreicht.

Das Profil verwendet die Klasse "GenericExtension" zum Abrufen des Werts für den Parameter $ORDERDESCRIPTION. Dieser Parameter wird zum Generieren der Nachricht zur Zahlungseinleitung für Wallet benötigt, indem der Task-Befehl GetOrderDescCmd aufgerufen wird. Auf diese Weise können verschiedene Geschäfte unterschiedliche Implementierungen des Befehls "GetOrderDescCmd" aufweisen und dennoch dasselbe Cashier-Profil für alle Geschäfte verwenden.)

Dieses Profil gibt die Verwendung von PaySuccessView, PayFailureView, PayCancelView und PayServiceView für die Parameter $SUCCESSURL, $FAILUREURL, $CANCELURL und $SERVICEURL an. Beachten Sie außerdem den Befehl PayResetPM für $FAILUREURL und $CANCELURL. Bei den Parametern fail=1 und cancel=1 handelt es sich um Parameter für die standardmäßige JSP-Datei (PayStatusPM.jsp), die sowohl von PayFailureView und PayCancelView verwendet wird. Der Parameter weist die JSP-Datei zum Anzeigen unterschiedlicher Nachrichten für Kunden an. Die angezeigte Nachricht hängt dabei vom jeweils gesetzten Parameter ab.

Weitere Informationen zu PaySuccessView, PayFailureView, PayCancelView und PayServiceView enthält der Abschnitt JavaServer Pages-Dateien für die Zahlung anpassen.

Weitere Informationen zu den für die Kassette für SET erforderlichen Parametern enthält IBM WebSphere Payment Manager für mehrere Plattformen, Kassette für SET, Version 3.1.

Verwandte Konzepte (1275 Byte)

Verwandte Referenzen (1292 Byte)

IBM Copyright