The India ACH (Automated Clearing House) Payments API allows businesses to efficiently initiate and manage domestic payments within India. Designed for handling bulk and low-value transactions, this API is suitable for payroll, vendor payments, recurring transactions, and other financial operations requiring automated processing.

Capabilities

  • Payment Initiation: Submit ACH payment requests to facilitate the transfer of funds between bank accounts within India.
  • Bulk Processing: Supports batch payments, enabling the submission of multiple transactions in a single request for efficient processing.
  • Status Tracking: Monitor the status of submitted payments to ensure successful processing and manage exceptions.
  • Secure and Compliant: Transactions are securely processed with encryption and comply with Indian regulatory requirements, including NPCI (National Payments Corporation of India) standards.

Technical Requirements

  • Authentication: Utilize OAuth 2.0 with the Client Credential Grant flow for secure access. Obtain a bearer token from the /v1.0/auth endpoint and include it in the authorisation header as Bearer <access_token>.
  • API Endpoint: ACH payment requests are sent to the /payment/in/v1.0/ach endpoint.
  • Headers: Ensure headers like Content-Type: application/json and authorisation: Bearer <access_token> are included in your requests.
  • Payload Format: Payments should be submitted in JSON format, conforming to the ACH payment schema provided in the API documentation.

Key Features for Developers

  • Automated Bulk Payments: Streamline bulk payment operations such as payroll, utility payments, or supplier payouts with automation, reducing manual effort and errors.
  • Batch Processing: Efficiently manage high volumes of transactions through batch processing, improving system performance and reducing transaction times.
  • Real-Time Monitoring: Access real-time updates on the status of each payment, providing transparency and enabling quick resolution of issues.
  • Detailed Error Responses: Receive comprehensive error codes and messages to help diagnose and resolve issues quickly during integration.

Example Workflow

sequenceDiagram participant Client participant Fileactive Client->>Fileactive: POST /v1.0/auth (Obtain Bearer Token) Fileactive-->>Client: 200 OK (Bearer Token) Client->>Fileactive: POST /payment/in/v1.0/ach (Submit ACH Payment) Fileactive-->>Client: 202 Accepted (Payment Processing) Client->>Fileactive: GET /payment/in/v1.0/ach/{paymentId} (Check Payment Status) alt Payment Completed Fileactive-->>Client: 200 OK (Payment Success) else Payment Pending Fileactive-->>Client: 202 Accepted (Payment Pending) else Payment Failed Fileactive-->>Client: 400 Bad Request (Payment Failed) end