-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat(user-action-details): add AccountNumberUserAction #102
feat(user-action-details): add AccountNumberUserAction #102
Conversation
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.
Optional comment, but A'ing since it's not blocking imo
fiatconnect-api.md
Outdated
institutionName: `string`, | ||
accountName: `string`, | ||
accountNumber: `string`, | ||
transactionReference: `string`, |
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 this be made optional for providers that don't require this? I imagine many providers will be able to cross reference the account the payment is from with the one on file. You can add the provision that if it's present, it MUST be included in the actual transfer itself.
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.
sounds reasonable. updated
…userActionDetailsSchema and type (#204) added to spec [here](fiatconnect/specification#102)
We've seen FiatConnect providers use the URLUserActionDetails schema and direct users to their own website just to explain to them that they need to send funds to the same CICO provider's bank account. This defies the intention of the UserActionDetails feature, which is supposed to give FiatConnect clients a chance to explain to users what steps are needed to complete a transfer in-- not just hand them off to complete arbitrary steps on some other website. This PR adds a UserActionDetails schema that should bridge the gap, allowing CICO providers to solicit a bank transfer from end-users without redirecting them to another website.