Closed judgej closed 8 years ago
The date for this has been moved back to early June. Voids and refunds and reusable tokens are also in the works, but with no announced release date.
Repeat transactions are back on, in API 16-05-2016 v1.
Now we have a better idea what the other transactions look like. It looks like the Request\Transaction
message can be moved to Request\Payment
(without the $transactionType
parameter, it being an implied "Payment").
When Authorize
comes out (which will be very similar to Payment
then there will likely be some more jigging around so that Payment
extended Authorize
. Until then, this will do.
So, the Repeat
transaction needs to be given a new and unique vendorTxCode
but the transactionId
of a previous Recurring
or Instalment
payment.
TODO:
AbstractRequest
.Requesr\Transaction
, switching it over to the Payment
or AbstractRequest
. This applies to the documentation as well as the code.Repeat transactions are now fully supported.
This is being released on test today, hopefully with a documentation update to follow quickly. This is the first new transaction type that the REST API is offering after the simple
payment
transaction.Repeat transactions support service subscriptions and are great for SAAS products. It could sit alongside Stripe on Laravel Spark, for example.