Potentially, yes. A principal may be prepared to work with the technology you have built, but it needs to understand and accept how that technology supports the regulated activity. That includes your ledger, onboarding process, monitoring, reconciliation, reporting and access controls. A working API integration is only one part of the exercise. The provider also needs to know how it will supervise the program, obtain records and intervene when a transaction or customer requires attention.
I would divide your requirements into what you must retain and what you are willing to adapt. You may be very attached to a particular customer journey or software component, but the principal may require changes to satisfy its policies or banking arrangements. Discuss those changes early. Who approves a customer? Who changes a transaction limit? Who can release a blocked payment? Owning the code does not automatically give you the final decision on each of those points. The useful outcome is a documented division of responsibility that allows your product to operate while giving the principal the controls and visibility it needs.