When contacting our payment gateway, we use uCommerce's OrderGuid as the primary identity for authorisation, settlement etc of payments. However, if I create a payment request using card details that result in a declined result, the payment gateway refuses to process subsequent attempts using the same OrderGuid.
I'm trying to work out what I could pass in this instance rather than the OrderGuid. At the card details stage, the basket and order guids will not change and my XML field is limited to 40 chars for the orderID (guid length) so I can't pass concatenated data.
Perhaps I could update the OrderGuid in the PurchaseOrder table before I retry?
You can use the ReferenceId on the payment to pass on different values to the payment gateway. By default uCommerce will assign an order only when payment is accepted by the gateway. By default uCommerce creates a new payment and a new reference id every time you pass the customer to the gateway.
Handling a declined payment attempt
When contacting our payment gateway, we use uCommerce's OrderGuid as the primary identity for authorisation, settlement etc of payments. However, if I create a payment request using card details that result in a declined result, the payment gateway refuses to process subsequent attempts using the same OrderGuid.
I'm trying to work out what I could pass in this instance rather than the OrderGuid. At the card details stage, the basket and order guids will not change and my XML field is limited to 40 chars for the orderID (guid length) so I can't pass concatenated data.
Perhaps I could update the OrderGuid in the PurchaseOrder table before I retry?
Any ideas appreciated.
Hi James,
You can use the ReferenceId on the payment to pass on different values to the payment gateway. By default uCommerce will assign an order only when payment is accepted by the gateway. By default uCommerce creates a new payment and a new reference id every time you pass the customer to the gateway.
is working on a reply...