Loading article…
Loading article…
Last updated on Aug 30, 2026
Common issues encountered when using Custom Offer Signup Pages, syncing data, or getting Maxio Support access to your Salesforce org, along with what to check to resolve them.
If a Custom Offer Signup Page shows an "Authorization Required" error, the Site Guest User doesn't have a license for the Chargify NG package.
To assign a license to the Site Guest User

A Custom Offer Signup Page can show an error stating that the chosen payment methods and/or payment gateways aren't properly configured in Advanced Billing, and directing the Customer to contact your Sales team for a new URL.

Check the following, based on the payment method the offer uses:
When Subscription creation fails on a signup page, the Customer sees an error message, and Salesforce logs an event with details to the Advanced Billing Event Log. A rendering error is also shown to the Customer and logged the same way. Possible messages include:
To append an error log to the end of the default or custom error message, check the Show_Error_Log__c field on the Signup Page record.
If you run into issues with the integration generally, start with the Advanced Billing Event Logs object in the Salesforce managed package. It shows which Lead, Account, Contact, or Opportunity records hit errors during insert or update, whether through a webhook or the API.
If you need more help, contact support@maxio.com and include the version of the package you're using.
If more than one Contact on the same Account has been linked to Advanced Billing (via Link Maxio AB Customer), a later sync for that Account can fail with an error status. This happens when the integration can no longer resolve a single match by email between the Account's linked Contacts and the Advanced Billing Customer.
To resolve it, use Migrate Maxio AB Contact to consolidate the Account back down to one linked Contact. See Migrate a Contact to a different Account.
Advanced Billing backfills a Customer's Salesforce ID automatically, once, during customer sync or when the Salesforce package is installed or updated. If a Customer record still shows no Salesforce ID after that, an admin with access to the Salesforce Developer Console can run the backfill manually.
To run the backfill manually
In Salesforce, open Developer Console > Debug > Execute Anonymous Window.
Paste and run:
CHRGFYNG.ChargifyBatchUpdateSFAccountIdInAB.executeBatch(new CHRGFYNG.ChargifyBatchUpdateSFAccountIdInAB());Maxio Support may sometimes ask for direct login access to your Salesforce org to troubleshoot an issue. This isn't specific to the integration, and Salesforce's own process for granting temporary support access may vary depending on your org's settings.
To grant Maxio Support access
If you can't complete these steps, one of the following may apply:
For more on granting login access, see Salesforce's documentation.
Still need help?
Reach out and our support team will take it from here.