GuidesAPI ReferenceRelease Notes
Release Notes
Back to All

June 18, 2024 - Test Release

3 months ago
  • API v2
  • Account Updater
  • TGAPI v2
  • PS v2

API v2

21530 Add support for RSA OAEP in BBE

  • Below endpoints are going to accept new optional fields as an input:

    • Tokenize endpoint:
      • Encrypted Controller
      • NetworkToken Controller
      • FraudPrevention Controller
    • TokenizeEncrypted & AssociateEncryptedCvv endpoints:
      • Pci Controller

  • Optional Fields added to the request body:

    • Padding - Defaults to PKCS1, other values OAEP
    • Digest:
      • PKCS1:
        • Ignored
      • OAEP:
        • SHA1 - Default if digest is not provided by client
        • SHA256
        • SHA384
        • SHA512

Account Updater

21007 Update Response of New Card Test Case for Test/Prod Consistency

  • The TEST Response for the test case for New Card now provides no new data, aligning with test case results in PROD and with documentation.

TGAPI v2

20250 User Story - TGAPI v2 P2PE PIN Translation Function

  • P2PE PIN fields:
    • The P2PE Decrypt function can be used for PIN block translation and KSN 96-80-bit translation. To invoke, you must specify the desired operation in the function's FIELD parameter and the required arguments for that field.
    • Encrypted PIN block translation:
      • Outputs a new encrypted PIN block in the desired format in place of the function.
      • FIELD: TRANSLATEPIN
      • PINBLOCK: The ISO4 encrypted PIN block from the terminal in hex format.
      • PINKSN: The 96-bit KSN used to DUKPT encrypt the PINBLOCK, in hex format.
        • First 8-characters indicate the input/output AWS Payment Cryptography keys to use for this translation
      • PINOUTFORMAT: The output ISO format of the translation. Values:
        • ISO0
        • ISO0-DUKPT
        • ISO3
        • ISO3-DUKPT
        • ISO4
        • ISO4-DUKPT
      • PINKSNCOMPATIBILITYMODE: Indicates that a legacy 80-bit KSN should be used for generating the DUKPT output. True/False
        • If true, we will convert the input KSN from 96 to 80 bits by removing ANSI X9.24-3-2017 compatibility mode padding.
          • IMPORTANT: If the PINKSN was not generated properly in compatibility mode, KSN data may be lost.
      • DEVICESERIALNUMBER: Optional device serial number.
      • DEVICEFIRMWAREVERSION: Optional device firmware version.
      • Example: 
        {{{{FUNCTION:P2PEDECRYPT,GROUP:<group-name>,FIELD:TRANSLATEPIN,PINBLOCK:<pinblock>,PINKSN:<pin KSN>,PINOUTFORMAT:<output-format>,PINKSNCOMPATIBILITYMODE:<true/false>}}}}
    • 96 to 80-bit KSN translation:
      • Outputs an 80-bit KSN derived from the input 96-bit KSN in hex format.
      • FIELD: TRANSLATEPIN
      • KSN: The input 96-bit KSN in hex format
        • IMPORTANT: If the PINKSN was not generated properly in compatibility mode, KSN data may be lost.
      • Example: 
        {{{{FUNCTION:P2PEDECRYPT,GROUP:<group-name>,FIELD:TRANSLATEKSN,KSN:<KSN to translate>}}}}

PS v2

21514 User Story - Payment Services IXOPAY