Merchant Configuration cannot be null.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing ExternalConfiguration.php and the Microform v2 upgrade changes referenced in the issue, then reproduce the "Merchant Configuration cannot be null" error with the listed sandbox credentials. Done means identifying which configuration value or initialization step is missing and confirming that the page loads successfully.
Written by the indexing model from the issue text.
Description
We are currently in the process of upgrading our Microform implementation from version 0.11 to version 2.0. As part of this upgrade, we have updated our codebase in alignment with the recent commits labeled "Modified Flex products", as referenced in the following screenshot:
🔗 https://prnt.sc/XR0Na8G41pig
Additionally, we have updated the ExternalConfiguration.php file with our sandbox credentials (merchantID, apiKeyID, and secretKey), as shown here:
🔗 https://prnt.sc/ODUWEA_qeDyh
However, when attempting to load the page, we encounter the following error:
"Merchant Configuration cannot be null."
Query:
In ExternalConfiguration.php, we have provided values for:
- merchantID
- apiKeyID
- secretKey
Could you please confirm if additional parameters (such as keyAlias, keyPass, authenticationType) are required for the configuration to function properly with Microform v2?
We would greatly appreciate your guidance on how to properly debug this issue and proceed with the configuration. Please let us know if any further details or logs are required from our end.
Looking forward to your support.
Thanks in Advance!
- Dominant language
- PHP
- Stars
- 5
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CyberSource/cybersource-flex-samples-php
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
CyberSource/cybersource-flex-samples-php#13 · 2 comments ·
-
Invalid merchant IDOpen
Difficulty 4/5 3-5 days Newbie friendliness 15/100
CyberSource/cybersource-flex-samples-php#9 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
CyberSource/cybersource-flex-samples-php#5 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
CyberSource/cybersource-flex-samples-php#4 · 3 comments ·
All issues in CyberSource/cybersource-flex-samples-php
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
domain/crm-after-sales Platform(Default) priority/high
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kind/bug status/to verify
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PHP-CS-Fixer/PHP-CS-Fixer#9867 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 2 days
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days