Skip to content

Commit d32a9a5

Browse files
committed
Merge pull request #100 from uphold/support/add-application-to-transaction-destination
Add application id to transaction destinations
2 parents e1e00bb + b8a895c commit d32a9a5

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

_transactions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,15 +80,15 @@ In step one, one prepares the transaction by specifying:
8080
- The _currency_ to denominate the transaction by.
8181
- The _amount_ of value to send in the denominated currency.
8282
- The _origin_ of the transaction can be an account id in the case of a _deposit_.
83-
- The _destination_ of the transaction, which can be in the form of a bitcoin address, an email address, an account id, or a Uphold username.
83+
- The _destination_ of the transaction, which can be in the form of a bitcoin address, an email address, an account id, an application id or an Uphold username.
8484

8585
The following table describes the types of transactions currently supported:
8686

8787
Type | Origin | Destination
8888
---------- | -------------------------- | -------------------------------------------------------
8989
deposit | _ACH_ or _SEPA_ account id | Uphold card id
9090
withdrawal | Uphold card id | _ACH_, _SEPA_ or _Bitcoin_ address
91-
transfer | Uphold card id | An email address, an Uphold username, an Uphold card id
91+
transfer | Uphold card id | An email address, an application id, an Uphold username or an Uphold card id
9292

9393
Upon preparing a transaction, a [Transaction Object](#transaction-object) will be returned with a newly-generated `id`.
9494
<aside class="notice">

0 commit comments

Comments
 (0)