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
PROD mid access (via access code) and API key generation in dev studio
Solution
Requirement:
Developer shall be allowed to key in and verify the access code received for prod MIDs
Developer shall be allowed to create API key for single/multiple prod MIDs
Developer shall be allowed to clone prod mid to sandbox mid.
This sandbox mid will be created under same client id (in lower environment)
Developer shall be able to see the prod MID config using "view" option (read only mode)
Developer shall not be allowed to generate prod API keys for prod MIDs unless it has gone through successful certification for respective client and developer.
Having said that, dev studio needs to provision an option for Fiserv certification team (Ramon’s team) to enable prod API key generation option at a developer and client ID level.
Once prod API key option is generated, dev studio to ensure that developer can generate prod API keys for the MIDs configured under respective client ID (enabled by Ramon’s team) only.
For Example :
THDPROD and THDSTAGE is client id in prod and stage region respectively.
Developer is provided with an access code for sharing THDPRODMID1, THDPRODMID2 from prod region.
Post successful verification of access code developer can see THDPRODMID1, THDPRODMID2 in dev studio.
If developer is cloning THDPRODMID1 to THDSANDBOXMID1 (new mid) then
THDSANDBOXMID1 shall get created under THDSTAGE
Alternatives
N/A
Additional Context
Scenarios:
Below are the scenarios covered for more understanding. As per current approach,
As soon as a contract is in place and either an E2E or Prod MID is created, merchant admin can provide access of these MIDs to developer using access code functionality.
Once developer gets an access to E2E or Prod MID, developer is allowed to generate API keys (E2E / Prod) against it and start using it.
Currently, we don’t have any mechanism in place to certify merchant automatically, we need to make sure that developer is not allowed to generate API keys for prod MIDs.
To ensure same, dev studio needs to support an intermediatory solution using which certification team can enable option of generating prod API keys in dev studio.
Update 03/27 -
Update with reference to quick chat (teams) with MP team. Marketplace is already supporting below functionality,
Send access code for prod MIDs
Create a sandbox mid by cloning prod mid
Dev Studio needs to ensure this functionality in QA stage.
Region
Commerce Hub
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
https://jira.onefiserv.net/browse/CHF-1192
Context
PROD mid access (via access code) and API key generation in dev studio
Solution
Requirement:
For Example :
THDSANDBOXMID1 shall get created under THDSTAGE
Alternatives
N/A
Additional Context
Scenarios:
Below are the scenarios covered for more understanding. As per current approach,
Update 03/27 -
Update with reference to quick chat (teams) with MP team. Marketplace is already supporting below functionality,
Send access code for prod MIDs
Create a sandbox mid by cloning prod mid
Dev Studio needs to ensure this functionality in QA stage.
Region
Commerce Hub
The text was updated successfully, but these errors were encountered: