two calls require for subscription_id generation

Open
#71 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api, backend

Research direction

Start by comparing PaymentsApi.createPayment(paymentRequest) and TransactionDetailsApi.getTransaction(Id) with the SOAP paySubscriptionCreateService() flow described in the issue. Determine how the REST client could expose subscriptionId in one call, then verify that the resulting flow supports the later Auth call.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Java
Stars
29
Forks
50
Avg merge
28m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CyberSource/cybersource-rest-client-java

All issues in CyberSource/cybersource-rest-client-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.