Tax Genius · India
B2B Application Lifecycle & Status
Understand application creation, payment, queued processing, completion, rejection and acknowledgement retrieval.
Application lifecycle and status
Track an application from its initial request to settlement, auditor review and issuance of an acknowledgement.
Create and retain identifiers
After a B2B application POST, persist tracking_id and external_correlation_id in the partner server. Do not derive a tracking identifier from a customer-facing route.
Settlement branch
- RAZORPAY_CHECKOUT — use the returned signed checkout URL when present.
- CUSTOM_DIRECT — processing is controlled by the approved wholesale arrangement; no hosted checkout URL is returned.
- Reconcile payments before declaring fulfilment started.
Documented states
- pending — newly registered, potentially awaiting payment or documents.
- under_process / queued — awaiting or undergoing processing and review.
- processed / completed — the guide describes a completed filing with acknowledgement availability.
- rejected — case flagged for discrepancies; inspect authorised error_message.
Completion, receipt and exception handling
Use verified webhook events and status reads to update your internal case. Check the response for acknowledgment_url after a processed outcome and authorise receipt retrieval.
The guide does not define every transition, processing SLA or guaranteed receipt delivery time.