Once the customer logs in, we will redirect them to your 'RedirectUri' defined in the front end JS. This should be a server side endpoint where you will consume the
authorization_code then make a
/tokens call to obtain customer
For each page loading the Zip account / payment buttons (showing account balance for logged in users), you will need to use the stored [refresh_token] to generate a new access_token each new session or after 30mins.
- This request requires the 'content-type': 'application/x-form-www-urlencoded'
client_secretare Zip provided values. Please request these if you do not already have them.
Short life token to be used for /charges /accounts /userinfo API calls.
Long life token to be stored used to create a new access tokens for future /charges and account functions.