Skip to main content
Release Date: May 5, 2021 Parent topic:Vindicia Subscribe-2021.04 Release Notes

​
Payment Features

​
Gift Card Integration via Topps Digital services- Merchant Options

In this release, gift card payment support has been added to Subscribe as part of the REST API for Topps Digital services cards. Topps Digital service (TDS) offers global gift card processing. In the Subscribe REST API, Gift Card and Gift Card Redemption endpoints have been added. A single gift card redemption call will initiate the flow of redemption as well as update the Gift card and Account objects. The Gift Card pin number serves as a secured unique Identifying number and is therefore stored as a hashed component in the system. See the following internal flow for Topps Gift Card Redemption: To enable the gift card payment option, a merchant option flag has been added— GIFT_CARD_PP_ID. By default, it is set to null. Select value Topps to enable. For more details on merchant configuration and set up, see the Topps Implementation Guide.

​
NMI Payment processor Integration

As explained in the external release note, Vindicia has integrated with NMI Payment Provider. Following are the internal configuration details:
  • NMI Processor must be placed in the stored_credentials_level using stack_conf
  • Name-Value Pairs:
    • NMI:security_key
    • NMI:merchant_id
    • NMI:hmac:key (this is needed for chargeback notifications)
  • Configuration file info: No changes are required to server host as no no test server is in use. Testing is performed by setting the account security_key to the relevant test user.
For details on specific merchant settings & implementation, see the NMI Implementation guide. (VIN-7787)

​
Enhance CyberSource as white label gateway solution for Barclays

Payment processor Barclays is changing payment gateway to CyberSource and therefore a CYBS payment provider Name Value Pair is configured (CYB:BackendProcessor = “Barclays”) a different partnerSolutionID is used. (VIN-10104)

​
Card on File- New Merchant Configuration

This feature allows disabling CIT/MIT for a merchant. This is needed mainly for Retain merchants that have not implemented CIT/MIT. The following merchant name value pairs should be used:
  • vin:SCIDisabled - globally disables CIT/MIT for the merchant
  • vin:PaymentProvider.SCIDisabled - disables CIT/MIT support per a specific payment provider for the merchant. In this release, supported for Orbital, Smartpay and Worldpay only.
(VIN-9928)

​
Subscribe Features

​
Vertex O Series 9.0 Support

Subscribe can be used without modification with Vertex O Series Version 9.0 targets through proper configuration. Configuration input:
  • STV_VRTX_HOST_URI identifies a Vertex O Series 9.0 provided by Merchant
  • STV_VRTX_HOST_VERSION is set to “9”
  • Valid Vertex credentials are configured
  • Product (or other) tax classifications values used in Subscribe must match predefined values in Merchant’s Vertex
(VIN-5626)

​
Retain Features

​
De-tokenization of Cybersource Tokens as part of Retain

As part of the Retain flow for failed transactions received from the merchant, we have added the ability to de-tokenize a Cybersource token to derive the PAN and submit the transaction, inclusive of the PAN, to Chase Paymentech for processing. (VIN 9586)

​
Internal Issues