- Solutions
- Our Platform
Our Platform
Paydock
Quick Contact
- Developers
Developers
Paydock
Resources
- About
About
Paydock
Newsroom
The Paydock WooCommerce Payment Extension has been tested and validated to work with the following versions:
Please note, our extension has not been tested for compatibility with any third-party plugins.
Important Information: Paydock has not yet extended testing beyond the versions listed in this section and has no plans to validate the extension against all versions of WooCommerce, PHP or available third-party plugins. We have no knowledge of the correct functioning of the extension with versions outside of those listed above. If you choose to use the extension with an unvalidated version of WooCommerce, PHP, or with any third-party plugins, please be aware that Paydock cannot confirm that the extension will work correctly and Paydock may not be able to provide the support necessary to ensure that the extension is able to function properly.
For the best experience and full support, we recommend using the validated versions specified above.
Start with installing the Paydock plugin. There are 2 methods available for you:
Installation using the WordPress Directory
Installation by Uploading a ZIP file
Open your web browser. Go to the WordPress site and log in with your administrator credentials.
Click the “Choose File” button and navigate to where you saved the Paydock plugin ZIP file. Select the file and click “Open”.
The Configuration page displays as follows:
3. Explore the configuration structure
Configure the plugin for transactions in a real store environment using your live Paydock keys and payment gateway settings.
Set up a test environment with the test keys for safely testing plugin features without real transactions.
Customise the appearance of the payment widget.
Manage and view logs of interactions between the plugin and the Paydock API for monitoring and troubleshooting.
To configure the plugin for test transactions, select the Sandbox checkbox on top of the “Sandbox Connection” tab. This ensures that all transactions are processed in a sandbox environment, allowing for safe testing without affecting your live operations.
Field | Data | Purpose |
---|---|---|
Connection to Paydock |
Selection out of:
|
Method of connecting to Paydock API. |
Public Key | public key | This key is used for authentication to ensure secure communication with the Payment Gateway. You must fill it out only if the API and Widget Token has not been entered. |
Secret Key | secret key | This key is used for authentication to ensure secure communication with the Payment Gateway. You must fill it out only if the API and Widget Token has not been entered. |
API Access Token | access token | This token authorizes API transactions. Only populate this field if the API Public Key and API Secret Key are not entered. |
Widget Access Token | widget access token | This token authorizes Widget transactions. Only populate the field if the API Public Key and API Secret Key are not entered. |
Field | Data | Purpose |
---|---|---|
Enable | checkbox | Tick the checkbox to enable “Cards” as a payment option during checkout. |
Supported card schemes | selection out of available card schemes | Select which Card type scheme logo to display during checkout. |
Gateway ID | id | Provide the Gateway ID for the respective payment gateway configured from Paydock. |
3DS | Selection out of possible options:
| Enable or disable 3DS. To enable, select either standalone 3DS or in-built 3DS. |
3DS service ID | id | Provide the 3DS service ID to be used for 3DS checks when enabled. Note: This field is only required when standalone 3DS is enabled. |
3DS flow | Selection out of possible options:
| When 3DS is enabled, select which 3DS flow to be supported.
|
Fraud | Selection out of possible options:
| Enable or disable Fraud. To enable, select either standalone Fraud or in-built Fraud. Note:
|
Fraud service id | id | Provide the Fraud service ID to be used for Fraud checks when enabled. Note: Required for “Standalone Fraud” and “In-built Fraud”. |
Direct Charge | checkbox | Tick the checkbox if you want the payment to be captured as soon as the order is placed. |
Save Card | checkbox | Tick the checkbox to allow your logged-in customer to save their cards during checkout. Note: Inbuilt 3DS flow with OTT; saved card option is not supported. |
Save card option | Selection out of possible options:
| Provide how you prefer the payment source information to be saved. Note: This field is only available when the “Save card” checkbox is ticked. |
Apple Pay
Google Pay
PayPal Smart Button
Afterpay v2
Field | Data | Purpose |
---|---|---|
Enable | checkbox | Tick the checkbox to enable the required “Wallet” payment methods as a payment option during checkout. |
Gateway ID | id | Provide the Gateway ID for the respective payment gateway configured from Paydock. |
Fraud | checkbox | Tick the checkbox to enable Fraud. |
Fraud Service ID | id | Provide the Fraud service ID to be used for Fraud checks when enabled. |
Direct Charge | checkbox | Tick the checkbox if you want the payment captured as soon as the order is placed and successful. |
Pay later | checkbox | Tick the checkbox to enable the Pay later option during checkout. Note: Available only for PayPal Smart Button. |
Afterpay v1
Zip
Field | Data | Purpose |
---|---|---|
Enable | checkbox | Tick the checkbox to enable the required “Alternative Payment Method” as a payment option during checkout. |
Gateway ID | id | Provide the Gateway ID for the respective payment gateway configured from Paydock. |
Fraud | checkbox | Tick the checkbox to enable Fraud. |
Fraud service ID | id | Provide the Fraud service ID to be used for Fraud checks when enabled. |
Direct Charge | checkbox | Tick the checkbox if you want the payment captured as soon as the order is placed. Note: This option for APMs is available only for Zip. |
Select version
Personalise payment method titles and descriptions
Stylise widget
Access WooCommerce orders
Click on “Add order.”
2. Create a new charge request through the Paydock dashboard.
Navigate to the charges page on the Paydock dashboard.
Click on the “Add New” tab.
Pre-requisite: Ensure that the order is in the “Paid via Paydock” status before initiating a refund.
Enter the refund amount
Process the refund:
Check the order status
Note: You can continue to issue partial refunds until the cumulative refund amount equals the total amount of the original order.
Pre-requisite:
Ensure that the order is in the “Authorised via Paydock” status, which means the funds have been authorised but not yet captured.
Select the authorised order
Capture the charge
Check the order status update
After capturing the charge, the order status automatically updates to “Paid via Paydock”.
Pre-requisite:
The order must be in either the “Authorised via Paydock” or “Paid via Paydock” status to proceed with a cancellation.
Select the Order to Cancel:
Initiate Cancellation:
Check the order status update
Paydock Holdings Pty Limited
L40,
2 Park Street,
Sydney,
NSW 2000,
Australia
Paydock Ltd
Arquen House,
4-6 Spicer Street,
St. Albans,
Hertfordshire,
England,
AL3 4PQ
Copyright © Paydock 2023. All Rights Reserved | Privacy Policy | Website Terms of Use