How do I schedule a one time payment out?
I cannot figure out how to do it?
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
Support Staff 1 Posted by Marc Guyer on 18 Nov, 2013 08:32 PM
Hi Thomas -- That's a difficult question to answer since there's a few ways to go. Based on the title of your post, I'm assuming that you want to schedule a one time payment for the future. In short, there's no way to schedule a "one-time invoice" for the future. That's what the subscription invoice is for. You can add custom charges to the current subscription invoice to be settled on the next bill date. Does that help to answer your question? If you have a more detailed use case, perhaps we can guide you better.
2 Posted by Thomas Eastes on 18 Nov, 2013 09:19 PM
Thanks for the response. That is unfortunate, ability to schedule out one
time payments would be a great feature to add. Can you add that. Here is
my issue. I have a launch fee and then the monthly subscription when I get
a new client. We offer to split up that one time launch fee into payments.
Now there are two ways we can handle this in cheddargetter but they both
suck. One way is to make a pricing plan and then make a calendar event to
remember to turn it off, BUT they are still needing to pay the monthly so
would have to take that into account in the plan etc. The other way which
is how we do it now is just make a calendar event for each time we need to
do a one time payment. This is obviously not ideal and we are in the
process of making a big spreadsheet to handle it all.
Everything else can be handled in Cheddargetter and this feature would
allow use to do it all within Cheddargetter. We could just schedule out
all the one time payments and forget about it. Which is the whole concept
of Cheddargetter. We love everything about Cheddargetter so far except for
this one missing core feature.
Now that you understand why I need this can we get it added in and when do
you think we could have that by? Or do you have a better way to handle
this type of situation? Please advise.
Support Staff 3 Posted by Marc Guyer on 19 Nov, 2013 03:57 PM
I see. I recommend using CG's hooks to trigger adding a custom charge to the pending invoice. You could use this to better automate your manual process. Listening to the transaction hook via Zapier, you could do one of several things. For example, send your ops team an email when a transaction runs prompting the team to lookup the customer's account to determine if a custom charge for an installment payment should be added to the next scheduled invoice (or just run a one-time invoice for the amount). Zapier can also do things like add a row to a google spreadsheet for you, or add a todo list entry to various todo list service providers.
If you'd like to go further into automating that process, you could listen for CG's hooks within your app triggering some logic to determine if the customer is on a payment plan for the setup fee and add a charge or execute a one-time invoice via the API accordingly. You could use the customer metadata feature in CG to record whether or not a customer is on a plan and how many payments they've made or need to still make (or whatever you decide).
In short, there are tools available to fully automate this. We're happy to help further should you have questions.
4 Posted by Thomas Eastes on 22 Nov, 2013 06:30 PM
All I am trying to do is say, I want to do a one time invoice and have it
actualy charge at this future date. All I need is a way on the one time
invoice screen to select a date to actually charge it.
I am putting Slava on this email and he is much more technical than me so
he will try to explain further what I need and can hopefully understand
your suggestions. I do not wan to build some thing through the api just
to schedule a payment out. That is basic functionality.
5 Posted by Jess Pendley on 25 Nov, 2013 05:22 PM
Our current solution to the issue would be to listen for the transaction hook and add a custom charge to the next pending subscription invoice.
The functionality to schedule future charges isn't currently on our development roadmap, so at this time that is the best way to achieve what you'd like.
If you have any other questions, please feel free to get back to us.
Jess Pendley closed this discussion on 25 Nov, 2013 05:22 PM.
Thomas Eastes re-opened this discussion on 25 Nov, 2013 06:36 PM
6 Posted by Thomas Eastes on 25 Nov, 2013 06:36 PM
I am putting Slava back into the thread and he will work with you to figure
this out. Thanks.
7 Posted by Slav Ivanyuk on 25 Nov, 2013 07:08 PM
Jess, could we schedule adding one time payments through Zapier? Would
something like that work?
Agile Harbor, LLC
8 Posted by Slav Ivanyuk on 25 Nov, 2013 07:13 PM
Or, could we set up some kind of cron job to do this? We don't have full
blown integration with you guys and I'm trying to think of quick and dirty
way to do scheduled one time payments where non-technical person could
create those payments to happen in the future.
Agile Harbor, LLC
9 Posted by Jess Pendley on 25 Nov, 2013 07:30 PM
Hi Slav --
I think Marc may have answered this earlier in the thread and you weren't able to see it, so I'll quote him here and then you can fire back any further questions that you might have.
Let us know if you need anything else.
Jess Pendley closed this discussion on 25 Nov, 2013 07:30 PM.
Marc Guyer re-opened this discussion on 25 Nov, 2013 10:08 PM
Support Staff 10 Posted by Marc Guyer on 25 Nov, 2013 10:08 PM
Slav -- Whatever you decide, I'm guessing you're going to need some custom logic on your side. We don't have Zapier input (only output) setup yet so that's not an option anyway. I can maybe help you further if you'll describe your functional requirements. It sounds like you're planning for a manual component where a member of your team adds a setup charge and indicates that it should be charged in 4 monthly payments. It also sounds like that is not standard procedure. So, what's standard procedure for a normal customer and what's the procedure for the special case customer?
11 Posted by Slav Ivanyuk on 26 Nov, 2013 04:26 AM
Marc, basically we need to split one time payment into several equal
payments spread out, once per month. Usually it's just one time payment,
but sometimes the customer doesn't have the funds available right away and
we offer to split it for him. This is on individual basis. We can setup
calendar to remind us to make the payment, but we'd rather prefer automate
it somehow. Did I answer your question?
Agile Harbor, LLC
Support Staff 12 Posted by Marc Guyer on 26 Nov, 2013 02:38 PM
Hi Slav -- I'm looking to understand the customer experience and the experience for your team when the installments functionality is desired. I see that you have several pricing plans but none include setup fee. So it the normal operation always a manual process? In other words, your team adds this special fee as a charge? I'm assuming that a similar experience is desired for the special case?
13 Posted by Slav Ivanyuk on 26 Nov, 2013 09:38 PM
Yes, this launch fee is always custom and different for each client basis.
Even the subscription itself is often custom per client.
What we want to do is split up this custom, manual, launch fee into several
Agile Harbor, LLC
14 Posted by Jess Pendley on 27 Nov, 2013 04:06 PM
Automating this process is going to take a lot of custom work on your end, including creating your own interface in your app to utilize the necessary customer metadata.
It is entirely up to you which direction you go, but our advice would be to keep it simple. There is the possibility that this is a functionality that we would add sometime in the future, but at the moment it isn't on our immediate development roadmap. The manual way that you're currently doing this may be your best - and least complex - way of handling it for the time being, but again, it is completely your decision.
Jess Pendley closed this discussion on 07 Apr, 2014 04:43 PM.