> For the complete documentation index, see [llms.txt](https://guide.pay.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.pay.gov.sg/overview/live-use-cases/usage-overview.md). # Usage overview
Use caseMethodIntegration required?WorkflowGetting started
Integrate PaySG with your licensing portal to enable users to make payments for license applicationsIntegration with e-servicesYes

  1. Payer accesses the licensing portal and inputs their details.
  2. The licensing portal’s backend system calls our API to create a payment link.
  3. Your portal redirects payer to PaySG’s payment page.
  4. Payer completes payment and PaySG redirects them back to a return URL of your choice.
  1. Read through our guide, specifically:

- Getting started

- Implementation timeline

- Integrating with your e-services

  1. Test out our services at staging.pay.gov.sg to assess if PaySG is suitable for your use case.
Collecting money from an individualSingle adhocNo
  1. Your team creates a payment service on PaySG.
  2. Your team creates a payment link and inputs the payer’s details.
  3. Send the payment link to the payer via email on PaySG, or send them a PaySG QR code.
  4. After successful payment, the payer receives a receipt through email.
  1. Read through our guide on using the PaySG dashboard.
  2. Decide which payment options you want to offer.
  3. Test out our services at staging.pay.gov.sg to assess if PaySG is suitable for your use case.
Collecting money from groups of peopleBulk adhocNo
  1. Your team creates a payment service on PaySG.
  2. Your team creates a csv file that includes the payers’ contact details and information.
  3. Your team uploads the csv file to bulk-create payment links.

  1. Your team sends out the payment links via individual or bulk email.

  1. After successful payment, the payer receives a receipt through email.
  1. Read through our guide on using the PaySG dashboard.
  2. Decide which payment options you want to offer.
  3. Test out our services at staging.pay.gov.sg to assess if PaySG is suitable for your use case.
Automated payments workflow for fine collectionsIntegration with FormSG via PlumberNo

Set up:

  1. Your team creates a FormSG form, PaySG payment service and Plumber pipe.
  2. Your team connects the FormSG form and PaySG payment service on Plumber.
  3. After successfully connecting the form and payment service, Plumber facilitates the creation of a payment service after a form input.

Payment flow:

  1. Payer inputs details on a FormSG form.
  2. Using payer's details, a payment link or fine letter is automatically created and sent to the payer’s email.
  3. After successful payment, the payer receives a receipt through email.
  1. For payment generation, test out the flow at go.gov.sg/paysg-plumber-demo. For payment and fine letter generation, test out the flow at go.gov.sg/paysg-fine-demo.
  2. Refer to our guide for more information on setting up the pipe for your own workflow.
--- # 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://guide.pay.gov.sg/overview/live-use-cases/usage-overview.md?ask=&goal= ``` `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.