# Get started

{% hint style="danger" %}
As of 25 June 2025,\
\
PaySG will not be onboarding new users until further notice. Users may onboard to our dashboard independently using the resources in the [Payment services section](https://guide.pay.gov.sg/start-using-the-dashboard/payment-services) but onboarding support will not be available. Use cases that require API keys and webhooks will not be able to onboard during this period. \
\
We remain fully operational for existing users and will continue to assist with critical technical issues, such as payment failures or unexpected system behaviours on PaySG’s end.
{% endhint %}

[**Learn more about what PaySG offers**](#user-content-fn-1)[^1]

1. Read through our [resource guide](https://guide.pay.gov.sg/overview/resource-guides). You can also log in to our [test environment (staging.pay.gov.sg)](https://staging.pay.gov.sg) to explore our features.
2. Refer to our [FAQs](https://guide.pay.gov.sg/faq) for common queries on setting up, usage and troubleshooting.

**Setup a collection workflow**

1. Once you've confirmed that PaySG fits your payment collection workflow, begin the [payment method onboarding ](https://guide.pay.gov.sg/overview/stripe-onboarding)process with Stripe, our underlying payment processor.
2. Test your end-to-end payment workflow in our [test environment](https://staging.pay.gov.sg) to ensure your set-up is working as expected. Verify that you've selected the correct settings and input the correct details as these can't be edited or deleted once created. 
3. Once you've verified that your set-up is working, you're ready to start collecting payments in our [live environment](https://pay.gov.sg).

**Estimated timeline**

{% hint style="warning" %}
The stakeholders and durations listed in the tables are **not prescriptive**. Stakeholders and durations differ between teams.
{% endhint %}

<table><thead><tr><th width="155">Phase</th><th width="160">Duration</th><th>Task</th><th>Stakeholder</th></tr></thead><tbody><tr><td>Budget approval</td><td>Based on your team</td><td>Seek clearance from your team/department head to budget for the transaction fees incurred by Stripe if necessary</td><td><ol><li>Your team</li><li>Team/department head who can approve budget requests</li></ol></td></tr><tr><td>Stripe set up</td><td>Based on your team</td><td>Follow the steps in our <a href="stripe-onboarding">Stripe onboarding guide</a></td><td><ol><li>Your team</li><li>Procurement/finance team</li></ol></td></tr><tr><td>Testing in PaySG's staging environment</td><td>2-4 weeks, based on your implementation team</td><td>Complete testing in our staging environment to ensure that details and payment flows are working as expected</td><td>For dashboard-only users: Your team<br><br>For API users:<br>Your technical team/vendor</td></tr><tr><td>Testing in PaySG's production environment</td><td>2-4 weeks, based on your implementation team</td><td>Complete testing in our staging environment to ensure that details and payment flows are working as expected</td><td>For dashboard-only users: Your team<br><br>For API users:<br>Your technical team/vendor</td></tr><tr><td>Go live</td><td>Based on your team</td><td></td><td>For dashboard-only users: Your team<br><br>For API users:<br>Your technical team/vendor</td></tr></tbody></table>

[^1]:


---

# Agent Instructions: 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:

```
GET https://guide.pay.gov.sg/overview/get-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.