You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/developers/about-receiving.mdx
+37-33Lines changed: 37 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,50 +106,54 @@ The examples below are simplified representations of the Open Payments API calls
106
106
</Disclosure>
107
107
108
108
4. The agent issues a <LinkOuthref="https://openpayments.dev/apis/auth-server/operations/post-request/"><Badgetext="POST"variant="success"size="small" /></LinkOut> request to your wallet provider's `authServer` URL. The request contains the access permissions the agent is requesting.
The `client` in the request above is your visitor's wallet address. This URL is only used by the agent and the wallets, and isn't available to the website.
133
+
:::
134
+
135
+
</Disclosure>
136
+
5. The response to the agent contains an access token that the agent needs to make its next request.
The `client` in the request above is your visitor's wallet address. This URL is only used by the agent and the wallets, and isn't available to the website.
132
-
:::
133
-
134
-
</Disclosure>
135
-
5. The response to the agent contains an access token that the agent needs to make its next request.
6. The agent issues a <LinkOuthref="https://openpayments.dev/apis/resource-server/operations/create-incoming-payment/"><Badgetext="POST"variant="success"size="small" /></LinkOut> request to your wallet provider's `resourceServer` URL. The purpose of this call is to request the information needed by your visitor's wallet provider so their provider correctly addresses the payment to you.
0 commit comments