> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/billing-and-payments/zuora-integration/zuora-central-sandbox-refresh.md). # Zuora Central Sandbox Refresh ### **Overview** When integrating a PeakCommerce Sandbox with a Zuora Central Sandbox, it's important to factor in various considerations during the refresh of the Zuora Central Sandbox from Production. ### **API Integration User** To facilitate PeakCommerce's Billing Integration, an integration user must be established in the Zuora Production tenant and synced to the Zuora Central Sandbox. Should the user exclusively be in the Zuora Central Sandbox, it will be deleted during a sandbox refresh, thereby disrupting the PeakCommerce Billing Integration. If the Zuora Central Sandbox refresh settings are configured to reset user passwords, you'll need to assign a fresh password to the PeakCommerce Sandbox Integration user. Simultaneously, generate a new Client Id and Client Secret. Both these credentials are closely linked. ### **Hosted Pages** Refreshing the Zuora Central Sandbox from Production also updates the hosted page configurations. Consequently, the hosted page 'Hosted Domains' will direct to PeakCommerce Production URLs rather than the sandbox endpoints. It's imperative to adjust these URLs in the Zuora Central Sandbox for all PeakCommerce-associated hosted pages; otherwise, errors will emerge during PeakCommerce payment procedures. Ensure that the Hosted Pages in Zuora direct to a testing gateway, not the production gateways. The assigned gateway in Zuora should align with the one in PeakCommerce. ### **Invoice Settlement** If your Zuora tenant uses **Invoice Settlement**, the corresponding setting in your PeakCommerce **Billing Integration** must be enabled, and its **Gateway Id** must hold a valid payment gateway id. A Zuora Central Sandbox refresh can change the payment gateway ids in the sandbox, so after a refresh, confirm the Gateway Id still matches a valid gateway and update it if it has changed — otherwise PeakCommerce won't process payments correctly. ### **Tax Engine** When integrating a tax engine with Zuora, remember that the Zuora Central Sandbox refresh replicates the Production configurations into the Sandbox. Any discrepancies between Sandbox and Production might disrupt both Zuora and PeakCommerce operations. For instance, complications can arise if: * Zuora Production links to a Production Tax Engine environment like Avalara. * The Zuora Central Sandbox needs to connect to a Sandbox Tax Engine environment instead of its production counterpart. * The Zuora Central Sandbox doesn't employ a tax engine, but Production does. * Tax codes in Production differ from those in the Sandbox. If any of these scenarios are applicable, errors might appear when orders are made through PeakCommerce e-commerce pages or in-app functionalities. To resolve such issues, post-refresh tax configurations in the Zuora Central Sandbox should either be revised (update or eliminate credentials and tax codes) or be entirely removed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/integrations/billing-and-payments/zuora-integration/zuora-central-sandbox-refresh.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.