This is what my team always did for QA when I worked in a space using payment processors. No need to roll back the transactions directly and risk flagging anyt

This is what my team always did for QA when I worked in a space using payment processors. No need to roll back the transactions directly and risk flagging anything. Plus, it's often useful having a real, live, paid and in good standing account and/or purchase in the system for further testing steps! (More true in the subscription space than the one-time purchase space... but even there... it's probably worth testing your refund flow end to end periodically eventually, once you have a healthy set of traffic under your belt to avoid standing out.)