Returns a merchant's connection to its starting state in Preczn so the merchant can onboard to it again. Use a reset when the merchant has to apply again from the start, for example after the processor rejects an application or the business changes owners, or when the connection holds the wrong credentials.

A reset:

• Sets the connection status to Unconfigured. For a connection that Preczn onboards, Preczn then checks the merchant's data and moves the status to Requirements or Ready.
• Permanently deletes the connection's credentials, the IDs the processor assigned (such as the MID and application ID), and all connection-specific data, including terms and conditions acceptance.
• Removes the connection's IDs from the merchant's owners and bank accounts.

A reset can't be undone. Before you reset a connection, know what you lose:

• The merchant can't process payments through this connection until you configure it or onboard the merchant again.
• Preczn no longer matches webhooks or status updates from the processor to this connection, because the IDs it matches on are gone.
• Deleted credentials and IDs can't be restored. You must enter them again.
• A reset changes Preczn only. It doesn't cancel an application in progress or close the merchant's account at the processor. Do that with the processor directly.

To correct only the status, use Update Connection Details with status instead. A status change keeps the credentials and IDs.

Preczn records each reset in the merchant's activity log, with your API key as the actor, and sends a merchant.updated webhook.