I used VS Code to install this package. There is a Visual Studio sln file as well, but I have not tested that out recently. There is a file called metro_sdk_c_sharp.code-workspace that contains the three "projects" from with VS Code.

• cardsavr - This is the core SDK that you will be programming against
• cardsavr_e2e - This contains some great examples of how to use the SDK
• cardsavr_tests - Simple tests that unit test the encryption and security libraries within the SDK

Cardsavr contains a set of REST endpoints. Although there are APIs for over a dozen entities, the SDK is primarily designed to address accessing a subset specifically for creating cardholders, and creating the data structures necessar for posting a job. Once a job is created, there needs to be frontend code that listens to feedback from the Virtual Browser System (VBS), and there is a javascript SDK along with code samples here: https://github.com/swch/Strivve-SDK

Additionally, in order to use Cardsavr, you will require application keys, and a username/password for your agent. This can be achieved by contacting developer-support@strivve.com.

All cardholder activity requires an active cardholder. Cardholders can be created using randomly generated usernames or based on usernames from a different source (SSO).

All cardholders must have addresses. A cardholder may have mutliple addressses to use with different cards.

In order to place a job, a cardholder must have a valid card on file.

These are created as part of the cardholder creation process, but are essential for embedded CardUpdatr to process updates on behalf of the cardholder. Grants can be sent to other parts of the system (e.g. the Javascritp SDK within the frontend) so jobs can be interactively posted. Cardholder agents run on the frontend, and thus their permissions must be scoped to only cardholders created for those short lived client sessions. Grants can be used once, and only work for two minutes.

Although there are endpoints for these entities, these are generally the responsibility of the frontend to save. There are examples on how to use them within the e2e folder.

To verify the tests function correctly, you may run:

dotnet test

from the cardsavr_tests folder.

To verify that your agent and integrator keys are configured correctly, you need to create a strivve_creds.json file (there is a sample file included).

dotnet test

That's it! We may occasionally add/remove functionality to/from the SDK, so we will send notifications of changes and deprecation schedules.