Remove Reference to AccessToken in Integration Guides

[KunJeongPark]

Summary of changes

• Change instruction for instantiating CoreConfig to use clientID instead of accessToken in README and /docs

Checklist

- [ ] Added a changelog entry

Authors

List GitHub usernames for everyone who contributed to this pull request.

• @KunJeongPark

[scannillo]

Suggested change

	// STEP 0: Enter a CLIENT_ID and fetch ORDER_ID from your server.
	// STEP 0: Fetch a CLIENT_ID and ORDER_ID from your server.

[scannillo]

Do we have a sample cURL or link to a cURL for how merchants can perform a clientID fetch on their server?

[KunJeongPark]

That's a good point, I don't think we have one for the function Steven wrote on for the merchant server. I can write it in as a comment until we have it in the integration guide that we can link. What do you think?

[sshropshire]

A typical merchant won't need to fetch a client ID. It will most likely be injected at compile time using an environment (or hardcoded) variable for most, unless they need to dynamically set their client ID.

[sshropshire]

We'll eventually support multiple merchants in the Demo app e.g. to test connected partner flows, so we need to set it dynamically for PPCP e2e testing.

[sshropshire]

On Android, we only mention that it's needed to construct a CoreConfig object. It is technically up to the merchant, and clientID doesn't need to be protected like the clientSecret does. Maybe we can do something similar here and eliminate step 0?

[scannillo]

Do we need this snippet in the README at all? We have this integration covered in our docs/ section per module.

[sshropshire]

We should be able to remove:

let paymentConfig = CoreConfig(clientID: "<CLIENT_ID>", environment: .sandbox)

is probably all that's needed.

[scannillo]

I mean this entire section under ## Sample Code in the README (link). IMO it can be removed. We don't have an equivalent in Android and the sample code for each flow already lives in docs/.

[sshropshire]

👍 agreed.

[sshropshire]

🌊