You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.
Considering how difficult it is to present what payment information is needed just by using the plaintext instruction in PaymentInstruction, we should commit to using links whenever OrderInstructions is a non-empty object. Doing so would mean that PFIs are responsible for creating payment widgets that can launched as web views by client applications. This allows PFIs to have full control over exactly how they collect payment details and prevents client applications from having to support a vague, general order instruction. This approach mirrors the known-customer-credential spec regarding web view use.
The text was updated successfully, but these errors were encountered:
Considering how difficult it is to present what payment information is needed just by using the plaintext
instruction
in PaymentInstruction, we should commit to using links wheneverOrderInstructions
is a non-empty object. Doing so would mean that PFIs are responsible for creating payment widgets that can launched as web views by client applications. This allows PFIs to have full control over exactly how they collect payment details and prevents client applications from having to support a vague, general order instruction. This approach mirrors the known-customer-credential spec regarding web view use.The text was updated successfully, but these errors were encountered: