PipedreamHQ / PipedreamHQ/pipedream
[Components] razorpay
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 101
Description
# razorpay
## URLs
- https://razorpay.com/docs/api/
- https://razorpay.com/docs/api/authentication
- https://razorpay.com/docs/api/sandbox-setup
- https://razorpay.com/docs/api/payments/
- https://razorpay.com/docs/api/partners/webhooks/create/
- https://razorpay.com/docs/api/partners/webhooks/delete
## Polling Sources
### new-invoice-paid
#### Prompt
Emit new event when an invoice is fully paid
#### URLs
- https://razorpay.com/docs/api/payments/invoices/fetch-all/
### new-order-created
#### Prompt
Emit new event when a new order is created
#### URLs
- https://razorpay.com/docs/api/orders/fetch-all
## Webhook Sources
### new-payment-captured-instant
#### Prompt
Emit new event when a payment is successfully captured
#### URLs
- https://razorpay.com/docs/api/payments/fetch-all-payments
Contributor guide
Research direction
Start with the linked Razorpay API documentation, especially authentication, sandbox setup, invoices, orders, payments, and webhooks. Confirm how the three named sources should work and what event payloads the API supports; done means the invoice-paid, order-created, and payment-captured events emit with the documented data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100