Add JSON::Transaction::MerchantAuthorize
#53
Conversation
There was a problem hiding this comment.
Datatrans::JSON::Transaction::Authorize is actually not for the authorize operation but rather for the init operation.
yeah this rather confusing ... I propose to rename Datatrans::JSON::Transaction::Authorize to Datatrans::JSON::Transaction::Initialize, but create an alias for it (for now).
Once we release the breaking change where the XML API is removed, we can also remove the class alias.
| require 'datatrans/json/transaction/response' | ||
|
|
||
| class Datatrans::JSON::Transaction | ||
| class MerchantAuthorize |
There was a problem hiding this comment.
Datatrans::JSON::Transaction::Authorize is actually not for the authorize operation but rather for the init operation.
yeah this rather confusing ... I propose to rename Datatrans::JSON::Transaction::Authorize to Datatrans::JSON::Transaction::Initialize, but create an alias for it (for now).
Once we release the breaking change where the XML API is removed, we can alias this class to Authorize.
There was a problem hiding this comment.
I think I know what you mean but I'm not sure in what order it would be best to rename / alias / deprecate... If you propose something, I can review it 🙏
Datatrans::JSON::Transaction::Authorizeis actually not for theauthorizeoperation but rather for theinitoperation.With these changes
MerchantAuthorizeis introduced, adding support forauthorizeoperation, and thereby support for authorizing transactions without user interaction; so-called merchant initiated payments.