Max Kotliar

> You can always create your own model that implements the interface and define fields mapping as you'd like. This is still the valid case. There is no need to...

@The-Don-Himself Don't get me wrong. I do not against the change and I see reasons behind it. The problem is such a change is a huge BC break and we...

I wish the storage extension was stateless.

As an idea: we can make use of context to store state

> Or one StorageExtension instance per Gateway instance This is the way to go, but I personally consider it as workaround as the service still has a state which is...

Hm, giving it one more thought I do not think there must not be any problems. The storage extension is only keeping the array of models scheduled for update. And...

A PR would be great.

This where it should be fixed https://github.com/Payum/PayumBundle/blob/17ee0b6f3f1fda1026dcea229c0c635971940d43/DependencyInjection/PayumExtension.php#L80

There are a lot of BC breaks, it couldn't be merged. Can we create a new extension called klarna_checkout_rest?

Do you have something like this in the config? ``` #app/config/config.yml payum: security: token_storage: Acme\PaymentBundle\Entity\PaymentToken: { doctrine: orm } storages: Acme\PaymentBundle\Entity\Payment: { doctrine: orm } gateways: offline: factory: offline ```