Data modelling question: An org holds regular events, charges a fee for the event to attendees, and allows attendees to pay either the whole payment in advance, or pay a deposit in advance, then the balance of the fee later.
Attendees can pay via the org's website and an online payment processor.
Seems to me the event fee would be best modelled in SF as 1 Opportunity with either 1 or 2 Payments: If 1 Payment, the attendee paid in full up front; If 2 Payments, 1 Payment is the deposit, the other is the balance. The 1st Payment is immediately marked as paid; the 2nd not till the balance is paid.
Seems like Payments is the most intuitive way to model this user case, but integration with a payment processor like C&P would require some trickery, as it creates Opportunities not Payments.
Any thoughts on how to best model this?
Unless you can find a payment processor that understands/is able to do partial payments/pledges then yes.
