Connector hub payment

Connector Hub Payment is the shared foundation behind payment features on a Drupal site. It does not process payments by itself: it is the common ground that separate, small modules build on, one per payment provider (Mollie, Stripe, Adyen, MultiSafepay, Buckaroo, ...). If a site needs to accept payments through more than one provider, or might add another one later, this is what keeps the "amount", "status" and "connection" parts consistent instead of each provider module reinventing them differently.

Features

• Exact amounts: money is stored as whole units (like cents), never as a decimal number that can quietly round incorrectly.
• One record per payment action (started, captured, cancelled, refunded) rather than a single record that tries to describe an entire purchase. A payment can stay successful while a linked refund is still being processed, and both are visible on their own.
• A consistent status for every action, translated from each provider's own wording, so an administrator reads the same status values regardless of which provider was used.
• Reuses Connector Hub's existing "connection" concept: configuring a payment provider account works the same way as configuring any other Connector Hub connection, including secret storage through the Key module and support for more than one account per provider.
• Built-in safety: registering a payment action is safe to retry (a repeated request will not create a duplicate record), and only explicitly recognized provider references are stored, never a raw, unfiltered response from the provider.

Use this when a site processes online payments and needs a consistent way to track them across one or more providers, especially if more than one provider is expected now or later.

Post-Installation

After enabling this module, a new "Payment operations" page appears under Content. It is read-only and lists every payment action and its status; there is nothing to configure on this page itself.

On its own, this module cannot take any payments: it also requires at least one provider adapter module (for example, one for Mollie) that depends on it. Once a provider adapter is installed, configure a connection for it the same way as any Connector Hub connection, under Configuration > Web services > Connector Hub: choose the provider, store its secret through the Key module, and save.

Additional Requirements

The Connector Hub module (required). The Key module (required, via Connector Hub) stores all secrets outside of configuration.

Recommended modules/libraries

None beyond Connector Hub and Key at this time. A provider adapter module (for Mollie, Stripe, Adyen, MultiSafepay, Buckaroo, or another provider) is what actually makes this module useful day to day; none are published yet.

Similar projects

Drupal Commerce's Payment module is the closest comparison, but it is built directly into Commerce's own order and cart lifecycle. Connector Hub Payment works without Commerce installed, which suits a site that needs to accept payments without Commerce's full order system, or that wants to respect Commerce's existing payment lifecycle rather than introduce a second, competing one when Commerce is already present.

Supporting this Module

No sponsorship links at this time.

Community Documentation

See this module's README.md for an architecture overview and CONTRIBUTING.md for how to add a new provider adapter. No video walkthrough or demo site yet, since no provider adapter has been published.