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
Currently every merchant has a default fallback which is a list of all of their configured connectors. We now want to make this profile-specific, i.e. each profile will have an associated default fallback that is a list of all the connectors associated with that profile.
This issue also entails development of Read/Write APIs for profile specific default fallbacks, and integration with the payments core.
Further on , we can also later on add the mca_id as many connectors with the same name can be there under a single profile_id
Possible Implementation
In interest of backwards compatibility, create two separate default fallback APIs for profiles (Read & Write). Additionally, implement profile-specific fallback usage in payments core routing with a feature flag.
Have you spent some time checking if this feature request has been raised before?
Feature Description
Currently every merchant has a default fallback which is a list of all of their configured connectors. We now want to make this profile-specific, i.e. each profile will have an associated default fallback that is a list of all the connectors associated with that profile.
This issue also entails development of Read/Write APIs for profile specific default fallbacks, and integration with the payments core.
Further on , we can also later on add the
mca_id
as many connectors with the same name can be there under a singleprofile_id
Possible Implementation
In interest of backwards compatibility, create two separate default fallback APIs for profiles (Read & Write). Additionally, implement profile-specific fallback usage in payments core routing with a feature flag.
Have you spent some time checking if this feature request has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
No, but I'm happy to collaborate on a PR with someone else
The text was updated successfully, but these errors were encountered: