razorpay / razorpay/razorpay-node

Issues with API call to charge customer on recurring payment

Open
#447 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
243
Forks
129
PR merge metrics
No merged PRs in 30d

Description

Hello everyone, any one facing issues with following api ?
curl --request POST
--url https://api.razorpay.com/v1/payments/create/recurring
--header 'Authorization: Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
--header 'Content-Type: application/json'
--header 'User-Agent: insomnia/11.0.2'
--data '{
"email": "xxxxxxxxxxxxxxx",
"contact": "xxxxxxxxxxxxx",
"amount": 300000,
"currency": "INR",
"order_id": "xxxxxxxxxxxxxxxx",
"customer_id": "xxxxxxxxxxxxxxxxxx",
"token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"recurring": "1",
"description": "Creating recurring payment for Gaurav Kumar",
"notes": {
"note_key 1": "Beam me up Scotty",
"note_key 2": "Tea. Earl Gray. Hot."
}
}'

I am getting error

{
"error": {
"code": "BAD_REQUEST_ERROR",
"description": "The requested URL was not found on the server.",

"source": "internal",
"step": "NA",
"reason": "NA",
"metadata": {}
}
}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names only the POST endpoint https://api.razorpay.com/v1/payments/create/recurring and its error response; no repository file or test is provided. Start by verifying the endpoint and request format against the project's API documentation. Done means establishing whether the URL is supported and identifying the corrected request or repository change needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
api, payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.