agiliq/merchant — Issue #19: adding transaction_id, subscription_id as part of standard response dictionary
Author: tinio
Created: 2011-11-08 00:30:13+00:00
State: open

Given that the various payment processor gateways have widely varying transaction response objects, it would be incredibly helpful to include 'transaction_id' and 'subscription_id' as a part of the standard response dictionary.

As an example, here's the implementation for the authorize.net gateway: tinio/merchant@55954480511dba80e99f93f039a6f75e9f19533e

@theju, if this sounds agreeable and doesn't go against a possible desire to keep the standard response dictionary simple, I'd be happy to implement this for additional gateways, and submit a proper Pull Request.

Thanks.