Create Recipient (ACH)

Overview

This endpoint allows entities to create a new ACH recipient, which can later be used only for ACH-related operations (e.g., ACH dispersions). Recipients created under this endpoint cannot be used for Bre-B payments, QR flows, or any other product.

The recipient can represent either a BUSINESS or an INDIVIDUAL, and must include the identification and account information required for ACH transfers.

Endpoint Details

Definition	Description
Endpoint	https://api.paas.sandbox.co.passportfintech.com/v1/recipients/ach
Method	POST
Headers	Content-Type: application/json, Authorization
Authentication	Access Token (Bearer Token)

Request Body

Parameter	Type	Required	Constraints	Description
customer_id	String	Yes	N/A	The unique identifier of the entity customer creating the recipient.
alias	String	No	[0-128]	Friendly name or label for the ACH recipient (e.g., `Pepito SAS5`)
recipient_type	String	Yes	`INDIVIDUAL` OR `BUSINESS`	Allowed values: `BUSINESS`, `INDIVIDUAL`.
identification_type	String	Yes	`CC`, `CE`, `NUIP`, `PPT`, `PEP`, `NIT`, `PAS`, `TDI`	Identification type (e.g., `NIT`). Cédula de Ciudadania: CC Foreign Card: CE Número Único de Identificación Persona: NUIP Temporary Protection Permit: PPT Special Permanence Permit: PEP Número de Identificación Tributaria: NIT Passport: PAS Id Card: TDI
identification_number	String	Yes	[1,30]	The recipient's identification number.
account_type	String	Yes	`LOW_VALUE`, `ORDINARY`, `CHECKING`, `SAVINGS`, or `INCLUSIVE_LOW_VALUE`	ACH account type.
account_number	String	Yes	[1-18]	ACH bank account number.
bank_name	String	Yes	For a comprehensive list of bank names, please refer to the section below.	Name of the bank associated with the account.

Bank List

Bank Name
BANCAMIA S.A BANCO AGRARIO BANCO AV VILLAS BANCO BGT PACTUAL BANCO CAJA SOCIAL BANCO CITIBANK COLOMBIA BANCO CONTACTAR S.A BANCO COOPERATIVO COOPCENTRAL BANCO CREDIFINANCIERA SA BANCO DE BOGOTA BANCO DE OCCIDENTE BANCO FALABELLA BANCO FINANDINA BANCO GNB SUDAMERIS BANCO MUNDO MUJER BANCO PICHINCHA S.A BANCO POPULAR BANCO PROCREDIT BANCO SERFINANZA SA BANCO UNION BANCO W SA BANCOLDEX BANCOLOMBIA BANCOOMEVA BANCOSANTANDER DE NEGOCIOS BBVA BNP PARIBAS COLOMBIA BOLD CF CFA FINANCIERA ANTIOQUIA COINK COLTEFINANCIERA CONFIAR COTRAFA ENTIDAD FINANCIERA CREZCAMOS DAVIPLATA DAVIVIENDA DING TECNIPAGOS SA FINANCIERA JURISCOOOP CF GLOBAL66 IRIS CF ITAU BANCO CORPBANCA ITAU* HELM BANK J.P. MORGAN COLOMBIA JFK COOPERATIVA FINANCIERA LULO BANK S.A. MIBANCO MOVII NEQUI NU PIBANK POWWI RAPPIPAY SCOTIABANK COLPATRIA UALA

Example Request

JSON
    
 
curl --location --request POST 'https://api.paas.develop.co.passportfintech.com/v1/recipients/ach' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
--data '{
    "customer_id": "8bebf7a7-9ca7-4a69-878b-e87f1578f7be",
    "alias": "Pepito SASA223222235232222",
    "recipient_type": "BUSINESS", 
    "identification_type": "NIT",
    "identification_number": "123456789",
    "account_type": "LOW_VALUE",
    "account_number": "880909090912",
    "bank_name": "BANCOLOMBIA"
}'
Copy

Response Body

HTTP Status Code: 200 OK.
The response will contain the recipient details along with its unique identifier.

Example of Response

JSON
    
 
{
    "created_at": "2025-11-17T17:08:24.890Z",
    "updated_at": "2025-11-17T17:08:24.890Z",
    "type": "ACH",
    "owner": {
        "type": "BUSINESS",
        "identification_type": "NIT",
        "identification_number": "123456789"
    },
    "alias": "Pepito SASA223222235232222",
    "account": {
        "account_type": "LOW_VALUE",
        "account_number": "880909090912"
    },
    "id": "c49714fc-b196-4e43-8efd-0d207922fa68",
    "customer_id": "8bebf7a7-9ca7-4a69-878b-e87f1578f7be"
}
Copy

The response indicates that the recipient has been successfully created, and it provides a unique recipient id that can be utilized for future transactions.
For ACH transactions, there is no need for key resolution.

Common Errors and Handling

HTTP Status Code	Meaning	Description
400 Bad Request	Invalid Data	Required fields are missing or contain incorrect values.
401 Unauthorized	Expired Token	The access token is invalid or has expired.
403 Forbidden	Access Denied	The request is not authorized to create a recipient.
500 Internal Server Error	Server Error	An unexpected error occurred while creating the recipient.

Best Practices

Ensure the customer_id is correct and associated with a valid entity customer.
Validate the recipient’s identification data before making the request.

Last updated on