What will happen if the Hivian doesn't have enough HIVE on the due date? (does it cancel the Recurrent payment operation or postpone it?)
What will happen if the Hivian doesn't have enough RC on the due date to create the transfer operation? (does it cancel the Recurrent payment operation or postpone it?)
There will be an API to query the status of a specific Recurrent payment operation?
There will be a specific memo in the transaction of Recurrent payment operation?
There will be an optional option to set an end date?
What will happen if the Hivian doesn't have enough HIVE on the due date? (does it cancel the Recurrent payment operation or postpone it?)
It will be noted as "failed" for that iteration and the next payment try will be at the next recurrence, so if it's a monthly payment and it fails for that month, the next payment tentative will be the next month.
I have coded a system to delete the recurrent transfer operation after x failed tentatives in a row but I don't know yet if it will make the final cut.
What will happen if the Hivian doesn't have enough RC on the due date to create the transfer operation? (does it cancel the Recurrent payment operation or postpone it?)
So far we charge all the RC upfront, so rc at the time of the transfer is not an issue. But it's not ideal to charge a lot of RC at once. So I'm looking at the feasibility to charge RC as it goes.
If the user doesn't have enough RC the operation will just not be executed I think.
There will be an API to query the status of a specific Recurrent payment operation?
Everything will be displayed as virtual operation (similar to what you see for witness pay), there will be filled_recurrent_transfer for a successful transfer and failed_recurrent_transfer for failures
So technically the api already exists in the form of get_account_history. But I'm thinking of adding something to hivemind to make it easier for dapps to work with it.
There will be a specific memo in the transaction of Recurrent payment operation?
You can set a memo when creating the recurrent transfer and it will be sent every time :)
There will be an optional option to set an end date?
It's not in the current implementation, but I think I'll add it in the coming week.
I have some questions:
What will happen if the Hivian doesn't have enough HIVE on the due date? (does it cancel the Recurrent payment operation or postpone it?)
What will happen if the Hivian doesn't have enough RC on the due date to create the transfer operation? (does it cancel the Recurrent payment operation or postpone it?)
There will be an API to query the status of a specific Recurrent payment operation?
There will be a specific memo in the transaction of Recurrent payment operation?
There will be an optional option to set an end date?
That's it (for now 🤣)
@mintrawa: Witness FR - Gen X - Geek 🤓 Gamer 🎮 traveler ⛩️
Don't miss the Hive Power UP Day! more info here
It will be noted as "failed" for that iteration and the next payment try will be at the next recurrence, so if it's a monthly payment and it fails for that month, the next payment tentative will be the next month.
I have coded a system to delete the recurrent transfer operation after x failed tentatives in a row but I don't know yet if it will make the final cut.
So far we charge all the RC upfront, so rc at the time of the transfer is not an issue. But it's not ideal to charge a lot of RC at once. So I'm looking at the feasibility to charge RC as it goes.
If the user doesn't have enough RC the operation will just not be executed I think.
Everything will be displayed as virtual operation (similar to what you see for witness pay), there will be filled_recurrent_transfer for a successful transfer and failed_recurrent_transfer for failures
So technically the api already exists in the form of get_account_history. But I'm thinking of adding something to hivemind to make it easier for dapps to work with it.
You can set a memo when creating the recurrent transfer and it will be sent every time :)
It's not in the current implementation, but I think I'll add it in the coming week.
Thanks for the explanations 👍
It depends on the RC required but if it is high, you're right, taking the whole on the original operation may not be the best option.
Glad to hear it for the memo and consider adding an optional option to set an end date 👍
@mintrawa: Witness FR - Gen X - Geek 🤓 Gamer 🎮 traveler ⛩️
Don't miss the Hive Power UP Day! more info here