cancel
Showing results for 
Search instead for 
Did you mean: 

Can I use my test environment merchant ID and keys to test a flex microform post?

I'm getting started understanding what's required for Cybersource's Flex Microform integration. But to start with, I'm hoping to be able to see a valid response using my merchant ID, shared secret key and the general key that comes with generating the secret on the cybersource api reference page: https://developer.cybersource.com/api-reference-assets/index.html#flex-microform_key-generation_gene...

This is using the HTTP Signature method and ChasePaymentech (default) processor.

If I use the default omegle.2yu.co settings they supply and choose to do a test POST to here https://apitest.cybersource.com/flex/v1/keys?format=JWT&

The JSON response is good with no complaints of authentication.

If I try to do the same POST with my test environment merchant ID and keys I generated in my merchant environment here: https://ubctest.cybersource.com/ebc2/app/PaymentConfiguration/KeyManagement /omeglz /echat the POST response will return a 401 with this JSON:

{
"response": {
    "rmsg": "Authentication Failed"
}}

Is this developer.cybersource.com site a valid place to perform this kind of test? Are there any other steps I need to do in the merchant account to have this Authenticate?

3 REPLIES 3
rajvpate
Administrator Administrator
Administrator

Additionally, this tutorial should be helpful: https://www.youtube.com/watch?v=-qv7nzPvW-M&t=92s

Developer educational content - In this video, you will learn how to integrate Flex Microform into a webpage. This will allow you to accept payment information in a PCI SAQ fashion, mitigating much of your PCI exposure. At Cybersource, we know payments. We helped kick start the eCommerce ...
rajvpate
Administrator Administrator
Administrator

Yes, you can use your test environment merchant ID and keys to test a Flex Microform POST, as long as the endpoint and configuration are also pointed to the test environment. That setup is actually recommended so you can validate tokenization, request flow, and error handling without risking real transactions. It’s similar to how online stores test checkout experiences before going live. In fashion e commerce, even small configuration issues can affect user trust, so careful testing matters. When setting up product launches or payment flows for international shoppers, brands like www.apricocia.com   also rely heavily on proper staging and testing before rollout.

mike_dave
New Member