Coinbase Commerce Module

17 Aufrufe Markdown

Review the legacy Coinbase Commerce settings and payment records so you can retire the method without losing track of outstanding payments.

Reaching the Screen

Go to Settings → Financial → Payment Gateways → All Modules and click Coinbase Commerce: {admin}/modules/payment?module=CoinbaseCommerce

What Is on the Screen

The form still contains three Commerce settings and the shared payment controls. It describes the legacy hosted charge integration, not Coinbase Business.

Coinbase's official transition notice states that Commerce closes after March 31, 2026, including dashboard access and new charges. Do not enable this module for new payments. This guide preserves the meaning of existing settings and records.

Before You Change Anything

Keep your existing Commerce transaction references and reports. Check unresolved payments before changing the offered methods. A Coinbase Business account requires its own approval and an integration using the new API.

This module uses the old Commerce API key and charge format. A Business/CDP key or JWT cannot replace its API Key value. It has no Business migration control, sandbox switch or connection-test button.

Fields

API KeyEmpty by default; required by the legacy charge integration. Commerce key generation is no longer a new-account setup path. Do not enter a Business key here.
Webhook Shared SecretEmpty by default. The old Commerce subscription's signing secret. Without it, the module skips signature checking but still queries the charge through the API.
Charge TitleOptional; empty by default. Used the company name when empty, or this title on the legacy payment page. Changing it cannot restore the service.

Status, commission, conversion, amount limits and country lists are explained in Payment Modules. The generated Callback URL, Success URL and Failed URL belong to this legacy module.

Tasks

Remove Commerce from New Payments

  1. Open Payment Gateways → Initial → Enabled Module Selection. Remove Coinbase Commerce from the offered methods.
  2. Select an already configured replacement and click Save Changes. Confirm on an unpaid client invoice that Commerce is no longer offered.
  3. Reconcile outstanding Commerce transactions before disabling Status in its module form. Then click Save Changes.
  4. Follow Coinbase's migration documentation for the separate Business integration. Saving this old form does not migrate charges, credentials or webhooks.

Understand the Existing Notifications

The old webhook destination was the complete Callback URL copied from WISECP. Its shared secret belonged in Webhook Shared Secret; existing setting changes require Save Changes.

This is a record of the legacy setup, not an instruction to create a new Commerce webhook. Business has different authentication and notification formats; its webhooks cannot be pointed at this module.

Legacy events identify a charge; the module reads that charge again before deciding. NEW and PENDING leave payment open. COMPLETED, RESOLVED and UNRESOLVED/OVERPAID are accepted. Other unresolved cases wait; expired or canceled charges are rejected.

Reconcile an Existing Payment

  1. Open the relevant invoice: {admin}/invoices/detail?id={invoice}. Review its Payments entries and transaction reference.
  2. Compare the recorded charge ID/code, amount and currency with your retained Coinbase records. Use the provider's support process if account records are inaccessible.
  3. Do not treat a return page, pending network transfer or excess payment as a second payment. Confirm the final outcome before changing the invoice status.
  4. Keep the verified reference with your records. Test any replacement integration separately before accepting real payments through it.

Handle an Existing Refund

The module has no refund or capture operation. Arrange any outstanding refund through the provider's current support/account process; there is no working Commerce refund button to configure here.

  1. Confirm the original transaction and the actual returned amount outside WISECP.
  2. After a full refund completes, use the invoice's Summary → Change Status controls.
  3. Select Refunded → Add as expense and click Update Status.
  4. WISECP records the refund without transferring funds. Keep partial refunds and any excess payment separate at their actual amounts.

Things to Watch

The Two Coinbase Services Are Different

Commerce's old API key, charge identifiers and callbacks do not match Business. The module requires a separate product update before it can support that service. Do not test new live payments to check whether saving a Business key worked.

No Recurring Payment Contract

This module offers no card storage, automatic payments, subscriptions or installments. Its old hosted-page currency descriptions are not a current list of assets accepted by Coinbase Business.

Required Privileges

Settings require Modules → Payment Gateways (MODULES_PAYMENT_SETTINGS). Invoice changes require Billing → Edit (INVOICES_OPERATION). Access to Coinbase account history and a Business application are separate provider permissions.

War das hilfreich?

Vielen Dank für Ihre Rückmeldung!

Brauchen Sie weitere Hilfe?

Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.