thread Re: Oauth access token connect to a customer in Archived Discussions (Read Only)

Oauth access token connect to a customer

adia — Tue, 01 Oct 2019 02:51:57 GMT

In my application, I have customer signup, create a customer profile (createCustomer) and store their card (createCustomerCard) in Square and then ask them to connect their seller account to Oauth for a seller marketplace.

How can I tie the access token returned from OAuth to a customer? I received back the fields: access_token, token_type, merchant_id, refresh_token.

Is there a way to pass a Customer ID in Oauth to be returned with the access token?

Re: Oauth access token connect to a customer

kellyj — Thu, 03 Oct 2019 18:46:18 GMT

@adia

If you want your application to OAuth merchants, you won't need to create a customer, just OAuth them. The merchant_id is what ties an access token to a particular merchant. This will allow you to call API endpoints on the merchant’s behalf. Then, you can create customers for merchants.

Hope that makes sense, let me know if you have further questions.

Re: Oauth access token connect to a customer

adia — Sun, 06 Oct 2019 18:16:32 GMT

Thank you @kellyj

Once I have the access_token it looks like I could call v1/me to retrieve the business information? I may be able to use that information to create a customer profile. Does the access_token provided allow legacy v1/ endpoints to be used? I'm trying this in the sandbox.

I have users signup to my marketplace application and create a profile, then they can Oauth their square account later. I'm not clear how I can use any of the information returned by Obtaining the token or retrieving the business information to tie it to their account in my application. Is it acceptable to add a customer ID to the optional state query param?

Re: Oauth access token connect to a customer

Kassi_ — Mon, 07 Oct 2019 21:33:05 GMT

@adia

Yes, it should work.Someone on the merchant-side would need to enter a CC info of course, and the payment form would need to be tied to the developer’s account, not the merchant’s account. For a subscription solution that could send the merchant to a payment form -> save the card on file for your Developer account, and charge it on a monthly basis (this is charging the merchant’s card).

Re: Oauth access token connect to a customer

adia — Fri, 11 Oct 2019 00:52:04 GMT

Thank you!