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
During wallet address creation, we want to let the ASE allow to add additional properties to be associated with the wallet address.
We need to update the createWalletAddress mutation input to take in additionalProperties.
These properties would be optionally visible when requesting a wallet address through Open Payments. The input is an optional array of objects with key & value and visibleInOpenPayments (suggested name), a flag that enables or disables this field from appearing in Open Payments Wallet Address lookup.
Tasks
Update createWalletAddress mutation input
Store these fields in a new table with structure: walletAddressId: FKfieldKey: stringfieldValue: stringvisibleInOpenPayments: bool, createdAt: Date, updatedAt: Date)
Expose these new fields when fetching wallet address via Open Payments (making sure to show only fields that are indeed enabled for visibility for Open Payments)
Expose these new fields when fetching wallet address via the Admin API
Context
During wallet address creation, we want to let the ASE allow to add additional properties to be associated with the wallet address.
We need to update the
createWalletAddress
mutation input to take in additionalProperties.These properties would be optionally visible when requesting a wallet address through Open Payments. The input is an optional array of objects with
key
&value
andvisibleInOpenPayments
(suggested name), a flag that enables or disables this field from appearing in Open Payments Wallet Address lookup.Tasks
createWalletAddress
mutation inputwalletAddressId: FK
fieldKey: string
fieldValue: string
visibleInOpenPayments: bool
,createdAt: Date
,updatedAt: Date
)PR
#2752
The text was updated successfully, but these errors were encountered: