Skip to main content
Version: 3.2

Authentication

OBSOLETE
Major Changes

This page has been imported from paypercloud v2 documentation and is obsolete. The new version will be published by 2026/02/18. We kept it here for you to have a slight overview of the layout.


Authentication

To authenticate a source (remotePOS) with the PayPuce PayPerCloud platform, a secret must be defined for this remotePOS. There can be only one secret per POS: creating a new secret will invalidate the previous one.

The secret is valid for 1 year and it will be used to generate an access token, able to make calls to the api. The access token is valid for 7 days. (duration will be decreased to 24h in a later release)

Security will be increased regularly.

API Key are unique

The secret used by a point of sale is different for each RemotePos, even if multiple RemotePos are in the same group.

Api Key Reset

An API key can be reset by going to the "Groups" or "POS" tab, clicking on the three dots, and selecting "New Key." As only one key is available, creating a new key will invalidate the previous one.

A test (or demo) environment can be requested by contacting PayPuce support. The Production environment is only available after validation.