Error codes returned from the API. All errors are associated with a user facing error message that can be shown to the end user.
Error Code | Cause | Resolution |
---|---|---|
| Sender ID not included in the request or auth token when performing an operation that requires a Sender ID. | Ensure the |
| Specified sender not found the request or auth token when performing an operation that requires a Sender ID. | Ensure the |
| Sender name is missing or invalid when creating or updating a sender. | Ensure the required sender fields are populated based on the response from If the |
| There was an issue creating the sender. See the error message for more details | See the error message for resolution. |
| There was an issue updating the sender. See the error message for more details | See the error message for resolution. |
| The provided value in the | Ensure the If the |
| The provided value in the | If the |
| The sender's date of birth indicates the sender is under the age of 18 when creating or updating a sender. | Do not attempt to create senders under the age of 18. |
| The provided | Double check the Double check that the recipient being requested belongs to the sender specified in the auth token. |
| The | Ensure the |
| Recipient name is missing or invalid when creating or updating a recipient. | Ensure the required recipient fields are populated based on the response from |
| The provided value in the | If the |
| Phone number does not match the expected format when creating or updating a recipient. | Ensure the phone number is being formatted correctly according to the specification. |
| The provided | Double check the |
| The | Ensure the |
| This error is thrown when a sender has reached their send amount limit within a 24 hour period. | Wait for time period to reset. |
| This error is thrown when a sender has reached their send amount limit within a 7 day period. | Wait for time period to reset. |
| This error is thrown when a sender has reached their total cost limit within a 24 hour period. | Wait for time period to reset. |
| This error is thrown when a sender has reached the number of transfers that can be sent in a 7 day period. | Wait for time period to reset. |
| This error is thrown when a sender has reached the number of transfers that can be sent in a 24 hour period. | Wait for time period to reset. |
| This error is thrown when the current transfer would exceed the send amount limit within a 24 hour period for a sender. | Wait for time period to reset. |
| This error is thrown when the current transfer would exceed the send amount limit within a 7 day period for a sender. | Wait for time period to reset. |
| This error is thrown when the current transfer would exceed the total cost limit, for a sender, within a 24 hour period. | Wait for time period to reset. |
| This error is thrown when a recipient has reached their receive amount limit within a 24 hour period. | Wait for time period to reset. |
| This error is thrown when a recipient has reached their receive amount limit within a 7 day period. | Wait for time period to reset. |
| This error happens when the receive amount limit for a recipient has been met for a monthly period. | Wait for time period to reset. |
| This error is thrown when a recipient has reached the number of transfers that can be received in a 24 hour period. | Wait for time period to reset. |
| This error is thrown when a recipient has reached the number of transfers that can be received within a month. | Wait for time period to reset. |
| This error is thrown when the send amount is less than the amount required for the cash pickup location. | Wait for time period to reset. |
| This error is thrown when the send amount is more than the amount allowed for the cash pickup location. | Wait for time period to reset. |
| No transfer was found matching the specified | Verify that the |
| No receipt was found for the given | Verify that the |
| The transfer amount exceeds the remaining balance for your account. | In a sandbox environment, contact your Brightwell support representative to resolve this issue. In a production environment, ensure your settlement account is funded. |
| The specified transfer amount is invalid. | Ensure the amount specified is an integer according to the Currencies documentation |
| The | Ensure the |
| The value for | The value for |
| The rate or fee has changed for this corridor since the provided quote was fetched. | Fetch a new quote using the Get Quote endpoint. |
| The rate or fee has changed for this corridor since the provided quote was fetched. | Fetch a new quote using the Get Quote endpoint. |
| The provided card is invalid or inactive. | Create a new card or choose a different transfer method or this transfer. |
| A transfer has already been submitted using the specified | Ensure this transfer submission was intentional and not an accidental resubmission. All unique transfers must have unique a |
| A | You can fetch a new |
| No quote was found matching the | Ensure the provided |
| An invalid value was provided for the | Verify the value provided for source transfer method is valid. |
| ||
| The issuer country specified on the card that was used for the source of funds is invalid. | Ensure the card being used as a source of funds is a valid Visa or Mastercard Debit card issued in the US. |
| The | Use the |
| The | Use the |
| The | Use the |
| The card specified as the source of funds was the same card specified as the recipient account. | Use a different card for the source of funds or the recipient account. |
| The | Populate the purpose of remittance field in the request. |
| Source of funds was set to | Use a different source of funds or contact your Brightwell Support representative. |
| Internal error retrieving quote. | In the sandbox environment, this might be a result of a temporary outage. In production, please reach out to your Brightwell support representative. |
| Maximum allowable amount exceeded for this transaction. | Resend the transfer with an Amount that doesn't exceed the maximum allowed amount |
| No corridor exists or is enabled that matches the destination country, destination currency, and transfer method combination specified in the request. | Ensure the correct country, currency, and transfer method are being submitted. Ensure the corridor in question is enabled based on the response from |
| Value passed for the destination country ISO 3 code is invalid. | Check to make sure that the value entered for the destination country ISO 3 code is correct. |
| A required field is missing. | Verify that all required fields are populated. |
| No Transfer Request was found matching the provided | Ensure the value passed for |
| The request was formatted incorrectly or missing required information. | Verify ID values are in the correct UUID format. Verify date values are in the ISO 8861 format. |
| There was an issue submitting the transfer to the remittance provider. | Contact your Brightwell support representative for more information. |
| The provided card does not support remittances. | Ensure the card is either a Visa debit card or a Mastercard debit card. Ensure the card is not a prepaid card. If it still doesn't work, try submitting a different card. |
| The expiration date is required to set up this card for remittances but was not sent in the request. | Submit the card's expiration date in the request body. |
| The card onboarding session is invalid or inactive. | Start a new card onboarding session and resubmit the card data. |
| The cardholder name must contain at least a first and last name. | Verify that the submitted cardholder name has at least 2 names included in the field. |
| The specified corridor was not found. | Ensure the correct country, currency, and transfer method are being submitted. Ensure the corridor in question is enabled based on the response from |
| A required field was not submitted in the request. | Ensure all required fields are populated according to the list of required fields returned from the API. For example, when creating a recipient, use the |
| A field value was submitted which does not match the regex validation pattern. | Ensure the submitted values match specified regex patterns. Regex validations are available in the associated |
| The currency of the card attached to the sender or recipient account does not match the corresponding currency of the transfer | Ensure quote and card currencies match. For example, if attempting to send 500 MXN to Mexico using |