Partial Outageshare-external
Business Eligibility Payment Issue
1

We are a company that has integrated with your API to provide our customers with access to WhatsApp.

We have several customers using our services, but one of them is experiencing a payment issue when trying to send a marketing template. They are encountering the following error:

"errors":[{"code":131042,"title":"Business eligibility payment issue","message":"Business eligibility payment issue","error_data":{"details":"Message failed to send because there were one or more errors related to your payment method."}}]

The error they are receiving is a Business Eligibility payment issue with error code 131042.

As far as we understand, this customer had a credit line while using HubSpot. After transitioning from HubSpot to our service, they are unable to change the default payment method to their credit card because of this credit line issue.

Somebody can direct us to the appropriate person or team that can assist in resolving this situation? We appreciate your help.

QSoft
Asked about 3 weeks ago
Selected Answer
1

Error code 131042 in Meta’s conversation platform indicates a Business Eligibility payment issue. This error typically arises due to problems with your payment method or billing setup.

To resolve this issue, you should:

Check your billing setup: Ensure that all payment methods linked to your Meta Business account are up-to-date and valid. Address any payment problems: Look for any outstanding payments or issues with your current payment method and resolve them promptly.

It might be best to change the credit line because it may still be linked to another service being used by your customer that Meta has not unlinked. Probably for fraud prevention purposes, you will get this error. So, ask your client if they use this line of credit with other services connected to the Meta Developer API or Meta Business Suite. Otherwise, it seems you will not be able to unlink this line.

Also, if you have just delete the other API without removing the payment method first, sometimes it will not reflect in the Meta application because you did not detach or remove the payment method first before deleting the previous API used by your client with the other company they used to get the API working. Lastly, the client may have more than one Business Suite accounts using the same line of credit (credit or debit card number), which they may have to unlink before your company uses it for the new API they are building. This error seems like a fraud prevention measure to avoid having the same credit line linked to multiple accounts.

October 29 at 10:01 AM
Eugene Harold
QSoft

Thank you very much for your response. Can you tell me any contact to send to our customer in order to be able to solve it? We can't find any place in Business Manager that lets us deconfigurate this credit line. We don't manage payments from our customer, they pay directly to Meta when they use our connection to the API, but I think that when they use a provider for hubspot they used this credit line.

Can we contact to anyone that could resolve this for them?

October 30 at 2:53 AM