If your Web integration uses the origin key or your iOS integration uses the client encryption public key, switch to the client key. In future versions the client key will be the only way to do client-side authentication. The client key makes it easier for you to manage the origins for your integration.
With the client key, you have:
- A single key for all your allowed origins in an environment.
- Flexibility to add and remove origins without having to generate a new client key.
- A human-readable prefix, test or live, so you can easily tell which environment a client key is linked to.
The client key also enables card type detection through Bank Identification Number (BIN) lookup, which is not available when using the origin key.
Availability and compatibility
The client key is available for the following:
|Web Drop-in and Components||Available for 3.10.1 and later. Previous versions require origin keys for client-side authentication.
Starting 4.0.0 the client key is the only way to do client-side authentication.
|iOS Drop-in and Components||3.7.0 and later.
Previous versions require client encryption public keys.
The client key is backwards compatible with the origin key and the public key. Generating a client key doesn't invalidate a pre-existing origin key or public key.
Switch to using the client key
- Log in to your Customer Area.
- Go to Account > API credentials, and select the API credential for your integration, for example ws@Company.[YourCompanyAccount].
- Add your domains under Allowed origins. These are the domains from which you will be sending your client-side requests.
- Under Authentication, select Generate New Client Key.
- Select Save.
originKey in your Web Drop-in or Web Components configuration object with:
publicKey in your iOS Drop-in or iOS Components configuration with