Developer forum

I do not think we have ever supported or tested subscription payments in any gateway. Dynamicweb recurring uses saved card functionality.

In this case I think that you need to alter the post template for Altapay to send the needed information for the subscription. Usually you have to declare that it is digital products if you do charge automatically - if it is physical products, you are not allowed to charge before the product has been sent.

BR Nicolai

It turns out to be a bit more problematic. I don't think I can change any template as this is server to server when executing IRecurring.Recurring, isn't it. Recurring has this code:

var request = CreateRequest();
request.SetParameter("transaction_id", originalOrder.TransactionNumber);
request.SetParameter("amount", order.TotalPrice.ToString(".00", NumberFormatInfo.InvariantInfo));

AltaPayResponse response = request.SendRequest("chargeSubscription");

XmlNodeList transactions = response.ResponseDocument.SelectNodes($"APIResponse/Body/Transactions/Transaction");
XmlNode payment = transactions?.Item(0);
XmlNode recurringPayment = transactions?.Item(1);

...
order.TransactionType = "ChargeSubscription";
order.TransactionStatus = recurringPayment?.SelectSingleNode("TransactionStatus")?.InnerText ?? string.Empty;
...
if (response.Result == RequestResult.Success)
{
    order.CaptureAmount = Converter.ToDouble(recurringPayment?.SelectSingleNode("CapturedAmount")?.InnerText);
    order.CaptureInfo = new OrderCaptureInfo(OrderCaptureInfo.OrderCaptureState.Success, "Recurring payment captured.");
    ...
}
else
{
    order.CaptureInfo = new OrderCaptureInfo(OrderCaptureInfo.OrderCaptureState.Failed, "Recurring payment failed.");
    order.SetXmlResponse(response.ResponseDocument.OuterXml);
    Services.Orders.Save(order, false); // Save changes to the custom AltaPayXml field.
    ...
}

So it seems to always assume that it has been captured (see bold line). This makes the problem bigger as the money is reserved bur not captured, while the UI now believes it is captured (because of the CaptureInfo state) and therefore doesn't allow capturing anymore :-(

Am I seeing this right?

Could I, while we look into this further, update the capture state to NotCaptured for an order and then try capturing it from the UI again?

Imar

Did you create the payment with subscribe and charge? I cannot see that working as it requires creating an agreement:

https://documentation.altapay.com/Content/Ecom/API/API%20Methods/createPaymentRequest.htm?Highlight=SubscriptionAndCharge

If you are running requrring I think you need the saved credit card feature.

I have asked one with Altapay knowledge to jump in the conversation :-)

Sorry for the slow response Stanislav. We had some miscommunication here on who would follow up ;-)

Anyway, setting it to Subscription did do the trick indeed. That doesn't create a transaction in AltaPay (which is good) but sets everything up to capture on the next recurrence of the order.

I do have another, related issue though. When the subscription is created in AltaPay it uses the recurring order ID (like REC123) instead of an actual order ID. Then when the recurring payment is made, it uses that same ID again:

This makes it somewhat difficult to see which order the payment belongs to; especially since the Orders node in the backend doesn't show recurring orders and the recurring node doesn't show normal orders.

I am not sure what the solution is though. At the time of transaction creation all we have is the REC ID. And then when placing the recurring transaction, we don't send the DW order ID anymore, but only the TransactionNumber. The AltaPay docs says this:

Would it make sense to populate transaction_info with the order ID so we have both the recurring template ID as well as the order ID?

And while I was on their doc site, I found this:

They don't quantify "for a while" but it might be necessary to change transaction_id to the agreement ID?

Thanks!

Imar