RM-32196
- Description
- This release updates transaction search in the Business Center for these gateways:
- Visa Platform Connect
- Chase Paymentech
- Barclays
- First Data Compass
- Visa Direct
- This release places the following search filters into the Payouts category in the transaction search filter drop-down menu:
- Payouts - Pull Funds Transfer (AFT)
- Payouts - Pull Funds Transfer Reversals (AFT)
- Payouts - Pull Funds Transfer Refunds (AFT)
- Payouts – Push Funds Transfer (OCT)
- Audience
- Users of transaction search who also use the gateways listed in the description above.
- Benefit
- This release consolidates searches for Payouts transactions into a single Payouts category.
- Technical Details
- None.
- Important Dates
- Released to Production April 16, 2025.
RM-32196
- Description
- This release adds the Cryptocurrency Purchase category to the Order Information section of the Transaction Details page, for merchants who use the Visa Direct gateway.
- Audience
- Merchants who use the Visa Direct gateway.
- Benefit
- Cryptocurrency transactions are now visible in the Transaction Details page.
- Technical Details
- None.
- Important Dates
- Released to production April 16, 2025.
RM-35378
- Description
- This release enables users to create a new subscription based on a previously successful transaction.
- For API users, send a POST request to the new endpoint/rbs/v1/subscriptions/follow-ons/{RequestID}where they will be exempt from providing the customer ID and only need to specify the subscription details. See the Technical Details section below.
- For Business Center users, the Transaction Management screen now has a Create Subscription option on the Transaction Details screen. Clicking this button will redirect the user to the subscription creation screen with pre-filled information from the transaction.
- Audience
- All users of Recurring Billing Subscriptions 2.0.
- Benefit
- Faster, simpler creation of new subscriptions. This eliminates the need to search for an existing token or create a new customer token and provide payment instrument details before subscription creation.
- Technical Details
- Users must have permissions to create subscriptions and view historical transaction details.
- In the API, you can use the endpointGET /rbs/v1/subscriptions/follow-ons/{RequestID}, to verify the payer data retrieved from the historical transaction (whose ID is passed in theRequestIDfield) to get the information you need to create a token and subscription.
- For example:
- GET /rbs/v1/subscriptions/follow-ons/7216512479796378604957 Response: { "_links": { "self": { "href": "rbs/v1/subscriptions/follow-ons/7216512479796378604957", "method": "GET" }, "create": { "href": "rbs/v1/subscriptions/follow-ons/7216512479796378604957", "method": "POST" } }, "buyerInformation": { "merchantCustomerID": "Merchant customer identifier", "email": test@cybs.com }, "paymentInstrument": { "id": "1F90575B08822A60E063AF598E0AB9BF", "card": { "number": "411111XXXXXX1111", "expirationMonth": "12", "expirationYear": "2024", "type": "001" }, "billTo": { "firstName": "John", "lastName": "Doe", "company": "CyberSource", "address1": "1 Market St", "locality": "San Francisco", "administrativeArea": "CA", "postalCode": "94105", "country": "US", "email": test@cybs.com, "phoneNumber": "4158880000" }
- Using the endpointPOST /rbs/v1/subscriptions/follow-ons/{RequestID}, they cancreate a new subscription.
- These fields arerequiredfor creating a subscription from an existing transaction:
- subscriptionInformation.name
- subscriptionInformation.startDate
- Using existing Plan:subscriptionInformation.planId
- Using One-Time Plan:orderInformation.amountDetails.billingAmount
- orderInformation.amountDetails.currency
- orderInformation.amountDetails.setupFee
- planInformation.billingPeriod.length
- planInformation.billingPeriod.unit
- To create a new subscription:
- Example Request POST /rbs/v1/subscriptions/follow-ons/721651247979637860495 { "clientReferenceInformation": { "code": "FollowOn from 7216512479796378604957", "partner": { "developerId": "ABCD1234", "solutionId": "GEF1234" }, "applicationName": "CYBS-SDK", "applicationVersion": "v1" }, "processingInformation": { "commerceIndicator": "recurring", "authorizationOptions": { "initiator": { "type": "merchant" } } }, "subscriptionInformation": { "planId": "6868912495476705603955", "name": "Subscription with PlanId", "startDate": "2024-08-01" } }Example Response { "_links": { "self": { "href": "/rbs/v1/subscriptions/4567000000000123456789", "method": "GET" }, "update": { "href": "/rbs/v1/subscriptions/4567000000000123456789", "method": "PATCH" }, "cancel": { "href": "/rbs/v1/subscriptions/4567000000000123456789/cancel", "method": "POST" }, "suspend": { "href": "/rbs/v1/subscriptions/4567000000000123456789/suspend", "method": "POST" }, "activate": { "href": "/rbs/v1/subscriptions/4567000000000123456789/activate", "method": "POST" } }, "id": "4567000000000123456789", "submitTimeUtc": "2020-11-01T071957Z", "status": "COMPLETED", "subscriptionInformation": { "code": "SUB1", "status": "ACTIVE" } }
- Important Dates
- Released to production April 16, 2025.
RM-35407
- Description
- For tokenised Click to Pay transactions, the transient token response is now enhanced to include the Bank Identification Number (BIN) and expiration date for the payment card number associated with that token, in addition to the network token BIN.
- Audience
- Users of click to Pay through Unified Checkout.
- Benefit
- More information about the customer's credentials enable merchants to make more sophisticated routing and risk decisions.
- Technical Details
- The new values appear within the metadata object of the API response:{ "metadata" : { "tokenizedCard" : { "card" : { "expirationYear" : "2025", "maskedValue" : "XXXXXXXXXXXX1089", "prefix" : "462294", "expirationMonth" : "12"
- Important Dates
- Released to production April 16, 2025.