Skip to main content
To successfully import your tokens, please encrypt the import file using the PGP public key and send it to the provided GCP signed URL.

Encryption

Merchants must encrypt the token file before sending it. A suggested approach to encryption is using GnuPG interface that can be used to encrypt files using PGP public keys. Please refer to the GnuPG documentation to learn how to add the public key to your keyring and how to encrypt your token file with the key.

File transfer

When you request a token import, a Google Cloud Storage signed URL is provided. This allows you to upload files directly via HTTPS. Sending to this Google Cloud Storage signed URL can be accomplished in a variety of ways described in this Google Cloud storage guide. For example, using cURL this request would look something like this.
In this example, google_signed_cloud_storage_url is the URL provided, and tokens.csv.gpg is the name of the encrypted token file.

Files sent by your payment service

When your previous payment service creates the token file, it must also encrypt it with the Gr4vy public PGP encryption key, not with a key of its own. If your payment service can’t upload to a signed URL, contact the team to arrange an SFTP account instead.