In this section, we explain how to establish connectivity and provide details
on the API design patterns and security model.
API communication details
Communication with the e-Wallets API involves transport layer and
application layer security. The transport layer
uses TLS to secure HTTP requests (HTTPS) and the
application layer uses
either PGP or
JWE encryption.
In addition, our Protocol standards to find details on
our API design patterns and strategy for maintaining a robust connection with
partners.
Key exchanges
Encryption keys need to be rotated before they expire or if they are
compromised. As part of your implementation, you need to have a process for
managing these exchanges.
To ensure key rotations do not cause temporary outages or require significant
management overhead, e-Wallets partners must support the use
of multiple encryption keys at once. During a key rotation, a second key will
be trusted and verified to be working correctly before the old key is removed.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-12-03 UTC.
[null,null,["Last updated 2024-12-03 UTC."],[[["This section provides instructions for establishing secure connectivity with the e-Wallets API, covering transport and application layer security measures using TLS, PGP, or JWE encryption."],["Details on API design patterns and strategies for maintaining a robust connection are available in the Protocol standards section."],["Encryption key rotation is essential for security, and partners must support multiple encryption keys to ensure seamless transitions during key changes, or risk launch delays."]]],["The e-Wallets API communication utilizes TLS for transport layer security (HTTPS) and either PGP or JWE encryption for application layer security. Partners must adhere to protocol standards for API design. Encryption key management is critical, with a mandatory requirement to support multiple encryption keys simultaneously during rotations to prevent outages. Key rotation processes must be implemented to avoid service disruptions, and lack of support is a blocking bug.\n"]]