Getting error when integrating RAZORPAY in medusa app

[Fox333-Lab]

Hi,
Tried integrating RAZORPAY in medusa application using the following guide:
https://medusajs.com/integrations/medusa-plugin-razorpay-v2/

but i am getting the below error when running the medusa application using command "yarn dev"

below is my content in medusa.config.ts:

module.exports = defineConfig({
projectConfig: {
databaseUrl: process.env.DATABASE_URL,
http: {
storeCors: process.env.STORE_CORS!,
adminCors: process.env.ADMIN_CORS!,
authCors: process.env.AUTH_CORS!,
jwtSecret: process.env.JWT_SECRET || "supersecret",
cookieSecret: process.env.COOKIE_SECRET || "supersecret",
},
},
plugins: ["medusa-plugin-razorpay-v2"],
modules: [
{
resolve: "@medusajs/medusa/payment",
options: {
dependencies: [
Modules.CUSTOMER,
Modules.ORDER,
Modules.PAYMENT,
Modules.CART,
ContainerRegistrationKeys.MANAGER,
ContainerRegistrationKeys.LOGGER,
Modules.LINK,
ContainerRegistrationKeys.LINK,
ContainerRegistrationKeys.QUERY,
ContainerRegistrationKeys.PG_CONNECTION,
],
providers: [
{
resolve: "medusa-plugin-razorpay-v2/providers/payment-razorpay/src",
id: "razorpay",
options: {
key_id:
process?.env?.RAZORPAY_TEST_KEY_ID ?? process?.env?.RAZORPAY_ID,
key_secret:
process?.env?.RAZORPAY_TEST_KEY_SECRET ??
process?.env?.RAZORPAY_SECRET,
razorpay_account:
process?.env?.RAZORPAY_TEST_ACCOUNT ??
process?.env?.RAZORPAY_ACCOUNT,
automatic_expiry_period: 30 /* any value between 12minuts and 30 days expressed in minutes */,
manual_expiry_period: 20,
refund_speed: "normal",
webhook_secret:
process?.env?.RAZORPAY_TEST_WEBHOOK_SECRET ??
process?.env?.RAZORPAY_WEBHOOK_SECRET,
},
},
],
},
},
],
});

medusa app version i am using is : 2.7.1

please help i need it urgently, any suggestions anybody.

Thanks in advance.

[vinodkumar-github]

The log indicates that the plugin couldn’t be resolved, so it’s likely an issue with the path resolution.

The current path is declared as:

resolve: "medusa-plugin-razorpay-v2/providers/payment-razorpay/src",
id: "razorpay",
...

That might be the root cause. NPM packages are typically installed using the format:

npm install [<@scope>/]<name>

Possible Solution

Based on this plugin’s file structure, try updating the resolve path to:

resolve: "@sgftech/payment-razorpay",

Let me know if that works!

[Fox333-Lab]

@vinodkumar-github its still throwing he same error when trying to run the application.

I have modified the config below as you suggested:

[vinodkumar-github]

@Fox333-Lab

Can you give latest logs.

this is my medusa-config.js which didnt give that issue.

ensure imports are correct too. double check that you import statement has "Modules" too.

Let me know if that worked

import {loadEnv, defineConfig, Modules, ContainerRegistrationKeys} from '@medusajs/framework/utils'

loadEnv(process.env.NODE_ENV || 'development', process.cwd())

module.exports = defineConfig({
  projectConfig: {
    databaseUrl: process.env.DATABASE_URL,
    http: {
      storeCors: process.env.STORE_CORS!,
      adminCors: process.env.ADMIN_CORS!,
      authCors: process.env.AUTH_CORS!,
      jwtSecret: process.env.JWT_SECRET || "supersecret",
      cookieSecret: process.env.COOKIE_SECRET || "supersecret",
    }
  },
  modules: [
    {      resolve: "@medusajs/medusa/payment",
      options: {
        dependencies: [
          Modules.CUSTOMER,
          Modules.ORDER,
          Modules.PAYMENT,
          Modules.CART,
          ContainerRegistrationKeys.MANAGER,
          ContainerRegistrationKeys.LOGGER,
          Modules.LINK,
          ContainerRegistrationKeys.LINK,
          ContainerRegistrationKeys.QUERY,
          ContainerRegistrationKeys.PG_CONNECTION
        ], providers: [{
          resolve:    "@sgftech/payment-razorpay",
          id: "razorpay",
          options: {
            key_id:
                process?.env?.RAZORPAY_TEST_KEY_ID ??
                process?.env?.RAZORPAY_ID,
            key_secret:
                process?.env?.RAZORPAY_TEST_KEY_SECRET ??
                process?.env?.RAZORPAY_SECRET,
            razorpay_account:
                process?.env?.RAZORPAY_TEST_ACCOUNT ??
                process?.env?.RAZORPAY_ACCOUNT,
            automatic_expiry_period: 30 /* any value between 12minuts and 30 days expressed in minutes*/,
            manual_expiry_period: 20,
            refund_speed: "normal",
            webhook_secret:
                process?.env?.RAZORPAY_TEST_WEBHOOK_SECRET ??
                process?.env?.RAZORPAY_WEBHOOK_SECRET
          }
        },    ],
      } },
 

  ],
})

[Fox333-Lab]

hi @vinodkumar-github,

thank you for your config that helped me resolve the issue
all the imports were present what was causing the issue was the below highlighted line which i commented and the medusa app started running again.

i am not sure why is this an issue as i had followed everything according to the official documentation of SGFGOV.

Anyways thank you very much @vinodkumar-github for your help.
Also are you aware of any repo which has implemented razorpay successfully in medusa v2, if yes please share the link it would be of great help.....Thank you

[vinodkumar-github]

@Fox333-Lab

Glad to hear it's resolved.

Medusa has undergone significant changes; what worked in v1 often doesn't in v2, and v3 is on the horizon. documentation of SGFGOV was originally for v1 but made minimal changes for v2. The line you commented (resolve path and plugin reference) are artifacts of that. We must implement with diligence as docs too can be wrong - especially for something that's still maturing like medusa.

Razorpay's APIs are known for their strong transactional focus, often at the expense of flexibility and developer experience. This plugin, in particular, required numerous workarounds, even resorting to raw database queries, to ensure Razorpay support. I'm also looking for a good reference on how to integrate the Razorpay SDK with Medusa's expected standards for a custom payment provider.

While Medusa's plugin architecture allows for flexible implementation, directly using a full repository for integration (as thats what you asked- a ready made Payment Provider Integrated & Production ready backed- rather than how to use this plugin) can introduce challenges. We might not know the full extent of what was integrated or modified, and subsequent updates could lead to issues if not handled with extreme care.

Speaking of alternatives, you might want to check out the Juspay website. They held a hackathon specifically for Medusa plugins and ultimately provided a complete Medusa repository with Juspay implemented.

[vinodkumar-github]

If using Razorpay is a must-have, I think the best path forward is for a few of us to team up. We could focus on streamlining the existing plugin to get it fully functional, and then submit a pull request to the repository owner. Trying to build something from scratch would be more effective but much tougher (need to pool more willing members) for now..

[SGFGOV]

So the upgrade does away with all the raw database queries, and is more medusafied. Try it and let me know :)

[vinodkumar-github]

Yes @SGFGOV .

First of all, thank you for the incredible dedication you've shown in enriching Medusa.

I’ve been quietly following your commits (barring the last few days), and finally had the chance to sit down with the latest updates — and I’m genuinely impressed.

I also want to clarify something I should have said earlier. When I previously raised concerns about raw queries or suggested a rewrite path, it wasn’t a critique of your work. It came from frustration with how Razorpay’s ecosystem compares to global providers in terms of DX and integration ease.

It truly feels Medusafied now. I particularly appreciated your approach to customer logic and metadata — it’s clear you’ve thought about this beyond just happy paths.

Here are a few areas we could continue improving together:

• Config clarity: Right now, developers must juggle several .env entries — razorpay_account, refund speed, expiry periods, etc. A bit more README context (like why Razorpay mandates these) or even optional fallbacks(refund speed, expiry periods) could help smooth the onboarding process.
• Plugin ergonomics: Some fields like automatic_expiry_period and manual_expiry_period might be better handled internally as optional plugin defaults, rather than being exposed in medusa-config.ts, which is ideally for module-level setup, not detailed Razorpay logic.
• Docs and onboarding: A few inline tips, testing instructions, or common gotchas would be really helpful for first-time users or contributors trying to onboard faster.

I will make a PR with few more changes after through testing.

Thanks again — looking forward to what comes next!

– vinodkumar

[SGFGOV]

@vinodkumar-github thank you for your encouraging comments..Happy to accept PRs..or you will need to wait till I find time :)

[vinodkumar-github]

Totally understand, @SGFGOV — your pace so far has already been impressive considering you’re juggling code, tests, docs, and support!

I’ll carve out some time soon to clean up the artefacts, enhance docs and send a small PR after testing. Will try to keep it minimal and scoped (identifier + a few validateOptions fixes), so it’s easy to review and doesn’t interfere with your roadmap.

Thanks again for being so open to collaboration — and for setting a solid foundation for Razorpay support in Medusa 🙌