Skip to main content
When you need to send PayChoice a file containing sensitive data — a customer or payment-method import, a reconciliation extract, anything with personal or financial details — encrypt it with the key below before sending. Only PayChoice holds the private key, so the file is unreadable to anyone else, including the service you send it through.

​
Key details

Always compare the fingerprint of the key you import against the one above before encrypting. If they differ, don’t use the key — contact support@paychoice.com.au.

​
Public key

Copy the block below into a file named paychoice.asc.
paychoice.asc

​
Encrypting a file

1

Import the key

2

Verify the fingerprint

The output must show 91F9 A5D7 274B 919B D0AD A372 C597 7993 40C6 BD50.
3

Encrypt

--trust-model always skips the interactive “use this key anyway?” prompt, which is appropriate once you’ve verified the fingerprint yourself. Add --armor if the channel you’re using needs a text file rather than binary.
4

Send the encrypted file

Send the .gpg file through the channel agreed with your PayChoice contact. Never send the unencrypted original, and don’t include the passphrase for anything else in the same message.
On Windows, Gpg4win includes Kleopatra, which does the same import → verify → encrypt steps through a GUI. On macOS, GPG Suite is the equivalent.

​
Key rotation

This key expires on 4 August 2028. We’ll publish the replacement here and note it in the changelog before the current key expires. If you’ve automated encryption, check this page (or the key’s expiry) before each transfer rather than hard-coding the key.