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
editorial: Clarify wording to not imply 'pull' only payments #474
Conversation
Some minor wording changes to make it clear that a paymentrequest may actually process a transaction rather than just supply credentials
by the merchant to process the transaction and determine successful | ||
fund transfer. This data is returned by the <a>payment method</a> | ||
by the merchant to process the transaction or validate the transaction | ||
has been processed. This data is returned by the <a>payment method</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please rewrite this to use active voice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposed:
An object that provides information enabling the merchant to process or validate a transaction (depending on the payment method).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this is editorial, I'm approving in the interest of moving this forward.
@mattsaxon could you please rebase this? |
this part of the spec already changed. Please send a new PR if you think it's still not clear. |
#474 (comment) in light of other changes to the specification.
New pull request: |
Some minor wording changes to make it clear that a paymentrequest may
actually process a transaction rather than just supply credentials
Preview | Diff