razorpay / razorpay/razorpay-node
The requested URL was not found on the server while creating Qr code.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 243
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce the behavior
- Create qrcode with instance await instance.qrCode.create
- getting 400 status code
Expected behavior
{
"id": "qr_HMsVL8HOpbMcjU",
"entity": "qr_code",
"created_at": 1623660301,
"name": "Store_1",
"usage": "single_use",
"type": "upi_qr",
"image_url": "https://rzp.io/i/BWcUVrLp",
"payment_amount": 75000,
"status": "active",
"description": Descp",
"fixed_amount": true,
"payments_amount_received": 0,
"payments_count_received": 0,
"notes": {
"purpose": "Test"
},
"close_by": 1681615838,
"closed_at": 1623660445,
"close_reason": "on_demand"
}
Actual behavior
Error generating QR code: {
statusCode: 400,
error: {
code: 'BAD_REQUEST_ERROR',
description: 'The requested URL was not found on the server.',
source: 'NA',
step: 'NA',
reason: 'NA',
metadata: {}
}
}
Code snippets
const qrCodeDetails = {
type: "upi_qr",
name: "Name",
usage: "single_use",
fixed_amount: true,
payment_amount: 75000,
description: "Descp",
close_by: Math.floor(Date.now() / 1000) + 600,
notes: {
purpose: "Test",
},
};
const qrCode = await instance.qrCode.create(qrCodeDetails);
Node version
20
Library version
v2.9.4
Additional Information
Trying to create qr code but its giving 400 error
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the instance.qrCode.create entry point in the v2.9.4 Node.js library and trace the request made for the supplied QR-code parameters. Reproduce the 400 response, then compare the requested route and payload with the expected QR-code response; done means the supplied call succeeds and returns the documented response shape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100