Razorpay Integration

Site Operators Site Operations Help
,
1

I was trying to integrate Razorpay Into openedx platform. Is this is the directory i should keep. Any inputs ?

razorpay/
├── setup.py
├── tutorrazorpay/
│ ├── init.py
│ └── plugin.py
├── build/
│ └── ecommerce/
│ └── razorpay_processor/
│ ├── init.py
│ ├── apps.py
│ ├── processor.py
│ ├── urls.py
│ └── views.py
└── templates/
└── ecommerce/
└── build/
└── ecommerce/
└── razorpay_processor/
└── templates/
└── razorpay/
├── checkout.html
├── cancel.html
└── error.html

This is for payment integration!

1 Like
2

For Open edX payment integration, this structure is partially correct, but it looks a bit mixed between Tutor plugin files, ecommerce Django app, and templates.

A few suggestions:

  • tutorrazorpay/ should only contain Tutor plugin logic (plugin.py, settings, hooks). The actual payment processor code usually shouldn’t live there.

  • The Razorpay payment processor should ideally be a proper Django app under ecommerce* , similar to existing processors:

    ecommerce/extensions/payment/processors/razorpay/

    with apps.py, processor.py, urls.py, and views.py.

  • The build/ directory generally shouldn’t be committed or manually structured like this—it’s normally generated during packaging.

  • Templates can be simplified and placed under:

    templates/ecommerce/razorpay/

    so Django’s template loader can find them cleanly.

If you follow the structure of existing ecommerce payment processors (like PayPal or CyberSource), it becomes much easier to register Razorpay in PAYMENT_PROCESSORS and wire it into ecommerce correctly.

Hope this helps — happy to clarify further if needed.