You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: user makes two different charges: $5 and $20 (total $25). They spend $2 of that to bring their available balance to my services to $23. They decide they want to refund the rest of their money.
Normally you'd just reference a debit and do a (partial) refund, which is fine for the most part. But when it comes into cases like this, it's not always possible. Another issue is finding a valid SQL query (if you store this stuff there) to be able to sort out intelligently the money and the IDs.
What I'm asking is for the ability to refund $ without needing to do so based on the transaction ID or anything. Worst case scenario your marketplace balance goes negative and the amount is paid for on the next invoice. This isn't any different than how it is now, just that your users don't have to worry about which transaction/URI/etc... they have to use.
The text was updated successfully, but these errors were encountered:
Scenario: user makes two different charges: $5 and $20 (total $25). They spend $2 of that to bring their available balance to my services to $23. They decide they want to refund the rest of their money.
Normally you'd just reference a debit and do a (partial) refund, which is fine for the most part. But when it comes into cases like this, it's not always possible. Another issue is finding a valid SQL query (if you store this stuff there) to be able to sort out intelligently the money and the IDs.
What I'm asking is for the ability to refund $ without needing to do so based on the transaction ID or anything. Worst case scenario your marketplace balance goes negative and the amount is paid for on the next invoice. This isn't any different than how it is now, just that your users don't have to worry about which transaction/URI/etc... they have to use.
The text was updated successfully, but these errors were encountered: