connect-examples | Example channels code templates

Update:

• Set Project to N/A to define the API client as a team-level one.
• Set Roles to Administrator

1. Please check whether your client role is Administrator.

The role of a member determines the permissions in AppGallery Connect. Administrator has most operation permissions, being able to add member accounts and assigning permissions to them. For details about the mapping between roles and permissions, please refer to Roles and Permissions.

1. Work with AppGallery Connect API

To call the AppGallery Connect API, you need to obtain authorization from the AppGallery Connect server in advance using either of the following modes: API client mode and OAuth client mode. To call the AppGallery Connect API in the API client mode, you need to manage your API client in AppGallery Connect. An API client can be managed only by your team account holder. The basic process is as follows:

A. Creating an API Client

• Sign in to AppGallery Connect and select Users and permissions.
• Go to Api Key > AppGalleryConnect API from the navigation tree on the left and click Create.
• Set Name to a customized client name, set Roles to the corresponding role, and click Confirm.
• After the client is successfully created, record the values of Client ID and Key in the client information list.

Check the screenshot below:

B. Obtaining the Token for Accessing the API

After an API client is created, the API client needs to be authenticated in AppGallery Connect. After the authentication is successful, the API client obtains an access token for accessing the AppGallery Connect API. With this access token, you can access the AppGallery Connect API.

To obtain an access token, you need to add the code for calling the Obtaining a Token API to your app program.

Before running the demo, complete preparations in the README file:

• Open this project by Android Studio.
• Go to AppGallery Connect page to create your new application. Make sure your application's package name is com.huawei.agc.clouddb.xxxx.
• Go to Auth tab and enable Huawei account authentication.
• Go to Cloud Database tab and enable database service, and import the object type in CloudDBQuickStart_1.json under the root directory of project. Or you can create it with name BookInfo, and add all fields in BookInfo.java in the sample project.
• Download agconnect-services.json from Generate view tab, and add it under app directory.
• Add your key store to build script, see app/build.gradle. To generate an key store, you can use tool provided by Android Studio: Build -> Generate signed bundle and apk -> Choose apk selection, and then do as hints step by step. Then fill the password and alias name into app/build.gradle. Export the SHA256 fingerprints by keytool: keytool -list -v -keystore xxxx.jks and fill it into "SHA256 fingerprints" in Generate view tab.
• Run the sample on Android device. Attention: Huawei mobile service(HMS) should have been installed on your devices already.

I've found the solution to the question, basically my "credentials access token was using authorization access token" that was the first mistake, the other was due to the itempotency key which has a max limit of 45 characters according to the API reference square connect api, and the other was how i returned the response which is meant to be in JSON format as far as the promise i consumed was doing. Here is the source code, (the java is fine, no need to edit that) it was only on the nodejs side. The API keys are referenced in the environmental variables side on the GCF platform. This will effectively allow processing a square payment through android applications using "serverless approach".

You will have to go through Square’s identity verification flow in the Square Dashboard to enable credit card processing before the can process transactions through the Square API in production. If you reside in a country other than the United States, Canada, Australia, the United Kingdom, or Japan you wont be able to process payments through Square.

You can, however, test payments with test cards using your sandbox credentials. You can find your sandbox credentials in your Developer Dashboard. The way to view sandbox transactions is to call the ListTransactions endpoint with your sandbox credentials to get a sandbox transaction report.

You should use the v2/transactions endpoints, as they are more performant. You are correct in your approach, I would be sure to implement a robust back off strategy if you do end up hitting the rate limit. Depending on the merchant size, downloading the full transaction history likely won't take more than a minute or so.

To keep the transactions up to date, you can regularly pull new transactions and do diffs, or utilize webhooks

Try to delete packages folder at solution root and rebuild or restore packages again.

That "card declined" message is actually the error you get back from Square's APIs. You can play around with the error messaging in the app.js file and the `error.jade. Try error.catagory, code, detail.

Keep in mind that this is just a sample app, to show that you can use the APIs with node.js, you probably don't want to use this code in your production system.

This is just informational to help you understand what is being returned from the API. The charge was processed successfully. If you remove the print_r($response) line, this will be hidden.