> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/contributing/development/paypal.md). # PayPal Technical details about how we implement PayPal and how to get started developing with it. ## Developing / testing sandbox ### Buyer account This is the account you'll use to make the (fake) payment. Go to , login with your personnal PayPal account then create a test account. ### Merchant account 1. Create an app here: 2. Use the generated merchant credentials to set the following variables in API's `.env`: ``` PAYPAL_ENVIRONMENT=sandbox PAYPAL_APP_ID=APP-________ ``` 3\. Encrypt your client secret, from the API repository: ```bash npm run script scripts/encrypt.js PAYPAL_CLIENT_SECRET ``` 4\. Manually create a ConnectedAccount with your `clientId` and your encrypted `clientSecret`: ```sql INSERT INTO "ConnectedAccounts" ("service", "clientId", "token", "CollectiveId") VALUES (E'paypal', clientId, clientSecret, hostCollectiveId); ``` 5\. Create buyer's credentials on And you're ready to go. Use the credentials generated in step 2. to authenticate when ordering. ## Known issues * The button may require multiple clicks to trigger on dev or staging. It should not affect production (see ) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.opencollective.com/help/contributing/development/paypal.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.