How does OrchestratorX Card Vault work?
- Your application communicates with OrchestratorX Card Vault via a middleware.
- All requests and responses to and from the middleware are signed and encrypted with the JWS and JWE algorithms.
- The vault supports CRD APIs on the
/dataand/cardsendpoints. - Cards are stored against the combination of merchant and customer identifiers.
- Internal hashing checks are in place to avoid data duplication.
Key Hierarchy
- Master Key — AES generated key that is encrypted/decrypted by the custodian keys to run the vault and associated configurations.
- Custodian Keys — AES generated key used to encrypt and decrypt the master key. It is broken into two keys (key 1 and key 2) and available with two custodians to enhance security.