Partner Errors

Guide to troubleshooting partner errors

CUSTOMER_NOT_FOUND

Customer not found
Common causes
  • The end customer could not be found.
Troubleshooting steps
1http code 404
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "CUSTOMER_NOT_FOUND",
5 "error_message": "the customer was not found",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

FLOWDOWN_NOT_COMPLETE

Flowdown not complete
Common causes
  • A flowdown, which is a prerequisite for creating an end customer, has not been completed.
Troubleshooting steps
1http code 412
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "FLOWDOWN_NOT_COMPLETE",
5 "error_message": "you must complete a flowdown to create and enable customers",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

QUESTIONNAIRE_NOT_COMPLETE

Questionnaire not complete
Common causes
  • A security questionnaire, which is a prerequisite for creating an end customer, has not been submitted.
Troubleshooting steps
1http code 412
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "QUESTIONNAIRE_NOT_COMPLETE",
5 "error_message": "you must complete the security questionnaire to create and enable customers",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

CUSTOMER_NOT_READY_FOR_ENABLEMENT

Customer not ready for enablement
Common causes
  • The end customer requires manual approval from Plaid's Partnerships team.
  • The end customer has been denied access to the Plaid API.
Troubleshooting steps
1http code 412
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "CUSTOMER_NOT_READY_FOR_ENABLEMENT",
5 "error_message": "this customer is not ready for enablement",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

CUSTOMER_ALREADY_ENABLED

Customer already enabled
Common causes
  • The end customer has already been enabled.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "CUSTOMER_ALREADY_ENABLED",
5 "error_message": "this customer has already been enabled",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

CUSTOMER_ALREADY_CREATED

Customer already created
Common causes
  • The end customer has already been created.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "CUSTOMER_ALREADY_CREATED",
5 "error_message": "this customer has already been created",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

LOGO_REQUIRED

Logo required
Common causes
  • A logo is required for this customer because the create_link_customization field was set to true and the co-branded consent field is in use.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "LOGO_REQUIRED",
5 "error_message": "a logo is required because create_link_customization is set to true and the co-branded consent pane is in use",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

INVALID_LOGO

Invalid logo
Common causes
  • The logo is not a valid base64-encoded string of a PNG of size 1024x1024.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "INVALID_LOGO",
5 "error_message": "the logo must be a base64-encoded string of a PNG of size 1024x1024",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

CONTACT_REQUIRED

Contact required
Common causes
  • A billing or technical contact is required, either in the API request or in the Dashboard.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "CONTACT_REQUIRED",
5 "error_message": "billing or technical contacts must be submitted either in the request or filled in for your team in the dashboard",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

ASSETS_UNDER_MANAGEMENT_REQUIRED

Assets Under Management required
Common causes
  • The assets_under_management field is required because you have a monthly service commitment, but it was omitted from your API request.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "ASSETS_UNDER_MANAGEMENT_REQUIRED",
5 "error_message": "assets under management must be submitted because your team has a monthly service commitment",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

CUSTOMER_REMOVAL_NOT_ALLOWED

Removal not allowed
Common causes
  • You have attempted to remove an end customer that has already been enabled in the Production environment, which is not allowed.
Troubleshooting steps
1http code 400
2{
3 "error_type": "PARTNER_ERROR",
4 "error_code": "CUSTOMER_REMOVAL_NOT_ALLOWED",
5 "error_message": "removal of a production-enabled end customer is not allowed. talk to your account manager to remove this end customer.",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}