Simone These status values are accessible in the specific objects, the Payment object exists for every mutation and is very generic. If you want the detailed version of each event you are better of using the /user/{userId}/event
endpoint which is a list of all Monetary accounts and all types.
So every Transferwise payment has both a TransferwisePayment object which contains the more detailed statuses and a Payment object.
Imantas
- I think that a regular payment which gets reverted will show up as a new Payment with the same amount. Not 100% sure though since I haven't seen that happen yet myself.
- If it results in a new Payment than it will definitely cause a Mutation callback event
- Read above ^ it's a bit tricky at the moment but the most reliable way I've found is either using the events endpoint so you directly see the different specific Objects. Or send API calls to the different types and combine them. So you would get all master-card-actions to get the card payments and then filter out any Payments with a type MASTERCARD for example.