Download OpenAPI specification:
Open Payments Authorization Server
+The authorization server handles grant requests and access token management for the Open Payments protocol, using GNAP (Grant Negotiation and Authorization Protocol).
+Endpoints:
+POST / — initiate a grant requestPOST /continue/{id} — continue a pending grant requestDELETE /continue/{id} — cancel a pending grant requestPOST /token/{id} — rotate an access tokenDELETE /token/{id} — revoke an access tokenFor an overview of how Open Payments authorization works, see the Authorization concepts page.
+Make a new grant request
+required | client (string) or client (object) or client (object) (client) |
object (interact-request) The client instance declares the parameters for interaction methods that it can support using the interact field. + | |
required | object |
object (subject) Information about the subject for which the client is requesting information. + |
{- "access_token": {
- "access": [
- {
- "type": "outgoing-payment",
- "actions": [
- "create",
- "read"
], - "limits": {
- "interval": "R12/2019-08-24T14:15:22Z/P1M",
- "debitAmount": {
- "value": "500",
- "assetCode": "USD",
- "assetScale": 2
}
}
}
]
}, - "interact": {
- "start": [
- "redirect"
], - "finish": {
- "method": "redirect",
- "nonce": "4edb2194-dbdf-46bb-9397-d5fd57b7c8a7"
}
}
}{- "interact": {
- "finish": "4105340a-05eb-4290-8739-f9e2b463bfa7"
}, - "continue": {
- "access_token": {
- "value": "33OMUKMKSKU80UPRY5NM"
}, - "wait": 30
}
}Continue a grant request during or after user interaction.
+| id required | string The unique reference ID of the grant request continuation. + |
| interact_ref | string The interaction reference generated for this +interaction by the AS. + |
{- "interact_ref": "ad82597c-bbfa-4eb0-b72e-328e005b8689"
}{- "access_token": {
- "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0",
- "expires_in": 3600,
- "access": [
- {
- "type": "outgoing-payment",
- "actions": [
- "create",
- "read"
], - "limits": {
- "interval": "R12/2019-08-24T14:15:22Z/P1M",
- "debitAmount": {
- "value": "500",
- "assetCode": "USD",
- "assetScale": 2
}
}
}
]
}, - "continue": {
- "access_token": {
- "value": "33OMUKMKSKU80UPRY5NM"
}, - "wait": 30
}
}Cancel a grant request or delete a grant client side.
+| id required | string The unique reference ID of the grant request continuation. + |
{- "error": {
- "description": "string",
- "code": "invalid_client"
}
}Management endpoint to rotate access token.
+| id required | string The unique reference of the access token to be managed. + |
{- "access_token": {
- "value": "OZB8CDFONP219RP1LT0OS9M2PMHKUR64TB8N6BW7",
- "expires_in": 3600,
- "access": [
- {
- "type": "outgoing-payment",
- "actions": [
- "create",
- "read"
], - "limits": {
- "interval": "R12/2019-08-24T14:15:22Z/P1M",
- "debitAmount": {
- "value": "500",
- "assetCode": "USD",
- "assetScale": 2
}
}
}
]
}
}Download OpenAPI specification:
An API for open access to financial accounts to send and receive payments.
+The resource server manages the core transaction resources of the Open Payments protocol: incoming payments, outgoing payments, and quotes. All resources are scoped to a wallet address and require an access token issued by the authorization server.
+Endpoints:
+/incoming-payments — create and manage incoming payments/outgoing-payments — create and manage outgoing payment instructions/quotes — request a quote for a specific send or receive amountFor a full overview of these resources, see the Resources concepts page.
+A client MUST create an incoming payment resource before it is possible to send any payments to the wallet address.
+When a client creates an incoming payment the receiving Account Servicing Entity generates unique payment details that can be used to address payments to the account and returns these details to the client as properties of the new incoming payment. Any payments received using those details are then associated with the incoming payment.
+All of the input parameters are optional.
+For example, the client could use the metadata property to store an external reference on the incoming payment and this can be shared with the account holder to assist with reconciliation.
If incomingAmount is specified and the total received using the payment details equals or exceeds the specified incomingAmount, then the receiving Account Servicing Entity MUST reject any further payments and set completed to true.
If an expiresAt value is defined, and the current date and time on the receiving Account Servicing Entity's systems exceeds that value, the receiving Account Servicing Entity MUST reject any further payments.
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
A subset of the incoming payments schema is accepted as input to create a new incoming payment.
+The incomingAmount must use the same assetCode and assetScale as the wallet address.
| walletAddress required | string <uri> (walletAddress) The URL of an Open Payments wallet address + |
object (amount) The maximum amount that should be paid into the wallet address under this incoming payment. + | |
| expiresAt | string <date-time> The date and time when payments into the incoming payment must no longer be accepted. + |
object Additional metadata associated with the incoming payment. (Optional) + |
{- "incomingAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "metadata": {
- "externalRef": "INV2022-02-0137"
}
}{- "incomingAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "receivedAmount": {
- "value": "0",
- "assetCode": "USD",
- "assetScale": 2
}, - "completed": false,
- "expiresAt": "2022-02-03T23:20:50.52Z",
- "metadata": {
- "externalRef": "INV2022-02-0137"
}, - "createdAt": "2022-03-12T23:20:50.52Z",
- "methods": [
- {
- "type": "ilp",
- "ilpAddress": "g.ilp.iwuyge987y.98y08y",
- "sharedSecret": "1c7eaXa4rd2fFOBl1iydvCT1tV5TbM3RW1WLCafu_JA"
}
]
}List all incoming payments on the wallet address
+| wallet-address required | string URL of a wallet address hosted by a Rafiki instance. + |
| cursor | string non-empty The cursor key to list from. + |
| first | integer [ 1 .. 100 ] The number of items to return after the cursor. + |
| last | integer [ 1 .. 100 ] The number of items to return before the cursor. + |
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "pagination": {
- "startCursor": "241de237-f989-42be-926d-c0c1fca57708",
- "endCursor": "315581f8-9967-45a0-9cd3-87b60b6d6414",
- "hasPreviousPage": false,
- "hasNextPage": true
}, - "result": [
- {
- "incomingAmount": {
- "value": "250",
- "assetCode": "USD",
- "assetScale": 2
}, - "receivedAmount": {
- "value": "250",
- "assetCode": "USD",
- "assetScale": 2
}, - "metadata": {
- "description": "Hi Mo, this is for the cappuccino I bought for you the other day.",
- "externalRef": "Coffee w/ Mo on 10 March 22"
}, - "expiresAt": "2022-04-12T23:20:50.52Z",
- "createdAt": "2022-03-12T23:20:50.52Z",
- "completed": true
}, - {
- "receivedAmount": {
- "value": "100",
- "assetCode": "USD",
- "assetScale": 2
}, - "expiresAt": "2022-04-12T23:20:50.52Z",
- "createdAt": "2022-03-12T23:20:50.52Z",
- "metadata": {
- "description": "I love your website, Alice! Thanks for the great content"
}, - "completed": false
}
]
}A client can fetch the latest state of an incoming payment to determine the amount received into the wallet address.
+| id required | string Sub-resource identifier + |
| Signature-Input | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "incomingAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "receivedAmount": {
- "value": "1234",
- "assetCode": "USD",
- "assetScale": 2
}, - "completed": false,
- "expiresAt": "2022-04-12T23:20:50.52Z",
- "createdAt": "2022-03-12T23:20:50.52Z",
- "metadata": {
- "description": "Thanks for the flowers!",
- "externalRef": "INV-12876"
}, - "methods": [
- {
- "type": "ilp",
- "ilpAddress": "g.ilp.iwuyge987y.98y08y",
- "sharedSecret": "1c7eaXa4rd2fFOBl1iydvCT1tV5TbM3RW1WLCafu_JA"
}
]
}A client with the appropriate permissions MAY mark a non-expired incoming payment as completed indicating that the client is not going to make any further payments toward this incoming payment, even though the full incomingAmount may not have been received.
This indicates to the receiving Account Servicing Entity that it can begin any post processing of the payment such as generating account statements or notifying the account holder of the completed payment.
+| id required | string Sub-resource identifier + |
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "incomingAmount": {
- "value": "250",
- "assetCode": "USD",
- "assetScale": 2
}, - "receivedAmount": {
- "value": "250",
- "assetCode": "USD",
- "assetScale": 2
}, - "completed": true,
- "expiresAt": "2022-04-12T23:20:50.52Z",
- "createdAt": "2022-03-12T23:20:50.52Z",
- "metadata": {
- "description": "Hi Mo, this is for the cappuccino I bought for you the other day.",
- "externalRef": "Coffee w/ Mo on 10 March 2"
}
}An outgoing payment is a sub-resource of a wallet address. It represents a payment from the wallet address.
+Once created, it is already authorized and SHOULD be processed immediately. If payment fails, the Account Servicing Entity must mark the outgoing payment as failed.
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
A subset of the outgoing payments schema is accepted as input to create a new outgoing payment.
+The debitAmount must use the same assetCode and assetScale as the wallet address.
Either provide a quoteId to create an outgoing payment based on a quote or provide incomingPayment and debitAmount to create an outgoing payment directly from an incoming payment.
| walletAddress required | string <uri> (walletAddress) The URL of an Open Payments wallet address + |
| quoteId required | string <uri> The URL of the quote defining this payment's amounts. + |
object Additional metadata associated with the outgoing payment. (Optional) + |
{- "metadata": {
- "externalRef": "INV2022-02-0137"
}
}{- "failed": false,
- "debitAmount": {
- "value": "2600",
- "assetCode": "USD",
- "assetScale": 2
}, - "receiveAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "sentAmount": {
- "value": "0",
- "assetCode": "USD",
- "assetScale": 2
}, - "grantSpentDebitAmount": {
- "value": "2600",
- "assetCode": "USD",
- "assetScale": 2
}, - "grantSpentReceiveAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "metadata": {
- "description": "Thank you for the shoes."
}, - "createdAt": "2022-03-12T23:20:50.52Z"
}List all outgoing payments on the wallet address
+| wallet-address required | string URL of a wallet address hosted by a Rafiki instance. + |
| cursor | string non-empty The cursor key to list from. + |
| first | integer [ 1 .. 100 ] The number of items to return after the cursor. + |
| last | integer [ 1 .. 100 ] The number of items to return before the cursor. + |
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "pagination": {
- "startCursor": "241de237-f989-42be-926d-c0c1fca57708",
- "endCursor": "315581f8-9967-45a0-9cd3-87b60b6d6414",
- "hasPreviousPage": false,
- "hasNextPage": true
}, - "result": [
- {
- "failed": false,
- "receiveAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "debitAmount": {
- "value": "2600",
- "assetCode": "USD",
- "assetScale": 2
}, - "sentAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "createdAt": "2022-03-12T23:20:50.52Z",
- "metadata": {
- "description": "APlusVideo subscription",
- "externalRef": "customer: 847458475"
}
}, - {
- "failed": false,
- "debitAmount": {
- "value": "7126",
- "assetCode": "USD",
- "assetScale": 2
}, - "receiveAmount": {
- "value": "7026",
- "assetCode": "USD",
- "assetScale": 2
}, - "sentAmount": {
- "value": "7026",
- "assetCode": "USD",
- "assetScale": 2
}, - "createdAt": "2022-03-12T23:20:50.52Z",
- "metadata": {
- "description": "Thank you for your purchase at ShoeShop!",
- "externalRef": "INV2022-8943756"
}
}
]
}A client can fetch the latest state of an outgoing payment.
+| id required | string Sub-resource identifier + |
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "failed": false,
- "debitAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "receiveAmount": {
- "value": "2198",
- "assetCode": "EUR",
- "assetScale": 2
}, - "sentAmount": {
- "value": "1205",
- "assetCode": "USD",
- "assetScale": 2
}, - "createdAt": "2022-03-12T23:20:50.52Z",
- "metadata": {
- "description": "Thanks for the flowers!",
- "externalRef": "INV-12876"
}
}Returns the spent amounts for the current outgoing payment grant corresponding to the presented GNAP access token, if any. If a grant was created with an interval (recurring), the amounts returned are for the current interval.
+| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "spentReceiveAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "spentDebitAmount": {
- "value": "2600",
- "assetCode": "USD",
- "assetScale": 2
}
}A quote is a sub-resource of a wallet address. It represents a quote for a payment from the wallet address.
+| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
A subset of the quotes schema is accepted as input to create a new quote.
+The quote must be created with a (debitAmount xor receiveAmount) unless the receiver is an Incoming Payment which has an incomingAmount.
| walletAddress required | string <uri> (walletAddress) The URL of an Open Payments wallet address + |
| receiver required | string <uri> (receiver) ^(https|http)://(.+)/incoming-payments/(.+)$ The URL of the incoming payment that is being paid. + |
| method required | string (payment-method) Value: "ilp" |
{- "method": "ilp"
}{- "debitAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "receiveAmount": {
- "value": "2198",
- "assetCode": "EUR",
- "assetScale": 2
}, - "method": "ilp",
- "createdAt": "2022-03-12T23:20:50.52Z",
- "expiresAt": "2022-04-12T23:20:50.52Z"
}A client can fetch the latest state of a quote.
+| id required | string Sub-resource identifier + |
| Signature-Input required | string Examples: Signature-Input: sig1=("@method" "@target-uri" "content-digest" "content-length" "content-type");created=1618884473;keyid="gnap-rsa" The Signature-Input field is a Dictionary structured field containing the metadata for one or more message signatures generated from components within the HTTP message. Each member describes a single message signature. The member's key is the label that uniquely identifies the message signature within the context of the HTTP message. The member's value is the serialization of the covered components Inner List plus all signature metadata parameters identified by the label. The following components MUST be included: - "@method" - "@target-uri" - "authorization". When the message contains a request body, the covered components MUST also include the following: - "content-digest" The keyid parameter of the signature MUST be set to the kid value of the JWK. See ietf-httpbis-message-signatures for more details. + |
| Signature required | string Examples: Signature: sig1=:EWJgAONk3D6542Scj8g51rYeMHw96cH2XiCMxcyL511wyemGcw==: The signature generated based on the Signature-Input, using the signing algorithm specified in the "alg" field of the JWK. + |
{- "debitAmount": {
- "value": "2500",
- "assetCode": "USD",
- "assetScale": 2
}, - "receiveAmount": {
- "value": "2198",
- "assetCode": "EUR",
- "assetScale": 2
}, - "method": "ilp",
- "createdAt": "2022-03-12T23:20:50.52Z",
- "expiresAt": "2022-04-12T23:20:50.52Z"
}Download OpenAPI specification:
The wallet address server exposes publicly accessible information about an Open Payments wallet address, including basic account details and the cryptographic keys used to verify requests from this wallet address.
+Endpoints:
+GET / — retrieve public details for a wallet addressGET /jwks.json — retrieve the JSON Web Key Set (JWKS) for a wallet addressFor an overview of wallet addresses and how they work in Open Payments, see the Wallet addresses concepts page.
+Retrieve the public information of the Wallet Address.
+This endpoint should be open to anonymous requests as it allows clients to verify a Wallet Address URL and get the basic information required to construct new transactions and discover the grant request URL.
+The content should be slow changing and cacheable for long periods. Servers SHOULD use cache control headers.
+{- "publicName": "Alice",
- "assetCode": "USD",
- "assetScale": 2,
}