Skip to content

Commit

Permalink
Rename field
Browse files Browse the repository at this point in the history
  • Loading branch information
Ifropc committed May 8, 2024
1 parent 72a5e7b commit abe416f
Show file tree
Hide file tree
Showing 2 changed files with 28 additions and 28 deletions.
4 changes: 2 additions & 2 deletions ecosystem/sep-0006.md
Original file line number Diff line number Diff line change
Expand Up @@ -1426,7 +1426,7 @@ Each object in the `transactions` array should have the following fields:
| `started_at` | UTC ISO 8601 string | (optional) Start date and time of transaction. |
| `updated_at` | UTC ISO 8601 string | (optional) The date and time of transaction reaching the current status. |
| `completed_at` | UTC ISO 8601 string | (optional) Completion date and time of transaction. |
| `action_required_by` | UTC ISO 8601 string | (optional) The date and time by when the user action is required. In certain statuses, such as `pending_user_transfer_start` or `incomplete`, anchor waits for the user action and `action_required_by` field should be used to show the time anchors gives for the user to make an action before transaction will automatically be moved into a different status (such as `expired` or to be `refunded`). `action_required_by` should only be specified for statuses where user action is required, and omitted for all other. Anchor should specify the action waited on using message or `more_info_url`. |
| `user_action_required_by` | UTC ISO 8601 string | (optional) The date and time by when the user action is required. In certain statuses, such as `pending_user_transfer_start` or `incomplete`, anchor waits for the user action and `user_action_required_by` field should be used to show the time anchors gives for the user to make an action before transaction will automatically be moved into a different status (such as `expired` or to be `refunded`). `user_action_required_by` should only be specified for statuses where user action is required, and omitted for all other. Anchor should specify the action waited on using message or `more_info_url`. |
| `stellar_transaction_id` | string | (optional) transaction_id on Stellar network of the transfer that either completed the deposit or started the withdrawal. |
| `external_transaction_id` | string | (optional) ID of transaction on external network that either started the deposit or completed the withdrawal. |
| `message` | string | (optional) Human readable explanation of transaction status, if needed. |
Expand Down Expand Up @@ -1789,7 +1789,7 @@ object containing an error message.

## Changelog

- `v4.1.0` Add `action_required_by` field to transaction responses and add new `on_hold` status
- `v4.1.0` Add `user_action_required_by` field to transaction responses and add new `on_hold` status
([#1484](https://github.com/stellar/stellar-protocol/pull/1484/))
- `v4.0.0`: Update flow to delegate getting KYC fields to SEP-12
([#1432](https://github.com/stellar/stellar-protocol/pull/1431))
Expand Down
Loading

0 comments on commit abe416f

Please sign in to comment.