default gateway can not be changed

[gavinwahl]

If you configure dinero like this:

dinero.configure({
    'default': {
        'type': 'dinero.gateways.AuthorizeNet',
        # ...
    }
    })

and then switch gateways:

dinero.configure({
    'default': {
        'type': 'dinero.gateways.Braintree',
        # ...
    }
    })

Oops, now all of your existing transactions won't work any more.

What if instead of using the name of the gateway to determine the default, it was something like:

dinero.configure({
    'braintree': {
        'type': 'dinero.gateways.Braintree',
        'default': True,
        # ...
    }, 
    'authorize.net': {
        'type': 'dinero.gateways.AuthorizeNet',
        # ...
    }
    })

Then the default could be safely changed without invalidating all existing transactions.

[rockymeza]

This also raises the issue of switching accounts on a gateway. You would be unable to refund payments within the same gateway company, but on a different account. Is there anyway to avoid this problem, or are we stuck at telling developers to be careful?

[gavinwahl]

You can still switch accounts -- configure authorize.net and when you get a new account add authorize.net.1.

[rockymeza]

That's what I meant by careful.

[colinta]

working on this on the customer branch. using 'default': True as described above.