-
Notifications
You must be signed in to change notification settings - Fork 47
Open
Description
There is a closed issue (#13) which indicates that the transaction.processorResponse property has been deprecated. The linked commit actually just corrects the deprecation notice from indicating that statusEvents should be used, to the correct property which is statusHistory.
We're currently using the transaction.processorResponse property returned from a chargePaymentMethod mutation to obtain the transaction legacy code, and so my question really is, when will this mutation stop returning the transaction.processorResponse property from the Sandbox/Live environments, and also how can we be informed of breaking changes that are being made to the GraphQL API in the future?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels