Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEP-6 + SEP-31: clarify that before sending the payment, the sending party should make a GET request to retrieve the expected amount_in #1203

Merged
merged 5 commits into from
May 16, 2022

Conversation

marcelosalloum
Copy link
Contributor

What

Clarify that before sending the payment, the sending party should make a GET request to retrieve the expected amount_in.

Also added a few polishes to the text.

Why

Some anchors could use additive fees in the transactions, which would make the amount proposed by the Wallet diverge from the one approved by the Anchor.

…reach the `GET /transactions/:id` endpoint to get the payment information before sending the payment to the Receiving Anchor.
…GET /transaction?id={id}` endpoint to get the payment `amount_in` before making the payment.
@marcelosalloum marcelosalloum self-assigned this May 13, 2022
@marcelosalloum marcelosalloum marked this pull request as ready for review May 13, 2022 21:54
JakeUrban
JakeUrban previously approved these changes May 13, 2022
Copy link
Contributor

@JakeUrban JakeUrban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with the suggestion

ecosystem/sep-0006.md Outdated Show resolved Hide resolved
@marcelosalloum marcelosalloum requested a review from JakeUrban May 16, 2022 16:45
Copy link
Contributor

@JakeUrban JakeUrban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants