Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

two calls require for subscription_id generation #71

Open
ashish060211 opened this issue Dec 22, 2020 · 1 comment
Open

two calls require for subscription_id generation #71

ashish060211 opened this issue Dec 22, 2020 · 1 comment

Comments

@ashish060211
Copy link

ashish060211 commented Dec 22, 2020

Currently If user want to generate subscription id from the token created against given credit card, he/she require two separate calls. First call is PaymentsApi.createPayment(paymentRequest) which return Id. Second call is TransactionDetailsApi.getTransaction(Id) which return subscriptionId to be used for Auth call later.
But in case of Soap api, it is happening in a single call of paySubscriptionCreateService(). Can you please fix it and make it single java rest api call.

@beniukdima
Copy link

I have a similar question:

we are trying to upgrade from SOAP SimpleOrder api requests to new REST api and can not find appropriate api for the following old SOAP request:
"ccAuthService_run", "recurringSubscriptionInfo_subscriptionID", "ccCaptureService_run" request. What new REST api call or calls should we use instead?

Request parameters used in SOAP service reference NVPTransactionProcessorClient.RunTransaction method:

var requestParameters = new Dictionary<string, string>
{
{"ccAuthService_run", "true"},
{"merchantID", MerchantId},
{"merchantReferenceCode", order.Id},
{"purchaseTotals_grandTotalAmount", amount},
{"purchaseTotals_currency", order.Price.Currency.Code},
{"recurringSubscriptionInfo_subscriptionID", subscriptionId},
{"ccCaptureService_run", "true" }
};

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants