Release v0.0.1.20

1. Addition of new APIs::
   (i) /kms/v2/keys - get
   (ii) /kms/v2/keys-password/{keyId} - patch
   (iii) /kms/v2/keys-pgp/{keyId} - patch
   (iv) /kms/v2/keys-scmp/{keyId} - patch

2. Addition of new verb/method in existing API
   endpoint: /kms/v2/keys-asym/{keyId}
   verb: patch

3. Enhancements to Payments API with update in existing field length.

Release v0.0.1.19

1. Addition of three new APIs:
   (i) Transient Token Data
   endpoint: "/up/v1/payment-details/{transientToken}"
   (ii) Unified Checkout Capture Context
   endpoint: "/up/v1/capture-contexts"
   (iii) Retrieve the EMV Dictionary
   endpoint: "/tss/v2/transactions/emvTagDetails"

2. Enhancements to Payments API with additional fields and update in existing field definition.

3. Enhancements to Decision API with additional fields and update in existing field definition.

4. Enhancements to PayerAuthEnrollment API with additional fields and update in existing field definition.

Release v0.0.1.18

Cybersource.Authentication.NetStandard ( v0.0.1.9 )

• Paths have been made platform independent

CyberSource.Rest.Client.NetStandard

• Enhancements to Payments API with additional fields and update in existing field definition.

Release v0.0.1.17

• Enhancements to Payments API

Release v0.0.1.16

Cybersource.Authentication.NetStandard ( v0.0.1.8 )

• Enhanced log masking

CyberSource.Rest.Client.NetStandard

• Enhanced Payments API with additional fields and update in existing field definition

Release v0.0.1.15

Cybersource.Authentication.NetStandard ( v0.0.1.7 )

• Fix for issue with persistence of masking configurations
• Fix for masking data with whitespace in logs
• Added prefix and bin to masking

CyberSource.Rest.Client.NetStandard

• Enhancements to Payments API and Transaction Search API
• Fix for Invoicing APIs

Release v0.0.1.14

• Enhancements to Payments API
• Addition of new KMS API endpoint

Release v0.0.1.13

• Enhancements to Payments API

Release v0.0.1.12

Cybersource.Authentication.NetStandard ( v0.0.1.6 )

• • Fix for cache issue
  • The first certificate that is cached is always reused, without option to add more certificates. Also, the certificate fetched from cache is never matched to the certificate that is required.
    Solution : Adding certificate based on name of the certificate file. If the certificate has not been seen before, the certificate is added to the cache. If the certificate already exists in the cache, it is returned from the cache.

CyberSource.Rest.Client.NetStandard

• Updates to Transaction Search and Details API
• Carries fix for cache issue from Cybersource.Authentication.NetStandard SDK

Release v0.0.1.11

Cybersource.Authentication.NetStandard ( v0.0.1.5 )

• Fix for #22

CyberSource.Rest.Client.NetStandard

• Enhancements to Payment API and Reporting API