Add a payment type/use case to incoming payments #375
adrianhopebailie
started this conversation in
Ideas
Replies: 3 comments
-
The ISO20022 data dictionary defines a code list which we could use here 😬
|
Beta Was this translation helpful? Give feedback.
0 replies
-
As long as we make this new property optional, I think I'm happy with it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Is the second column also standardized and stable? If so, could we use that? Abbreviations are awful and have no place in modern data formats unless necessary for performance reasons which this clearly wouldn't be. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be very useful to the ASE hosting the incoming payment resource to know the purpose of the incoming payment. For example, is this a web monetisation payment or a P2P remittance or an ecommerce payment.
This helps the ASE decide what payment methods to present. E.g. For Web Monetization always present an ILP connection, for P2P remittance some other method may be more appropriate.
This also has some implications for compliance as often an account may only be permitted to be party to specific use cases or the data required for compliance is different.
Beta Was this translation helpful? Give feedback.
All reactions