Documentación

BUSINESS_DETAILS_NOT_ALLOWED_FOR_PERSONAL_CONTACT

Message: The request tried to create a personal contact for a Rapyd wallet, but the contact type was personal and business details were given. Business details are not allowed for a personal contact. The request was rejected. Corrective action: In the contact object, set business_details to null.

Explanation: You attempted to provide business information for a personal contact. To resolve this, ensure that the contact type is personal and the business details field is empty.

Error Example:{"contact":{"contact_type":"personal","business_details":{"name":"Acme Corp"}}}

Correct Example:

{
    "contact": {
        "contact_type": "personal",
        "business_details": null
    }
}

CANNOT_CREATE_MORE_THAN_ONE_BUSINESS_CONTACT

Message: The request tried to add a second business contact to a company wallet, but a company wallet can have only one business contact. The request was rejected. Corrective action: Set contact_type to personal.

Explanation: A company wallet is restricted to a single business contact. Additional contacts must be registered as personal contacts.

CREATE_PERSONAL_WALLET_REQUIRES_PERSONAL_CONTACT

Message: The request tried to create a personal wallet, but the contact type was business. The request was rejected. Corrective action: In the contact object, set contact_type to personal.

Explanation: Person wallets are designed for individuals and cannot be assigned a business contact type. Change the contact type to personal.

Error Example:{"type":"person","contact":{"contact_type":"business"}}

Correct Example:

{
    "type": "person",
    "contact": {
        "contact_type": "personal"
    }
}

ERROR_ADD_CONTACT_TOO_MANY_CONTACTS

Message: The request tried to add a contact to a personal wallet, but a personal wallet can have only one contact. The request was rejected. Corrective action: None. Determine why an attempt was made to give a personal wallet two contacts. Consider creating a company wallet.

Explanation: You tried to exceed the limit of one contact for a personal wallet. If you need multiple contacts for a single entity, use a company wallet instead.

ERROR_CREATE_EWALLET_CONTACT

Message: The request tried to create a contact in a wallet, but the operation failed. Corrective action: Verify that the wallet exists, and check all input parameters.

Explanation: You can add a person contact to a client wallet or company wallet. The operation can fail if the wallet is a person wallet, if the wallet is disabled or deleted, or the request contains malformed data. Verify that the wallet ID is correct and enabled, and that all parameters have correct values.

ERROR_CREATE_PERSONAL_CONTACT_WRONG_IDENTIFICATION_TYPE

Message: The request tried to create a personal contact for a wallet, but the type of identification is not supported for a personal contact. The request was rejected. Corrective action: Set identification_type to one of the values for a personal contact, as returned in the response to List Official Identification Documents.

Explanation: The provided identification type is not valid for a personal contact in the specified country. Use a supported type.

Correct Example:

{
    "identification_type": "Passport",
    "identification_number": "12345678"
}

ERROR_DEFAULT_CONTACT_PHONE_NUMBER_DIFFERENT_THAN_EWALLET_PHONE_NUMBER

Message: The request tried to create a wallet, but there was a mismatch between the phone numbers provided. The request was rejected. Corrective action: If you provide a phone number for the wallet, it must have the same value as the phone_number field in the contact object.

Explanation: The phone number defined in the contact details does not match the phone number for the wallet itself. Best practice is to add the phone number only to the contact.

Correct Example:

{
    "phone_number": "+15550001",
    "contact": {
        "phone_number": "+15550001"
    }
}

ERROR_DELETE_BUSINESS_CONTACT

Message: The request tried to remove a business contact from a company wallet, but this operation is not possible. The request was rejected. Corrective action: None. If you are trying to replace the business contact with another business contact, use Update Wallet Contact.

Explanation: You cannot delete the business contact of a company wallet. To change the details, update the existing contact instead of deleting it.

ERROR_DELETE_CONTACT_FROM_PERSONAL_EWALLET

Message: The request tried to delete a contact, but the wallet was a personal wallet. A personal wallet can have only one contact and it cannot be deleted. The request was rejected. Corrective action: None. Determine why an attempt was made to delete the contact.

Explanation: The personal contact of a person wallet is a required component of the wallet structure. If you need to delete the contact from the system, you must disable the wallet using Change Wallet Status or delete it using Delete Wallet.

ERROR_DELETE_EWALLET_CONTACT

Message: The request tried to delete a contact from a wallet, but the contact was not found. The request was rejected. Corrective action: Determine whether the contact was already deleted, and why there were multiple requests to delete it.

Explanation: The system could not find the contact ID provided in the request. Verify the contact ID or check whether it has already been removed.

ERROR_EWALLET_CONTACT_ADDRESS_CITY_NOT_FOUND

Message: The request attempted an operation that requires a wallet contact, but the city of the contact was not found. The request was rejected. Corrective action: Use Update Wallet Contact to add the name of the city to the city field in the address object.

Explanation: The operation failed because the contact's city information is missing. Update the contact to include a valid city name in the address section.

Correct Example:

{
    "contact": {
        "address": {
            "city": "Reykjavik"
        }
    }
}

ERROR_EWALLET_CONTACT_COUNTRY_NOT_SUPPORTED

Message: The request tried to create or update a wallet contact, but the country is not supported. The request was rejected. Corrective action: Contact Rapyd Client Support.

Explanation: The country you want is not supported for this action. Contact Rapyd Client Support for details.

ERROR_EWALLET_CONTACT_NOT_FOUND

Message: The request attempted an operation that requires a wallet contact, but the contact was not found. The request was rejected. Corrective action: Provide the ID of a valid wallet contact, which is a string starting with cont_.

Explanation: The specified contact ID contains a typo or was deleted. Verify that the ID is correct and was not deleted.

ERROR_GET_EWALLET_CONTACT

Message: The request attempted an operation that requires a wallet contact, but the contact was not found. The request was rejected. Corrective action: In the path, specify the ID of a valid wallet, a string starting with ewallet, and the ID of a valid contact belonging to that wallet, a string starting with cont.

Explanation: The contact could not be retrieved because the wallet ID or contact ID in the URL path is incorrect or deleted. Double-check both identifiers.

ERROR_UPDATE_EWALLET_CONTACT

Message: The request tried to update a business wallet contact, but there was a format error in the business details. The request was rejected. Corrective action: Provide all data in the correct format. See the API reference.

Explanation: One or more fields within the business details object contain invalid data or are formatted incorrectly. Review the API documentation for data types and required patterns.

Error Example:{"business_details":{"mcc":"Veterinary Services"}}

Correct Example:

{
    "business_details": {
        "mcc": "0742"
    }
}

ERROR_UPDATE_WALLET_CONTACT_TYPE

Message: The request tried to change the type of a wallet contact, but this operation is not allowed. The request was rejected. Corrective action: None. Create a new wallet with the type of contact you want.

Explanation: You cannot switch a contact from personal to business (or vice versa) after creation. You must create a new wallet with the appropriate configuration.

ERROR_WALLET_CONTACT_NATIONALITY_CODE_NOT_VALID

Message: The request tried to add or update a nationality, but it was not in the correct format. The request was rejected. Corrective action: In the country field, enter the 2-letter ISO 3166-1 ALPHA-2 country code.

Explanation: The value provided is not a valid country code. Use the correct ISO code.

Error Example:{"nationality":"UK"}

Correct Example:

{
    "nationality": "GB"
}

EWALLET_BUSINESS_DETAILS_ADDRESS_LINE1_NOT_VALID

Message: The request created a wallet, but the address of the contact did not have a line1 field or was not an object. The wallet was created and it is not valid without it. Corrective action: Contact Client Support.

Explanation: The wallet was created with incomplete address data. Run Update Wallet Contact to fill in the missing data.

EWALLET_BUSINESS_DETAILS_ADDRESS_NAME_NOT_VALID

Message: The request created a wallet, but the address of the contact did not have a name. The wallet was created and it is not valid without it. Corrective action: Contact Client Support.

Explanation: A wallet was created but lacks a valid business name in the address. Run Update Wallet Contact to fill in the missing data.

EWALLET_UPDATED_WITH_NO_BUSINESS_DETAILS_DUE_TO_INVALID_ADDRESS

Message: The request tried to update a wallet, but the business address was missing required information or contained special characters. The request was rejected. Corrective action: Inside the address object, which is inside the business_details object, provide name with alphanumerics and spaces and line_1 with a string.

Explanation: The update failed because the business address contained invalid characters or was missing key fields. Submit valid data that includes only alphanumeric characters and spaces.

Correct Example:

{
    "business_details": {
        "address": {
            "name": "Four Star Services",
            "line_1": "123 Main Street"
        }
    }
}

INVALID_EWALLET_BUSINESS_ENTITY_TYPE

Message: The request tried to create a company wallet, but the entity type was missing or not recognized. The request was rejected. Corrective action: In the business_details object, set entity_type to one of the following values: sole_prop, partnership, company, government, charity, NPO, association, trust.

Explanation: The value provided for the business entity type is not supported. Select a valid category from the allowed list.

Correct Example:

{
    "business_details": {
        "entity_type": "partnership"
    }
}

INVALID_EWALLET_BUSINESS_NAME

Message: The request tried to create a company wallet, but the business name was missing or contained special characters. The request was rejected. Corrective action: In the business_details object, set the name field to a string made up of alphabetic characters and spaces.

Explanation: In the contact object, the business name is missing.

Error Example:{"contact":"business_details":{"name":""}}

Correct Example:

{
    "contact": {
        "business_details": {
            "name": "Four Star Services"
        }
    }
}

INVALID_EWALLET_BUSINESS_REGISTRATION_NUMBER

Message: The request tried to create a company wallet, but the business registration number was missing or contained special characters. The request was rejected. Corrective action: In the business_details object, set the registration_number field to a string made up of alphabetic characters and spaces.

Explanation: The registration number is not in the correct format. Ensure that it contains only alphanumeric characters in the format required by the relevant government agency.

Correct Example:

{
    "business_details": {
        "registration_number": "ABC123456"
    }
}

INVALID_EWALLET_BUSINESS_SUB_CATEGORY

Message: The request tried to create a company wallet, but business_sub_category contained special characters. The request was rejected. Corrective action: Provide a valid business subcategory.

Explanation: The subcategory field contains invalid formatting or characters. Provide a valid string that matches supported industry subcategories.

INVALID_EWALLET_CONTACT_TYPE

Message: The request tried to create or update a wallet contact, but the contact type was not recognized. The request was rejected. Corrective action: Set contact_type to personal or business.

Explanation: The contact type value must be specifically personal or business. Any other string will produce this error.

Correct Example:

{
    "contact_type": "personal"
}

INVALID_EWALLET_INDUSTRY_CATEGORY

Message: The request tried to create a company wallet, but industry_category was not set or contained special characters. The request was rejected. Corrective action: Provide a valid industry category.

Explanation: In the contact.business_details object, the industry_category field is missing or contains a value that is not recognized. Use a standard industry name using alphanumeric characters.

INVALID_GENDER

Message: The request tried to create a wallet contact, but the gender was not recognized. The request was rejected. Corrective action: Set gender to one of the following values: male, female, other, not_applicable

Explanation: The value provided for gender does not match the system's allowed options. Choose one of the supported values.

Error Example:{"gender":"m"}

Correct Example:

{
    "gender": "male"
}

INVALID_HOUSE_TYPE

Message: The request tried to create a wallet contact, but the house type was not recognized. The request was rejected. Corrective action: Set house_type to one of the following values: lease, live_with_family, own, owner, month_to_month, housing_project

Explanation: The house type provided is not valid. Select a value from the enumeration provided in the API reference.

Correct Example:

{
    "house_type": "own"
}

INVALID_MARITAL_STATUS

Message: The request tried to create a wallet contact, but the marital status was not recognized. The request was rejected. Corrective action: Set marital_status to one of the following values: married, single, divorced, widowed, cohabiting, not_applicable

Explanation: The marital status provided is not valid. Select a value from the enumeration provided in the API reference.

Correct Example:

{
    "marital_status": "single"
}

INVALID_MIDDLE_NAME

Message: The request tried to create a wallet contact, but the middle name contained special characters. The request was rejected. Corrective action: Use only alphabetic characters and spaces for middle_name.

Explanation: The middle_name field contains invalid symbols or numbers. Remove any non-alphabetic characters and resubmit.

Error Example:{"middle_name":"J. (Joy)"}

Correct Example:

{
    "middle_name": "Joy"
}

INVALID_SECOND_LAST_NAME

Message: The request tried to create a wallet contact, but the second last name contained special characters. The request was rejected. Corrective action: Use only alphabetic characters and spaces for second_last_name.

Explanation: The second last name field contains prohibited characters. Remove any non-alphabetic characters and resubmit.

Correct Example:

{
    "second_last_name": "Smith"
}