SDK - Token Management

For configuration code samples, see our Configuration Code for SDKs article.

To access the history of your token updates in the .NET SDK, you may use the TokenUpdaterHistory() public method.

You may access this method in the ReportingService class, using the following portico configuration details:

var porticoConfig = new PorticoConfig {
    SecretApiKey = " ",
    IsSafDataSupported = true,
    RequestLogger = new RequestConsoleLogger(),
    ServiceUrl = ServiceEndpoints.PORTICO_TEST
};

In order to access this functionality you will need a valid SecretApiKey and ServiceUrl.

While IsSafDataSupported is not mandatory, it is a part of the test configuration class.

Below are the request parameters with the methods that will set the value in the request:

• ReportStartDate
• ReportEndDate
• Limit
• Offset
• TokenValue
• Action

Below are the response parameters that will be returned from the SDK. They will map to the the TokenUpdaterHistoryResponse class:

• CountAccountsClosed
• CountContactCardholder
• CountUpdateExpirationDate
• CountUpdateCardNumber
• Limit
• Offset
• ReportEndDate
• ReportStartDate
• TotalMatchingRecords
• Results
  • NewCardNumber
  • NewExpirationDate
  • PreviousCardNumber
  • PreviousExpirationDate
  • TokenValue
  • UpdateAction
  • UpdateDate

The PorticoReportingTests file within the test project contains the following test cases for the Report Token Updater History functionality.

• ReportTokenUpdaterHistory_WithStartDateAndResultTypeDetails_ReturnsValidResults
• ReportTokenUpdaterHistory_WithAllCriteria_ReturnsExpectedDetails
• ReportTokenUpdaterHistory_WithStartDateAndEndDateAndResultTypeDetails
• ReportTokenUpdaterHistory_WithStartDateAndCountsResultType_ReturnsValidCounts
• ReportTokenUpdaterHistory_WithStartAndEndDate_TokenValue_LimitOffset_CountsType_ReturnsResponse
• ReportTokenUpdaterHistory_WithStartDateAndEndDateAndResultTypeCounts

These tests validate the token updater history reporting feature, ensuring that reports can be generated using various filters. They ensure that all expected fields and counts are present in the response.