New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payment Processing Quirks #2012
Comments
I've removed this page entirely now, it didn't really hold anything of value.
The config page is just a static list so we can't dynamically change the behavior of the configuration screen. I'm not sure how we'd allow such functionality, but doing so is quite a lot priority
It does not, no
FOSSBilling doesn't save payment details. You'd need to use a payment gateway that supports creating subscriptions. If the community doesn't add it in the near future, though, I've been contacted with paid work to add the functionality in for Stripe and will be doing so once I've finished up my current project.
I don't think anything from InvoiceNinja can actually apply to FOSSBilling. Playing with their demo (briefly), it doesn't seem like it has finalized invoices. You can take an invoice that's already been paid and then go as far as adding on new line-items to then change the value of that invoice. FOSSBilling does finalize invoices at which point they are locked for editing. Do I agree that "approve" isn't as descriptive as it could be though. Maybe something along the lines of "finalize and send"? |
Thanks!
I think there is a config option for this. But InvoiceNinja also has options such as marking an invoice as sent for example when you send it to the customer via a different communication channel, which we have needed before. Options like this might be useful to copy. "Finalize and Send" is definitely better, maybe "Send" would be enough as with proper invoices it should indeed be implicit that an invoice is finalized once sent out. |
I am on the latest 0.6.4
The text was updated successfully, but these errors were encountered: