Package DE_EPAGES::CyberMUT::API::Object::LineItemPaymentCyberMUT
object interface for LineItemPaymentCyberMUT. What is this good for anyway? When a shopper picks a payment method to pay for his purchases, a corresponding payment line item is put into the basket. It has some data attached, like in this case the "Gateway", i.e. the bank chosen by the shopper to do the transaction with.
Base |
DE_EPAGES::ExternalPayment::API::Object::LineItemPaymentExternal |
Functions
className
Returns the class name, used for DAL access.
Syntax |
$ClassName = $LineItemPaymentCyberMUT->className; |
Return |
|
executePayment
Servlet output encoding is set to 'ISO-8859-1'. So why is this done? Why would it even matter? Well, this routine is used to generate an HTML page containing the form that the user clicks to be with his transaction data along to CyberMUT. The reasoning for setting the encoding here is that CyberMUT requires the form submission to be done in Latin1 (ISO-8859-1). Specifying <form accept-charset="ISO-8859-1"> might also do the job, but better just leave this alone as it appears to work.
Syntax |
$LineItemPaymentCyberMUT->executePayment($hParams); |
Input |
|
updateOnExecute
Set relevant data items on the payment line item. Most of this is handled by the superclass. There is one thing which may be specific to each request and which is not handled by the superclass, and that's the "Gateway", which is the bank (one of three possibilites from a dropdown menu) chosen for this transaction.
Syntax |
$PaymentLineItem->updateOnExecute; |