[BitShares 2.0 Technologies] Recurring & Scheduled Payments (Discussion)

[cube]

https://github.com/cryptonomex/graphene-ui/issues/808

Should the issue be raised in graphene repo instead?

[xeroc]

https://github.com/cryptonomex/graphene-ui/issues/808

[abit]

1) you setup a withdraw permission:

Code: [Select]

get_prototype_operation withdraw_permission_create_operation
[
  25,{
    "fee": {
      "amount": 0,
      "asset_id": "1.3.0"
    },
    "withdraw_from_account": "1.2.0",
    "authorized_account": "1.2.0",
    "withdrawal_limit": {
      "amount": 0,
      "asset_id": "1.3.0"
    },
    "withdrawal_period_sec": 0,
    "periods_until_expiration": 0,
    "period_start_time": "1970-01-01T00:00:00"
  }
]

All you need to define is

* The account from which to withdraw
* The account that is allowed to withdraw
* The asset and amount limit that is allowed to withdraw
* And the period in which the limit is reset (e.g. 1k$ monthly.)
* as well as the start time


2) The other party can withdraw funds from your account with the
withdraw operation:

Code: [Select]

get_prototype_operation withdraw_permission_claim_operation
[
  27,{
    "fee": {
      "amount": 0,
      "asset_id": "1.3.0"
    },
    "withdraw_permission": "1.12.0",
    "withdraw_from_account": "1.2.0",
    "withdraw_to_account": "1.2.0",
    "amount_to_withdraw": {
      "amount": 0,
      "asset_id": "1.3.0"
    }
  }
]
You need

* The actually object id of that withdrawal permission
* the account to withdraw from (imho redundant)
* the account to withdraw to
* and the amount

The biggest problem here is that the withdraw permissions are not
"searchable" and I don't think they are in the results of
get_full_account yet. @abit: maybe you can help add them there.

Once you have a withdraw permission object id (and the matching
account), you can create a withdrawal transaction!

If you have time please submit an issue to github if not already done.

[xeroc]

1) you setup a withdraw permission:

Code: [Select]

get_prototype_operation withdraw_permission_create_operation
[
  25,{
    "fee": {
      "amount": 0,
      "asset_id": "1.3.0"
    },
    "withdraw_from_account": "1.2.0",
    "authorized_account": "1.2.0",
    "withdrawal_limit": {
      "amount": 0,
      "asset_id": "1.3.0"
    },
    "withdrawal_period_sec": 0,
    "periods_until_expiration": 0,
    "period_start_time": "1970-01-01T00:00:00"
  }
]

All you need to define is

* The account from which to withdraw
* The account that is allowed to withdraw
* The asset and amount limit that is allowed to withdraw
* And the period in which the limit is reset (e.g. 1k$ monthly.)
* as well as the start time


2) The other party can withdraw funds from your account with the
withdraw operation:

Code: [Select]

get_prototype_operation withdraw_permission_claim_operation
[
  27,{
    "fee": {
      "amount": 0,
      "asset_id": "1.3.0"
    },
    "withdraw_permission": "1.12.0",
    "withdraw_from_account": "1.2.0",
    "withdraw_to_account": "1.2.0",
    "amount_to_withdraw": {
      "amount": 0,
      "asset_id": "1.3.0"
    }
  }
]
You need

* The actually object id of that withdrawal permission
* the account to withdraw from (imho redundant)
* the account to withdraw to
* and the amount

The biggest problem here is that the withdraw permissions are not
"searchable" and I don't think they are in the results of
get_full_account yet. @abit: maybe you can help add them there.

Once you have a withdraw permission object id (and the matching
account), you can create a withdrawal transaction!

[svk]

Status?
Does that include a basic set of conditions to create transaction rules in the GUI?

We need some documentation of how this is implemented in the blockchain before we can add it to the GUI. At the moment I have no idea how it works.

[btswolf]

Status?
Does that include a basic set of conditions to create transaction rules in the GUI?

[Samupaha]

This was very positive surprise. I've heard that many merchants were not interested in bitcoin because it didn't work with subscription based business models.

[Tuck Fheman]

PayPal 2.0!

How about having a debit card that can withdraw $X monthly from your blockchain account?!

[xeroc]

PayPal 2.0!

How about having a debit card that can withdraw $X monthly from your blockchain account?!

[Tuck Fheman]

BitShares 2.0 Technologies
Recurring & Scheduled Payments



Give direct debit authority or limited withdraw permissions to anyone
BitShares is the first smart contract platform with built in support for recurring payments and subscription payments. This feature allows users to authorize 3rd parties to make withdraws from their accounts within certain limits. This is convenient for anyone who likes to “set it and forget it” when it comes to their monthly bills and subscriptions.

full length

PayPal 2.0!

[emski]

Who has figured out the magic in this already?

Looks like you've been busy lately.
The magnitude of changes is incredible.
Lets see how it will work out.

[xeroc]

Who has figured out the magic in this already?

[xeroc]

BitShares 2.0 Technologies
Recurring & Scheduled Payments



Give direct debit authority or limited withdraw permissions to anyone
BitShares is the first smart contract platform with built in support for recurring payments and subscription payments. This feature allows users to authorize 3rd parties to make withdraws from their accounts within certain limits. This is convenient for anyone who likes to “set it and forget it” when it comes to their monthly bills and subscriptions.

full length