At which stage in the payment process should I collect payment details (card number etc)? It appears the payment method is chosen in Payment.master [PaymentDetails] and RequestPayment invoked). However Submit.master seems to show an order summary and displays a button to submit the basket.
I'm implementing my own IPaymentMethodService class and a little
confused as to when the service methods are invoked during the payment
process and which XSLT is responsible for what.
I've read the articles on publicvoid_dk but there seems little documentation on this actual flow.
The XSLT APIs are designed to work with the standard payment gateway integration where control is handed over to the payment gateway itself and all credit information is handled there.
If you need to handle card information on your end you can drop into .NET and create a PaymentRequest object with the relevant information added to the AdditionalProperties dictionary like cardno, cvv, etc..
You can then feed the object directly to your PaymentMethodService when ready.
When you say 'drop into .NET', do you mean for example - after server-side validation, I create a PaymentRequest, instanciate an IPaymentMethodService object and invoke the RequestPayment / AquirePayment methods myself?
You can ask your payment method for the configure service by using payment.PaymentMethod.GetPaymentMethodService().
From there you'll execute RequestPayment with the PaymentRequest you instantiate with relevant information which is used to initiate payment and validate card info.
From there everything is handled internally in the PaymentMethodService.
Once the transaction is approved you'll call the Checkout pipeline to complete the order.
IPaymentMethodService / uCommerce store payment flow
At which stage in the payment process should I collect payment details (card number etc)? It appears the payment method is chosen in Payment.master [PaymentDetails] and RequestPayment invoked). However Submit.master seems to show an order summary and displays a button to submit the basket.
I'm implementing my own IPaymentMethodService class and a little confused as to when the service methods are invoked during the payment process and which XSLT is responsible for what.
I've read the articles on publicvoid_dk but there seems little documentation on this actual flow.
Cheers
Hi James,
The XSLT APIs are designed to work with the standard payment gateway integration where control is handed over to the payment gateway itself and all credit information is handled there.
If you need to handle card information on your end you can drop into .NET and create a PaymentRequest object with the relevant information added to the AdditionalProperties dictionary like cardno, cvv, etc..
You can then feed the object directly to your PaymentMethodService when ready.
Thanks for the quick reply Søren.
When you say 'drop into .NET', do you mean for example - after server-side validation, I create a PaymentRequest, instanciate an IPaymentMethodService object and invoke the RequestPayment / AquirePayment methods myself?
You can ask your payment method for the configure service by using payment.PaymentMethod.GetPaymentMethodService().
From there you'll execute RequestPayment with the PaymentRequest you instantiate with relevant information which is used to initiate payment and validate card info.
From there everything is handled internally in the PaymentMethodService.
Once the transaction is approved you'll call the Checkout pipeline to complete the order.
is working on a reply...