Sender Creation Failure Reasons

The Creation Failed tab on the Senders page lists senders that could not be created. This page explains the error codes you can see there and what each one means.

What the tab shows

The list shows each failed sender's name, email, phone number, error code, and the time of the failure (Eastern).

Select a row to open the failure details:

Detail	Description
Failed (Eastern)	When the creation attempt failed
HTTP status	The HTTP status returned for the failure
Trace ID	The identifier for the failed request
Error code	The code that identifies the failure. See the tables below
Field	The field the error relates to, when there is one
Error message	A description of the problem
Raw error detail	The full error response

The raw error detail is a list, with a code, a fieldId, and a message for each error. A failed attempt can include more than one error.

Example

Detail	Value
Error code	`InvalidSenderAddress`
HTTP status	Bad Request
Field	`ADDRESS_LINE_1`
Error message	Sender must have a valid, non-PO Box, street address.

[
  {
    "code": "InvalidSenderAddress",
    "fieldId": "ADDRESS_LINE_1",
    "message": "Sender must have a valid, non-PO Box, street address."
  }
]

Sender data problems

Error code	What it means	HTTP status
`InvalidSenderAddress`	The sender address is invalid	400
`InvalidSenderName`	The sender name does not meet requirements	400
`InvalidSenderFields`	Sender data failed validation	400
`InvalidSenderCountrySubdivision`	The sender state or province is invalid	500
`InvalidTypeOfId`	The sender ID type is not supported	400
`SenderInvalidTypeOfIdLength`	The sender ID length is incorrect	400
`InvalidIdExpirationDate`	The sender ID has expired	400
`SenderInvalidPhoneNumber`	The sender phone number format is invalid	400

Field validation

These errors come from field-level validation. The Field value in the failure details names the field.

Error code	What it means	HTTP status
`MissingRequiredField`	A required field was not provided	400
`FieldNotFound`	A required field is missing from the request	400
`ValueTooShort`	The value is shorter than the minimum length	400
`ValueTooLong`	The value is longer than the maximum length	400
`ValueRegexFailure`	The value does not match the required pattern	400
`InvalidFieldValue`	The value does not meet requirements	400
`InvalidEnumOption`	The value is not a supported option	400
`UnknownField`	A field was sent that is not recognized	400
`DuplicatedField`	A field appears more than once	400

Sender eligibility

Error code	What it means	HTTP status
`SenderInvalidDateOfBirthUnder18`	The sender is under 18	400
`SenderInvalidDateOfBirthOver100`	The sender is over 100	400
`NonUsSenderNotAllowed`	A non-U.S. sender is not permitted	500
`SenderForbidden`	The sender is blocked or restricted	403
`SenderUnauthorized`	The sender lacks required permissions	403
`SenderUndetermined`	The sender cannot be determined	400

Create or update failed

Error code	What it means	HTTP status
`SenderNotCreated`	The sender creation process failed	400, 500
`SenderNotUpdated`	The sender update process failed	500
`InvalidSenderError`	A general sender error	400
`InvalidSenderGroupId`	The sender group ID is invalid	500

Partner enrollment

When the payout partner requires an enrolled sender first, enrollment can fail.

Error code	What it means	HTTP status
`InvalidRspSenderId`	The partner sender ID is invalid	400
`RelationshipWithSenderRequired`	The relationship with the sender is missing	500
`RelationshipWithSenderNotFound`	The relationship with the sender does not exist	400, 500

Identity and compliance checks

If a sender cannot be created because of an identity or compliance check, the failure details do not say which check applied. Contact PayMitto Support for help with these senders.

For an overview of senders and how the Senders page works, see Senders Overview.