generate
Generate a transaction that moves an amount of currency to the given party.
Note: an Amount of Currency is only fungible for a given Issuer Party within a FungibleAsset
Return
A Pair of the same transaction builder passed in as tx, and the list of keys that need to sign the resulting transaction for it to be valid.
Parameters
The ServiceHub to provide access to the database session.
A builder, which may contain inputs, outputs and commands already. The relevant components needed to move the cash will be added on top.
How much currency to send.
the recipient party.
ourIdentity is used to determine the where the change will be sent. If anonymous is true then an anonymous identity will be generated from this and the change will be spent to that, otherwise ourIdentity will be used as is.
if non-null, the asset states will be filtered to only include those issued by the set of given parties. This can be useful if the party you're trying to pay has expectations about which type of asset claims they are willing to accept.
whether or not to use CI to send the change to
Throws
when a cash spending transaction fails because there is insufficient quantity for a given currency (and optionally set of Issuer Parties).
Generate a transaction that moves an amount of currency to the given party.
Note: an Amount of Currency is only fungible for a given Issuer Party within a FungibleAsset
Return
A Pair of the same transaction builder passed in as tx, and the list of keys that need to sign the resulting transaction for it to be valid.
Parameters
The ServiceHub to provide access to the database session.
A builder, which may contain inputs, outputs and commands already. The relevant components needed to move the cash will be added on top.
How much currency to send.
the recipient party.
ourIdentity is used to determine the where the change will be sent. If anonymous is true then an anonymous identity will be generated from this and the change will be spent to that, otherwise ourIdentity will be used as is.
if non-null, the asset states will be filtered to only include those issued by the set of given parties. This can be useful if the party you're trying to pay has expectations about which type of asset claims they are willing to accept.
whether or not to use CI to send the change to along with CI Mode, by default it does not use CI KEY_PAIR_WITH_CERT use CI using keypair with certificates KEY_PAIR use CI using key pair
Throws
when a cash spending transaction fails because there is insufficient quantity for a given currency (and optionally set of Issuer Parties).
Generate a transaction that moves money of the given amounts to the recipients specified.
Note: an Amount of Currency is only fungible for a given Issuer Party within a FungibleAsset
Return
A Pair of the same transaction builder passed in as tx, and the list of keys that need to sign the resulting transaction for it to be valid.
Parameters
The ServiceHub to provide access to the database session.
A builder, which may contain inputs, outputs and commands already. The relevant components needed to move the cash will be added on top.
A list of amounts to pay, and the party to send the payment to.
ourIdentity is used to determine the where the change will be sent. If anonymous is true then an anonymous identity will be generated from this and the change will be spent to that, otherwise ourIdentity will be used as is.
if non-null, the asset states will be filtered to only include those issued by the set of given parties. This can be useful if the party you're trying to pay has expectations about which type of asset claims they are willing to accept.
whether or not to use CI to send the change to
Throws
when a cash spending transaction fails because there is insufficient quantity for a given currency (and optionally set of Issuer Parties).
Generate a transaction that moves money of the given amounts to the recipients specified.
Note: an Amount of Currency is only fungible for a given Issuer Party within a FungibleAsset
Return
A Pair of the same transaction builder passed in as tx, and the list of keys that need to sign the resulting transaction for it to be valid.
Parameters
The ServiceHub to provide access to the database session.
A builder, which may contain inputs, outputs and commands already. The relevant components needed to move the cash will be added on top.
A list of amounts to pay, and the party to send the payment to.
ourIdentity is used to determine the where the change will be sent. If anonymous is true then an anonymous identity will be generated from this and the change will be spent to that, otherwise ourIdentity will be used as is.
if non-null, the asset states will be filtered to only include those issued by the set of given parties. This can be useful if the party you're trying to pay has expectations about which type of asset claims they are willing to accept.
whether or not to use CI to send the change to along with CI Mode, by default it does not use CI KEY_PAIR_WITH_CERT use CI using keypair with certificates KEY_PAIR use CI using key pair
Throws
when a cash spending transaction fails because there is insufficient quantity for a given currency (and optionally set of Issuer Parties).
Deprecated
Our identity should be specified
Replace with
generateSpend(services, tx, amount, to, ourIdentity, onlyFromParties)Generate a transaction that moves an amount of currency to the given party, and sends any change back to sole identity of the calling node. Fails for nodes with multiple identities.
Note: an Amount of Currency is only fungible for a given Issuer Party within a FungibleAsset
Return
A Pair of the same transaction builder passed in as tx, and the list of keys that need to sign the resulting transaction for it to be valid.
Parameters
The ServiceHub to provide access to the database session.
A builder, which may contain inputs, outputs and commands already. The relevant components needed to move the cash will be added on top.
How much currency to send.
the recipient party.
if non-null, the asset states will be filtered to only include those issued by the set of given parties. This can be useful if the party you're trying to pay has expectations about which type of asset claims they are willing to accept.
Throws
when a cash spending transaction fails because there is insufficient quantity for a given currency (and optionally set of Issuer Parties).
Deprecated
Our identity should be specified
Replace with
generateSpend(services, tx, amount, to, ourIdentity, onlyFromParties)Generate a transaction that moves money of the given amounts to the recipients specified, and sends any change back to sole identity of the calling node. Fails for nodes with multiple identities.
Note: an Amount of Currency is only fungible for a given Issuer Party within a FungibleAsset
Return
A Pair of the same transaction builder passed in as tx, and the list of keys that need to sign the resulting transaction for it to be valid.
Parameters
The ServiceHub to provide access to the database session.
A builder, which may contain inputs, outputs and commands already. The relevant components needed to move the cash will be added on top.
A list of amounts to pay, and the party to send the payment to.
if non-null, the asset states will be filtered to only include those issued by the set of given parties. This can be useful if the party you're trying to pay has expectations about which type of asset claims they are willing to accept.
Throws
when a cash spending transaction fails because there is insufficient quantity for a given currency (and optionally set of Issuer Parties).