TL;DR Key takeaways
- A compatible replacement using the same key can preserve a plain Ethereum account’s deposit address; contract wallets depend on their own control rules.
- Exporting a key does not revoke another usable copy. Address continuity is not proof of exclusive signing control.
- Validate export authority, rebuild required controls and payment operations, and test a completed merchant payment—not just a signature.
For a PSP, changing merchant deposit addresses is a customer-facing migration, not just a back-office setting. Payment instructions may need updating, integrations may need changing, and transfers sent to old destinations still need handling. Keeping the existing addresses is an understandable priority when replacing wallet infrastructure.
That can be possible. But preserving a deposit address and ending the old provider’s signing authority are different outcomes. A successful wallet export may help deliver the first without delivering the second. The migration decision turns on which kind of independence your business needs.
The same account can have a new interface
For a plain key-controlled Ethereum account, the address derives from the public key associated with its private key. A compatible replacement using that same key can operate the existing onchain account and preserve its deposit address. Changing the interface is not the same as creating a new account. This distinction follows from the account model described by Ethereum.
The qualification matters: this is an explanation of plain key-controlled Ethereum accounts, not a promise of portability across every network, custody arrangement or replacement service. Your PSP still needs access to the required signing material, and the destination service must support using it. Seeing an assigned deposit address in a provider’s dashboard does not establish either condition.
A contract wallet is different. Ethereum contract accounts are controlled by code and do not have private keys of their own. If you export the key of a signer authorized by a wallet contract, you have exported that signer’s key—not the contract wallet itself. Importing it into an ordinary wallet interface does not make the contract address appear as a key-controlled account.
To keep that contract’s deposit address usable, the replacement must be able to interact with the existing contract under its control rules. If those rules permit changing authorized signers, retaining the address while replacing signing authority may be possible. That depends on the contract’s design and the replacement’s capabilities; it cannot be inferred from the availability of key export.
A copied key is not a clean handover
For a plain key-controlled account, exporting the private key gives the replacement signing power. It does not, by itself, take that power away from anyone else with a usable copy or signing path. Turnkey makes this explicit in its documentation: an exported wallet remains in Turnkey and continues signing as before.
Consider a hypothetical PSP that imports the keys behind its merchants’ Ethereum deposit addresses into a replacement service. A test deposit reaches an existing address, and the new service successfully transfers the funds onward. Merchant instructions remain unchanged. From a continuity perspective, the test looks successful.
Yet it proves only that the new arrangement works. If the original provider-side signing path remains usable, it can still authorize transactions for those accounts. Turning off the old integration is not onchain revocation. Disabling API credentials may close a particular access route, but it does not invalidate another usable copy of the private key.
This creates an important distinction between two reasons for switching. If the PSP wants to stop depending on the old API or operating model, retaining the same account may serve that goal. If it wants to eliminate the risk associated with the existing signing key, retaining that key does not solve the problem.
For a plain key-controlled Ethereum account, replacing the controlling key means using a different address. Keeping the address therefore requires a separate assessment of what can be disabled at the old provider and what assurance is available about any remaining signing material. Export alone establishes neither exclusive control nor a clean security break.
Who can actually authorize the exit?
Even where address preservation is technically possible, the person running the migration may not have authority to export the wallet. Application access, wallet ownership and export authorization are not interchangeable.
In Privy’s documented model, application credentials alone do not authorize export of user-owned wallets: the owner’s authorization is required. A wallet owned by a user-plus-server 2-of-2 quorum requires both parties to authorize export. Privy also documents that a DENY policy can prevent export. Those details can change whether a PSP can execute an exit itself or must coordinate with other parties.
The useful procurement question is therefore not simply, “Does the platform support export?” It is, “Can the party responsible for our exit complete an export under this wallet’s actual ownership and policy configuration?” A visible Export button is a starting point for checking that authority, not evidence that the intended operator can complete the action alone.
Validate that authorization path before making unchanged addresses a migration commitment. A demonstration using a wallet with different owners or fewer approval requirements does not establish portability for the production arrangement.
The key does not carry the operating model
Once export is authorized and the replacement can sign, two further parts of the migration remain: governance and payment operations.
An offchain approval rule is not embedded in an Ethereum private key. Suppose the current service requires two people to approve a withdrawal. Importing the account’s raw key elsewhere does not reproduce that rule. The replacement needs its own controls, and anyone retaining a usable copy of the key may have a signing route outside those controls. Rules enforced by a wallet contract are a separate matter: they remain part of the contract’s execution logic.
Export should consequently be treated as a sensitive transfer of signing authority, not a routine configuration download. The migration must account for who can handle the material, where it can be used and how the required approvals will be enforced afterward.
Nor does an imported key bring across the business context around the address. Merchant mappings, transaction history, payment notifications and reconciliation workflows need separate migration or replacement. The blockchain may still recognize the same account while your payment system no longer knows which merchant to credit.
For a PSP comparing stablecoin settlement providers or replacing its wallet-infrastructure layer, the acceptance test should be a completed merchant payment, not merely a successful signature. An incoming transfer to an existing address should be detected on the intended network, attributed to the correct merchant, credited once and reconciled. Any onward transfer should follow the required approval process.
That test establishes operational continuity. A separate review must establish what signing authority remains in the old arrangement. Neither result should be used as a substitute for the other.
Conclusion
Keeping existing deposit addresses can spare merchants a disruptive change. It does not automatically deliver independence from the old provider. Establish address continuity, export authority, signing control and payment operations separately. If the exit requires a new controlling key for a plain Ethereum account, plan for a new deposit address too.
For requesting more information about how we can help reach out to us. We're here to help and answer any questions you may have.