dinkbit / conekta-cashier

Laravel + Conekta = Painless subscription billing. http://laravel.com

Laravel Conekta Cashier

Port of Stripe Laravel Cashier to Conekta

Please note the latest version of Laravel Cashier supports Laravel 5+, if you are looking for the Laravel 4 implementation see the 1.0 branch.

---

Laravel Cashier

• Introduction
• Configuration
• Subscribing To A Plan
• Single Charges
• Swapping Subscriptions
• Cancelling A Subscription
• Resuming A Subscription
• Checking Subscription Status
• Handling Failed Payments
• Handling Other Conekta Webhooks

Introduction

Laravel Cashier provides an expressive, fluent interface to Conekta's subscription billing services. It handles almost all of the boilerplate subscription billing code you are dreading writing. In addition to basic subscription management, Cashier can handle coupons, swapping subscription, subscription "quantities", cancellation grace periods, and even generate invoice PDFs.

Configuration

Composer

First, add the Cashier package to your composer.json file:

"dinkbit/conekta-cashier": "~2.0" (For Conekta 1.0.0 PHP-SDK 2.0)

Service Provider

Next, register the Dinkbit\ConektaCashier\CashierServiceProvider in your app configuration file.

Migration

Before using Cashier, we'll need to add several columns to your database. Don't worry, you can use the conekta-cashier:table Artisan command to create a migration to add the necessary column. For example, to add the column to the users table use php artisan conekta-cashier:table users. Once the migration has been created, simply run the migrate command.

Model Setup

Next, add the Billable trait and appropriate date mutators to your model definition:

use Dinkbit\ConektaCashier\Billable;
use Dinkbit\ConektaCashier\Contracts\Billable as BillableContract;

class User extends Eloquent implements BillableContract {

	use Billable;

	protected $dates = ['trial_ends_at', 'subscription_ends_at'];

}

Conekta Key

Finally, set your Conekta key in your services.php config file:

'conekta' => [
	'model'  => 'User',
	'secret' => env('CONEKTA_API_SECRET'),
],

Alternatively you can store it in one of your bootstrap files or service providers, such as the AppServiceProvider:

User::setConektaKey('conekta-key');

Subscribing To A Plan

Once you have a model instance, you can easily subscribe that user to a given Conekta plan:

$user = User::find(1);

$user->subscription('monthly')->create($creditCardToken);

You can also extend a subscription trial.

$subscription = $user->subscription('monthly')->create($creditCardToken);

$user->extendTrial(Carbon::now()->addMonth());

The subscription method will automatically create the Conekta subscription, as well as update your database with Conekta customer ID and other relevant billing information. If your plan has a trial configured in Conekta, the trial end date will also automatically be set on the user record.

If your plan has a trial period that is not configured in Conekta, you must set the trial end date manually after subscribing:

$user->trial_ends_at = Carbon::now()->addDays(14);

$user->save();

Specifying Additional User Details

If you would like to specify additional customer details, you may do so by passing them as second argument to the create method:

$user->subscription('monthly')->create($creditCardToken, [
	'email' => $email, 'name' => 'Joe Doe'
]);

To learn more about the additional fields supported by Conekta, check out Conekta's documentation on customer creation.

Single Charges

If you would like to make a "one off" charge against a subscribed customer's credit card, you may use the charge method:

$user->charge(100);

The charge method accepts the amount you would like to charge in the lowest denominator of the currency. So, for example, the example above will charge 100 cents, or $1.00, against the user's credit card.

The charge method accepts an array as its second argument, allowing you to pass any options you wish to the underlying Conekta charge creation:

$user->charge(100, [
	'card' => $token,
]);

The charge method will return false if the charge fails. This typically indicates the charge was denied:

if ( ! $user->charge(100))
{
	// The charge was denied...
}

If the charge is successful, the full Conekta response will be returned from the method.

Swapping Subscriptions

To swap a user to a new subscription, use the swap method:

$user->subscription('premium')->swap();

If the user is on trial, the trial will be maintained as normal. Also, if a "quantity" exists for the subscription, that quantity will also be maintained.

Cancelling A Subscription

Cancelling a subscription is a walk in the park:

$user->subscription()->cancel();

When a subscription is cancelled, Cashier will automatically set the subscription_ends_at column on your database. This column is used to know when the subscribed method should begin returning false. For example, if a customer cancels a subscription on March 1st, but the subscription was not scheduled to end until March 5th, the subscribed method will continue to return true until March 5th.

Resuming A Subscription

If a user has cancelled their subscription and you wish to resume it, use the resume method:

$user->subscription('monthly')->resume($creditCardToken);

If the user cancels a subscription and then resumes that subscription before the subscription has fully expired, they will not be billed immediately. Their subscription will simply be re-activated, and they will be billed on the original billing cycle.

Checking Subscription Status

To verify that a user is subscribed to your application, use the subscribed command:

if ($user->subscribed())
{
	//
}

The subscribed method makes a great candidate for a route middleware:

public function handle($request, Closure $next)
{
	if ($request->user() && ! $request->user()->subscribed())
	{
		return redirect('billing');
	}

	return $next($request);
}

You may also determine if the user is still within their trial period (if applicable) using the onTrial method:

if ($user->onTrial())
{
	//
}

To determine if the user was once an active subscriber, but has cancelled their subscription, you may use the cancelled method:

if ($user->cancelled())
{
	//
}

You may also determine if a user has cancelled their subscription, but are still on their "grace period" until the subscription fully expires. For example, if a user cancels a subscription on March 5th that was scheduled to end on March 10th, the user is on their "grace period" until March 10th. Note that the subscribed method still returns true during this time.

if ($user->onGracePeriod())
{
	//
}

The everSubscribed method may be used to determine if the user has ever subscribed to a plan in your application:

if ($user->everSubscribed())
{
	//
}

The onPlan method may be used to determine if the user is subscribed to a given plan based on its ID:

if ($user->onPlan('monthly'))
{
	//
}

Handling Failed Payments

What if a customer's credit card expires? No worries - Cashier includes a Webhook controller that can easily cancel the customer's subscription for you. Just point a route to the controller:

Route::post('conekta/webhook', 'Dinkbit\ConektaCashier\WebhookController@handleWebhook');

That's it! Failed payments will be captured and handled by the controller. The controller will cancel the customer's subscription after three failed payment attempts. The conekta/webhook URI in this example is just for example. You will need to configure the URI in your Conekta settings.

Handling Other Conekta Webhooks

If you have additional Conekta webhook events you would like to handle, simply extend the Webhook controller. Your method names should correspond to Cashier's expected convention, specifically, methods should be prefixed with handle and the name of the Conekta webhook you wish to handle. For example, if you wish to handle the invoice.payment_succeeded webhook, you should add a handleInvoicePaymentSucceeded method to the controller.

class WebhookController extends Dinkbit\ConektaCashier\WebhookController {

	public function handleInvoicePaymentSucceeded($payload)
	{
		// Handle The Event
	}

}

Note: In addition to updating the subscription information in your database, the Webhook controller will also cancel the subscription via the Conekta API.

Todo

• Add Invoices support when Conekta has them.

conekta-cashier's Issues

No se puede instalar con Laravel 5.4 y actualizar Conekta a 3.0

Hola, acabo de empezar con la versión 5.4 de Laravel pero me da problemas a la hora de instalar el paquete, esto es lo que sale

vagrant@homestead:/Code/vistas$ clear
vagrant@homestead:/Code/vistas$ composer require dinkbit/conekta-cashier
Using version ^2.2 for dinkbit/conekta-cashier
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Conclusion: don't install dinkbit/conekta-cashier v2.2.1
- Conclusion: remove laravel/framework v5.4.4
- Installation request for dinkbit/conekta-cashier ^2.2 -> satisfiable by dinkbit/conekta-cashier[v2.2.0, v2.2.1].
- Conclusion: don't install laravel/framework v5.4.4
- dinkbit/conekta-cashier v2.2.0 requires illuminate/support 5.0.|5.1.|5.2.|5.3. -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- don't install illuminate/support v5.1.1|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.13|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.16|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.2|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.20|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.22|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.25|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.28|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.30|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.31|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.41|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.6|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.1.8|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.0|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.19|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.21|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.24|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.25|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.26|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.27|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.28|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.31|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.32|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.37|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.43|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.45|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.6|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.2.7|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.3.0|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.3.16|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.3.23|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.3.4|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.0|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.22|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.25|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.26|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.28|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.33|don't install laravel/framework v5.4.4
- don't install illuminate/support v5.0.4|don't install laravel/framework v5.4.4
- Installation request for laravel/framework (locked at v5.4.4, required as 5.4.*) -> satisfiable by laravel/framework[v5.4.4].

Installation failed, reverting ./composer.json to its original content.

Además de que ya requiere la actualización a la nueva versión de Conekta.

Actualizar tarjeta de una suscripción cancelada.

Cuando se intenta actualizar la tarjeta de una suscripción cancelada, Conekta regresa error.

Esto es porque el método updateSubscription() que es llamado desde updateCard() intenta crear una nueva suscripción, pero sólo tiene el parámetro 'card'.

¿De qué otra manera se puede actualizar una tarjeta de una suscripción cancelada por un pago fallido por una tarjeta vencida?

How to send email? 'email is missing'

When doing
$user->subscription('monthly')->create('tok_test_visa_4242');
getting a validation error
Conekta_ParameterValidationError with message 'email is missing.'

Instalacion en laravel 5.2

Hola, estoy tratando de usar el paquete en laravel 5.2, y al momento de instalarlo me retorna varios errores de requerimiento de paquetes, cuando liberaran la version para laravel 5.2?

Problem with webhooks controller

It seems that Conekta has changed the Event API so now it asks for the API key, thus, leading to an unhandled webhook. Also, the where used with the Event API returns an error because it must receive an array of options.

Composer conekta-php version

The last version required by composer is ~2.0.4, while current Conekta-php version is on 4.0.3 with support for PHP 7.0, is this library contemplated to be maintained?

Call to a member function extendTrial() on null

Hola quiero implementar extendTrial() pero obtengo un error:

$subscription = $order->subscription('monthly')->create($request->conektaTokenId, [
'email' => '[email protected]',
'name' => 'Nombre'
]);
$subscription->extendTrial(Carbon::now()->addMonth());

Call to a member function extendTrial() on null

Pagos únicos en OXXO y tarjetas

Es posible efectuar cobros en oxxo?

Service Provider and Migration error

Uso Laravel 5.8 y tengo este problema, ya puse la clase en los providers y me sigue marcando el mismo error, hay alguna manera de solventarlo ¿?

Originally posted by @eichgi in #36 (comment)

Conekta Cashier not working with Laravel 5.4.*

I tried installing Conekta Cashier on Laravel 5.4 and I wasn't able to install it. It works with Laravel 5.3 so I had to downgrade, I hope you can fix it soon. Thank you.

PHP Error Call to undefined method: $user->subscription()->canceled()

I get a call to undefined method error when using the $user->subscription()->canceled() method.

PHP Error: Call to undefined method Dinkbit\ConektaCashier\ConektaGateway::canceled() on line 1

Conekta_Error exception message not returned

Is there a reason why failed charges return false as opposed to the Conekta_Error exception message? (See here)

Would it not be better to return the exception message so that I can display a useful error to the user?

Cancelar suscripción al 3er intento de cobro fallido

Hola.

En la documentación dice que se cancelará la suscripción al 3er intento de cobro, pero veo que en el código del webhook se cancela inmediatamente cuando se recibe el evento 'subscription.payment_failed'. ¿No debería cancelarse hasta cuando Conekta envíe el evento 'subscription.canceled'? Según la documentación de Conekta el evento de cancelación se envía automáticamente después del 3er intento de cobro.

Gracias.

Add spark compatibility

Will be great if you add compatibility with laravel spark ;)

Incompatible con Laravel 6.6.0

Hola, ¿cuando es posible que sea compatible con la última versión de Laravel? o al menos las versiones 6.x

¿Como funcionará la opción de pagos en Oxxo? gracias!

Change Conekta-php to 2.0.5

Conekta-php in composer is the previous version, should pull the newest.

php artisan conekta-cashier:table users

Al ejecutar el comando:
php artisan conekta-cashier:table users

en Laravel 5.5 me retorna el siguiente error:

In BoundMethod.php line 135:

  Method Dinkbit\ConektaCashier\CashierTableCommand::handle() does not exist

¿Cómo se puede solucionar eso? La dependencia ya ha sido agregada en composer.json

No puedo instalar con laravel 5.2

COMPOSER OUTPUT:

php /Users/jfhernandeze/Code/hubbify/composer.phar require dinkbit/conekta-cashier:v2.1.4 -n --no-progress
./composer.json has been updated

php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for dinkbit/conekta-cashier v2.1.4 -> satisfiable by dinkbit/conekta-cashier[v2.1.4].
- Conclusion: remove symfony/debug v3.0.1
- Conclusion: don't install symfony/debug v3.0.1
- dinkbit/conekta-cashier v2.1.4 requires symfony/http-kernel ~2.3 -> satisfiable by symfony/http-kernel[v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.3.4, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6, v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.24 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.25 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.26 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.27 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.28 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.29 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.30 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.31 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.32 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.33 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.34 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.35 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.36 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.3.37 requires symfony/debug ~2.3.24|~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.5.10 requires symfony/debug ~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.5.11 requires symfony/debug ~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.5.12 requires symfony/debug ~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.5.9 requires symfony/debug ~2.5.9|~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.5.10, v2.5.11, v2.5.12, v2.5.9, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.8.0 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.8.1 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.8.2 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.10 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.11 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.12 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.13 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.2 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.3 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.4 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.5 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.6 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.7 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.8 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.6.9 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.0 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.1 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.2 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.3 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.4 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.5 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.6 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.7 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.8 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- symfony/http-kernel v2.7.9 requires symfony/debug ~2.6,>=2.6.2 -> satisfiable by symfony/debug[v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
- Can only install one of: symfony/debug[v2.8.0, v3.0.1].
- Can only install one of: symfony/debug[v2.8.1, v3.0.1].
- Can only install one of: symfony/debug[v2.8.2, v3.0.1].
- symfony/http-kernel v2.3.0 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.1 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.10 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.11 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.12 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.13 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.14 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.15 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.16 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.17 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.18 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.19 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.2 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.20 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.21 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.22 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.23 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.3 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.4 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.5 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.6 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.7 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.8 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.3.9 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.0 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.1 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.10 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.2 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.3 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.4 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.5 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.6 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.7 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.8 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.4.9 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.0 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.1 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.2 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.3 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.4 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.5 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.6 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.7 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.5.8 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.6.0 conflicts with symfony/debug[v3.0.1].
- symfony/http-kernel v2.6.1 conflicts with symfony/debug[v3.0.1].
- Can only install one of: symfony/debug[v2.3.24, v3.0.1].
- Can only install one of: symfony/debug[v2.3.25, v3.0.1].
- Can only install one of: symfony/debug[v2.3.26, v3.0.1].
- Can only install one of: symfony/debug[v2.3.27, v3.0.1].
- Can only install one of: symfony/debug[v2.3.28, v3.0.1].
- Can only install one of: symfony/debug[v2.3.29, v3.0.1].
- Can only install one of: symfony/debug[v2.3.30, v3.0.1].
- Can only install one of: symfony/debug[v2.3.31, v3.0.1].
- Can only install one of: symfony/debug[v2.3.32, v3.0.1].
- Can only install one of: symfony/debug[v2.3.33, v3.0.1].
- Can only install one of: symfony/debug[v2.3.34, v3.0.1].
- Can only install one of: symfony/debug[v2.3.35, v3.0.1].
- Can only install one of: symfony/debug[v2.3.36, v3.0.1].
- Can only install one of: symfony/debug[v2.3.37, v3.0.1].
- Can only install one of: symfony/debug[v2.5.10, v3.0.1].
- Can only install one of: symfony/debug[v2.5.11, v3.0.1].
- Can only install one of: symfony/debug[v2.5.12, v3.0.1].
- Can only install one of: symfony/debug[v2.5.9, v3.0.1].
- Can only install one of: symfony/debug[v2.6.10, v3.0.1].
- Can only install one of: symfony/debug[v2.6.11, v3.0.1].
- Can only install one of: symfony/debug[v2.6.12, v3.0.1].
- Can only install one of: symfony/debug[v2.6.13, v3.0.1].
- Can only install one of: symfony/debug[v2.6.2, v3.0.1].
- Can only install one of: symfony/debug[v2.6.3, v3.0.1].
- Can only install one of: symfony/debug[v2.6.4, v3.0.1].
- Can only install one of: symfony/debug[v2.6.5, v3.0.1].
- Can only install one of: symfony/debug[v2.6.6, v3.0.1].
- Can only install one of: symfony/debug[v2.6.7, v3.0.1].
- Can only install one of: symfony/debug[v2.6.8, v3.0.1].
- Can only install one of: symfony/debug[v2.6.9, v3.0.1].
- Can only install one of: symfony/debug[v2.7.0, v3.0.1].
- Can only install one of: symfony/debug[v2.7.1, v3.0.1].
- Can only install one of: symfony/debug[v2.7.2, v3.0.1].
- Can only install one of: symfony/debug[v2.7.3, v3.0.1].
- Can only install one of: symfony/debug[v2.7.4, v3.0.1].
- Can only install one of: symfony/debug[v2.7.5, v3.0.1].
- Can only install one of: symfony/debug[v2.7.6, v3.0.1].
- Can only install one of: symfony/debug[v2.7.7, v3.0.1].
- Can only install one of: symfony/debug[v2.7.8, v3.0.1].
- Can only install one of: symfony/debug[v2.7.9, v3.0.1].
- Installation request for symfony/debug == 3.0.1.0 -> satisfiable by symfony/debug[v3.0.1].

Installation failed, reverting ./composer.json to its original content.

Actualizar a conekta-php 3.0.0

Composer debería de solicitar la versión más reciente de conekta-php

Creating a customer without a subscription

Laravel Cashier's Billable comes with a method to create a customer without a subscription out of the box.

From what I can tell this functionality is missing from Conekta Cashier. Whilst not necessarily recommended for Cashier, it would be great to integrate this and be able to leverage Cashier for both subscriptions and one-time charges on users with no subscriptions.

Problemas con instalación en Laravel 5.2.32

Using version ^2.1 for dinkbit/conekta-cashier
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install dinkbit/conekta-cashier v2.1.8
    - Conclusion: don't install dinkbit/conekta-cashier v2.1.7
    - Conclusion: don't install dinkbit/conekta-cashier v2.1.6
    - Conclusion: don't install dinkbit/conekta-cashier v2.1.5
    - Conclusion: don't install dinkbit/conekta-cashier v2.1.4
    - Conclusion: remove laravel/framework v5.2.32
    - Installation request for symfony/http-foundation (locked at v3.0.6) -> satisfiable by symfony/http-foundation[v3.0.6].
    - Installation request for symfony/debug (locked at v3.0.6) -> satisfiable by symfony/debug[v3.0.6].
    - Conclusion: don't install laravel/framework v5.2.32
    - dinkbit/conekta-cashier v2.1.0 requires illuminate/support 5.0.*|5.1.* -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.6, v5.1.8].
    - dinkbit/conekta-cashier v2.1.1 requires illuminate/support 5.0.*|5.1.* -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.6, v5.1.8].
    - dinkbit/conekta-cashier v2.1.2 requires illuminate/support 5.0.*|5.1.* -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.6, v5.1.8].
    - dinkbit/conekta-cashier v2.1.3 requires illuminate/support 5.0.*|5.1.* -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.6, v5.1.8].
    - don't install illuminate/support v5.0.0|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.0.22|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.0.25|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.0.26|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.0.28|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.0.33|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.0.4|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.1|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.13|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.16|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.2|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.20|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.22|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.25|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.28|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.30|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.31|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.6|don't install laravel/framework v5.2.32
    - don't install illuminate/support v5.1.8|don't install laravel/framework v5.2.32
    - Installation request for laravel/framework (locked at v5.2.32, required as 5.2.*) -> satisfiable by laravel/framework[v5.2.32].
    - Installation request for dinkbit/conekta-cashier ^2.1 -> satisfiable by dinkbit/conekta-cashier[v2.1.0, v2.1.1, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8].


Installation failed, reverting ./composer.json to its original content.

Obtener siguiente fecha de pago y monto de la subscripción

¿Cuál sería la manera más sencilla o ideal de obtener la fecha en la que será el siguiente cobro y el monto de la suscripción?

Veo que existe un parámetro llamdo "billing_cycle_end" que podría utilizar pero no encuentro una manera fácil o nativa de obtenerlo a través de Cashier.

Gracias

Conekta webhook

El único webhook que me funciona es el de la ruta que pones de ejemplo con la función handleWebhook. Al hacer uno nuevo, si este recibe algún parámetro empieza a fallar. Ya probé quitando tanto la palabra array como dejándola y nada.

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;

use App\Http\Requests;
use App\Http\Controllers\Controller;

use Dinkbit\ConektaCashier\WebhookController as WebhookController;

class WebhookController extends WebhookController
{
    public function failed(array $payload) {

    }
}

Idk

Problemas with install

Hi,

I have problems trying to use your package:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for dinkbit/conekta-cashier dev-master -> satisfiable by dinkbit/conekta-cashier[dev-master].
    - dinkbit/conekta-cashier dev-master requires conekta/conekta-php dev-master -> no matching package found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.