Contracts & bindings

BillingServiceProvider registers one service provider per module, and each binds its contracts to a default implementation. To replace a capability, bind your own implementation of the contract in a service provider that boots after the package's.

The core contracts

The unbound licensing key contracts

The licensing module deliberately leaves two crypto-core contracts unbound, because they hold the issuer private key — a host secret, not a package default:

LicenseMint and RevocationPublisher resolve these lazily, so resolving either one before the host has bound the key surfaces a clear container error rather than minting with no key:

use Cbox\License\Contracts\LicenseIssuer;
use Cbox\License\Contracts\RevocationListIssuer;
use Cbox\License\Ed25519LicenseIssuer;
use Cbox\License\Ed25519RevocationListIssuer;

public function register(): void
{
    $this->app->singleton(LicenseIssuer::class, fn () => new Ed25519LicenseIssuer(config('services.licensing.private_key')));
    $this->app->singleton(RevocationListIssuer::class, fn () => new Ed25519RevocationListIssuer(config('services.licensing.private_key')));
}

See Licensing.

Rebinding

use Cbox\Billing\Payment\Contracts\PaymentGateway;

public function register(): void
{
    $this->app->bind(PaymentGateway::class, StripeGateway::class);
}

Two contracts you almost always bind yourself in production: the AllowanceLeaseSource (your billing-side allowance authority) and the EntitlementWriter (cbox-id ships the receiving contract). The rest have working defaults.

Related

• Storage adapters
• Payment gateways
• Testing