Now the change is actually more consequent. Not only the two classes, but all adequate references or local member variables were also refactored accordingly.
The only place where "singlePayments" IMO is still valid are the HTTP/REST methods, these can cover multiple payments, but the Entity/POJO class only represents one payment.
I hope you can handle this soon enough to avoid merge conflicts...
Now the change is actually more consequent. Not only the two classes, but all adequate references or local member variables were also refactored accordingly. The only place where "singlePayments" IMO is still valid are the HTTP/REST methods, these can cover multiple payments, but the Entity/POJO class only represents one payment.
I hope you can handle this soon enough to avoid merge conflicts...