There's additional criteria that ccbill uses to delimit the pricing options that will show up on one of their custom forms. It is accomplished through two fields that are passed to CCBill; those two fields are the "subscriptionTypeId" & "allowedTypes" variables. If aMember could more appropriately account for those variables (as optional customization fields) in the CCBill integration, it would make the integration more thorough for people customizing their pricing options (for when aMember re-directs to CCBill) to be more consistent with how aMember redirects the customer for payment. For example, if a customer selects a recurring pricing option product coupled with credit card payment selection from the aMember interface, proper plugin integration will prevent the customer from again seeing a redundant select box at ccbill asking which pricing option they want to choose. By accounting for those two variables above more thoroughly, CCBill's custom form could present the sales page with the exact same inputs that were specified/recieved from aMember (instead of redundantly presenting a select box again when the customer has already selected their choice from aMember). These specific CCBill form options (aligned exactly for aMember's redirects) can be customized at CCBill through their form customization tool which creates linking code, containing tailored values, for the two variables i mentioned above (delimiting the payment types shown in the ccBill custom form). aMember's ccBill plugin does not properly account for those two variables mentioned above; aMember instead puts the main ccbill account # as default value for both of those variables (which can cause redundant purchase selections). I would love to see otherwise (since those two variables have larger scope & intent), as it would make integration more thorough and less redundant/confusion for customer sign-ups. CCBill generates those form customization variables from their webadmin panel using: "Form Admin" >> "View Form List" >> "Select 4-letter form" >> "Generate HTML" >> "Add Available Subscription Type" >> "Submit" >> "English - Submit" >> "variables are now shown as input type fields (shown in the attachment)"
Thanks Alex for your good answer/explanation in the help forum. This was a case where it was user error on my part. I misunderstood the meaning of the already existing "ccBill Product/Subscription ID" field in the product settings. That is the field that already would've captured the variables I was previously asking about. I had mistakenly been putting my "ccbill main account ID" in that field instead (when in fact "ccbill main account ID" is already captured appropriately elsewhere in the ccbill plugin settings). My mistake, ...good response Alex. I love aMember, as it is very well-designed software, and I can't wait til you get a chance to integrate it with Community Builder. That is the last thing that I need before it enables me to become a very rich man!!!!! Keep up the great work Alex -v/r, Fred