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
The readme states the following in the Server integration section:
If `useAuthenticate` is set, then the `authorize` will use the `AUTHENTICATE`/`AUTHORISE`
method of reserving the transaction details.
If `useAuthenticate` is not set (the default) then the `DEFERRED`/`RELEASE`
method of reserving the transaction details will be used.
Seemingly this doesn't allow for a regular PAYMENT txtype - why is this the case? SagePay allows it. I cannot find an explanation for this, or a way to set the txtype manually.
Am I missing something obvious?
The text was updated successfully, but these errors were encountered:
Most gateways just have single authorize() and a purchase() equivalent. Sagepay just happens to have two different modes of authorize(), and you may need to use one or the other, depending on how the payment is finally going to be captured. Hopefully the default authorize() options will be what most people need.
The readme states the following in the Server integration section:
Seemingly this doesn't allow for a regular PAYMENT txtype - why is this the case? SagePay allows it. I cannot find an explanation for this, or a way to set the txtype manually.
Am I missing something obvious?
The text was updated successfully, but these errors were encountered: