Checkout.com Module
Collect card payments with Checkout.com and let clients save a card for future renewals.
Reaching the Screen
Go to Settings → Financial → Payment Gateways, open All Modules and click Checkout.com: {admin}/modules/payment?module=CheckoutCom
Use Payment Gateways to manage the methods clients see.
What Is on the Screen
The module card contains API keys, webhook verification, processing channel, payment method and environment settings.
In this version, the normal payment flow uses your site's card form. The client may then complete bank verification. Saved cards and automatic payments are supported; provider-managed subscriptions and installments are not.
The module also contains a hosted payment page integration. Its allowed-method list affects that page; it does not change the normal card form.
Before You Configure It
- A Checkout.com account enabled for your country, currency and payment methods, plus sandbox access for testing.
- Public and secret API keys from the same environment, with permission to tokenize cards, manage instruments, request and read payments, and issue refunds.
- A reachable HTTPS callback address and its webhook signature key.
Fields
For Status, commission, currency conversion, amount limits and country lists, see Payment Gateways. Callback URL, Success URL and Failed URL are supplied by WISECP.
Tasks
Create the API keys
- In the Checkout.com Dashboard, open Developers → Keys → Create a new key.
- Create public and secret keys for the test environment. Allow the processing channel and the operations listed under prerequisites.
- Copy the keys. Under Developers → Keys, open the applicable key and copy its associated processing channel ID.
Connect the account
- Open the Checkout.com module card and select Status to unlock its settings.
- Enter Secret Key, Public Key and, if needed, Processing Channel ID.
- Select Test Mode for sandbox keys and keep Capture Automatically enabled for immediate collection.
- Click Save Changes. The gateway settings are saved; complete webhook setup before testing a payment.
Configure payment notifications
- Copy Callback URL from the module card.
- In the same Checkout.com environment, open Developers → Webhooks and create a configuration for that HTTPS address.
- Include payment_captured and payment failure events such as payment_declined and payment_capture_declined. Save the configuration and copy its signature key.
- Enter it in Webhook Signature Key and click Save Changes. WISECP can now verify notifications sent to this address.
Test the client payment
- As a client, start a test order or open an unpaid invoice and select the Checkout.com payment method.
- Enter a Checkout.com test card in the card form. Complete any bank verification requested.
- Check the payment in Checkout.com and the invoice in WISECP. A completed capture marks the invoice paid; authorization alone leaves it open.
- Before taking real payments, replace both keys and the webhook configuration with production values, clear Test Mode, and save.
Enable saved cards and renewals
- Return to Payment Gateways → Initial Settings. Select Checkout.com under Card Storage Module and click Save Changes.
- The account owner can add a card from their client account or save it during payment. Card registration uses a zero-amount verification.
- The client selects Turn On Auto-Pay from the card menu under Saved Cards. Renewal invoices can then use automatic collection.
- A successful renewal payment closes its invoice. Removing the saved card also removes its reusable instrument from Checkout.com.
Refund an invoice
- Open the paid invoice: {admin}/invoices/detail?id={invoice}
- Under Summary → Change Status, select Refunded and Refund via payment gateway.
- Click Update Status. An accepted refund request updates the invoice; check completion in Checkout.com.
Things to Watch
A success page can appear while the payment is still authorized. Confirm the invoice status before providing service. With automatic capture disabled, capture the payment in Checkout.com.
An incorrect signature key prevents webhook verification. The return page can also check payment status, but clients may close it. Configure notifications for reliable confirmation.
The module uses the amount booked against the invoice. If that record is missing but a payment ID remains, the request can refund the full payment. Refund carefully when one payment covered several invoices.
Required Privileges
Payment Module Settings (MODULES_PAYMENT_SETTINGS) is required to configure the module. Refunds also require INVOICES_OPERATION.
Related Articles
Vielen Dank für Ihre Rückmeldung!
Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.