After creating your Tazapay account at https://tazapay.com, and completing the required steps to validate your account, you can connect it to Foxy by following these steps:

1. Log in to your Tazapay account, and proceed to the “API Keys” section
2. If there isn't already a public key generated, click to generate one
3. Open the Foxy administration for your store, and go to the “payments” section.
4. Ensure you are on “Live Servers” for your payment servers (this requires an active Foxy subscription for your store)
5. Check the checkbox for “Accept payments using your Tazapay account”
6. From the Tazapay administration, copy the “API_Key” value into the “api key” field in Foxy, and also the “API_Secret” value from Tazapay into the “api secret” field in Foxy.
7. Save the payments page in the Foxy administration

At this point Tazapay will be enabled for your store. We recommend completing a purchase on your store to confirm that everything is working correctly.

You can create a test Tazapay account from their sandbox site at https://sandbox.tazapay.com. You would then copy the API key and secret values into the “payments” page of the Foxy administration just like as described above - but ensuring that you are on “Test Servers” for your payments page. Note that your API secret should also begin with sandbox_, if it doesn't, then you might be copying live credentials instead.

There are some test card numbers available on the Tazapay site here.

Contact tazapay for info. Know more? Feel free to edit this page with info.

At the time of the customer completing the transaction - we don't necessarily know whether the transaction was completed yet or not. We instead rely on a notification from the gateway after the checkout has been completed to confirm whether the transaction was approved or not. To handle this, transactions are initially marked as pending, and when we get a confirmation from the gateway on the result of the transaction, we update it accordingly. Each time the status changes, a webhook/datafeed will be sent to your endpoint if configured with the transaction details and the status node will be present.

The status node can contain one of three different values: pending, approved or rejected. Depending on the types of actions you're needing to perform at your endpoint, you need to make sure the appropriate status value is present first.

If you have tips, experience, or helpful notes related to this gateway that would benefit others, please add them below, including your name and the date. We reserve the right to edit or remove comments that don't add value to this page.