I have a developer helping move to a self hosted version of sharetribe Go. He’s telling me that it’s impossible for to transfer all my sellers banking data from stripe connect into the self hosted version and that I need to ask all of their to resubmit their banking data again. Please keep in mind I am not changing my stripe account. It’s the same.
The strip support teams claims it can be done. has anyone dealt with this please provide any help you can so I can resolve this.Thank you.
This is absolutely certain: if you migrate to the Community Edition of Sharetribe Go and restore, there, a backup of your hosted marketplace that we, the Sharetribe team, has provided, your sellers will not have to connect their payment details again. They’ll be able to use the exact same Stripe account details that they’re using, right now. That information can be migrated smoothly.
In order to achieve this, you must use the same Stripe Platform account yourself. If you would decide to start using a different account then sellers would have to start from scratch. I understand that you’re not planning to use a different Stripe Platform account, so you’ll be all good.
Unfortunately, your developer is wrong on this one.
He’s mentioned that an encryption key is needed. That is correct: one random encryption key has to be generated in the new config file of your Community Edition installation. This is happening at https://github.com/sharetribe/go/blob/master/config/config.defaults.yml#L478 and is explained at https://github.com/sharetribe/go#enable-stripe. That key is secret: we will not share ours, that is for sure. But you don’t need ours: your developer has to generate a new one, as with any installation. That key doesn’t lock you in, it’s only used to encrypt communications but can be anything. Just make sure to have something unique, secret, and that you save securely.
After configuring that unique encryption key and restoring the data from the backup, you’ll have to update your Stripe API keys (from your Admin panel) (it’s a good idea to add new ones). This will make sure the Stripe key is stored encrypted with the correct new encryption key so that it can be decrypted and used when making API calls to Stripe
Does it clarify things? Hopefully, you’ll be able to discuss this with your developer and he’ll review and adjust positively.