korozcolt / payments-symfony

v1.0.1 2026-10-02 01:37 UTC

Requires

• php: ^8.2
• ext-pdo: *
• korozcolt/payments-core: ^1.0
• nyholm/psr7: ^1.8
• symfony/config: ^6.4|^7.0
• symfony/console: ^6.4|^7.0
• symfony/dependency-injection: ^6.4|^7.0
• symfony/framework-bundle: ^6.4|^7.0
• symfony/http-client: ^6.4|^7.0
• symfony/http-foundation: ^6.4|^7.0
• symfony/http-kernel: ^6.4|^7.0
• symfony/routing: ^6.4|^7.0

Requires (Dev)

• pestphp/pest: ^2.0|^3.0
• symfony/browser-kit: ^6.4|^7.0

MIT

• symfony
• payments
• mercadopago
• symfony-bundle
• colombia
• epayco
• Wompi

Published on Packagist.org on 2026-10-02 01:39 UTC

README

Symfony bundle for korozcolt/payments-core: Wompi, MercadoPago and ePayco.

Tested against Symfony 7.4 with a real kernel: bundle configuration, schema command, HTTP webhooks (400/401/200/405), PSR-14 events through event_dispatcher, console command.

Part of the korozcolt/payments ecosystem

The gateway logic (Wompi, MercadoPago, ePayco) is written once, in payments-core, and each framework gets a thin adapter. Install the adapter for your framework; Composer pulls the core in.

Package	What it is
payments	Laravel adapter (also the monorepo)
payments-core	Framework-agnostic core: drivers, manager, webhooks
payments-codeigniter4	CodeIgniter 4 adapter
payments-slim	Slim 4 / PSR-15 adapter
payments-symfony (this package)	Symfony bundle

Why it is split this way, how the pieces relate and what is on the roadmap: ecosystem guide.

Install

composer require korozcolt/payments-symfony

Register the bundle (Flex does it for you; otherwise config/bundles.php):

Korbytes\Payments\Symfony\PaymentsBundle::class => ['all' => true],

Configure

# config/packages/payments.yaml
payments:
    default: wompi
    urls:
        return: 'https://shop.example/payments/return'
    # the payment tables live in any database reachable by PDO:
    dsn: '%env(PAYMENTS_DATABASE_DSN)%'        # e.g. mysql:host=db;dbname=shop;charset=utf8mb4
    username: '%env(PAYMENTS_DATABASE_USER)%'
    password: '%env(PAYMENTS_DATABASE_PASSWORD)%'
    # ...or reuse an existing \PDO service instead of dsn/username/password:
    # pdo: 'app.pdo'
    drivers:
        wompi:
            sandbox: true
            public_key: '%env(WOMPI_PUBLIC_KEY)%'
            private_key: '%env(WOMPI_PRIVATE_KEY)%'
            integrity_secret: '%env(WOMPI_INTEGRITY_SECRET)%'
            events_secret: '%env(WOMPI_EVENTS_SECRET)%'

MercadoPago: access_token, public_key, webhook_secret. ePayco: public_key, private_key, p_cust_id_cliente, p_key. Payout credentials go under payouts: (separate from drivers:).

Options: enabled, subscriptions.scheduled_providers, logging.enabled, statement_descriptor, and http_client (service id of a PSR-18 client that also implements the PSR-17 factories; default: Symfony HttpClient with a 30 s timeout).

Routes:

# config/routes/payments.yaml
payments:
    resource: '@PaymentsBundle/config/routes.php'

This exposes POST /payments/webhooks/{provider}. Point the provider's dashboard at it.

Create the tables

php bin/console payments:schema            # creates them on the configured connection
php bin/console payments:schema --dump     # prints the SQL, e.g. for a Doctrine migration

MySQL, PostgreSQL and SQLite are supported.

Charge

use Korbytes\Payments\Core\Standalone;
use Korbytes\Payments\DTOs\PaymentData;

public function checkout(Standalone $payments): JsonResponse
{
    $charge = $payments->driver('wompi')->charge(new PaymentData(referenceId: 'ORDER-1001', amount: 5000000));

    return $this->json(['reference' => $charge->reference, 'signature' => $charge->signature, 'widget' => $charge->widgetUrl]);
}

Events

The core dispatches through Symfony's event_dispatcher, so use normal listeners:

use Korbytes\Payments\Core\Events\PaymentApproved;
use Symfony\Component\EventDispatcher\Attribute\AsEventListener;

#[AsEventListener]
final class MarkOrderPaid
{
    public function __invoke(PaymentApproved $event): void
    {
        // $event->transaction->reference_id ...
    }
}

Subscriptions (Wompi)

0 * * * * php bin/console payments:process-subscriptions

Webhook answers are identical to the Laravel, CodeIgniter and Slim adapters: 400 unknown/unavailable provider, 401 bad signature, 200 processed (also 200 + success:false for known failures), 500 unexpected error.