You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I setup my 3 Sandbox accounts (AUS, NZ and UK) to make sure the issue persists everywhere.
I enabled PCI for all of them. I'm using PHP SDK and Direct Connection method. Whenever I create a new transaction, code V6010 is returned, which means "Invalid TransactionType, account not certified for eCome only MOTO or Recurring available".
Looks like a bug, unless I'm doing something wrong. And I'm stuck with this and can't test my Direct Connection integration in sandbox.
The text was updated successfully, but these errors were encountered:
Thanks for submitting this issue. The error message could be more clear, in this instance it is only the first part which is a problem: "Invalid TransactionType"
You should just need to add a TransactionType to your request and you should be good to go!
I'll see if we can improve the validation around that field for the next release.
eWay PHP SDK version v1.2.3
I setup my 3 Sandbox accounts (AUS, NZ and UK) to make sure the issue persists everywhere.
I enabled PCI for all of them. I'm using PHP SDK and Direct Connection method. Whenever I create a new transaction, code V6010 is returned, which means "Invalid TransactionType, account not certified for eCome only MOTO or Recurring available".
Looks like a bug, unless I'm doing something wrong. And I'm stuck with this and can't test my Direct Connection integration in sandbox.
The text was updated successfully, but these errors were encountered: