On This Page

Features Introduced This Week

RM-28905

Description
This release of Decision Manager updates the Identity Behavior Analysis (IBA) triggering values to improve model accuracy. This update will enhance the visibility of the IBA system, account for evolved consumer behavior patterns, and ensure the continued accuracy of IBA info codes.
Audience
Users of Decision Manager's Identity Behavior Analysis modeling system.
Benefit
Improved accuracy of IBA info codes and adjusted behavior patterns.
Technical Details
None.
Important Dates
Released to production May 24, 2024.

RM-28804

Description
The Token Management Service has been updated to enable provisioning of a network token by sending a device token in the payment subscription service.
Audience
Merchants that use TMS with VTS network tokenization enabled.
Benefit
Merchants can create Card-on-File tokens using device tokens.
Technical Details
When you send a payment request that also requests the creation of a token, pass the device token in the value of the
tokenizedCard.number
 field, as shown in the partial API request example below. When the authorization is successful, TMS creates the token and provides the token ID in the API response. 
...
},
  "processingInformation": {
    "actionList": [
      "TOKEN_CREATE"
],
  "actionTokenTypes": [
    "instrumentIdentifier"
],
  "commerceIndicator": "internet"
},
  "paymentInformation": {
    "tokenizedCard": {
      "number": "{pass the device token here}",
...
Important Dates
Released to production May 24, 2024.

RM-28492

Description
Secure Acceptance is updated with two new API fields to comply with mandates from the Kindgom of Saudi Arabia (KSA) regarding credentials on file and transaction agreement.
Audience
Merchants that use Secure Acceptance to accept payments from customers in the KSA.
Benefit
Maintaining complaince enables merchants to accept payments from customers in the KSA.
Technical Details
The new fields are:
transaction_reason
This is an existing request field, which now accepts new values and is mandatory in the KSA for recurring payments. If you are setting up an agreement to charge a consumer in future, use this field to indicate the reason for those future charges. Valid values include:
  • setup_recurring
    : use this value to use the payment token for a fixed amount on a fixed schedule.
  • setup_standing_order
    : use this value to use the payment token for a variable amount on a fixed schedule.
  • setup_installments
    : use this value to use the payment token for a regular payment with a specified value in the
    recurring_number_of_installments
     field.
  • setup_unscheduled_payments
    : use this value to use the payment token for unscheduled payments (merchant or customer initiated).
transaction_agreement_id
Unique ID generated by the merchant for recurring and unscheduled card-on-file transactions, and shared in subsequent transactions. This field is required for all unscheduled card-on-file and recurring subsequent transactions from Saudi Arabia merchants. The merchant generates an agreement ID for each card holder or payment agreement. This field can contain foreign/Arabic character set. This value is forwarded to the Saudi payment processor.
Important Dates
Released to production May 21, 2024.