Error codes

Lina Pay API error guide for integrators. For each code: what happened, why, what to do, whether you can retry, and when to contact Lina.

What an error response looks like

A single contract, the same on every route. Use errorCode to decide how to handle the error and keep the traceId: it is what Lina needs to investigate. message is always a list.

{
  "message": ["paymentRequestId must be a valid UUID."],
  "type": "error",
  "errorCode": "A003-27",
  "traceId": "3f2c9a1e-7b4d-4e0a-9c2f-1d5e6a7b8c90",
  "statusCode": 400
}

Code format

P003-21 = domain P, type 003, route 21. Type 001 = internal failure, 002 = not found, 003 = invalid request, 004 = no permission, 005 = 401 (A/P) or 409 (J), 006 = conflict. Note: the type does not guarantee the HTTP status; handle errors by statusCode and errorCode together.

No specific errorCode

An unforeseen scenario becomes EPM-<status> with a generic message. Account holder rejections may arrive with the holder's own code (E0xx) or EC00x and status 424.

Can I retry?

SAFE_RETRY/CONTACT_SUPPORT

Policy for every Lina 500 error. Retry with backoff (2s, 4s, 8s), up to 3 attempts. If it persists, contact Lina with the traceId, errorCode, endpoint, and time.

SAFE_RETRY

Retrying does not create or change anything beyond what was intended. Use backoff (2s, 4s, 8s) and at most 3 attempts.

RETRY_AFTER_FIX

The request is wrong. Fix the indicated field/credential; resending it as is returns the same error.

CHECK_STATUS_FIRST

The operation may have happened. Query the resource (GET) and only redo it if it is confirmed that nothing was created.

DO_NOT_RETRY

The resource state or a business rule prevents the operation. Retrying does not change the result.

CONTACT_SUPPORT

Depends on configuration or a fix at Lina, or is an external infrastructure failure (account holder, SPI, DICT, ICP). Do not retry; open a ticket with the traceId, errorCode, endpoint, and time.

NOT_VALIDATED

There is not enough evidence in the code to guarantee a policy. When in doubt about a financial operation, treat it as CHECK_STATUS_FIRST.

Origin vs. next action

Origin is where the failure started. Who acts is who needs to do something. An account holder rejection (origin) usually requires the integrator to guide the user (who acts).

Who acts

Integrator fixes the call or checks the state · End user resolves account, balance, limit, or authorization (the integrator guides them) · Lina support configuration, credentials, and internal failures.

When contacting Lina

Send the traceId, errorCode, method and endpoint, date/time (with time zone), and the resource identifier (paymentRequestId, consentId, enrollmentId). Do not send tokens or the user's personal data.

Catalog by domain

Filter by domain, status, retry policy, who acts, and audience, or search by code, route, message, or action. Click a code to see its scenarios, what to do, and an example response.

320 errorCodes687 scenarios120 scenarios with retry confirmed in code69 account holder E codes4 EC business codes

AAutomatic payments (Automatic Pix and sweeping)108 codes

route 1POST /automatic-payments

A001-1500Internal EPM failure while creating the automatic payment request.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the create automatic payment request function
What happened: Internal EPM failure while creating the automatic payment request.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the create automatic payment request function"
  ],
  "type": "error",
  "errorCode": "A001-1",
  "traceId": "<uuid>",
  "statusCode": 500
}

A003-1400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

25 scenario(s) · endpoint POST /automatic-payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: recurringConsent, redirectUri; optional: canBeAutomaticallyRevoked, requestExpiresAt.

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid automatic payment configuration. You need to provide at least one of the two options: firstPayment or paymentConfig
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid automatic payment configuration. You need to provide at least one of the two options: firstPayment or paymentConfig
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The data provided in the request is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The data provided in the request is invalid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Start Date] Start date must be greater than current date
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Start Date] Start date must be greater than current date
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Expiration Date] Expiration date must be greater than current date
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Expiration Date] Expiration date must be greater than current date
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Reference Start Date] Reference start date must be greater than current date
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Reference Start Date] Reference start date must be greater than current date
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [First Payment Date] First payment date must be in YYYY-MM-DD format
What happened: The request was rejected by an EPM validation rule.
Likely cause: [First Payment Date] First payment date must be in YYYY-MM-DD format
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [First Payment Date] First payment date must be greater than current date
What happened: The request was rejected by an EPM validation rule.
Likely cause: [First Payment Date] First payment date must be greater than current date
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Logged User] CPF/CNPJ must be valid
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Logged User] CPF/CNPJ must be valid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Business Entity] CPF/CNPJ must be valid
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Business Entity] CPF/CNPJ must be valid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Creditor] Multiple creditors are not allowed, only one is expected
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Creditor] Multiple creditors are not allowed, only one is expected
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Creditor] One creditor must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Creditor] One creditor must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Creditor] Person type must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Creditor] Person type must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Creditor] Person type must be "PESSOA_JURIDICA"
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Creditor] Person type must be "PESSOA_JURIDICA"
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Creditor] CPF/CNPJ must be valid
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Creditor] CPF/CNPJ must be valid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Creditor] Name must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Creditor] Name must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Contract Debtor] CPF/CNPJ must be valid
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Contract Debtor] CPF/CNPJ must be valid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Debitor] Account type must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Debitor] Account type must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Debitor] Issuer must be provided for CACC or SVGS account type
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Debitor] Issuer must be provided for CACC or SVGS account type
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Debitor] Account type must be "CACC", "SVGS" or "TRAN"
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Debitor] Account type must be "CACC", "SVGS" or "TRAN"
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Recurring Configuration] Both fixed and maximum variable amount cannot be provided simultaneously
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Recurring Configuration] Both fixed and maximum variable amount cannot be provided simultaneously
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Recurring Configuration] Fixed amount and minimum variable amount cannot be provided simultaneously
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Recurring Configuration] Fixed amount and minimum variable amount cannot be provided simultaneously
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Recurring Configuration] Fixed amount must be greater than 0
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Recurring Configuration] Fixed amount must be greater than 0
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Recurring Configuration] Maximum variable amount must be greater than 0
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Recurring Configuration] Maximum variable amount must be greater than 0
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: [Recurring Configuration] Minimum variable amount must be less than maximum variable amount
What happened: The request was rejected by an EPM validation rule.
Likely cause: [Recurring Configuration] Minimum variable amount must be less than maximum variable amount
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "A003-1",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-1403The resource belongs to another tenant or sub-tenant. · The credentials used are not allowed to perform this operation.RETRY_AFTER_FIXCONTACT_SUPPORT

2 scenario(s) · endpoint POST /automatic-payments · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to perform this operation
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-1",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-1401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-1",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 2GET /automatic-payments/requests

A001-2500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/requests

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that lists automatic payment requests
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that lists automatic payment requests"
  ],
  "type": "error",
  "errorCode": "A001-2",
  "traceId": "<uuid>",
  "statusCode": 500
}

A004-2403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/requests

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-2",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-2401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/requests

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-2",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 3GET /automatic-payments/:userCpf

A001-3500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/:userCpf

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that fetches the user's automatic payment requests
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that fetches the user's automatic payment requests"
  ],
  "type": "error",
  "errorCode": "A001-3",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-3404There are no records for the filter provided.DO_NOT_RETRY

1 scenario(s) · endpoint GET /automatic-payments/:userCpf

404DO_NOT_RETRYconfirmedIntegrator

Message: No payment request found for the provided CPF
What happened: There are no records for the filter provided.
Likely cause: Query returned no results. This is not a failure.
What to do: Treat it as an empty list in your application.

Example response:

{
  "message": [
    "No payment request found for the provided CPF"
  ],
  "type": "error",
  "errorCode": "A002-3",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-3403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/:userCpf

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-3",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-3401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/:userCpf

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-3",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 4GET /automatic-payments/subtenants/:cpf

A001-4500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/subtenants/:cpf

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that fetches the user's sub-tenants
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that fetches the user's sub-tenants"
  ],
  "type": "error",
  "errorCode": "A001-4",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-4404There are no records for the filter provided.DO_NOT_RETRY

1 scenario(s) · endpoint GET /automatic-payments/subtenants/:cpf

404DO_NOT_RETRYconfirmedIntegrator

Message: No sub-tenant found for the provided CPF
What happened: There are no records for the filter provided.
Likely cause: Query returned no results. This is not a failure.
What to do: Treat it as an empty list in your application.

Example response:

{
  "message": [
    "No sub-tenant found for the provided CPF"
  ],
  "type": "error",
  "errorCode": "A002-4",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-4403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/subtenants/:cpf

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-4",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-4401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/subtenants/:cpf

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-4",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 5GET /automatic-payments/sub-tenants/:subTenantId

A001-5500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/sub-tenants/:subTenantId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that lists the sub-tenant's payment requests
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that lists the sub-tenant's payment requests"
  ],
  "type": "error",
  "errorCode": "A001-5",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-5404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/sub-tenants/:subTenantId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

A004-5403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/sub-tenants/:subTenantId

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-5",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-5401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/sub-tenants/:subTenantId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-5",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 6GET /automatic-payments/tenants/:tenantId

A001-6500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/tenants/:tenantId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that lists the tenant's payment requests
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that lists the tenant's payment requests"
  ],
  "type": "error",
  "errorCode": "A001-6",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-6404There are no records for the filter provided.DO_NOT_RETRY

1 scenario(s) · endpoint GET /automatic-payments/tenants/:tenantId

404DO_NOT_RETRYconfirmedIntegrator

Message: No payment request found for the provided tenant
What happened: There are no records for the filter provided.
Likely cause: Query returned no results. This is not a failure.
What to do: Treat it as an empty list in your application.

Example response:

{
  "message": [
    "No payment request found for the provided tenant"
  ],
  "type": "error",
  "errorCode": "A002-6",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-6403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/tenants/:tenantId

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-6",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-6401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/tenants/:tenantId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-6",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 7GET /automatic-payments/payments/tenants/:tenantId

A001-7500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/payments/tenants/:tenantId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that lists the tenant's payments
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that lists the tenant's payments"
  ],
  "type": "error",
  "errorCode": "A001-7",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-7404There are no records for the filter provided.DO_NOT_RETRY

1 scenario(s) · endpoint GET /automatic-payments/payments/tenants/:tenantId

404DO_NOT_RETRYconfirmedIntegrator

Message: No payment found for the provided tenant
What happened: There are no records for the filter provided.
Likely cause: Query returned no results. This is not a failure.
What to do: Treat it as an empty list in your application.

Example response:

{
  "message": [
    "No payment found for the provided tenant"
  ],
  "type": "error",
  "errorCode": "A002-7",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-7400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/payments/tenants/:tenantId

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId is required
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "tenantId is required"
  ],
  "type": "error",
  "errorCode": "A003-7",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-7403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/payments/tenants/:tenantId

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-7",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-7401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/payments/tenants/:tenantId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-7",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 8GET /automatic-payments/payments/sub-tenants/:subTenantId

A001-8500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/payments/sub-tenants/:subTenantId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that lists the sub-tenant's payments
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that lists the sub-tenant's payments"
  ],
  "type": "error",
  "errorCode": "A001-8",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-8404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/payments/sub-tenants/:subTenantId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

A004-8403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/payments/sub-tenants/:subTenantId

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-8",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-8401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/payments/sub-tenants/:subTenantId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-8",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 9GET /automatic-payments/request/:automaticPaymentsRequestId

A001-9500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/request/:automaticPaymentsRequestId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that fetches the automatic payment request
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that fetches the automatic payment request"
  ],
  "type": "error",
  "errorCode": "A001-9",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-9404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /automatic-payments/request/:automaticPaymentsRequestId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Automatic payment request with ID <id> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment request not found"
  ],
  "type": "error",
  "errorCode": "A002-9",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-9403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/request/:automaticPaymentsRequestId

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-9",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-9401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/request/:automaticPaymentsRequestId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-9",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 10PATCH /automatic-payments/request/:paymentRequestId/details

A001-10500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/details

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Internal problem in the function that updates the automatic payment request details
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that updates the automatic payment request details"
  ],
  "type": "error",
  "errorCode": "A001-10",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-10404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/details

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment request not found"
  ],
  "type": "error",
  "errorCode": "A002-10",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-10400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +1RETRY_AFTER_FIX

5 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/details · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — optional: additionalInformation, remittanceInformation, maximumVariableAmount.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDetailsMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDetailsMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDetailsMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "A003-10",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-10403The resource belongs to another tenant or sub-tenant. · The credentials used are not allowed to perform this operation.RETRY_AFTER_FIXCONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/details · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: Payment request does not belong to the sub-tenant of the authenticated user
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Payment request does not belong to the sub-tenant of the authenticated user"
  ],
  "type": "error",
  "errorCode": "A004-10",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-10401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/details

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-10",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 11POST /automatic-payments/recurring-consents

A001-11500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/recurring-consents

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the create recurring consent function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the create recurring consent function"
  ],
  "type": "error",
  "errorCode": "A001-11",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-11404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /automatic-payments/recurring-consents · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: No creditor found for automatic payment request
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring configuration not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "No creditor found for automatic payment request"
  ],
  "type": "error",
  "errorCode": "A002-11",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-11400The request was rejected by an EPM validation rule. · The request body or parameters failed format validation.RETRY_AFTER_FIX

5 scenario(s) · endpoint POST /automatic-payments/recurring-consents · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: Unsupported interval type: <interval>
What happened: The request was rejected by an EPM validation rule.
Likely cause: Unsupported interval type: <interval>
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: organisationId, authorisationServerId; optional: recurringConsent, paymentRequestId, platform, redirectUri, requestExpiresAt.

400RETRY_AFTER_FIXinferredIntegrator

Message: It is necessary to provide recurringConsent or paymentRequestId in the request body
What happened: The request was rejected by an EPM validation rule.
Likely cause: It is necessary to provide recurringConsent or paymentRequestId in the request body
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields recurringConsent and paymentRequestId cannot both be provided at the same time
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields recurringConsent and paymentRequestId cannot both be provided at the same time
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided request data is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided request data is invalid
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Unsupported interval type: <interval>"
  ],
  "type": "error",
  "errorCode": "A003-11",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-11403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/recurring-consents

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-11",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-11401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/recurring-consents

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-11",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 12GET /automatic-payments/recurring-consents/:recurringConsentId

A001-12500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the find recurring consent function
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the find recurring consent function"
  ],
  "type": "error",
  "errorCode": "A001-12",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-12404The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: ConsentId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Automatic payment with ConsentId <consentId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring consent not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "ConsentId must be informed"
  ],
  "type": "error",
  "errorCode": "A002-12",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-12400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId

400RETRY_AFTER_FIXinferredIntegrator

Message: Payment request is missing organisationId or authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: Payment request is missing organisationId or authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Payment request is missing organisationId or authorisationServerId"
  ],
  "type": "error",
  "errorCode": "A003-12",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-12403The resource belongs to another tenant or sub-tenant. · Operation not allowed for these credentials. · +1RETRY_AFTER_FIXNOT_VALIDATEDCONTACT_SUPPORT

3 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: Recurring consent does not belong to the sub-tenant of the authenticated user
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403NOT_VALIDATEDnot verifiedIntegrator

Message: Error fetching token
What happened: Operation not allowed for these credentials.
Likely cause: Error fetching token
What to do: Check the credentials and sub-tenant used. If it persists, contact Lina support with the traceId.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Recurring consent does not belong to the sub-tenant of the authenticated user"
  ],
  "type": "error",
  "errorCode": "A004-12",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-12401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-12",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 13GET /automatic-payments/recurring-consents/:recurringConsentId/request

A001-13500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId/request

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that fetches the automatic payment request by recurring consent
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that fetches the automatic payment request by recurring consent"
  ],
  "type": "error",
  "errorCode": "A001-13",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-13404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId/request

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found for the provided recurring consent
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment request not found for the provided recurring consent"
  ],
  "type": "error",
  "errorCode": "A002-13",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-13403The resource belongs to another tenant or sub-tenant. · The credentials used are not allowed to perform this operation.RETRY_AFTER_FIXCONTACT_SUPPORT

2 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId/request · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: Payment request does not belong to the sub-tenant of the authenticated user
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Payment request does not belong to the sub-tenant of the authenticated user"
  ],
  "type": "error",
  "errorCode": "A004-13",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-13401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-consents/:recurringConsentId/request

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-13",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 14PATCH /automatic-payments/recurring-consents/:recurringConsentId

A001-14500The change/revocation may have been applied at the account holder, but the EPM failed to save it.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /automatic-payments/recurring-consents/:recurringConsentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the update/revoke recurring consent function
What happened: The change/revocation may have been applied at the account holder, but the EPM failed to save it.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the update/revoke recurring consent function"
  ],
  "type": "error",
  "errorCode": "A001-14",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-14404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/recurring-consents/:recurringConsentId

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring consent not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Recurring consent not found"
  ],
  "type": "error",
  "errorCode": "A002-14",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-14400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/recurring-consents/:recurringConsentId

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided update data is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided update data is invalid
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "The provided update data is invalid"
  ],
  "type": "error",
  "errorCode": "A003-14",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-14403Operation not allowed for these credentials. · The credentials used are not allowed to perform this operation.NOT_VALIDATEDCONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /automatic-payments/recurring-consents/:recurringConsentId · the same code covers different scenarios: read message[] to tell them apart

403NOT_VALIDATEDnot verifiedIntegrator

Message: Error fetching token
What happened: Operation not allowed for these credentials.
Likely cause: Error fetching token
What to do: Check the credentials and sub-tenant used. If it persists, contact Lina support with the traceId.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Error fetching token"
  ],
  "type": "error",
  "errorCode": "A004-14",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-14401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/recurring-consents/:recurringConsentId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-14",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 15POST /automatic-payments/recurring-payments/validate

A001-15500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/recurring-payments/validate

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the validate recurring payment function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the validate recurring payment function"
  ],
  "type": "error",
  "errorCode": "A001-15",
  "traceId": "<uuid>",
  "statusCode": 500
}

A003-15400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /automatic-payments/recurring-payments/validate · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: state, code, idToken, tenantId; optional: platform.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment data is invalid or the consent was not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment data is invalid or the consent was not found
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "A003-15",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-15403Operation not allowed for these credentials. · The credentials used are not allowed to perform this operation.NOT_VALIDATEDCONTACT_SUPPORT

2 scenario(s) · endpoint POST /automatic-payments/recurring-payments/validate · the same code covers different scenarios: read message[] to tell them apart

403NOT_VALIDATEDnot verifiedIntegrator

Message: Error fetching token
What happened: Operation not allowed for these credentials.
Likely cause: Error fetching token
What to do: Check the credentials and sub-tenant used. If it persists, contact Lina support with the traceId.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Error fetching token"
  ],
  "type": "error",
  "errorCode": "A004-15",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-15401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/recurring-payments/validate

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-15",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 16POST /automatic-payments/consents/:consentId/recurring-payments

A001-16500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/consents/:consentId/recurring-payments

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the process recurring payment function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the process recurring payment function"
  ],
  "type": "error",
  "errorCode": "A001-16",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-16404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/consents/:consentId/recurring-payments

404RETRY_AFTER_FIXinferredIntegrator

Message: Consent not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Consent not found"
  ],
  "type": "error",
  "errorCode": "A002-16",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-16403Operation not allowed for these credentials. · The credentials used are not allowed to perform this operation.NOT_VALIDATEDCONTACT_SUPPORT

2 scenario(s) · endpoint POST /automatic-payments/consents/:consentId/recurring-payments · the same code covers different scenarios: read message[] to tell them apart

403NOT_VALIDATEDnot verifiedIntegrator

Message: Error fetching token
What happened: Operation not allowed for these credentials.
Likely cause: Error fetching token
What to do: Check the credentials and sub-tenant used. If it persists, contact Lina support with the traceId.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Error fetching token"
  ],
  "type": "error",
  "errorCode": "A004-16",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-16401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/consents/:consentId/recurring-payments

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-16",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 17POST /automatic-payments/recurring-payments

A001-17500Internal EPM failure while creating the recurring payment; the institution may already have received the request.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/recurring-payments

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the create recurring payment function
What happened: Internal EPM failure while creating the recurring payment; the institution may already have received the request.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the create recurring payment function"
  ],
  "type": "error",
  "errorCode": "A001-17",
  "traceId": "<uuid>",
  "statusCode": 500
}

A003-17400The account holder rejected the payment creation with 400/404. · The request was rejected by an EPM validation rule. · +2RETRY_AFTER_FIXDO_NOT_RETRY

23 scenario(s) · endpoint POST /automatic-payments/recurring-payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid orgId or asId provided
What happened: The account holder rejected the payment creation with 400/404.
Likely cause: Any 400/404 from the account holder becomes this message: it may be an incorrect orgId/asId or a payment content error. The message does not distinguish between them.
What to do: Check the consent's organisationId/authorisationServerId and the payment payload. If they are correct, contact Lina support with the traceId (the actual reason is only in the log).
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

400RETRY_AFTER_FIXinferredIntegrator

Message: The request body cannot be empty
What happened: The request was rejected by an EPM validation rule.
Likely cause: The request body cannot be empty
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: When you are creating the first payment, you must inform all the required fields
What happened: The request was rejected by an EPM validation rule.
Likely cause: When you are creating the first payment, you must inform all the required fields
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid Payload, please check if you have filled all the required fields
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid Payload, please check if you have filled all the required fields
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid Payload, please check if you have filled all the required fields
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid Payload, please check if you have filled all the required fields
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Payment body validation messages built at runtime.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid Payload, please check if you have filled all the required fields
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid Payload, please check if you have filled all the required fields
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: creditorAccount is required for Sweeping payments
What happened: The request was rejected by an EPM validation rule.
Likely cause: creditorAccount is required for Sweeping payments
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: riskSignals is required for Sweeping payments
What happened: The request was rejected by an EPM validation rule.
Likely cause: riskSignals is required for Sweeping payments
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: authorisationFlow is required for Sweeping payments
What happened: The request was rejected by an EPM validation rule.
Likely cause: authorisationFlow is required for Sweeping payments
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: localInstrument is required for Sweeping payments
What happened: The request was rejected by an EPM validation rule.
Likely cause: localInstrument is required for Sweeping payments
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Payment body validation messages built at runtime.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the amount of the payment must be equal to the fixed amount
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the amount of the payment must be equal to the fixed amount
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the amount of the payment must be less than the maximum variable amount
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the amount of the payment must be less than the maximum variable amount
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the amount of the payment must be greater than the minimum variable amount
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the amount of the payment must be greater than the minimum variable amount
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXinferredIntegrator

Message: Sweeping configuration not found for this payment request
What happened: The request was rejected by an EPM validation rule.
Likely cause: Sweeping configuration not found for this payment request
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the amount of the payment (<amountCents>) must be less than or equal to the transaction limit (<transactionLimitCents>)
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the amount of the payment (<amountCents>) must be less than or equal to the transaction limit (<transactionLimitCents>)
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the total amount (<totalCents>) would exceed the total allowed amount (<totalAllowedCents>)
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the total amount (<totalCents>) would exceed the total allowed amount (<totalAllowedCents>)
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the total amount for period <period> (<periodCents>) would exceed the periodic limit (<limitCents>)
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the total amount for period <period> (<periodCents>) would exceed the periodic limit (<limitCents>)
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: Error, the number of payments for period <period> (<periodCount>) would exceed the periodic quantity limit (<quantityLimit>)
What happened: The payment amount violates the recurring consent limits.
Likely cause: Error, the number of payments for period <period> (<periodCount>) would exceed the periodic quantity limit (<quantityLimit>)
What to do: Adjust the amount (or date) to respect the consent's fixed amount, variable minimum/maximum, or period/total limits. If the limit needs to change, the end user must authorize a new consent.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment data is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment data is invalid
What to do: Adjust the data indicated in message[] and resend.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payments can only be created for an automatic payment request with status <AUTORIZADO>. Current status: <status>
What happened: The automatic payment request is not AUTORIZADO.
Likely cause: Payments can only be created after the user has authorized the recurring consent.
What to do: Query the request (GET /automatic-payments/request/:id). If it is pending, complete the authorization with the user; if revoked/expired, start a new consent.

400RETRY_AFTER_FIXinferredIntegrator

Message: Sweeping payments require FullBodyRecurringPaymentDto with creditorAccount and riskSignals
What happened: The request was rejected by an EPM validation rule.
Likely cause: Sweeping payments require FullBodyRecurringPaymentDto with creditorAccount and riskSignals
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Invalid orgId or asId provided"
  ],
  "type": "error",
  "errorCode": "A003-17",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-17403The resource belongs to another tenant or sub-tenant. · The credentials used are not allowed to perform this operation.RETRY_AFTER_FIXCONTACT_SUPPORT

2 scenario(s) · endpoint POST /automatic-payments/recurring-payments · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "A004-17",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-17401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/recurring-payments

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-17",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 18GET /automatic-payments/recurring-payments/:recurringPaymentId

A001-18500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/:recurringPaymentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the find recurring payment function
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the find recurring payment function"
  ],
  "type": "error",
  "errorCode": "A001-18",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-18404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/:recurringPaymentId

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Recurring payment not found"
  ],
  "type": "error",
  "errorCode": "A002-18",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-18403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/:recurringPaymentId

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-18",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-18401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/:recurringPaymentId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-18",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 19GET /automatic-payments/recurring-payments/external/:recurringPaymentId

A001-19500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/external/:recurringPaymentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the find recurring payment at the holder function
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the find recurring payment at the holder function"
  ],
  "type": "error",
  "errorCode": "A001-19",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-19404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/external/:recurringPaymentId

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring payment not found at the holder
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Recurring payment not found at the holder"
  ],
  "type": "error",
  "errorCode": "A002-19",
  "traceId": "<uuid>",
  "statusCode": 404
}

A004-19403The resource belongs to another tenant or sub-tenant. · Operation not allowed for these credentials. · +1RETRY_AFTER_FIXNOT_VALIDATEDCONTACT_SUPPORT

3 scenario(s) · endpoint GET /automatic-payments/recurring-payments/external/:recurringPaymentId · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: Recurring payment does not belong to the sub-tenant of the authenticated user
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403NOT_VALIDATEDnot verifiedIntegrator

Message: Error fetching token
What happened: Operation not allowed for these credentials.
Likely cause: Error fetching token
What to do: Check the credentials and sub-tenant used. If it persists, contact Lina support with the traceId.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Recurring payment does not belong to the sub-tenant of the authenticated user"
  ],
  "type": "error",
  "errorCode": "A004-19",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-19401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /automatic-payments/recurring-payments/external/:recurringPaymentId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-19",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 20PATCH /automatic-payments/recurring-payments/:recurringPaymentId

A001-20500Internal failure while cancelling the recurring payment.SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /automatic-payments/recurring-payments/:recurringPaymentId · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that updates the recurring payment
What happened: Internal failure while cancelling the recurring payment.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that updates the recurring payment
What happened: Internal failure while cancelling the recurring payment.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that updates the recurring payment"
  ],
  "type": "error",
  "errorCode": "A001-20",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-20404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /automatic-payments/recurring-payments/:recurringPaymentId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Recurring payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Recurring payment not found"
  ],
  "type": "error",
  "errorCode": "A002-20",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-20400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /automatic-payments/recurring-payments/:recurringPaymentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: cpfCancelledBy.

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided update data is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided update data is invalid
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "A003-20",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-20403The resource belongs to another tenant or sub-tenant. · The credentials used are not allowed to perform this operation.RETRY_AFTER_FIXCONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /automatic-payments/recurring-payments/:recurringPaymentId · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to perform this operation
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-20",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-20401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/recurring-payments/:recurringPaymentId

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-20",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 21POST /automatic-payments/recurring-payments/:originalRecurringPaymentId/retry

A001-21500Internal failure while updating the retry permission. · The retry may have been accepted by the account holder, but the EPM failed to save the result.SAFE_RETRY/CONTACT_SUPPORT

3 scenario(s) · endpoint POST /automatic-payments/recurring-payments/:originalRecurringPaymentId/retry · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Failed to update retry permition: <internal technical detail>
What happened: Internal failure while updating the retry permission.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the retry recurring payment function
What happened: The retry may have been accepted by the account holder, but the EPM failed to save the result.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the retry recurring payment function
What happened: The retry may have been accepted by the account holder, but the EPM failed to save the result.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Failed to update retry permition: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "A001-21",
  "traceId": "<uuid>",
  "statusCode": 500
}

A002-21404The requested resource was not found.RETRY_AFTER_FIX

6 scenario(s) · endpoint POST /automatic-payments/recurring-payments/:originalRecurringPaymentId/retry · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment with externalPaymentId <originalRecurringPaymentId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment with paymentId <originalRecurringPaymentId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request with consentId <recurringConsentId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment with externalPaymentId <originalRecurringPaymentId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request with consentId <automaticPaymentRequest> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Resource not found. Contact support informing the traceId of this response.
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Payment with externalPaymentId <originalRecurringPaymentId> not found"
  ],
  "type": "error",
  "errorCode": "A002-21",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-21400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule. · +3RETRY_AFTER_FIXDO_NOT_RETRYCONTACT_SUPPORTCHECK_STATUS_FIRST

10 scenario(s) · endpoint POST /automatic-payments/recurring-payments/:originalRecurringPaymentId/retry · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: date; optional: endToEndId.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payment with externalPaymentId <originalRecurringPaymentId> is not allowed to retry
What happened: The original payment can no longer be retried.
Likely cause: The payment does not allow retries (isRetryAllowed = false), for example because it has already been retried.
What to do: Do not retry. Inform the user/payee; the charge must go through the next cycle or another channel.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payment with externalPaymentId <originalRecurringPaymentId> cannot be retried. Minimum <minDaysRequired> days required before due date (<daysUntilDueDate> days remaining)
What happened: The original payment can no longer be retried.
Likely cause: Retry window closed: 7 days after the scheduled date (5 days for weekly frequency). Note: the number in the message is days elapsed, not remaining.
What to do: Do not retry. Inform the user/payee; the charge must go through the next cycle or another channel.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payment with externalPaymentId <originalRecurringPaymentId> cannot be retried. It is the last day of the current cycle
What happened: The original payment can no longer be retried.
Likely cause: It is the last day of the billing cycle.
What to do: Do not retry. Inform the user/payee; the charge must go through the next cycle or another channel.

400CONTACT_SUPPORTconfirmedIntegrator

Message: Failed to send retry payment: <internal technical detail>
What happened: The account holder rejected the retry.
Likely cause: Failed to send retry payment: <internal technical detail>
What to do: Do not retry automatically. Query the original payment and contact Lina support with the traceId. The message may contain internal technical text.
Contact Lina: Yes, to resolve it. Include the traceId.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

400CHECK_STATUS_FIRSTconfirmedIntegrator

Message: dynamic message
What happened: The payment to be retried is not rejected at the account holder.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Query the payment (GET /automatic-payments/recurring-payments/external/:recurringPaymentId). Retrying only makes sense for a payment REJEITADO (RJCT) at the account holder.

400CHECK_STATUS_FIRSTconfirmedIntegrator

Message: dynamic message
What happened: The payment to be retried is not rejected at the account holder.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Query the payment (GET /automatic-payments/recurring-payments/external/:recurringPaymentId). Retrying only makes sense for a payment REJEITADO (RJCT) at the account holder.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "A003-21",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-21403The resource belongs to another tenant or sub-tenant. · Operation not allowed for these credentials. · +1RETRY_AFTER_FIXNOT_VALIDATEDCONTACT_SUPPORT

3 scenario(s) · endpoint POST /automatic-payments/recurring-payments/:originalRecurringPaymentId/retry · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to perform this operation
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403NOT_VALIDATEDnot verifiedIntegrator

Message: Error fetching token
What happened: Operation not allowed for these credentials.
Likely cause: Error fetching token
What to do: Check the credentials and sub-tenant used. If it persists, contact Lina support with the traceId.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-21",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-21401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/recurring-payments/:originalRecurringPaymentId/retry

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-21",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 22POST /automatic-payments/recurring-consents/update-consents

A001-22500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/recurring-consents/update-consents

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Internal problem in the function that updates recurring consents
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that updates recurring consents"
  ],
  "type": "error",
  "errorCode": "A001-22",
  "traceId": "<uuid>",
  "statusCode": 500
}

A004-22403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /automatic-payments/recurring-consents/update-consents

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-22",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-22401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/recurring-consents/update-consents

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-22",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 23PATCH /automatic-payments/request/:paymentRequestId/sweeping (authentication guard)

A004-23403The credentials used are not allowed to perform this operation.CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/sweeping (authentication guard)

403CONTACT_SUPPORTconfirmedLina support

Message: You do not have permission to perform this operation
What happened: The credentials used are not allowed to perform this operation.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Confirm you are using the correct client (tenant x sub-tenant). If so, ask Lina to grant the role/feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "You do not have permission to perform this operation"
  ],
  "type": "error",
  "errorCode": "A004-23",
  "traceId": "<uuid>",
  "statusCode": 403
}

A005-23401Missing, invalid, or expired access token.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/sweeping (authentication guard)

401RETRY_AFTER_FIXconfirmedIntegrator

Message: Invalid or missing authentication token
What happened: Missing, invalid, or expired access token.
Likely cause: Authorization header without a valid Bearer issued by Lina's identity provider.
What to do: Obtain a new access token (client credentials) and resend with Authorization: Bearer <token>.

Example response:

{
  "message": [
    "Invalid or missing authentication token"
  ],
  "type": "error",
  "errorCode": "A005-23",
  "traceId": "<uuid>",
  "statusCode": 401
}

route 23POST /automatic-payments/values

A003-23400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /automatic-payments/values

400RETRY_AFTER_FIXinferredIntegrator

Message: Each object must have at least one payment and a value
What happened: The request was rejected by an EPM validation rule.
Likely cause: Each object must have at least one payment and a value
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Each object must have at least one payment and a value"
  ],
  "type": "error",
  "errorCode": "A003-23",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 25PATCH /automatic-payments/future-payments/:paymentId

A002-25404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/future-payments/:paymentId

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment not found"
  ],
  "type": "error",
  "errorCode": "A002-25",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-25400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /automatic-payments/future-payments/:paymentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid date format: <date>. Expected format: YYYY-MM-DD
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid date format: <date>. Expected format: YYYY-MM-DD
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid date: <date>. Date is not valid.
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid date: <date>. Date is not valid.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Invalid date: <date>. The date does not exist (e.g., 2026-02-31 or 2026-03-32).
What happened: The request was rejected by an EPM validation rule.
Likely cause: Invalid date: <date>. The date does not exist (e.g., 2026-02-31 or 2026-03-32).
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Date must be within payment cycle: <startDateCycle.toISOString().slice(0, 10> to <endDateCycle.toISOString().slice(0, 10)>. Received: <date>
What happened: The request was rejected by an EPM validation rule.
Likely cause: Date must be within payment cycle: <startDateCycle.toISOString().slice(0, 10> to <endDateCycle.toISOString().slice(0, 10)>. Received: <date>
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Invalid date format: <date>. Expected format: YYYY-MM-DD"
  ],
  "type": "error",
  "errorCode": "A003-25",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 26PATCH /automatic-payments/future-payments/request/:paymentRequestId

A002-26404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/future-payments/request/:paymentRequestId

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment not found"
  ],
  "type": "error",
  "errorCode": "A002-26",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-26400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/future-payments/request/:paymentRequestId

400RETRY_AFTER_FIXinferredIntegrator

Message: Date must be valid with this payment cycle
What happened: The request was rejected by an EPM validation rule.
Likely cause: Date must be valid with this payment cycle
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Date must be valid with this payment cycle"
  ],
  "type": "error",
  "errorCode": "A003-26",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 27PATCH /automatic-payments/request/:paymentRequestId/sweeping

A001-27500Internal failure while updating the sweeping configuration.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/sweeping

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: dynamic message
What happened: Internal failure while updating the sweeping configuration.
Likely cause: Unexpected error. The message sent is "Error updating sweeping configuration".
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

A002-27404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/sweeping

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment request not found"
  ],
  "type": "error",
  "errorCode": "A002-27",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-27400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +3RETRY_AFTER_FIXDO_NOT_RETRY

6 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/sweeping · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — optional: totalAllowedAmount, transactionLimit, periodicLimits, startDateTime, expirationDateTime.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: Provide at least one sweeping field to update
What happened: The request was rejected by an EPM validation rule.
Likely cause: Provide at least one sweeping field to update
What to do: Adjust the data indicated in message[] and resend.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payment request does not have a sweeping configuration
What happened: The request has no sweeping configuration.
Likely cause: Payment request does not have a sweeping configuration
What to do: Use this route only for sweeping requests (smart transfers).

400DO_NOT_RETRYconfirmedIntegrator

Message: Sweeping configuration cannot be updated because the payment request is not in pending status
What happened: The sweeping configuration can only be changed while the request is PENDENTE.
Likely cause: Sweeping configuration cannot be updated because the payment request is not in pending status
What to do: Query the request. If it has already been authorized, the change requires a new consent.

400RETRY_AFTER_FIXinferredIntegrator

Message: periodicLimits.<period> must keep at least one of quantityLimit or transactionLimit
What happened: The request was rejected by an EPM validation rule.
Likely cause: periodicLimits.<period> must keep at least one of quantityLimit or transactionLimit
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "A003-27",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-27403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/sweeping

403RETRY_AFTER_FIXinferredIntegrator

Message: Payment request does not belong to the sub-tenant of the authenticated user
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "Payment request does not belong to the sub-tenant of the authenticated user"
  ],
  "type": "error",
  "errorCode": "A004-27",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 28PATCH /automatic-payments/request/:paymentRequestId/data-consent/cancel

A001-28500Failed to cancel the associated data consent.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/data-consent/cancel

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: dynamic message
What happened: Failed to cancel the associated data consent.
Likely cause: Unexpected error when calling the data partner. The message sent is "Error cancelling data consent".
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

A002-28404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/data-consent/cancel

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment request not found"
  ],
  "type": "error",
  "errorCode": "A002-28",
  "traceId": "<uuid>",
  "statusCode": 404
}

A003-28400A path identifier is not a valid UUID. · The request has no data consent to cancel.RETRY_AFTER_FIXDO_NOT_RETRY

2 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/data-consent/cancel · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400DO_NOT_RETRYconfirmedIntegrator

Message: The payment request does not have a dataConsentId to cancel
What happened: The request has no data consent to cancel.
Likely cause: The payment request does not have a dataConsentId to cancel
What to do: Nothing to cancel; treat it as completed.

Example response:

{
  "message": [
    "paymentRequestId must be a valid UUID."
  ],
  "type": "error",
  "errorCode": "A003-28",
  "traceId": "<uuid>",
  "statusCode": 400
}

A004-28403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /automatic-payments/request/:paymentRequestId/data-consent/cancel

403RETRY_AFTER_FIXinferredIntegrator

Message: Payment request does not belong to the sub-tenant of the authenticated user
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "Payment request does not belong to the sub-tenant of the authenticated user"
  ],
  "type": "error",
  "errorCode": "A004-28",
  "traceId": "<uuid>",
  "statusCode": 403
}

CCross-cutting integrations (identity, anti-fraud)4 codes

integration 1Anti-fraud IDwall — JSR, open-integration, automatic payments, and retry

C004-1403The CPF was blocked by the anti-fraud check.Cross-cuttingDO_NOT_RETRY

1 scenario(s) · endpoint Anti-fraud IDwall — JSR, open-integration, automatic payments, and retry

403DO_NOT_RETRYconfirmedIntegrator

Message: CPF identified in a fraud occurrence
What happened: The CPF was blocked by the anti-fraud check.
Likely cause: CPF identified in a fraud occurrence (IDwall).
What to do: Tell the user the operation cannot be completed through this channel. Do not retry and do not expose the "fraud" reason to the end user.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "CPF identified in a fraud occurrence"
  ],
  "type": "error",
  "errorCode": "C004-1",
  "traceId": "<uuid>",
  "statusCode": 403
}

integration 1Identity provider — tenant client (tenant and sub-tenant creation/management)

C002-1404Client not found in Lina's identity provider.Cross-cuttingCONTACT_SUPPORT

4 scenario(s) · endpoint Identity provider — tenant client (tenant and sub-tenant creation/management) · the same code covers different scenarios: read message[] to tell them apart

404CONTACT_SUPPORTinferredLina support

Message: Client Not Found
What happened: Client not found in Lina's identity provider.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Contact Lina support.
Contact Lina: Yes, to resolve it. Include the traceId.

404CONTACT_SUPPORTinferredLina support

Message: Client Not Found
What happened: Client not found in Lina's identity provider.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Contact Lina support.
Contact Lina: Yes, to resolve it. Include the traceId.

404CONTACT_SUPPORTinferredLina support

Message: Client Not Found
What happened: Client not found in Lina's identity provider.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Contact Lina support.
Contact Lina: Yes, to resolve it. Include the traceId.

404CONTACT_SUPPORTinferredLina support

Message: Client Not Found
What happened: Client not found in Lina's identity provider.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Contact Lina support.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Client Not Found"
  ],
  "type": "error",
  "errorCode": "C002-1",
  "traceId": "<uuid>",
  "statusCode": 404
}

integration 1Tenant middleware — any route authenticated by sub-tenant

C003-1400The tenant or sub-tenant of the credentials is inactive.Cross-cuttingCONTACT_SUPPORT

1 scenario(s) · endpoint Tenant middleware — any route authenticated by sub-tenant

400CONTACT_SUPPORTconfirmedLina support

Message: Tenant is inactive
What happened: The tenant or sub-tenant of the credentials is inactive.
Likely cause: Registration deactivated at Lina.
What to do: Contact your Lina account manager/support to reactivate the registration. Do not retry.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Tenant is inactive"
  ],
  "type": "error",
  "errorCode": "C003-1",
  "traceId": "<uuid>",
  "statusCode": 400
}

integration 2Identity provider — RP client secret

C002-2404RP client not found in Lina's identity provider.Cross-cuttingCONTACT_SUPPORT

2 scenario(s) · endpoint Identity provider — RP client secret · the same code covers different scenarios: read message[] to tell them apart

404CONTACT_SUPPORTinferredLina support

Message: Client Not Found
What happened: RP client not found in Lina's identity provider.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

404CONTACT_SUPPORTinferredLina support

Message: Client Not Found
What happened: RP client not found in Lina's identity provider.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Client Not Found"
  ],
  "type": "error",
  "errorCode": "C002-2",
  "traceId": "<uuid>",
  "statusCode": 404
}

GManagement: tenants, sub-tenants, accounts, users, features27 codes

route 3PATCH /tenants/:tenantId

G002-3404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /tenants/:tenantId

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant with tenantId:'<tenantId>' not found.
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Tenant with tenantId:'<tenantId>' not found."
  ],
  "type": "error",
  "errorCode": "G002-3",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 8POST /sub-tenants

G003-8400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

2 scenario(s) · endpoint POST /sub-tenants · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: Tenant with tenantId:'<tenantClientId>' not exists.
What happened: The request was rejected by an EPM validation rule.
Likely cause: Tenant with tenantId:'<tenantClientId>' not exists.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Sub Tenant with SubTenantId:'<subTenantId>' arread exist.
What happened: The request was rejected by an EPM validation rule.
Likely cause: Sub Tenant with SubTenantId:'<subTenantId>' arread exist.
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Tenant with tenantId:'<tenantClientId>' not exists."
  ],
  "type": "error",
  "errorCode": "G003-8",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 9PATCH /sub-tenants

G002-9404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /sub-tenants

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-9",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 10POST /sub-tenants/domains

G002-10404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint POST /sub-tenants/domains

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-10",
  "traceId": "<uuid>",
  "statusCode": 404
}

G003-10400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint POST /sub-tenants/domains

400RETRY_AFTER_FIXinferredIntegrator

Message: Domain already added to this subTenant:'<subTenantId>'.
What happened: The request was rejected by an EPM validation rule.
Likely cause: Domain already added to this subTenant:'<subTenantId>'.
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Domain already added to this subTenant:'<subTenantId>'."
  ],
  "type": "error",
  "errorCode": "G003-10",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 11GET /sub-tenants

G002-11404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

6 scenario(s) · endpoint GET /sub-tenants · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: ConsentId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with ConsentId <consentId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: EnrollmentId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with EnrollmentId <enrollmentId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-11",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 12GET /sub-tenants/lina/:subTenantId

G002-12404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /sub-tenants/lina/:subTenantId

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-12",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 13GET /sub-tenants/:subTenantId/participants/most-used

G002-13404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /sub-tenants/:subTenantId/participants/most-used

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenantId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "SubTenantId must be informed"
  ],
  "type": "error",
  "errorCode": "G002-13",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 16PATCH /sub-tenants/:subTenantId/deactivate

G002-16404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /sub-tenants/:subTenantId/deactivate

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-16",
  "traceId": "<uuid>",
  "statusCode": 404
}

G003-16400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /sub-tenants/:subTenantId/deactivate

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> is already deactivated
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with subTenantId <subTenantId> is already deactivated
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> is already deactivated"
  ],
  "type": "error",
  "errorCode": "G003-16",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 17PATCH /sub-tenants/:subTenantId/reactivate

G002-17404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /sub-tenants/:subTenantId/reactivate

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-17",
  "traceId": "<uuid>",
  "statusCode": 404
}

G003-17400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /sub-tenants/:subTenantId/reactivate · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> is already active
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with subTenantId <subTenantId> is already active
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> cannot be reactivated while its tenant is inactive
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with subTenantId <subTenantId> cannot be reactivated while its tenant is inactive
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> is already active"
  ],
  "type": "error",
  "errorCode": "G003-17",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 18PATCH /sub-tenants/:subTenantId/participants-preference

G002-18404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /sub-tenants/:subTenantId/participants-preference

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-18",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 20GET /sub-tenants-accounts/bank-identifiers/:ispb

G002-20404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /sub-tenants-accounts/bank-identifiers/:ispb

404RETRY_AFTER_FIXinferredIntegrator

Message: Bank identifier with ISPB <ispb> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Bank identifier with ISPB <ispb> not found"
  ],
  "type": "error",
  "errorCode": "G002-20",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 21POST /sub-tenants-accounts/:subTenantId/receiving-accounts

G002-21404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint POST /sub-tenants-accounts/:subTenantId/receiving-accounts

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "G002-21",
  "traceId": "<uuid>",
  "statusCode": 404
}

G003-21400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint POST /sub-tenants-accounts/:subTenantId/receiving-accounts

400RETRY_AFTER_FIXinferredIntegrator

Message: ISPB <ispb> is not registered in the bank identifier catalog
What happened: The request was rejected by an EPM validation rule.
Likely cause: ISPB <ispb> is not registered in the bank identifier catalog
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "ISPB <ispb> is not registered in the bank identifier catalog"
  ],
  "type": "error",
  "errorCode": "G003-21",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 23GET /sub-tenants-accounts/:subTenantId/receiving-accounts/:accountId

G002-23404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /sub-tenants-accounts/:subTenantId/receiving-accounts/:accountId

404RETRY_AFTER_FIXinferredIntegrator

Message: Receiving account <accountId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Receiving account <accountId> not found"
  ],
  "type": "error",
  "errorCode": "G002-23",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 24PATCH /sub-tenants-accounts/:subTenantId/receiving-accounts/:accountId

G002-24404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /sub-tenants-accounts/:subTenantId/receiving-accounts/:accountId

404RETRY_AFTER_FIXinferredIntegrator

Message: Receiving account <accountId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Receiving account <accountId> not found"
  ],
  "type": "error",
  "errorCode": "G002-24",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 25DELETE /sub-tenants-accounts/:subTenantId/receiving-accounts/:accountId

G002-25404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint DELETE /sub-tenants-accounts/:subTenantId/receiving-accounts/:accountId

404RETRY_AFTER_FIXinferredIntegrator

Message: Receiving account <accountId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Receiving account <accountId> not found"
  ],
  "type": "error",
  "errorCode": "G002-25",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 26POST /users

G002-26404The tenant/sub-tenant registration required for the operation was not found or is incomplete.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint POST /users

404RETRY_AFTER_FIXinferredIntegrator

Message: User created not found in Keycloak
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "User created not found in Keycloak"
  ],
  "type": "error",
  "errorCode": "G002-26",
  "traceId": "<uuid>",
  "statusCode": 404
}

G003-26400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

2 scenario(s) · endpoint POST /users · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to create a user with this tenant
What happened: The request was rejected by an EPM validation rule.
Likely cause: You do not have permission to create a user with this tenant
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to create a user with these groups
What happened: The request was rejected by an EPM validation rule.
Likely cause: You do not have permission to create a user with these groups
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "You do not have permission to create a user with this tenant"
  ],
  "type": "error",
  "errorCode": "G003-26",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 27GET /users

G003-27400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /users

400RETRY_AFTER_FIXinferredIntegrator

Message: pageSize cannot exceed 50 users per request
What happened: The request was rejected by an EPM validation rule.
Likely cause: pageSize cannot exceed 50 users per request
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "pageSize cannot exceed 50 users per request"
  ],
  "type": "error",
  "errorCode": "G003-27",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 30PUT /users/:userId/disable

G004-30403The resource belongs to another tenant or sub-tenant.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PUT /users/:userId/disable

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to disable this user. Tenant mismatch.
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "You do not have permission to disable this user. Tenant mismatch."
  ],
  "type": "error",
  "errorCode": "G004-30",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 31GET /users/:userId/groups

G004-31403The resource belongs to another tenant or sub-tenant.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /users/:userId/groups

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to fetch groups. Tenant mismatch.
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "You do not have permission to fetch groups. Tenant mismatch."
  ],
  "type": "error",
  "errorCode": "G004-31",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 32PUT /users/:userId

G004-32403The resource belongs to another tenant or sub-tenant.Portal / tenant managementRETRY_AFTER_FIX

3 scenario(s) · endpoint PUT /users/:userId · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to edit this user. Tenant mismatch.
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403RETRY_AFTER_FIXinferredIntegrator

Message: You can only assign users to your own tenant.
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403RETRY_AFTER_FIXinferredIntegrator

Message: You can only assign users to subtenants under your tenant.
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "You do not have permission to edit this user. Tenant mismatch."
  ],
  "type": "error",
  "errorCode": "G004-32",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 33PUT /users/:userId/profile

G004-33403The resource belongs to another tenant or sub-tenant.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PUT /users/:userId/profile

403RETRY_AFTER_FIXinferredIntegrator

Message: You do not have permission to edit this user. Tenant mismatch.
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "You do not have permission to edit this user. Tenant mismatch."
  ],
  "type": "error",
  "errorCode": "G004-33",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 34PUT /users/:userId/reset-password

G003-34400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint PUT /users/:userId/reset-password

400RETRY_AFTER_FIXinferredIntegrator

Message: User email is required to reset password
What happened: The request was rejected by an EPM validation rule.
Likely cause: User email is required to reset password
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "User email is required to reset password"
  ],
  "type": "error",
  "errorCode": "G003-34",
  "traceId": "<uuid>",
  "statusCode": 400
}

JJSR: enrollments and enrollment requests78 codes

route 1POST /jsr/enrollments

J001-1500Failure during enrollment creation or device registration; the account holder may already have created the resource. · Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

3 scenario(s) · endpoint POST /jsr/enrollments · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: There was an internal error in the create enrollment function
What happened: Failure during enrollment creation or device registration; the account holder may already have created the resource.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Error altering payment request: <internal technical detail>
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Error finding payment request: <internal technical detail>
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the create enrollment function"
  ],
  "type": "error",
  "errorCode": "J001-1",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-1404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

5 scenario(s) · endpoint POST /jsr/enrollments · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: User not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-1",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-1400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

10 scenario(s) · endpoint POST /jsr/enrollments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: organisationId, authorisationServerId, enrollment, riskSignals, redirectUri; optional: paymentId, automaticPaymentId, enrollmentRequestId, businessType, businessIdentity, productType.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field enrollment is required in the request body
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field enrollment is required in the request body
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field riskSignals is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field riskSignals is required
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: O header X-Client-IP deve ser informado
What happened: The request was rejected by an EPM validation rule.
Likely cause: O header X-Client-IP deve ser informado
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: O header X-Client-IP deve ser informado
What happened: The request was rejected by an EPM validation rule.
Likely cause: O header X-Client-IP deve ser informado
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields paymentId and automaticPaymentId cannot be informed at the same time
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields paymentId and automaticPaymentId cannot be informed at the same time
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field enrollmentRequestId cannot be informed with paymentId or automaticPaymentId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field enrollmentRequestId cannot be informed with paymentId or automaticPaymentId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: O header X-Client-IP deve ser informado
What happened: The request was rejected by an EPM validation rule.
Likely cause: O header X-Client-IP deve ser informado
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: The request was rejected by an EPM validation rule.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-1",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-1403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-1",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 2POST /jsr/enrollments/validate

J001-2500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/validate

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: There was an internal error in the validate enrollment function
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the validate enrollment function"
  ],
  "type": "error",
  "errorCode": "J001-2",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-2404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /jsr/enrollments/validate · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "Tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-2",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-2400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/enrollments/validate · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: state, code, idToken, tenantId, platform; optional: rp.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: O campo tenantId deve ser informado
What happened: The request was rejected by an EPM validation rule.
Likely cause: O campo tenantId deve ser informado
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-2",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-2403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/validate

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-2",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 3POST /jsr/enrollments/:enrollmentId/device/options

J001-3500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device/options · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Internal problem in the function that saves the enrollment user
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: There was an internal error in the register device options function
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that saves the enrollment user"
  ],
  "type": "error",
  "errorCode": "J001-3",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-3404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device/options · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: { id: registerOptions.data.user.id, username: enrollmentRequest.enrollmentCpf, }
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-3",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-3400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

6 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device/options · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: tenantId, platform; optional: rp.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields enrollmentId, tenantId, and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields enrollmentId, tenantId, and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-3",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-3403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device/options

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-3",
  "traceId": "<uuid>",
  "statusCode": 403
}

J005-3409The enrollment user already exists.DO_NOT_RETRY

1 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device/options

409DO_NOT_RETRYinferredIntegrator

Message: The user already exists
What happened: The enrollment user already exists.
Likely cause: The user already exists
What to do: Do not recreate the user; continue the flow with the existing user (GET /jsr/enrollments/users/:userName).

Example response:

{
  "message": [
    "The user already exists"
  ],
  "type": "error",
  "errorCode": "J005-3",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 4POST /jsr/enrollments/device/options

J001-4500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint POST /jsr/enrollments/device/options · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Internal problem in the function that saves the enrollment user
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: There was an internal error in the generate register device options function
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that saves the enrollment user"
  ],
  "type": "error",
  "errorCode": "J001-4",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-4404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/enrollments/device/options · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: { id: registerOptions.data.user.id, username: enrollmentOrm.enrollmentCpf, }
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-4",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-4400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

5 scenario(s) · endpoint POST /jsr/enrollments/device/options · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: state, code, idToken, tenantId, platform; optional: rp.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields tenantId and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields tenantId and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-4",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-4403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/device/options

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-4",
  "traceId": "<uuid>",
  "statusCode": 403
}

J005-4409The enrollment user already exists.DO_NOT_RETRY

1 scenario(s) · endpoint POST /jsr/enrollments/device/options

409DO_NOT_RETRYinferredIntegrator

Message: The user already exists
What happened: The enrollment user already exists.
Likely cause: The user already exists
What to do: Do not recreate the user; continue the flow with the existing user (GET /jsr/enrollments/users/:userName).

Example response:

{
  "message": [
    "The user already exists"
  ],
  "type": "error",
  "errorCode": "J005-4",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 5POST /jsr/enrollments/:enrollmentId/device

J001-5500Failure during enrollment creation or device registration; the account holder may already have created the resource.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: There was an internal error in the register device function
What happened: Failure during enrollment creation or device registration; the account holder may already have created the resource.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the register device function"
  ],
  "type": "error",
  "errorCode": "J001-5",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-5404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-5",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-5400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

6 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: id, rawId, response; optional: type, authenticatorAttachment, clientExtensionResults.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields enrollmentId, tenantId, and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields enrollmentId, tenantId, and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-5",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-5403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/:enrollmentId/device

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-5",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 6POST /jsr/consents

J001-6500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

4 scenario(s) · endpoint POST /jsr/consents · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the create consent and FIDO sign options function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error creating payment: <internal technical detail>
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error altering payment request: <internal technical detail>
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error altering payment request: <internal technical detail>
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the create consent and FIDO sign options function"
  ],
  "type": "error",
  "errorCode": "J001-6",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-6404The requested resource was not found.RETRY_AFTER_FIX

7 scenario(s) · endpoint POST /jsr/consents · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: The FIDO sign options (fidoSignOptions) were not generated
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Error alter status payment: <internal technical detail>
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "The FIDO sign options (fidoSignOptions) were not generated"
  ],
  "type": "error",
  "errorCode": "J002-6",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-6400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

22 scenario(s) · endpoint POST /jsr/consents · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: fidoSignOptions, enrollmentId; optional: organisationId, authorisationServerId, paymentId, automaticPaymentRequestId, payment, automaticPaymentRequest.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields subTenantId, clientIp, and enrollmentId must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields subTenantId, clientIp, and enrollmentId must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have a registered passKeyId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have a registered passKeyId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Unknown schedule type: <type>
What happened: The request was rejected by an EPM validation rule.
Likely cause: Unknown schedule type: <type>
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Unknown schedule type: <type>
What happened: The request was rejected by an EPM validation rule.
Likely cause: Unknown schedule type: <type>
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Unknown schedule type: <type>
What happened: The request was rejected by an EPM validation rule.
Likely cause: Unknown schedule type: <type>
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: No valid schedule field was filled, or more than one field was filled.
What happened: The request was rejected by an EPM validation rule.
Likely cause: No valid schedule field was filled, or more than one field was filled.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: No valid schedule field was filled, or more than one field was filled.
What happened: The request was rejected by an EPM validation rule.
Likely cause: No valid schedule field was filled, or more than one field was filled.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The txId must match the quantity of Payments".
What happened: The request was rejected by an EPM validation rule.
Likely cause: The txId must match the quantity of Payments".
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The originalRecurringPaymentId cannot be used with a scheduled payment. Please use the originalRecurringPaymentId only for one-time payments.
What happened: The request was rejected by an EPM validation rule.
Likely cause: The originalRecurringPaymentId cannot be used with a scheduled payment. Please use the originalRecurringPaymentId only for one-time payments.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The originalRecurringPaymentId <originalRecurringPaymentId> does not exist.
What happened: The request was rejected by an EPM validation rule.
Likely cause: The originalRecurringPaymentId <originalRecurringPaymentId> does not exist.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The originalRecurringPaymentId <originalRecurringPaymentId> is not allowed to be used for a new payment.
What happened: The request was rejected by an EPM validation rule.
Likely cause: The originalRecurringPaymentId <originalRecurringPaymentId> is not allowed to be used for a new payment.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: id must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: id must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: updatePaymentStatus must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: updatePaymentStatus must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Tenant CNPJ must be informed to generate payment endToEndId
What happened: The request was rejected by an EPM validation rule.
Likely cause: Tenant CNPJ must be informed to generate payment endToEndId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Schedule must be informed for scheduled payments
What happened: The request was rejected by an EPM validation rule.
Likely cause: Schedule must be informed for scheduled payments
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Date is not within the allowed range D+1 and D+730.
What happened: The request was rejected by an EPM validation rule.
Likely cause: Date is not within the allowed range D+1 and D+730.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: No valid schedule field was filled, or more than one field was filled.
What happened: The request was rejected by an EPM validation rule.
Likely cause: No valid schedule field was filled, or more than one field was filled.
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-6",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 7POST /jsr/automatic-consents

J001-7500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/automatic-consents

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the create automatic consent and FIDO sign options function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the create automatic consent and FIDO sign options function"
  ],
  "type": "error",
  "errorCode": "J001-7",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-7404The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/automatic-consents · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: The FIDO sign options (fidoSignOptions) were not generated
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "The FIDO sign options (fidoSignOptions) were not generated"
  ],
  "type": "error",
  "errorCode": "J002-7",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-7400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

8 scenario(s) · endpoint POST /jsr/automatic-consents · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: fidoSignOptions, enrollmentId, organisationId, authorisationServerId, automaticPaymentRequestId.

400RETRY_AFTER_FIXinferredIntegrator

Message: Automatic payment cannot be created because it is not in pending status
What happened: The request was rejected by an EPM validation rule.
Likely cause: Automatic payment cannot be created because it is not in pending status
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: automaticPaymentRequestId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: automaticPaymentRequestId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields subTenantId, clientIp, enrollmentId, and automaticPaymentRequestId must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields subTenantId, clientIp, enrollmentId, and automaticPaymentRequestId must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have a registered passKeyId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have a registered passKeyId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-7",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 8POST /jsr/payments

J001-8500Failed to authorize the consent and make the payment with biometrics.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/payments

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the authorize consent and make payment function
What happened: Failed to authorize the consent and make the payment with biometrics.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the authorize consent and make payment function"
  ],
  "type": "error",
  "errorCode": "J001-8",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-8404The requested resource was not found. · The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/payments · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment request not found"
  ],
  "type": "error",
  "errorCode": "J002-8",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-8400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

8 scenario(s) · endpoint POST /jsr/payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: enrollmentId, riskSignals, fidoAssertion; optional: paymentRequestId, automaticPaymentRequestId.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field paymentRequestId is required and automaticPaymentRequestId is not accepted on this route
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field paymentRequestId is required and automaticPaymentRequestId is not accepted on this route
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenant must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenant must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment request does not have a consentId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment request does not have a consentId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment request does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment request does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-8",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 9POST /jsr/automatic-payments

J001-9500Failed to authorize the consent and make the payment with biometrics.SAFE_RETRY/CONTACT_SUPPORT

3 scenario(s) · endpoint POST /jsr/automatic-payments · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Failed to authorize the consent and make the payment with biometrics.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error updating automatic payment request: <internal technical detail>
What happened: Failed to authorize the consent and make the payment with biometrics.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the authorize automatic consent and make automatic payment function
What happened: Failed to authorize the consent and make the payment with biometrics.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "J001-9",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-9404The requested resource was not found. · The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

6 scenario(s) · endpoint POST /jsr/automatic-payments · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: ConsentId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment with ConsentId <consentId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request with ID <apr> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "ConsentId must be informed"
  ],
  "type": "error",
  "errorCode": "J002-9",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-9400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

9 scenario(s) · endpoint POST /jsr/automatic-payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: enrollmentId, automaticPaymentRequestId, riskSignals, fidoAssertion.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field automaticPaymentRequestId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field automaticPaymentRequestId is required
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field paymentRequestId is not accepted on this route
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field paymentRequestId is not accepted on this route
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenant must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenant must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment request does not have a consentId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment request does not have a consentId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment request does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment request does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-9",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-9403The automatic payment request belongs to another sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /jsr/automatic-payments

403RETRY_AFTER_FIXconfirmedIntegrator

Message: The automatic payment request does not belong to the authenticated sub-tenant
What happened: The automatic payment request belongs to another sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the sub-tenant that owns the request.

Example response:

{
  "message": [
    "The automatic payment request does not belong to the authenticated sub-tenant"
  ],
  "type": "error",
  "errorCode": "J004-9",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 11GET /jsr/enrollments/:enrollmentId

J001-11500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the find enrollment function
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the find enrollment function"
  ],
  "type": "error",
  "errorCode": "J001-11",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-11404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-11",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-11400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

4 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields enrollmentId and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields enrollmentId and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "enrollmentId must be informed"
  ],
  "type": "error",
  "errorCode": "J003-11",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-11403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-11",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 12GET /jsr/enrollments/:enrollmentId/challenge

J002-12404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId/challenge · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found or without a registered passKeyId
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-12",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-12400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

3 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId/challenge · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: rp must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: rp must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "enrollmentId must be informed"
  ],
  "type": "error",
  "errorCode": "J003-12",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 13GET /jsr/enrollments/:enrollmentId/payments

J002-13404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId/payments · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-13",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-13400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

6 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId/payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — optional: cancelDataConsent.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: filters.startDate as string
What happened: The request was rejected by an EPM validation rule.
Likely cause: filters.startDate as string
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: filters.endDate as string
What happened: The request was rejected by an EPM validation rule.
Likely cause: filters.endDate as string
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: startDate must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: startDate must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-13",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-13403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /jsr/enrollments/:enrollmentId/payments

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "J004-13",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 14PUT /jsr/enrollments/:enrollmentId

J001-14500Internal EPM failure.Portal / tenant managementSAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PUT /jsr/enrollments/:enrollmentId

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: There was an internal error in the update enrollment function
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the update enrollment function"
  ],
  "type": "error",
  "errorCode": "J001-14",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-14404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

2 scenario(s) · endpoint PUT /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-14",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-14400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

5 scenario(s) · endpoint PUT /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields enrollmentId, tenantId, and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields enrollmentId, tenantId, and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "enrollmentId must be informed"
  ],
  "type": "error",
  "errorCode": "J003-14",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-14403The EPM could not authenticate with the account holder institution.Portal / tenant managementCONTACT_SUPPORT

1 scenario(s) · endpoint PUT /jsr/enrollments/:enrollmentId

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-14",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 15PATCH /jsr/enrollments/:enrollmentId

J001-15500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the revoke enrollment function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the revoke enrollment function"
  ],
  "type": "error",
  "errorCode": "J001-15",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-15404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-15",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-15400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

7 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — optional: cancelDataConsent.

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: X-Client-IP must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: X-Client-IP must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields enrollmentId, tenantId, and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields enrollmentId, tenantId, and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have an organisationId/authorisationServerId
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have an organisationId/authorisationServerId
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The fields enrollmentId, tenantId, and clientIp must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: The fields enrollmentId, tenantId, and clientIp must be provided
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-15",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-15403The EPM could not authenticate with the account holder institution.CONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId · the same code covers different scenarios: read message[] to tell them apart

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

403CONTACT_SUPPORTinferredLina support

Message: Could not authenticate with the holder institution
What happened: The EPM could not authenticate with the account holder institution.
Likely cause: Failed to obtain the RP client token (EPM credentials/certificate with the account holder). Does not depend on the integrator's request.
What to do: Do not retry in a loop. Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "Could not authenticate with the holder institution"
  ],
  "type": "error",
  "errorCode": "J004-15",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 16PATCH /jsr/enrollments/:enrollmentId/data-consent/cancel

J001-16500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId/data-consent/cancel

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: There was an internal error in the cancel data consent function
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "There was an internal error in the cancel data consent function"
  ],
  "type": "error",
  "errorCode": "J001-16",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-16404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId/data-consent/cancel

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Enrollment not found"
  ],
  "type": "error",
  "errorCode": "J002-16",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-16400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

3 scenario(s) · endpoint PATCH /jsr/enrollments/:enrollmentId/data-consent/cancel · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollmentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollmentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: tenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: tenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The enrollment does not have a dataConsentId to cancel
What happened: The request was rejected by an EPM validation rule.
Likely cause: The enrollment does not have a dataConsentId to cancel
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "enrollmentId must be informed"
  ],
  "type": "error",
  "errorCode": "J003-16",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 17POST /jsr/enrollments/users

J001-17500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /jsr/enrollments/users

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Internal problem in the function that saves the enrollment user
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Internal problem in the function that saves the enrollment user"
  ],
  "type": "error",
  "errorCode": "J001-17",
  "traceId": "<uuid>",
  "statusCode": 500
}

J002-17404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /jsr/enrollments/users

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-17",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-17400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/enrollments/users · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: id, username.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: username must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: username must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-17",
  "traceId": "<uuid>",
  "statusCode": 400
}

J005-17409The enrollment user already exists.DO_NOT_RETRY

1 scenario(s) · endpoint POST /jsr/enrollments/users

409DO_NOT_RETRYinferredIntegrator

Message: The user already exists
What happened: The enrollment user already exists.
Likely cause: The user already exists
What to do: Do not recreate the user; continue the flow with the existing user (GET /jsr/enrollments/users/:userName).

Example response:

{
  "message": [
    "The user already exists"
  ],
  "type": "error",
  "errorCode": "J005-17",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 18GET /jsr/enrollments/users/:userName

J002-18404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint GET /jsr/enrollments/users/:userName · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Sub-tenant not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment user not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Sub-tenant not found"
  ],
  "type": "error",
  "errorCode": "J002-18",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-18400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /jsr/enrollments/users/:userName · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: username must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: username must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "subTenantId must be informed"
  ],
  "type": "error",
  "errorCode": "J003-18",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-18403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /jsr/enrollments/users/:userName

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "J004-18",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 19POST /jsr/enrollment-requests

J002-19404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /jsr/enrollment-requests

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "J002-19",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-19400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

4 scenario(s) · endpoint POST /jsr/enrollment-requests · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — optional: document, businessIdentity, displayMode, redirectUri, externalId.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field document (CPF of the representative) is required when businessIdentity is informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field document (CPF of the representative) is required when businessIdentity is informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field redirectUri must contain a valid URL
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field redirectUri must contain a valid URL
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-19",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-19403The resource belongs to another tenant or sub-tenant. · The enrollment-without-payment feature is not enabled for the sub-tenant.RETRY_AFTER_FIXCONTACT_SUPPORT

2 scenario(s) · endpoint POST /jsr/enrollment-requests · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403CONTACT_SUPPORTconfirmedLina support

Message: The sub-tenant does not have the <ENROLLMENT_STANDALONE_FEATURE> feature
What happened: The enrollment-without-payment feature is not enabled for the sub-tenant.
Likely cause: The API client does not have the role required by the route, or the feature is not enabled for the sub-tenant.
What to do: Ask Lina to enable the feature.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "J004-19",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 20GET /jsr/enrollment-requests/:enrollmentRequestId

J002-20404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /jsr/enrollment-requests/:enrollmentRequestId

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Enrollment request not found"
  ],
  "type": "error",
  "errorCode": "J002-20",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-20400A path identifier is not a valid UUID.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /jsr/enrollment-requests/:enrollmentRequestId

400RETRY_AFTER_FIXconfirmedIntegrator

Message: enrollmentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: enrollmentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

Example response:

{
  "message": [
    "enrollmentRequestId must be a valid UUID."
  ],
  "type": "error",
  "errorCode": "J003-20",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-20403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /jsr/enrollment-requests/:enrollmentRequestId

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "J004-20",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 21PATCH /jsr/enrollment-requests/:enrollmentRequestId/cancel

J002-21404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/cancel

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Enrollment request not found"
  ],
  "type": "error",
  "errorCode": "J002-21",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-21400A path identifier is not a valid UUID.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/cancel

400RETRY_AFTER_FIXconfirmedIntegrator

Message: enrollmentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: enrollmentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

Example response:

{
  "message": [
    "enrollmentRequestId must be a valid UUID."
  ],
  "type": "error",
  "errorCode": "J003-21",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-21403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/cancel

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "J004-21",
  "traceId": "<uuid>",
  "statusCode": 403
}

J005-21409The enrollment request is already in a final state and cannot be cancelled.DO_NOT_RETRY

1 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/cancel

409DO_NOT_RETRYconfirmedIntegrator

Message: An enrollment request with status <status> cannot be cancelled
What happened: The enrollment request is already in a final state and cannot be cancelled.
Likely cause: An enrollment request with status <status> cannot be cancelled
What to do: Query the request (GET /jsr/enrollment-requests/:id). Cancelling a request that is already CANCELADO returns success.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "An enrollment request with status <status> cannot be cancelled"
  ],
  "type": "error",
  "errorCode": "J005-21",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 22PATCH /jsr/enrollment-requests/:enrollmentRequestId/document

J002-22404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/document

404RETRY_AFTER_FIXinferredIntegrator

Message: Enrollment request not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Enrollment request not found"
  ],
  "type": "error",
  "errorCode": "J002-22",
  "traceId": "<uuid>",
  "statusCode": 404
}

J003-22400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +1RETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/document · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: document; optional: businessIdentity.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: enrollmentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: enrollmentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field document must be a valid CPF
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field document must be a valid CPF
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The field businessIdentity must be a valid CNPJ
What happened: The request was rejected by an EPM validation rule.
Likely cause: The field businessIdentity must be a valid CNPJ
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "J003-22",
  "traceId": "<uuid>",
  "statusCode": 400
}

J004-22403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/document

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "J004-22",
  "traceId": "<uuid>",
  "statusCode": 403
}

J005-22409The document can only be provided while the request is PENDENTE. · The enrollment request already has a document.DO_NOT_RETRY

2 scenario(s) · endpoint PATCH /jsr/enrollment-requests/:enrollmentRequestId/document · the same code covers different scenarios: read message[] to tell them apart

409DO_NOT_RETRYconfirmedIntegrator

Message: The document of an enrollment request with status <status> cannot be changed
What happened: The document can only be provided while the request is PENDENTE.
Likely cause: The document of an enrollment request with status <status> cannot be changed
What to do: Query the request. If it has expired or been cancelled, create a new enrollment request.

409DO_NOT_RETRYconfirmedIntegrator

Message: The enrollment request already has a document
What happened: The enrollment request already has a document.
Likely cause: The enrollment request already has a document
What to do: Do not send it again; continue to POST /jsr/enrollments with the enrollmentRequestId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "The document of an enrollment request with status <status> cannot be changed"
  ],
  "type": "error",
  "errorCode": "J005-22",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 23POST /jsr/enrollments (with enrollmentRequestId)

J002-23404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /jsr/enrollments (with enrollmentRequestId)

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

J005-23409The enrollment request status does not allow starting the enrollment. · The enrollment request has expired. · +1DO_NOT_RETRYRETRY_AFTER_FIX

3 scenario(s) · endpoint POST /jsr/enrollments (with enrollmentRequestId) · the same code covers different scenarios: read message[] to tell them apart

409DO_NOT_RETRYconfirmedIntegrator

Message: An enrollment request with status <status> cannot start an enrollment
What happened: The enrollment request status does not allow starting the enrollment.
Likely cause: An enrollment request with status <status> cannot start an enrollment
What to do: Query the request; if it is in a final state, create a new one.

409DO_NOT_RETRYconfirmedIntegrator

Message: The enrollment request has expired
What happened: The enrollment request has expired.
Likely cause: The enrollment request has expired
What to do: Create a new enrollment request (POST /jsr/enrollment-requests).

409RETRY_AFTER_FIXconfirmedIntegrator

Message: The enrollment request has no user document yet
What happened: The enrollment request does not have the user's document yet.
Likely cause: The enrollment request has no user document yet
What to do: Provide the document (PATCH /jsr/enrollment-requests/:id/document) and try again.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "An enrollment request with status <status> cannot start an enrollment"
  ],
  "type": "error",
  "errorCode": "J005-23",
  "traceId": "<uuid>",
  "statusCode": 409
}

PPayments: open-integration and /payments73 codes

route 1GET /open-integration/participants/available

P001-1500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /open-integration/participants/available

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error find subTenant: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error find subTenant: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-1",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-1404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /open-integration/participants/available · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenantId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found"
  ],
  "type": "error",
  "errorCode": "P002-1",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-1400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /open-integration/participants/available

400RETRY_AFTER_FIXinferredIntegrator

Message: Payment ID or payment DTO must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: Payment ID or payment DTO must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Payment ID or payment DTO must be informed"
  ],
  "type": "error",
  "errorCode": "P003-1",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 2GET /open-integration/participants/registered

P001-2500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /open-integration/participants/registered

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error find subTenant: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error find subTenant: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-2",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-2404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /open-integration/participants/registered

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenantId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "SubTenantId must be informed"
  ],
  "type": "error",
  "errorCode": "P002-2",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 3POST /open-integration/consents

P002-3404The requested resource was not found. · The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /open-integration/consents · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment request not found: <paymentRequestId>
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant not found: <tenantId>
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Payment request not found: <paymentRequestId>"
  ],
  "type": "error",
  "errorCode": "P002-3",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-3400The request body or parameters failed format validation. · The payment request has already been consumed (paid). · +2RETRY_AFTER_FIXDO_NOT_RETRY

6 scenario(s) · endpoint POST /open-integration/consents · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: organisationId, authorisationServerId; optional: paymentId, payment, redirectUri, platform.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payment already consumed: <paymentRequestId>
What happened: The payment request has already been consumed (paid).
Likely cause: The request has already generated a payment.
What to do: Do not create another consent for this request. Check the result (GET /payments/consents/:consentId/external or GET /payments/requests/:paymentRequestId). To charge again, create a new request.

400DO_NOT_RETRYconfirmedIntegrator

Message: Payment request expired: <paymentRequestId>
What happened: The payment request has expired.
Likely cause: The request deadline (requestExpiresAt) has passed.
What to do: Create a new payment request (POST /payments) and restart the journey with the user.

400RETRY_AFTER_FIXinferredIntegrator

Message: The payment value is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: The payment value is required
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: qrCode must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: qrCode must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: url must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: url must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "P003-3",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 4PATCH /open-integration/consents/:consentId/payments/cancel

P001-4500Failed to cancel at the account holder (timeout, 5xx, or unconfirmed rejection).SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /open-integration/consents/:consentId/payments/cancel · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error cancel consent payment: <internal technical detail>
What happened: Failed to cancel at the account holder (timeout, 5xx, or unconfirmed rejection).
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Failed to cancel at the account holder (timeout, 5xx, or unconfirmed rejection).
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error cancel consent payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-4",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-4404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /open-integration/consents/:consentId/payments/cancel · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: ConsentId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "ConsentId must be informed"
  ],
  "type": "error",
  "errorCode": "P002-4",
  "traceId": "<uuid>",
  "statusCode": 404
}

P004-4403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /open-integration/consents/:consentId/payments/cancel · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403RETRY_AFTER_FIXinferredIntegrator

Message: Payment request does not belong to the subtenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-4",
  "traceId": "<uuid>",
  "statusCode": 403
}

P006-4409The consent has no cancellable payments.DO_NOT_RETRY

1 scenario(s) · endpoint PATCH /open-integration/consents/:consentId/payments/cancel

409DO_NOT_RETRYconfirmedIntegrator

Message: Consent with ID <consentId> has no cancellable payments
What happened: The consent has no cancellable payments.
Likely cause: Only PENDENTE, RECEBIDO, EM_PROCESSAMENTO, or PROGRAMADO payments can be cancelled.
What to do: Query the consent's payments; the other states are already final.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Consent with ID <consentId> has no cancellable payments"
  ],
  "type": "error",
  "errorCode": "P006-4",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 5POST /open-integration/validate

P001-5500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint POST /open-integration/validate · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Error in callback validate
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Error creating consent: <internal technical detail>
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response:

{
  "message": [
    "Error in callback validate"
  ],
  "type": "error",
  "errorCode": "P001-5",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-5404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /open-integration/validate · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant not found: <tenantId>
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant not found: <consentId>
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Tenant not found: <tenantId>"
  ],
  "type": "error",
  "errorCode": "P002-5",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 6POST /open-integration/error-callback/resolve

P002-6404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint POST /open-integration/error-callback/resolve · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant not found: <tenantId>
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: No consent resolved for state <state>
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: No payment record found for state <state>
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Tenant not found: <tenantId>"
  ],
  "type": "error",
  "errorCode": "P002-6",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 7POST /open-integration/consents/:consentId/payments

P001-7500Failed to create the payment at the account holder, or after creating it. The actual result may be unknown.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /open-integration/consents/:consentId/payments

500CONTACT_SUPPORTruleLina support

Message: Error creating consent: <internal technical detail>
What happened: Failed to create the payment at the account holder, or after creating it. The actual result may be unknown.
Likely cause: Timeout (30s), network error, or internal failure after the call to the account holder. The EPM marks the request as ERRO, but the payment may have been created without the externalPaymentId being saved.
What to do: External infrastructure failure (account holder). Do not retry the operation: contact Lina support with the traceId before offering a new payment to the user. To check the state, use GET /payments/consents/:consentId/external (CONSUMED means a payment was made).
Contact Lina: Yes, to resolve it. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error creating consent: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-7",
  "traceId": "<uuid>",
  "statusCode": 500
}

route 8POST /open-integration/payments

P001-8500Failed to create the payment at the account holder, or after creating it. The actual result may be unknown.CONTACT_SUPPORT

1 scenario(s) · endpoint POST /open-integration/payments

500CONTACT_SUPPORTruleLina support

Message: Error creating consent: <internal technical detail>
What happened: Failed to create the payment at the account holder, or after creating it. The actual result may be unknown.
Likely cause: Timeout (30s), network error, or internal failure after the call to the account holder. The EPM marks the request as ERRO, but the payment may have been created without the externalPaymentId being saved.
What to do: External infrastructure failure (account holder). Do not retry the operation: contact Lina support with the traceId before offering a new payment to the user. To check the state, use GET /payments/consents/:consentId/external (CONSUMED means a payment was made).
Contact Lina: Yes, to resolve it. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error creating consent: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-8",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-8404The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /open-integration/payments

404RETRY_AFTER_FIXinferredIntegrator

Message: Tenant not found: <tenantId>
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Tenant not found: <tenantId>"
  ],
  "type": "error",
  "errorCode": "P002-8",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 9PATCH /open-integration/payments/:paymentId/cancel

P001-9500Failed to cancel at the account holder (timeout, 5xx, or unconfirmed rejection).SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint PATCH /open-integration/payments/:paymentId/cancel · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error cancelling payment: <internal technical detail>
What happened: Failed to cancel at the account holder (timeout, 5xx, or unconfirmed rejection).
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Failed to cancel at the account holder (timeout, 5xx, or unconfirmed rejection).
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error cancelling payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-9",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-9404The tenant/sub-tenant registration required for the operation was not found or is incomplete. · The requested resource was not found.RETRY_AFTER_FIX

3 scenario(s) · endpoint PATCH /open-integration/payments/:paymentId/cancel · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P004-9403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /open-integration/payments/:paymentId/cancel · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403RETRY_AFTER_FIXinferredIntegrator

Message: Payment request does not belong to the subtenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-9",
  "traceId": "<uuid>",
  "statusCode": 403
}

P006-9409The payment is already cancelled.DO_NOT_RETRY

1 scenario(s) · endpoint PATCH /open-integration/payments/:paymentId/cancel

409DO_NOT_RETRYconfirmedIntegrator

Message: Payment with ID <paymentId> is already cancelled
What happened: The payment is already cancelled.
Likely cause: Payment with ID <paymentId> is already cancelled
What to do: Nada a fazer: trate como cancelado.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Payment with ID <paymentId> is already cancelled"
  ],
  "type": "error",
  "errorCode": "P006-9",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 10POST /payments

P001-10500Internal failure while creating the payment request.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint POST /payments

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error creating payment: <internal technical detail>
What happened: Internal failure while creating the payment request.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error creating payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-10",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-10404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /payments · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found / … has no tenant
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId <subTenantId> not found / … has no tenant
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId <subTenantId> not found / … has no tenant"
  ],
  "type": "error",
  "errorCode": "P002-10",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-10400The request was rejected by an EPM validation rule. · The request body or parameters failed format validation.RETRY_AFTER_FIX

18 scenario(s) · endpoint POST /payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: The data provided is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The data provided is invalid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The data provided is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The data provided is invalid
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: redirectUri, cpfCnpj, value, creditor; optional: details, externalId, qrCode, debitor, originalRecurringPaymentId, schedule, txId, requestExpiresAt, businessCnpj.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: qrCode must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: qrCode must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: qrPayload must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: qrPayload must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: redirectUri must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: redirectUri must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: cpfCnpj must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: cpfCnpj must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: accountIspb must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: accountIspb must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidDataMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: qrCode must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: qrCode must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: pixKey must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: pixKey must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "The data provided is invalid"
  ],
  "type": "error",
  "errorCode": "P003-10",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-10403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /payments

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-10",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 11PATCH /payments/:paymentId

P001-11500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /payments/:paymentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error creating payment: <internal technical detail>
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error creating payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-11",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-11404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /payments/:paymentId · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-11400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +1RETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /payments/:paymentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — optional: details, document, externalId, redirectUri, cpfCnpj, value, creditor, debitor, consentId, externalPaymentId.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: id must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: id must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: paymentDto must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: paymentDto must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "P003-11",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 12PATCH /payments/:paymentId/status

P001-12500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /payments/:paymentId/status

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error alter status payment: <internal technical detail>
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error alter status payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-12",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-12404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint PATCH /payments/:paymentId/status · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-12400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +1RETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /payments/:paymentId/status · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: status; optional: requestStatus, debitor, externalPaymentId, endToEndId, consentId, orgId, asId, cpfCnpj, localInstrument, apiVersion, paymentCancelledBy, rejectionReason, rejectionReasonDetail, cancellationReason, cancelledFrom, cancelledAt.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: id must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: id must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: updatePaymentStatus must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: updatePaymentStatus must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "P003-12",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 13GET /payments

P001-13500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint GET /payments · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error getting tenant: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payments: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error getting tenant: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-13",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-13404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenantId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "SubTenantId must be informed"
  ],
  "type": "error",
  "errorCode": "P002-13",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-13400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

6 scenario(s) · endpoint GET /payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided status filter is not a valid value
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided status filter is not a valid value
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: limitPerPage must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: limitPerPage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: page must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: page must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: startDate must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: startDate must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: endDate must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: endDate must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: startDateFormatted must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: startDateFormatted must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "The provided status filter is not a valid value"
  ],
  "type": "error",
  "errorCode": "P003-13",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-13403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments

403RETRY_AFTER_FIXinferredIntegrator

Message: The sub-tenant does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response:

{
  "message": [
    "The sub-tenant does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-13",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 14GET /payments/requests

P001-14500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/requests

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payments: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payments: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-14",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-14404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments/requests · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: SubTenantId must be informed
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "SubTenantId must be informed"
  ],
  "type": "error",
  "errorCode": "P002-14",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-14400The request body or parameters failed format validation. · The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

9 scenario(s) · endpoint GET /payments/requests · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Check the endpoint contract (Swagger) for the expected types.

400RETRY_AFTER_FIXinferredIntegrator

Message: Admin users must provide subTenantId or cpfCnpj
What happened: The request was rejected by an EPM validation rule.
Likely cause: Admin users must provide subTenantId or cpfCnpj
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided status filter has invalid value(s)
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided status filter has invalid value(s)
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided type filter has invalid value(s)
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided type filter has invalid value(s)
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: limitPerPage must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: limitPerPage must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: page must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: page must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: startDate must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: startDate must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: endDate must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: endDate must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: startDateFormatted must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: startDateFormatted must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "P003-14",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 15GET /payments/requests/:paymentRequestId

P001-15500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/requests/:paymentRequestId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment request: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payment request: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-15",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-15404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/requests/:paymentRequestId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-15400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/requests/:paymentRequestId

400RETRY_AFTER_FIXinferredIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: The request was rejected by an EPM validation rule.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "paymentRequestId must be a valid UUID."
  ],
  "type": "error",
  "errorCode": "P003-15",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-15403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/requests/:paymentRequestId

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-15",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 16PATCH /payments/requests/:paymentRequestId

P001-16500Internal EPM failure during an operation that may already have been sent to the account holder.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error updating payment request CPF/CNPJ: <internal technical detail>
What happened: Internal EPM failure during an operation that may already have been sent to the account holder.
Likely cause: Unexpected error. The EPM does not guarantee that nothing was created/changed before the failure.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error updating payment request CPF/CNPJ: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-16",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-16404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-16400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +1RETRY_AFTER_FIX

3 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: cpfCnpj.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided CPF/CNPJ data for the update is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided CPF/CNPJ data for the update is invalid
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "P003-16",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-16403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-16",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 17PATCH /payments/requests/:paymentRequestId/description

P001-17500Internal EPM failure.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId/description

500SAFE_RETRY/CONTACT_SUPPORTruleLina support

Message: Error updating payment request description: <internal technical detail>
What happened: Internal EPM failure.
Likely cause: Unexpected processing error.
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error updating payment request description: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-17",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-17404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId/description

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-17400The request body or parameters failed format validation. · A path identifier is not a valid UUID. · +1RETRY_AFTER_FIX

3 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId/description · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXconfirmedIntegrator

Message: List of validation messages, one per invalid field
What happened: The request body or parameters failed format validation.
Likely cause: Missing required field, wrong type, or invalid format. Each item in message[] names the field (nested fields appear as [parent].[child]: …).
What to do: Fix exactly the fields listed in message[] and resend. Request body — required: externalComment.

400RETRY_AFTER_FIXconfirmedIntegrator

Message: paymentRequestId must be a valid UUID.
What happened: A path identifier is not a valid UUID.
Likely cause: paymentRequestId must be a valid UUID.
What to do: Send the identifier in UUID format (e.g. 550e8400-e29b-41d4-a716-446655440000), exactly as returned by the API.

400RETRY_AFTER_FIXinferredIntegrator

Message: The provided description data is invalid
What happened: The request was rejected by an EPM validation rule.
Likely cause: The provided description data is invalid
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "List of validation messages, one per invalid field"
  ],
  "type": "error",
  "errorCode": "P003-17",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-17403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint PATCH /payments/requests/:paymentRequestId/description

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-17",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 18GET /payments/:paymentId/external

P002-18404The requested resource was not found. · The tenant/sub-tenant registration required for the operation was not found or is incomplete.RETRY_AFTER_FIX

5 scenario(s) · endpoint GET /payments/:paymentId/external · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The tenant/sub-tenant registration required for the operation was not found or is incomplete.
Likely cause: No sub-tenant exists for the identifier sent, or the registration has no tenant/CNPJ/configuration.
What to do: Check the subTenantId sent. If it is correct, contact Lina support: the registration needs to be completed.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment not found"
  ],
  "type": "error",
  "errorCode": "P002-18",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-18400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

4 scenario(s) · endpoint GET /payments/:paymentId/external · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: paymentId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: paymentId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "paymentId must be informed"
  ],
  "type": "error",
  "errorCode": "P003-18",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-18403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments/:paymentId/external · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

P005-18401The account holder institution rejected the authentication of the query made by the EPM.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/:paymentId/external

401CONTACT_SUPPORTinferredLina support

Message: The account holder institution rejected the call authentication
What happened: The account holder institution rejected the authentication of the query made by the EPM.
Likely cause: EPM credentials with the account holder. Does not depend on the integrator's token.
What to do: Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "The account holder institution rejected the call authentication"
  ],
  "type": "error",
  "errorCode": "P005-18",
  "traceId": "<uuid>",
  "statusCode": 401
}

P006-18409The account holder returned a conflict on the query.NOT_VALIDATED

1 scenario(s) · endpoint GET /payments/:paymentId/external

409NOT_VALIDATEDnot verifiedIntegrator

Message: The account holder institution returned a conflict when querying the payment
What happened: The account holder returned a conflict on the query.
Likely cause: The account holder institution returned a conflict when querying the payment
What to do: Wait a few seconds and query again; if it persists, contact Lina support.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "The account holder institution returned a conflict when querying the payment"
  ],
  "type": "error",
  "errorCode": "P006-18",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 19GET /payments/:paymentId

P001-19500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/:paymentId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-19",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-19404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/:paymentId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-19400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments/:paymentId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: id must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: id must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantClientId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantClientId must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "id must be informed"
  ],
  "type": "error",
  "errorCode": "P003-19",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-19403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/:paymentId

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-19",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 20GET /payments/consent/:consent_id

P001-20500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/consent/:consent_id

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-20",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-20404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments/consent/:consent_id · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: Payment not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Payment not found"
  ],
  "type": "error",
  "errorCode": "P002-20",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 21GET /payments/consents/:consentId/external

P002-21404The requested resource was not found.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments/consents/:consentId/external · the same code covers different scenarios: read message[] to tell them apart

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

404RETRY_AFTER_FIXinferredIntegrator

Message: Consent not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Consent not found"
  ],
  "type": "error",
  "errorCode": "P002-21",
  "traceId": "<uuid>",
  "statusCode": 404
}

P003-21400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/consents/:consentId/external

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

P004-21403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

2 scenario(s) · endpoint GET /payments/consents/:consentId/external · the same code covers different scenarios: read message[] to tell them apart

403RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

403RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

P005-21401The account holder institution rejected the authentication of the query made by the EPM.CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/consents/:consentId/external

401CONTACT_SUPPORTinferredLina support

Message: The account holder institution rejected the call authentication
What happened: The account holder institution rejected the authentication of the query made by the EPM.
Likely cause: EPM credentials with the account holder. Does not depend on the integrator's token.
What to do: Contact Lina support with the traceId.
Contact Lina: Yes, to resolve it. Include the traceId.

Example response:

{
  "message": [
    "The account holder institution rejected the call authentication"
  ],
  "type": "error",
  "errorCode": "P005-21",
  "traceId": "<uuid>",
  "statusCode": 401
}

P006-21409The account holder returned a conflict on the query.NOT_VALIDATED

1 scenario(s) · endpoint GET /payments/consents/:consentId/external

409NOT_VALIDATEDnot verifiedIntegrator

Message: The account holder institution returned a conflict when querying the consent
What happened: The account holder returned a conflict on the query.
Likely cause: The account holder institution returned a conflict when querying the consent
What to do: Wait a few seconds and query again; if it persists, contact Lina support.
Contact Lina: If it persists or the state is inconclusive. Include the traceId.

Example response:

{
  "message": [
    "The account holder institution returned a conflict when querying the consent"
  ],
  "type": "error",
  "errorCode": "P006-21",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 22GET /payments/external/:externalId

P001-22500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

1 scenario(s) · endpoint GET /payments/external/:externalId

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-22",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-22404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/external/:externalId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P004-22403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/external/:externalId

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-22",
  "traceId": "<uuid>",
  "statusCode": 403
}

route 23GET /payments/txid/:txId

P001-23500Internal EPM failure while processing the query.SAFE_RETRY/CONTACT_SUPPORT

2 scenario(s) · endpoint GET /payments/txid/:txId · the same code covers different scenarios: read message[] to tell them apart

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

500SAFE_RETRY/CONTACT_SUPPORTruleIntegrator

Message: Error finding payment: <internal technical detail>
What happened: Internal EPM failure while processing the query.
Likely cause: Unexpected processing error (database, internal dependency, or account holder).
What to do: Retry with backoff (2s, 4s, 8s), up to 3 attempts. If the error persists, contact Lina support with the traceId.
Contact Lina: Yes, if the error persists after 3 attempts. Include the traceId.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Error finding payment: <internal technical detail>"
  ],
  "type": "error",
  "errorCode": "P001-23",
  "traceId": "<uuid>",
  "statusCode": 500
}

P002-23404The requested resource was not found.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/txid/:txId

404RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

P003-23400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

3 scenario(s) · endpoint GET /payments/txid/:txId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: txId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: txId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantClientId must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantClientId must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: invalidTxIdMessage must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "txId must be informed"
  ],
  "type": "error",
  "errorCode": "P003-23",
  "traceId": "<uuid>",
  "statusCode": 400
}

P004-23403The resource belongs to another tenant or sub-tenant.RETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments/txid/:txId

403RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant <id> does not belong to the authenticated tenant
What happened: The resource belongs to another tenant or sub-tenant.
Likely cause: The subTenantId (or resource) provided does not belong to the tenant of the credentials used.
What to do: Use the credentials of the tenant that owns the resource, or fix the subTenantId sent.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant <id> does not belong to the authenticated tenant"
  ],
  "type": "error",
  "errorCode": "P004-23",
  "traceId": "<uuid>",
  "statusCode": 403
}

RReports5 codes

route 2GET /schedule-reports/daily

R003-2400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /schedule-reports/daily

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with id '<subTenantId>' not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with id '<subTenantId>' not found
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with id '<subTenantId>' not found"
  ],
  "type": "error",
  "errorCode": "R003-2",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 3GET /schedule-reports/summary

R003-3400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

4 scenario(s) · endpoint GET /schedule-reports/summary · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: startDate must be before or equal to endDate
What happened: The request was rejected by an EPM validation rule.
Likely cause: startDate must be before or equal to endDate
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Tenant with id '<userTenantId>' not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: Tenant with id '<userTenantId>' not found
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Access denied: SubTenant '<subTenantId>' does not belong to your tenant
What happened: The request was rejected by an EPM validation rule.
Likely cause: Access denied: SubTenant '<subTenantId>' does not belong to your tenant
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with id '<subTenantId>' not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with id '<subTenantId>' not found
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "startDate must be before or equal to endDate"
  ],
  "type": "error",
  "errorCode": "R003-3",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 4GET /schedule-reports/fails

R003-4400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

3 scenario(s) · endpoint GET /schedule-reports/fails · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: reportIds query parameter must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: reportIds query parameter must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: At least one report ID must be provided
What happened: The request was rejected by an EPM validation rule.
Likely cause: At least one report ID must be provided
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Tenant with id '<userTenantId>' not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: Tenant with id '<userTenantId>' not found
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "reportIds query parameter must be provided"
  ],
  "type": "error",
  "errorCode": "R003-4",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 7GET /payments-view/automatic-payment-request/:automaticPaymentRequestId/payments

R002-7404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments-view/automatic-payment-request/:automaticPaymentRequestId/payments

404RETRY_AFTER_FIXinferredIntegrator

Message: Automatic payment request <automaticPaymentRequestId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Automatic payment request <automaticPaymentRequestId> not found"
  ],
  "type": "error",
  "errorCode": "R002-7",
  "traceId": "<uuid>",
  "statusCode": 404
}

route 8GET /payments-view/automatic-payment/:automaticPaymentId/retried-payments

R002-8404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /payments-view/automatic-payment/:automaticPaymentId/retried-payments

404RETRY_AFTER_FIXinferredIntegrator

Message: Resource <automaticPaymentOrPaymentId> not found as automatic payment or payment
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Resource <automaticPaymentOrPaymentId> not found as automatic payment or payment"
  ],
  "type": "error",
  "errorCode": "R002-8",
  "traceId": "<uuid>",
  "statusCode": 404
}

WWebhooks: registration (tenant) and account holder notifications10 codes

route 1POST /webhooks

W003-1400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

3 scenario(s) · endpoint POST /webhooks · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId:'<subTenantId>' do not exists.
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with subTenantId:'<subTenantId>' do not exists.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Webhook with type:'<type>' already exists.
What happened: The request was rejected by an EPM validation rule.
Likely cause: Webhook with type:'<type>' already exists.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: toSave must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: toSave must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId:'<subTenantId>' do not exists."
  ],
  "type": "error",
  "errorCode": "W003-1",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 2PATCH /webhooks/:webhookId

W003-2400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

4 scenario(s) · endpoint PATCH /webhooks/:webhookId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId:'<subTenantId>' do not exists.
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with subTenantId:'<subTenantId>' do not exists.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: webhookId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: webhookId is required
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Webhook with ID <webhookId> not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: Webhook with ID <webhookId> not found
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: webhookReturn must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: webhookReturn must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "SubTenant with subTenantId:'<subTenantId>' do not exists."
  ],
  "type": "error",
  "errorCode": "W003-2",
  "traceId": "<uuid>",
  "statusCode": 400
}

W006-2409The current state of the resource does not allow this operation.Portal / tenant managementCHECK_STATUS_FIRST

1 scenario(s) · endpoint PATCH /webhooks/:webhookId

409CHECK_STATUS_FIRSTinferredIntegrator

Message: Webhook with type:'<type>' already exists.
What happened: The current state of the resource does not allow this operation.
Likely cause: Webhook with type:'<type>' already exists.
What to do: Query the resource (GET) to learn its current state before any new action. Do not resend the same request.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Webhook with type:'<type>' already exists."
  ],
  "type": "error",
  "errorCode": "W006-2",
  "traceId": "<uuid>",
  "statusCode": 409
}

route 3PATCH /webhooks/sub-tenant/:subTenantId

W003-3400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

5 scenario(s) · endpoint PATCH /webhooks/sub-tenant/:subTenantId · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId is required
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: type is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: type is required
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: SubTenant with subTenantId:'<subTenantId>' do not exists.
What happened: The request was rejected by an EPM validation rule.
Likely cause: SubTenant with subTenantId:'<subTenantId>' do not exists.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: Webhook not found
What happened: The request was rejected by an EPM validation rule.
Likely cause: Webhook not found
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: webhookReturn must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: webhookReturn must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "subTenantId is required"
  ],
  "type": "error",
  "errorCode": "W003-3",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 4GET /webhooks/:webhookId

W002-4404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /webhooks/:webhookId

404RETRY_AFTER_FIXinferredIntegrator

Message: Webhook with ID <webhookId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Webhook with ID <webhookId> not found"
  ],
  "type": "error",
  "errorCode": "W002-4",
  "traceId": "<uuid>",
  "statusCode": 404
}

W003-4400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /webhooks/:webhookId

400RETRY_AFTER_FIXinferredIntegrator

Message: webhookId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: webhookId is required
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "webhookId is required"
  ],
  "type": "error",
  "errorCode": "W003-4",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 5GET /webhooks

W002-5404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /webhooks

404RETRY_AFTER_FIXinferredIntegrator

Message: Webhooks not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response:

{
  "message": [
    "Webhooks not found"
  ],
  "type": "error",
  "errorCode": "W002-5",
  "traceId": "<uuid>",
  "statusCode": 404
}

W003-5400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint GET /webhooks

400RETRY_AFTER_FIXinferredIntegrator

Message: subTenantId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: subTenantId is required
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "subTenantId is required"
  ],
  "type": "error",
  "errorCode": "W003-5",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 6DELETE /webhooks/:webhookId

W002-6404The requested resource was not found.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint DELETE /webhooks/:webhookId

404RETRY_AFTER_FIXinferredIntegrator

Message: Webhook with ID <webhookId> not found
What happened: The requested resource was not found.
Likely cause: Identifier does not exist, belongs to another environment (sandbox x production), or to another sub-tenant.
What to do: Check the identifier sent (use the value returned when the resource was created) and the environment.

Example response (<…> placeholders are replaced at runtime):

{
  "message": [
    "Webhook with ID <webhookId> not found"
  ],
  "type": "error",
  "errorCode": "W002-6",
  "traceId": "<uuid>",
  "statusCode": 404
}

W003-6400The request was rejected by an EPM validation rule.Portal / tenant managementRETRY_AFTER_FIX

1 scenario(s) · endpoint DELETE /webhooks/:webhookId

400RETRY_AFTER_FIXinferredIntegrator

Message: webhookId is required
What happened: The request was rejected by an EPM validation rule.
Likely cause: webhookId is required
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "webhookId is required"
  ],
  "type": "error",
  "errorCode": "W003-6",
  "traceId": "<uuid>",
  "statusCode": 400
}

XPix, QR Code, and Linked Journey3 codes

route 1POST /pix/details

X003-1400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

5 scenario(s) · endpoint POST /pix/details · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: Exactly one of pixKey or qrCode must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: Exactly one of pixKey or qrCode must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: dynamic message
What happened: The request was rejected by an EPM validation rule.
Likely cause: Message built at runtime; see message[] in the response.
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: qrPayload must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: qrPayload must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: qrPayload must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: qrPayload must be informed
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: pixKey must be informed
What happened: The request was rejected by an EPM validation rule.
Likely cause: pixKey must be informed
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Exactly one of pixKey or qrCode must be informed"
  ],
  "type": "error",
  "errorCode": "X003-1",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 2POST /linked-journey/jsr

X003-2400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

1 scenario(s) · endpoint POST /linked-journey/jsr

400RETRY_AFTER_FIXinferredIntegrator

Message: enrollment.enrollment.document is required for the data consent
What happened: The request was rejected by an EPM validation rule.
Likely cause: enrollment.enrollment.document is required for the data consent
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "enrollment.enrollment.document is required for the data consent"
  ],
  "type": "error",
  "errorCode": "X003-2",
  "traceId": "<uuid>",
  "statusCode": 400
}

route 3POST /linked-journey/automatic-payments

X003-3400The request was rejected by an EPM validation rule.RETRY_AFTER_FIX

2 scenario(s) · endpoint POST /linked-journey/automatic-payments · the same code covers different scenarios: read message[] to tell them apart

400RETRY_AFTER_FIXinferredIntegrator

Message: Only recurringConfiguration.sweeping is allowed in the optimized automatic payments journey
What happened: The request was rejected by an EPM validation rule.
Likely cause: Only recurringConfiguration.sweeping is allowed in the optimized automatic payments journey
What to do: Adjust the data indicated in message[] and resend.

400RETRY_AFTER_FIXinferredIntegrator

Message: recurringConsent.loggedUser.document.identification is required for the data consent
What happened: The request was rejected by an EPM validation rule.
Likely cause: recurringConsent.loggedUser.document.identification is required for the data consent
What to do: Adjust the data indicated in message[] and resend.

Example response:

{
  "message": [
    "Only recurringConfiguration.sweeping is allowed in the optimized automatic payments journey"
  ],
  "type": "error",
  "errorCode": "X003-3",
  "traceId": "<uuid>",
  "statusCode": 400
}

Account holder business errors (EC001–EC004)

Known account holder rejections with an EPM-specific message. They take precedence over the E0xx codes.

errorCode	Status	What happened	What to do	Retry
`EC001`	400	The authorization returned by the institution has expired or is invalid (authorization callback).	Do not resend the same `code`/`state`. Restart the consent flow with the user.	DO_NOT_RETRY
`EC002`	400	Payment date invalid for the account holder.	For single payments, use the current date (Brasília time zone). Fix it and create a new consent.	RETRY_AFTER_FIX
`EC003`	424	The institution's platform could not resolve the request.	Check `organisationId` and `authorisationServerId` (use the values from `GET /open-integration/participants/available`). Correct? Contact Lina.	RETRY_AFTER_FIX
`EC004`	424	The institution could not resolve the request (generic platform error).	Check the resource state; if it persists, advise the user to try later or choose another institution, and contact Lina.	NOT_VALIDATED

Account holder rejections (E001–E070)

These codes are returned to the client as errorCode when the account holder responds 422 with a cataloged name: status 424 and message "<operation>: <ERROR_NAME>" (e.g. Error updating RP Payment: SALDO_INSUFICIENTE). In other flows the same rejection may arrive as EPM-424, EPM-500, or an internal route code. The classification below is inferred from the OFB semantics of the name, not from testing.

Code	Name	Origin	Who acts	Retry	Guidance	Suggested user-facing text
E001	CHALLENGE_INVALIDO	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.	Oops! Something went wrong. We couldn't enable biometric payments. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E002	CONTA_DEBITO_DIVERGENTE_CONSENTIMENTO_VINCULO	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.	Oops! Something went wrong. We couldn't complete your payment right now. No amount was debited from your account. To pay now, you can complete the transaction without enabling biometric payments. (Pay without enrollment)
E003	CONTA_INVALIDA	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.	Oops! Something went wrong. We couldn't open your institution's app because the account is not compatible with biometric payments or does not exist. To pay, choose another bank and try again. (Restart everything)
E004	ERRO_IDEMPOTENCIA	JSR / Enrollments	Integrator	CHECK_STATUS_FIRST	Idempotency conflict at the account holder: the same key was used with different content. Check the state; do not resend.	Oops! Something went wrong. We couldn't open your institution's app due to a temporary problem. Please try again in a few moments. (Try again)
E005	EXTENSION_INVALIDA	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't enable biometric payments. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E006	FALTAM_SINAIS_OBRIGATORIOS_DA_PLATAFORMA	JSR / Enrollments	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.	Oops! Something went wrong. We couldn't open your institution's app due to a temporary problem. Please try again in a few moments. (Try again)
E007	MAXIMO_CHALLENGES_ATINGIDO	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.	Oops! Something went wrong. We couldn't process your institution's authorization. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E008	MOTIVO_REJEICAO	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E009	MOTIVO_REVOGACAO	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E010	ORIGEM_FIDO_INVALIDA	JSR / Enrollments	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.	Oops! Something went wrong. We couldn't enable biometric payments. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E011	PARAMETRO_INVALIDO	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't open your institution's app due to a temporary problem. Please try again in a few moments. (Try again)
E012	PARAMETRO_NAO_INFORMADO	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't open your institution's app. To pay, choose the bank again and try again. (Restart everything)
E013	PERMISSAO_INVALIDA_VINCULO_CONSENTIMENTO	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't process your payment right now. No amount was debited from your account. To pay now, you can complete the transaction without enabling biometric payments. (Pay without enrollment)
E014	PERMISSOES_INVALIDAS	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't open your institution's app. To pay, choose the bank again and try again. (Restart everything)
E015	PUBLIC_KEY_INVALIDA	JSR / Enrollments	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.	Oops! Something went wrong. We couldn't enable biometric payments. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E016	REJEITADO_OUTRO_SEM_DETALHES	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E017	REVOGADO_OUTRO_SEM_DETALHES	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E018	RISCO	JSR / Enrollments	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.	Oops! Something went wrong. We couldn't complete your payment right now for security reasons. To pay, choose a bank and try again. (Restart everything)
E019	RP_ID_HASH_INVALIDO	JSR / Enrollments	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.	Oops! Something went wrong. We couldn't enable biometric payments. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E020	RP_INVALIDA	JSR / Enrollments	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.	Oops! Something went wrong. We couldn't process your institution's authorization. We'll redirect you to your bank's app to authorize your account registration again. (Restart step)
E021	STATUS_CONSENTIMENTO_INVALIDO	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't process your payment right now due to a temporary problem. No amount was debited from your account. Please try again in a few moments. (Try again)
E022	STATUS_INVALIDO	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E023	STATUS_VINCULO_INVALIDO	JSR / Enrollments	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).	Oops! Something went wrong. We couldn't open your institution's app due to a temporary problem. Please try again in a few moments. (Try again)
E024	AUTENTICACAO_DIVERGENTE	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E025	CAMPO_NAO_PERMITIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E026	CANCELAMENTO_FORA_PERIODO_PERMITIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E027	CHAVE_PIX_DIVERGENTE_AGENDAMENTO_LIQUIDACAO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E028	COBRANCA_INVALIDA	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E029	CONSENTIMENTO_INVALIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E030	CONSENTIMENTO_NAO_PERMITE_CANCELAMENTO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E031	CONSENTIMENTO_PENDENTE_AUTORIZACAO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E032	CONTA_NAO_PERMITE_PAGAMENTO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E033	CONTAS_ORIGEM_DESTINO_IGUAIS	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E034	DATA_PAGAMENTO_INVALIDA	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E035	DETALHE_EDICAO_INVALIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E036	DETALHE_PAGAMENTO_INVALIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E037	DETALHE_TENTATIVA_INVALIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E038	FALHA_AGENDAMENTO_PAGAMENTOS	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E039	FALHA_INFRAESTRUTURA	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E040	FALHA_INFRAESTRUTURA_DETENTORA	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E041	FALHA_INFRAESTRUTURA_DICT	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E042	FALHA_INFRAESTRUTURA_ICP	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E043	FALHA_INFRAESTRUTURA_PSP_RECEBEDOR	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E044	FALHA_INFRAESTRUTURA_SPI	Payments / Automatic	Lina support	CONTACT_SUPPORT	Infrastructure failure at the account holder/SPI/DICT/ICP. Do not retry the operation: contact Lina support with the traceId. To check the state, query the resource (GET).
E045	FALTAM_SINAIS_OBRIGATORIOS_PLATAFORMA	Payments / Automatic	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.
E046	FLUXO_NAO_SUPORTADO_PRODUTO	Payments / Automatic	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.
E047	FORA_PRAZO_PERMITIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E048	FORMA_PAGAMENTO_INVALIDA	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E049	FUNCIONALIDADE_NAO_HABILITADA	Payments / Automatic	Lina support	CONTACT_SUPPORT	Platform/participant configuration. Contact Lina support with the traceId.
E050	LIMITE_PERIODO_QUANTIDADE_EXCEDIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E051	LIMITE_PERIODO_VALOR_EXCEDIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E053	LIMITE_VALOR_TOTAL_CONSENTIMENTO_EXCEDIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E054	LIMITE_VALOR_TRANSACAO_CONSENTIMENTO_EXCEDIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E055	NAO_INFORMADO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E056	NAO_PERMITIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E057	PAGAMENTO_DIVERGENTE_CONSENTIMENTO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E058	PAGAMENTO_NAO_PERMITE_CANCELAMENTO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E059	PAGAMENTO_RECUSADO_DETENTORA	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E060	PAGAMENTO_RECUSADO_SPI	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E061	PERMISSAO_INSUFICIENTE	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E062	PROPOSITO_INVALIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).
E063	QRCODE_INVALIDO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E064	REJEITADO_USUARIO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E065	SALDO_INSUFICIENTE	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E066	TEMPO_EXPIRADO_AUTORIZACAO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E067	TEMPO_EXPIRADO_CONSUMO	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E068	TITULARIDADE_INCONSISTENTE	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E069	VALOR_ACIMA_LIMITE	Payments / Automatic	End user	DO_NOT_RETRY	Rejection related to the account, authorization, limit, or a user/institution decision. Guide the user; a new attempt only makes sense after they resolve the cause (e.g. balance, limit) or start a new flow.
E070	VALOR_INVALIDO	Payments / Automatic	Integrator	RETRY_AFTER_FIX	Data sent does not comply with the account holder's rule. Fix the indicated field and redo the operation (new flow, if the consent has already been consumed).

Generic and non-standard codes

Generic codes (EPM-<status>) appear when the exception has no mapped errorCode. The message is generic and ends with “Contact support informing the traceId of this response.”

errorCode	Status	When it appears	What to do	Retry
`EPM-400`	400	Validation without a route code (e.g. `POST /automatic-payments/recurring-payments`, `/linked-journey/*`) or a malformed identifier.	Fix the field; the generic message does not say which one — compare with the contract.	RETRY_AFTER_FIX
`EPM-401`	401	Missing, invalid, or expired token (routes without a specific code).	Renew the access token and resend.	RETRY_AFTER_FIX
`EPM-403`	403	The client does not have the role required by the route.	Confirm you are using the right credentials (tenant x sub-tenant); if so, ask Lina to grant access.	CONTACT_SUPPORT
`EPM-404`	404	Resource not found in a scenario without a code.	Check the identifier and the environment.	RETRY_AFTER_FIX
`EPM-409`	409	State conflict in a scenario without a code.	Query the resource before acting.	CHECK_STATUS_FIRST
`EPM-424`	424	The account holder rejected the request (422 without a cataloged name) or responded 5xx.	External failure (account holder infrastructure or a rejection without a cataloged name). Do not retry; contact Lina with the traceId. To check the state, query the resource (GET).	CONTACT_SUPPORT
`EPM-500`	500	Unexpected error, including timeout or network error with the account holder when creating consents and recurring payments.	Retry with backoff (2s, 4s, 8s), up to 3 attempts. If it persists, contact Lina with the traceId.	SAFE_RETRY/CONTACT_SUPPORT
`PAYMENT_NOT_ALLOWED`	422	Payer or payee on a restricted list.	Tell the user the operation cannot be completed. Do not retry.	DO_NOT_RETRY
`EPM-MTLS-001`	400	mTLS certificate domain not authorized for the tenant.	Use the registered domain or ask Lina to register the new domain.	RETRY_AFTER_FIX
`MISSING_API_KEY` `INVALID_API_KEY`	401	`/wake/*` routes: `X-Api-Key` header missing or invalid.	Send the current API key provided by Lina.	RETRY_AFTER_FIX