Variable names used on developers.payeezy.com

[ScotteSolutionsLtd]

Hello, thank you for this example. I was wondering if you could explain where the 2 different API keys in the code here come from:

paymentJS_php_integration/config.php

Line 13 in 12df0ae

'apiKey' => '{PAYEEZY_APIKEY}',

At least one is from the developer portal, though they have different names there.
PAYMENTJS2 APIKEY vs. PAYEEZY_APIKEY
PAYMENTJS2 APISECRET vs. PAYEEZY_APISECRET
PAYEEZY_APISECRET < ---> Payment.JS Secret ?
PAYEEZY_AUTHTOKEN <--> Reporting Token ?

Can you detail what these are called in the developer portal versus your code - and/or if something is also required to be retrieved from a Firstdata (demo) account?

[Martyn911]

Also interested in this information

[brandon-garcia]

So basically there are two sets of credentials needed, one to authenticate with Payment.JS, another to authenticate with the target gateway.

In developer.payeezy.com under your "My APIs" page (/user/me/apps), you will see a list of the apps you have created credentials for. This page will contain details like:

• API Key
• API Secret
• Payment.JS Secret
• Reporting Token

If you created your app to have access to both Payment.JS and to Payeezy (sandbox or live) then
the API Key will be the same for Payment.JS and for Payeezy (otherwise you will need to contact your integration support person). And then you will use "API Secret" for the Payeezy API Secret and "Payment.JS Secret" for the Payment.JS API Secret.

"Reporting Token" and "PAYEEZY_AUTHTOKEN" are not the same.
The "PAYEEZY_AUTHTOKEN" value is found under the Merchant record you have registered
which can be found on your "Merchants" page (/user/me/merchants) under the table header
"Token".