Reply
Member
Posts: 4
Registered: ‎11-25-2019

refId parameter for Subscription

Hi,

 

we are using the AcceptUI Hosted form which has nounce properly works.

 

1. We get the nounce from Payment form and then we call the createTransactionAPI Using that nounce parameter.

 

2. Once customer transaction is the success we use the createCustomerProfile and based on their 

Customer Profile Id and customer Payment Profile Id we start the Subscription for customer for future payment.

 

But the problem that we are sending the refId in createTransaction API which has planId basically but when we get the webhook response for auto deduction then in that response we are not getting that refId. parameter 

 

Our need that a single customer can subscribe more than one subscription and we need to update their subscription expiry in each month/year based on the planid.

 

Thanks 

Member
Posts: 6
Registered: ‎12-02-2019

Re: refId parameter for Subscription

Sending the refId in createTransaction API  was not a good idea.

Authorize.Net Wizard
Posts: 115
Registered: ‎11-29-2017

Re: refId parameter for Subscription

refId is supported in the CreateTransaction api and subsequent webhooks.

 

From your description you would like to send a CreateTransaction request with a refId, have that refId carry over to the recurring billing subscription, and be used in subsequent recurring billing transactions. Please let me know if I have it wrong.

 

This scheme is not currently supported. The refId is not carried over to the subscription and related subscription updates and transactions associated with the subscription will not have the refId.

Member
Posts: 4
Registered: ‎11-25-2019

Re: refId parameter for Subscription

What's the proposed solution flow-

 

Customers can subscribe for more than one subscription together, during subscribe they have to pay the current month/year immediately but for future transactions that should be automatically.

 

Currently, we are just using the refId to know which transaction associated with which planId they have registered.

 

What we have supposed to be a workable solution that when user subscribe a plan we just pass the refId in ARB refId field and we are assuming that refId always come in webhooks call Right ?