The RippleNet Server API provides you the ability to develop custom applications to manage or interact with your RippleNet instance.
Check out the best practices and tutorials.
The RippleNet Server API provides you the ability to develop custom applications to manage or interact with your RippleNet instance.
Check out the best practices and tutorials.
All API operations require a bearer access token for your target environment.<br>Learn how to request the access token.
The RippleNet Server API creates a dynamic [domainPrefix] that consists of {tenant}.{environment}.
Note: This example uses aperture as the tenant. Your tenant ID is different.
| Environment | Domaing Prefix | Domain | Base URL |
|---|---|---|---|
| Test | aperture.test | ripplexcurrent.com | https://aperture.test.ripplexcurrent.com |
| UAT | aperture.uat | ripplexcurrent.com | https://aperture.uat.ripplexcurrent.com |
| Production | aperture.prod | ripplexcurrent.com | https://aperture.prod.ripplexcurrent.com |
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/
https://[domainPrefix].ripplexcurrent.com/v4/
The page number for paginated results. The value is zero-based, where 0 represents the first page.<br/> Set it to 0 to get the first page of results.
Filters for payments based on the type of payment. Valid types are REGULAR, RETURN.
Filters for payments based on the role of the responding connector. Valid roles are SENDING, INTERMEDIARY, RECEIVING, and INTERNAL. The INTERNAL role is meant for payments between RippleNet Cloud and RippleNet where the sender and receiver accounts are on the same RippleNet instance. Use role with state to find payments waiting on action from you as the sending or receiving (or internal) connector.
Deprecated, should use states parameter. Returns payments in the specified state. The following options are valid: ACCEPTED, COMPLETED, EXECUTED, FAILED, LOCKED, LOCK_DECLINED, PREPARED, RETURNED, and SETTLEMENT_DECLINED
Returns payments in the specified states. The following options are valid: ACCEPTED, COMPLETED, EXECUTED, FAILED, LOCKED, LOCK_DECLINED, PREPARED, RETURNED, and SETTLEMENT_DECLINED
Filters for payments where the payments range_field column value is before this specified time stamp (not inclusive). You can also specify after to create a time range between after and before. If before is specified, range_field must also be specified.
Filters for payments where the payments range_field column value is after this specified time stamp (not inclusive). You can also specify before to create a time range between after and before. If after is specified, range_field must also be specified.
Designates the column name of the payments database table that is used for filtering payments before/after/between time stamps. The following options are valid: CREATED_AT, MODIFIED_AT, ACCEPTED_AT, LOCKED_AT, EXECUTED_AT, COMPLETED_AT, RETURNED_AT and EXPIRES_AT. For example, if you specify range_field=MODIFIED_AT, you would specify a time stamp (in the 24 character ISO 8601 YYYY-MM-DDTHH:mm:ss.sssZ format used in payment objects) as the value for before and/or after to fetch payments before, after, or between the specified time range(s) (not inclusive). If range_field is specified, before and/or after must also be specified.
Designates the column name of the payments database table that is used for filtering payments greater/less/between amounts. For example, if you specify amount_range_field=SENDING_AMOUNT, you would specify an amount as the value for greater and/or less to fetch payments greater, less, or between the specified amounts (inclusive). If amount_range_field is specified, minAmount and/or maxAmount must also be specified.
Returns payments with the specified labels. <p>If you apply with_labels with <i>multiple</i> labels, the response returns payments with at least one of the specified labels.</p> <p>For example, the query, </p> <p><b>?with_labels=string1,string2</b></p> <p>returns payments with either "string1" OR "string2".</p>
Returns payments that do <i>not</i> have any of the specified labels. <p>If you apply without_labels with <i>multiple</i> labels, the response returns payments that do not have any of the specified labels.</p> <p>For example, the query,</p> <p><b>?without_labels=string3,string4</b></p> <p>returns payments that are not labeled with either "string3" OR "string4".</p> <p>If you apply both with_labels <i>and</i> without_labels parameters, the response returns payments that have at least one of the specified with_labels strings but omits payments that also have any of the the without_labels strings. </p> <p>For example, the query, </p> <p><b>?with_labels=string1&without_labels=string3</b></p> <p>returns payments with "string1" but not payments with "string3".</p>
Sorts results according to the specified field. Valid options are PAYMENT_ID, EXPIRES_AT, MODIFIED_AT and CREATED_AT.
Sorts result according to the specified direction. Valid options are ASC, DESC.
This parameter can be used to exclude additional info being returned for each payment object. Additional info which will be excluded if the flag set to false include user_info, ripplenet_info, execution_results and internal_info.labels
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments
https://[domainPrefix].ripplexcurrent.com/v4/payments
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments?page=0&size=10&sending_host=string&receiving_host=string&sending_account=string&receiving_account=string&sending_currency=string&receiving_currency=string&payment_type=string&internal_id=string&sender_end_to_end_id=string&connector_role=string&state=string&states=string&before=string&after=string&range_field=string&amount_range_field=SENDING_AMOUNT&min_amount=0&max_amount=0&with_labels=string&without_labels=string&sort_field=MODIFIED_AT&sort_direction=DESC&load_additional_details=true&payment_ids=497f6eca-6276-4993-bfeb-53cbbbba6f08&payment_id=497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'Authorization: YOUR_API_KEY_HERE'Successful response
Sort details of this page
Unique identifier of a payment.
Hash of all values in the Contract object used to ensure immutability. Once a payment transitions to the LOCKED state, the values in this object cannot change.
State of the payment. For details about payment states, see Payment States in the RippleNet Developer Guide.
Date and time at which the payment was last modified, as an ISO-8601 timestamp in UTC.
Represents all immutable parts of a payment agreed upon by all participants as a part of the Lock payment flow. Once a payment transitions to the LOCKED state, the values in this object cannot change.
ID that the sender can specify. Persisted on all RippleNet instances that participate in the payment.
Date and time at which this payment contract was created, as an ISO-8601 timestamp in UTC.
Date and time after which this payment contract expires, as an ISO-8601 timestamp in UTC.
JSON response object that represents a quote for a proposed payment or return payment.
Unique identifier for the quote.
Date and time at which the quote was created, as an ISO-8601 timestamp in UTC.
Date and time after which the quote and its pricing expire, as an ISO-8601 timestamp in UTC.
Indicates how the amount field should be treated for calculating quote values.
Indicates whether a quote's pricing is INDICATIVE or FIRM. An INDICATIVE quote allows for price movements between quote issuance and payment execution, such that the quoted amount and delivered amount may differ. A FIRM quote ensures that the quoted and delivered payment amounts are equal.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code that can be used to filter quotes at the opposite end of the quote request. For example, you can filter by this currency code to find the receiving currency for a quote with a SENDER_AMOUNT quote_type. If not sent in the request, this field value is set to null.
Transfer and exchange elements. A transfer element represents a movement of funds between two accounts. An exchange element represents the exchange of currencies between two accounts.
Triggered when a quote causes an account to go below its minimum_allowed_balance. Otherwise, this field value is set to null.
JSON object containing payment method metadata.
Application-provided data explaining actions taken by RippleNet applications.
RippleNet address of the node from which the RippleNetInfo originated.
If applicable, provides an array of RippleNetInfoEntry's explaining transitions into the SETTLEMENT_DECLINED state
Information explaining the action taken by a RippleNet application. Could be a RippleNet error code, or a written explanation of the action taken
A Base64-encoded execution condition for this payment, the fulfillment of which will be presented to the validator to complete this payment. This value must match the execution_condition in the associated crypto transaction.
Unique identifier of the crypto transaction associated with this payment.
Address of the validator that validated the payment.
If the payment_type is RETURN, provides the payment ID of the original payment that this payment returns. Otherwise, this field value is set to null.
If the payment_type is REGULAR and the payment has an associated return payment, provides the payment ID of the return payment. Otherwise, this field value is set to null.
Represents the actual movement of funds in a payment. Each execution result corresponds to a quote element and represents its execution in a payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Represents the actual movement of funds in a payment as part of liquidation of a Wallet Receive payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Payment liquidation details
Reason behind failure of the liquidation, only applicable if the status is failure
Represents the movement of funds after an On-Demand Liquidity payment fails at intermediary transfer or destination exchange.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Date and time at which the payment was last accepted, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last locked, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last executed, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last completed, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was returned, as an ISO-8601 timestamp in UTC.
JSON object containing information that only the RippleNet instance that set it can view. These values can be set by the sender when accepting a payment and by an intermediary or receiver when locking the payment.
Role of the RippleNet node that sets one or more values in the Internal Info object.
Use as follows:
SENDING: Sending account in the payment resides on this RippleNet instance.RECEIVING: Receiving account in the payment resides on this RippleNet instance.INTERMEDIARY: Neither sending nor receiving accounts in the payment reside on this RippleNet instance.INTERNAL: Both sending and receiving accounts in the payment (usually between RippleNet Cloud and RippleNet) reside on this RippleNet instance.Array of objects that provide label values that are set by including the sub_state field at any stage of the payment's lifecycle. Labels can used as a filtering mechanism when searching for payments. Labels are visible only to the node that added them to this copy of a payment. If the values that populate this array are not set in the request or if the values set in the request are not viewable by your node, this array is empty.
ID that is viewable only to the node that set it. This value can be set by the sender when accepting a payment. This value can also be set by any intermediary and the receiver when locking the payment. If this value is not set in the request or if the value set in the request is not viewable by your node, this field value is set to null.
User-provided data with arbitrary key/value pairs.
RippleNet address of the node that provided the user information.
User information optionally provided when accepting the payment.
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when locking the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when declining to lock the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying acceptance of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying settlement of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settling the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settlement for the payment is declined. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when failing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
Payment sub-state information provided using sub_state and memo fields when finalizing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when completing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, user information optionally provided when forwarding the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, information optionally provided using return_reasons when returning the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
{ "first": true, "last": true, "number": 0, "numberOfElements": 0, "size": 0, "totalElements": 0, "totalPages": 0, "sort": [ { … } ], "content": [ { … } ] }
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}
https://[domainPrefix].ripplexcurrent.com/v4/payments/{payment_id}
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}' \
-H 'Authorization: YOUR_API_KEY_HERE'Successfully retrieved payment.
Unique identifier of a payment.
Hash of all values in the Contract object used to ensure immutability. Once a payment transitions to the LOCKED state, the values in this object cannot change.
State of the payment. For details about payment states, see Payment States in the RippleNet Developer Guide.
Date and time at which the payment was last modified, as an ISO-8601 timestamp in UTC.
Represents all immutable parts of a payment agreed upon by all participants as a part of the Lock payment flow. Once a payment transitions to the LOCKED state, the values in this object cannot change.
ID that the sender can specify. Persisted on all RippleNet instances that participate in the payment.
Date and time at which this payment contract was created, as an ISO-8601 timestamp in UTC.
Date and time after which this payment contract expires, as an ISO-8601 timestamp in UTC.
JSON response object that represents a quote for a proposed payment or return payment.
Unique identifier for the quote.
Date and time at which the quote was created, as an ISO-8601 timestamp in UTC.
Date and time after which the quote and its pricing expire, as an ISO-8601 timestamp in UTC.
Indicates how the amount field should be treated for calculating quote values.
Indicates whether a quote's pricing is INDICATIVE or FIRM. An INDICATIVE quote allows for price movements between quote issuance and payment execution, such that the quoted amount and delivered amount may differ. A FIRM quote ensures that the quoted and delivered payment amounts are equal.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code that can be used to filter quotes at the opposite end of the quote request. For example, you can filter by this currency code to find the receiving currency for a quote with a SENDER_AMOUNT quote_type. If not sent in the request, this field value is set to null.
Transfer and exchange elements. A transfer element represents a movement of funds between two accounts. An exchange element represents the exchange of currencies between two accounts.
Unique identifier for the quote element.
Type of quote element.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order of each quote element along the liquidity path. If a quote includes five quote elements, each one is enacted according to its quote_element_order number to make the proposed payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Fees the sender is charging. When quote_element_type is set to EXCHANGE, this field value is always set to 0.
Fees the receiver is charging. When quote_element_type is set to EXCHANGE, this field value is always set to 0.
Currency code of the sending amount. Included in quote elements with quote_element_type set to EXCHANGE.
Currency code of the receiving amount. Included in quote elements with quote_element_type set to EXCHANGE.
Triggered when a quote causes an account to go below its minimum_allowed_balance. Otherwise, this field value is set to null.
JSON object containing payment method metadata.
Details about the payout method.
Category of the payout method. Defaults to <code>OTHER</code> if not specified.
Itemized list of fees charged by each node.
Fees charged by each node participating in the payment.
Application-provided data explaining actions taken by RippleNet applications.
RippleNet address of the node from which the RippleNetInfo originated.
If applicable, provides an array of RippleNetInfoEntry's explaining transitions into the SETTLEMENT_DECLINED state
Information explaining the action taken by a RippleNet application. Could be a RippleNet error code, or a written explanation of the action taken
A Base64-encoded execution condition for this payment, the fulfillment of which will be presented to the validator to complete this payment. This value must match the execution_condition in the associated crypto transaction.
Unique identifier of the crypto transaction associated with this payment.
Address of the validator that validated the payment.
If the payment_type is RETURN, provides the payment ID of the original payment that this payment returns. Otherwise, this field value is set to null.
If the payment_type is REGULAR and the payment has an associated return payment, provides the payment ID of the return payment. Otherwise, this field value is set to null.
Represents the actual movement of funds in a payment. Each execution result corresponds to a quote element and represents its execution in a payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Represents the actual movement of funds in a payment as part of liquidation of a Wallet Receive payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Payment liquidation details
Reason behind failure of the liquidation, only applicable if the status is failure
Represents the movement of funds after an On-Demand Liquidity payment fails at intermediary transfer or destination exchange.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Date and time at which the payment was last accepted, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last locked, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last executed, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last completed, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was returned, as an ISO-8601 timestamp in UTC.
JSON object containing information that only the RippleNet instance that set it can view. These values can be set by the sender when accepting a payment and by an intermediary or receiver when locking the payment.
Role of the RippleNet node that sets one or more values in the Internal Info object.
Use as follows:
SENDING: Sending account in the payment resides on this RippleNet instance.RECEIVING: Receiving account in the payment resides on this RippleNet instance.INTERMEDIARY: Neither sending nor receiving accounts in the payment reside on this RippleNet instance.INTERNAL: Both sending and receiving accounts in the payment (usually between RippleNet Cloud and RippleNet) reside on this RippleNet instance.Array of objects that provide label values that are set by including the sub_state field at any stage of the payment's lifecycle. Labels can used as a filtering mechanism when searching for payments. Labels are visible only to the node that added them to this copy of a payment. If the values that populate this array are not set in the request or if the values set in the request are not viewable by your node, this array is empty.
ID that is viewable only to the node that set it. This value can be set by the sender when accepting a payment. This value can also be set by any intermediary and the receiver when locking the payment. If this value is not set in the request or if the value set in the request is not viewable by your node, this field value is set to null.
User-provided data with arbitrary key/value pairs.
RippleNet address of the node that provided the user information.
User information optionally provided when accepting the payment.
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when locking the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when declining to lock the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying acceptance of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying settlement of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settling the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settlement for the payment is declined. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when failing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
Payment sub-state information provided using sub_state and memo fields when finalizing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when completing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, user information optionally provided when forwarding the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, information optionally provided using return_reasons when returning the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
{ "payment_id": "d485f100-2af7-4e48-9ab1-3c7e28775691", "contract_hash": "ccb23bd87f13cc13b9d616a9723f76e112aeac8628b2082e0f8bf3b8c670b103", "payment_state": "COMPLETED", "modified_at": "2019-10-01T18:25:47.347Z", "contract": { "sender_end_to_end_id": "string", "created_at": "2019-10-01T18:18:13.665Z", "expires_at": "2019-10-01T18:55:22.824Z", "quote": { … }, "fee_info": { … } }, "ripplenet_info": [ { … } ], "execution_condition": "PrefixSha256Condition{subtypes=[ED25519-SHA-256], type=PREFIX-SHA-256, fingerprint=sfGGHCrkyaMsLQNB62w_4zarlPChHKm47JkXVQbs1z0, cost=132360}", "crypto_transaction_id": "4e05da26-7872-4a1f-b9b7-db7604757c37", "validator": "rn.us.ca.san_francisco", "payment_type": "REGULAR", "returns_payment_with_id": "a69b322f-faa4-4531-bcff-897e5839c130", "returned_by_payment_with_id": "c929a87b-81b8-4878-b21c-1aeaa4fe9276", "execution_results": [ { … } ], "liquidation_execution_results": [ { … } ], "liquidation_details": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "string", "failure_reason": "string", "failure_count": 0 }, "push_forward_execution_results": [ { … } ], "accepted_at": "2019-10-01T18:25:47.347Z", "locked_at": "2019-10-01T18:25:47.347Z", "executed_at": "2019-10-01T18:25:47.347Z", "completed_at": "2019-10-01T18:25:47.347Z", "returned_at": "2019-10-01T18:25:47.347Z", "internal_info": { "connector_role": "RECEIVING", "labels": [ … ], "internal_id": "string" }, "user_info": [ { … } ] }
Locks a payment. The beneficiary and all intermediary institutions agree to proceed with the payment by making successful Lock Payment requests. When the payment is still in a partially LOCKED state, the beneficiary and all intermediary institutions who have not locked, can reject lock payment or fail payment.
Once fully LOCKED, the originating institution can either fail payment or Settle payment. If the originating institution sends a Settle payment request, one of three things will happen:
PREPARED state.SETTLEMENT_DECLINED, orcrypto_transaction_id expires move to the FAILED state.Note: Currently, when making a Create quote to return payment to a RippleNet Cloud account on a RippleNet ledger, the RippleNet user must lock and complete the payment. This means that the RippleNet user takes all action on the return: Get and Accept Quote, Lock, Settle, and Complete payment.
ID that intermediaries and the receiver can set when locking a payment. The ID is viewable only by the node that set it.
Provide one or more arbitrary key/value pairs. <p></p> <p><b>Caution:</b> Ripple recommends that you always include this object, even when empty, to ensure that the RippleNet Payment Object includes the <code>created_at</code> timestamp, which records when the payment was locked. To add an empty object, include: <code>{"user_info":[]}</code></p>
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}/lock
https://[domainPrefix].ripplexcurrent.com/v4/payments/{payment_id}/lock
curl -i -X POST \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}/lock' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"internal_id": "string",
"user_info": {}
}'Successfully locked payment.
Unique identifier of a payment.
Hash of all values in the Contract object used to ensure immutability. Once a payment transitions to the LOCKED state, the values in this object cannot change.
State of the payment. For details about payment states, see Payment States in the RippleNet Developer Guide.
Date and time at which the payment was last modified, as an ISO-8601 timestamp in UTC.
Represents all immutable parts of a payment agreed upon by all participants as a part of the Lock payment flow. Once a payment transitions to the LOCKED state, the values in this object cannot change.
ID that the sender can specify. Persisted on all RippleNet instances that participate in the payment.
Date and time at which this payment contract was created, as an ISO-8601 timestamp in UTC.
Date and time after which this payment contract expires, as an ISO-8601 timestamp in UTC.
JSON response object that represents a quote for a proposed payment or return payment.
Unique identifier for the quote.
Date and time at which the quote was created, as an ISO-8601 timestamp in UTC.
Date and time after which the quote and its pricing expire, as an ISO-8601 timestamp in UTC.
Indicates how the amount field should be treated for calculating quote values.
Indicates whether a quote's pricing is INDICATIVE or FIRM. An INDICATIVE quote allows for price movements between quote issuance and payment execution, such that the quoted amount and delivered amount may differ. A FIRM quote ensures that the quoted and delivered payment amounts are equal.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code that can be used to filter quotes at the opposite end of the quote request. For example, you can filter by this currency code to find the receiving currency for a quote with a SENDER_AMOUNT quote_type. If not sent in the request, this field value is set to null.
Transfer and exchange elements. A transfer element represents a movement of funds between two accounts. An exchange element represents the exchange of currencies between two accounts.
Unique identifier for the quote element.
Type of quote element.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order of each quote element along the liquidity path. If a quote includes five quote elements, each one is enacted according to its quote_element_order number to make the proposed payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Fees the sender is charging. When quote_element_type is set to EXCHANGE, this field value is always set to 0.
Fees the receiver is charging. When quote_element_type is set to EXCHANGE, this field value is always set to 0.
Currency code of the sending amount. Included in quote elements with quote_element_type set to EXCHANGE.
Currency code of the receiving amount. Included in quote elements with quote_element_type set to EXCHANGE.
Triggered when a quote causes an account to go below its minimum_allowed_balance. Otherwise, this field value is set to null.
JSON object containing payment method metadata.
Details about the payout method.
Category of the payout method. Defaults to <code>OTHER</code> if not specified.
Itemized list of fees charged by each node.
Fees charged by each node participating in the payment.
Application-provided data explaining actions taken by RippleNet applications.
RippleNet address of the node from which the RippleNetInfo originated.
If applicable, provides an array of RippleNetInfoEntry's explaining transitions into the SETTLEMENT_DECLINED state
Information explaining the action taken by a RippleNet application. Could be a RippleNet error code, or a written explanation of the action taken
A Base64-encoded execution condition for this payment, the fulfillment of which will be presented to the validator to complete this payment. This value must match the execution_condition in the associated crypto transaction.
Unique identifier of the crypto transaction associated with this payment.
Address of the validator that validated the payment.
If the payment_type is RETURN, provides the payment ID of the original payment that this payment returns. Otherwise, this field value is set to null.
If the payment_type is REGULAR and the payment has an associated return payment, provides the payment ID of the return payment. Otherwise, this field value is set to null.
Represents the actual movement of funds in a payment. Each execution result corresponds to a quote element and represents its execution in a payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Represents the actual movement of funds in a payment as part of liquidation of a Wallet Receive payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Payment liquidation details
Reason behind failure of the liquidation, only applicable if the status is failure
Represents the movement of funds after an On-Demand Liquidity payment fails at intermediary transfer or destination exchange.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Date and time at which the payment was last accepted, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last locked, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last executed, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was last completed, as an ISO-8601 timestamp in UTC.
Date and time at which the payment was returned, as an ISO-8601 timestamp in UTC.
JSON object containing information that only the RippleNet instance that set it can view. These values can be set by the sender when accepting a payment and by an intermediary or receiver when locking the payment.
Role of the RippleNet node that sets one or more values in the Internal Info object.
Use as follows:
SENDING: Sending account in the payment resides on this RippleNet instance.RECEIVING: Receiving account in the payment resides on this RippleNet instance.INTERMEDIARY: Neither sending nor receiving accounts in the payment reside on this RippleNet instance.INTERNAL: Both sending and receiving accounts in the payment (usually between RippleNet Cloud and RippleNet) reside on this RippleNet instance.Array of objects that provide label values that are set by including the sub_state field at any stage of the payment's lifecycle. Labels can used as a filtering mechanism when searching for payments. Labels are visible only to the node that added them to this copy of a payment. If the values that populate this array are not set in the request or if the values set in the request are not viewable by your node, this array is empty.
ID that is viewable only to the node that set it. This value can be set by the sender when accepting a payment. This value can also be set by any intermediary and the receiver when locking the payment. If this value is not set in the request or if the value set in the request is not viewable by your node, this field value is set to null.
User-provided data with arbitrary key/value pairs.
RippleNet address of the node that provided the user information.
User information optionally provided when accepting the payment.
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when locking the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when declining to lock the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying acceptance of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying settlement of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settling the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settlement for the payment is declined. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when failing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
Payment sub-state information provided using sub_state and memo fields when finalizing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when completing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, user information optionally provided when forwarding the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, information optionally provided using return_reasons when returning the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
{ "payment_id": "d485f100-2af7-4e48-9ab1-3c7e28775691", "contract_hash": "ccb23bd87f13cc13b9d616a9723f76e112aeac8628b2082e0f8bf3b8c670b103", "payment_state": "COMPLETED", "modified_at": "2019-10-01T18:25:47.347Z", "contract": { "sender_end_to_end_id": "string", "created_at": "2019-10-01T18:18:13.665Z", "expires_at": "2019-10-01T18:55:22.824Z", "quote": { … }, "fee_info": { … } }, "ripplenet_info": [ { … } ], "execution_condition": "PrefixSha256Condition{subtypes=[ED25519-SHA-256], type=PREFIX-SHA-256, fingerprint=sfGGHCrkyaMsLQNB62w_4zarlPChHKm47JkXVQbs1z0, cost=132360}", "crypto_transaction_id": "4e05da26-7872-4a1f-b9b7-db7604757c37", "validator": "rn.us.ca.san_francisco", "payment_type": "REGULAR", "returns_payment_with_id": "a69b322f-faa4-4531-bcff-897e5839c130", "returned_by_payment_with_id": "c929a87b-81b8-4878-b21c-1aeaa4fe9276", "execution_results": [ { … } ], "liquidation_execution_results": [ { … } ], "liquidation_details": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "string", "failure_reason": "string", "failure_count": 0 }, "push_forward_execution_results": [ { … } ], "accepted_at": "2019-10-01T18:25:47.347Z", "locked_at": "2019-10-01T18:25:47.347Z", "executed_at": "2019-10-01T18:25:47.347Z", "completed_at": "2019-10-01T18:25:47.347Z", "returned_at": "2019-10-01T18:25:47.347Z", "internal_info": { "connector_role": "RECEIVING", "labels": [ … ], "internal_id": "string" }, "user_info": [ { … } ] }
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/info
https://[domainPrefix].ripplexcurrent.com/v4/v4/orchestration/info
curl -i -X GET \
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/info \
-H 'Authorization: YOUR_API_KEY_HERE'{ "name": "Integration Module", "version": "1.2.0" }