Hi there. We are a SaaS with clients that have payment gateway accounts with Square. Our clients use our SaaS to create and manage customers and invoices, but they wish to grant our SaaS access to their payment gateway account via API so that we can create shareable payment links for them that they can share with their customers to secure payment for invoices. We then need to be able to process successful payment webhook events resulting from those shareable payment links to update the status of those invoices in our SaaS. We can’t expect our clients to manage customers, invoices, payments or webhooks in their payment gateway accounts - whatever needs to be done there we need to be able to do for them via API by way of an authorized connection to their account.
OK. Sorry… long intro. We’ve built the API-driven framework and webhooks to accomplish all of this in our Sandbox account, but now we need to roll it out in Production. We’re presented with the following message:
You must activate your Square account for payments by visiting squareup.com/activate before you can process card payments in production.
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
To launch your app in a production environment, you need to activate your Square account for payments. The activation process involves providing some additional information about your business. If you’re having trouble with the activation process, it might be due to a glitch or a specific issue with your account.
In your case, since you’re developing a SaaS platform for your clients, you should consider using Square’s OAuth API. This allows your clients to authorize your application to take actions on their behalf. Once a client authorizes your application, you’ll receive an access token for that client’s Square account. You can then use this access token to make API requests on behalf of that client.
Remember, each of your clients will need to have their own activated Square account. They will need to go through the activation process themselves to set up their payment processing. Once they’ve done that, they can authorize your application to access their account using OAuth.
For more information on using OAuth with Square, you can refer to the OAuth API Overview in the Square Developer Documentation.
I could have sworn that when I originally created this topic a few hours ago that on this same screen there was that note about having to activate our Square account for payments, but I certainly could have been looking elsewhere I guess and been confused.
Have you built out the OAuth flow? Once you’ve built the OAuth flow and the customer authorized your application with the correct credentials you’l be able to make API calls on behalf of the seller with the generated access token.
Oh, we’ve done all of this and it all works wonderfully in our Sandbox, so we’re pretty much ready to take it live in Production. I thought that we had to go done some “account activation” road to do so, but it sounds like you’re saying that all we need to do is to move our OAuth flow etc. code out of our own “development” environment and into production, provide our production Square account with the correct “production redirect URL” and use the production values of application ID and application secret in our code and we’re good to go. If so, wonderful! I just thought that we had to do more for some reason.
I’m Square Dev AI, here to help answer your question!
