Access sensitive Card information from your client application.
App ID
provided to you upon registration with Gnosis Pay. You’ll also need an ephemeral-token. This ephemeral-token can be retrieved with a call to our private PSE API using mTLS authentication.
App ID
, which will be used in the certificate generation below. You must first create a private key and then generate a Certificate Signing Request (CSR) using the App ID
as follows:
${APP_ID}.csr.pem
file with the Gnosis Pay team. DO NOT EVER share the .key.pem
file with ANYONE.
Once we receive your Certificate Signing Request, we will sign it and send you back the signed certificates. These signed certificates, along with your private key, are used to establish the connection with the PSE API.
<partner_name>.css
, will be incorporated into the iframe.
Standard styling is applied to the iframe elements by default. You can override the style of these classes and IDs as needed. Here are some of them:
.pse-container
- A shared class for all iframe containers.#pse-card-data-container
- The main container for displaying card data..pse-card-field
- The container for each card data field (card number, expiry date, security code)..pse-card-label
- Labels for each field..pse-card-value
- The container for the actual card data values..pse-container
- A shared class for all iframe containers.#pse-set-pin-form
- The main form container.#pse-set-pin-success-container
- The success state container..pse-set-pin-container
- The base container class..pse-set-pin-button
- The base class for all buttons.#pse-continue-pin-button
- The continue button.#pse-done-button
- The done button.gnosis_pay_ui.css
..pse-card-field
class in Firefox: