razorpay / razorpay/razorpay-java
Payout Status Remains "Processing" in Test Mode Using /v1/payouts API
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 74
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
Hello Razorpay Community,
I've been integrating Razorpay's payouts API (https://api.razorpay.com/v1/payouts) into our system and conducting tests in the test environment. After initiating a payout successfully, I've noticed that the payout status is consistently marked as "Processing" and does not change to "Processed."
Here's a brief overview of the steps I've followed:
- Used the /v1/payouts endpoint to create a payout.
- The request is successful, and the payout is created with a status of "Processing."
- However, even after waiting, the status does not update to "Processed."
I understand that this is the test environment, and actual fund transfers aren't taking place. My questions are: - Is it expected behavior in the test environment for the payout status to remain "Processing" without changing to "Processed"?
- Are there any steps I can take to simulate the status change to "Processed" for testing purposes?
- Does Razorpay provide any mechanism or endpoint in the test mode to manually update or simulate different payout statuses?
We are currently not testing in live mode and want to ensure our integration handles all potential statuses correctly. Any guidance or insights on this matter would be greatly appreciated.
Thank you for your assistance.
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 with the /v1/payouts endpoint and the test-environment behavior described in the issue. Check Razorpay's payout documentation for documented status transitions and test simulation options; done means confirming whether Processing is expected and identifying any supported way to exercise other statuses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, payments
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100