> For the complete documentation index, see [llms.txt](https://docs.pgecom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pgecom.com/api-endpoint/payment/pg-pay/configurepgpay.md).

# ConfigurePGPay

You'll need to navigate to your PGecom account and click on **Settings > Developer**

<figure><img src="/files/ct0bqjlVA2kwsvYoPDXq" alt=""><figcaption><p>PG Pay Merchant Set Up</p></figcaption></figure>

Then make sure that you fill out all the information

* Success Url
* Error Url
* Merchant Name

Please keep in mind once you've set the merchant name, you can **NOT** change it

The Success URL is very important so we can redirect the customer back to your platform

Expect the following params from the success or error URL

* **status**=completed&
* **orderId**=7f4f7086-74d6-4cd4-bdfa-5e10f761d562

At the your success or error URL will look like this

```
// Succcess URL - Success

https://sandbox.pgecom.com/payment-success?status=completed&orderId=7f4f7086-74d6-4cd4-bdfa-5e10f761d562

// Error URL - Error
https://sandbo.pgecom.com/payment-error?status=declined
```

Hope you enjoy PG Pay as much as we enjoy building it 🎉


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pgecom.com/api-endpoint/payment/pg-pay/configurepgpay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.