ARTICLE AD BOX
I am reverse-engineering the Meta Business Suite MV4B onboarding flow using GraphQL. My goal is to automate the payment method setup.
The Problem: I have successfully executed the following sequence:
CreateMV4BAccountMutation
MV4BOnboardingViewContainerQuery (to get the paymentAccountID)
useMV4BCreateBizApplicationMutation
The script completes without errors, and the payment account is created. However, when I refresh the Business Suite UI, the "Add Payment Method" button is still disabled (greyed out), or the UI doesn't reflect that the account is ready for card entry.
Current Script Logic:
JavaScript
// I am fetching the paymentAccountID from the onboarding query paymentAccountID = response.data.business.mv4b_billable_account.billing_payment_account.payment_legacy_account_id; // Then I trigger the application mutation // variables: {"input":{"client_mutation_id":"4","business_id": bm_id, "selected_country":"CL"...}}What I've Tried:
Running BillingGKQuery and BillingQEQuery to match the web session's state.
Checking BillingCheckHasRequiredAccountInfoStateQuery.
Question: Is there a specific "activation" mutation or a final state_update call required to enable the payment UI? It seems like I'm missing the bridge between creating the application and actually enabling the payment method input.
Any help on the missing GraphQL doc_id or mutation name for this step would be appreciated.
