#Create Payment for profile
1 messages · Page 1 of 1 (latest)
It starts with access_, I assume it's the organization access token from my app? I went through the Client Links Beta etc.
Can I use the organization token to create a payment for a different profile? Or do I need the access token of that payment profile?
Since it says: "Application fees are only allowed for OAuth payments
Let me take it up with "Paul van den Boer" he helped me through the Client Links Beta at the time (March 2024). & I'll dig into Vincent's Api Client code to see what's new
You can not use Applications fees with organization access tokens. There's simply no OAuth app to assign the application fee to 🙂
Interesting, was that always the case or a change since March 2024?
I do see refresh tokens in my database, so I assume I have to request a new access token for the partnered profile before being able to create the payment?
There's no application with Organzation Access Tokens, so application fees are not possible. This is since forever. Only OAuth tokens (which also start with access_) could do that.
Since you have a refresh token, it sounds like you have OAuth tokens and those expire
Well, I have 1 token starting with access_ likely an organizational token meant for other purposes.
Can I check token expiry anywhere?
access_ is for both. if you have a refresh token, it's OAuth because Organzation Access Tokens does not have it
Thanks, I'll likely misinterpret the flow due to lack of testable profiles at the time
🙂
That's better, feel free to close this topic.
@frozen spruce one more issue I face, I created a profile for my partner (Client Links Beta) which is a profile attached to my organization.
However, that profile Id doesn't seems usable at Create Payment.
I also see that partner as "Customer", the customer profile Id does work to create a payment for
I'm so confused. Could be another mistake in my code but ...