-
Notifications
You must be signed in to change notification settings - Fork 26
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
Pay by check #128
Comments
Then click Insert Options.
|
Awesome! I had a small problem following directions but I figured it out. Thank you so much!! |
Thanks for all the help on this. It looks like everything is processing nicely. It looks like the line item information is passed to the Caldera outgoing email but is not passed to the CiviCRM invoice. Is that correct or should the line item detail be appearing in the CiviCRM invoice? |
@lyonsdigital all line items should appear in the invoice, what CiviCRM version are you on? |
I'm on 5.13.4. I've created a page to recertify individuals. I'm getting an email with a long list of names who were recertified. I have an attatched CSV with the same information. However, it appears that the list is not transcribed to the invoice in CiviCRM. It would be nice to have that list of five names or fewer on the invoice for the member organization to see who they are paying to certify. The client is complaining that even though they have the information, it's not presented in an easy enough way to easily read. |
You need to upgrade to CiviCRM v5.16+ or include this patch civicrm/civicrm-core/pull/13477 |
Thank you again |
I'm stymied. I need to generate a contribution invoice for CiviCRM and my client offers the options to pay later by check or pay now by credit card.
Do I need separate contribution processors and conditions for each payment scenario? How do I pass the pay later back to CiviCRM?
Since a manager is processing recertification for multiple contacts, should I be using the order or contribution processor? Sorry for all the questions, but I am very confused right now.
The text was updated successfully, but these errors were encountered: