Documentation
Test environmentLive environmentStatusContact us
  • Overview
    • Get started
    • Resource guides
      • For business users
      • For finance teams
      • For integration teams
    • Stripe onboarding
    • Live use cases
      • Usage overview
  • Start using the dashboard
    • Access
    • Payment services
    • Collaborators and access control
    • One-time payment links
      • Single link creation
      • Bulk link creation
      • Send payment links
      • Payment link page
      • Payment receipt email
    • Subscriptions
      • Set-up
      • View subscriptions
      • Manage subscriptions
    • Payments and refunds
      • Payment methods
      • Dashboard
      • Refunds
    • Payouts
    • Reports
    • Payment workflows with Plumber
      • Set-up
      • Testing
    • Payment forms
      • Set-up
      • Testing
      • Resources
  • Start an API integration
    • Get started
    • Endpoints
    • Integrating with your e-services
    • Errors
    • Idempotency
    • Pagination
    • Go-live checklist
  • API RESOURCES
    • Events
      • The event object
      • Types of events
    • Payments
      • Create a payment
      • Retrieve payments
      • Send email for payment
      • Cancel a payment
      • Refund a payment
      • Get all payments from payment service
  • WEBHOOKS
    • Introduction
    • Set-up
      • Events
      • Best practices
  • FAQ
    • Access
    • Costs
    • Timeline
    • API keys
    • API integration
    • Payments
    • Payment methods
    • Payouts and transaction fees
    • Refunds
    • Security and compliance
    • Downtime and maintenance
  • Policies
    • Privacy Policy
    • Terms of Use
Powered by GitBook
On this page

Was this helpful?

  1. Start an API integration

Go-live checklist

PreviousPaginationNextEvents

Last updated 11 months ago

Was this helpful?

The following steps should be completed 1 week before your go-live date.

  1. Create your payment service at and retrieve the payment service ID from the URL.

  1. Select an email address for the API key to be issued to. We recommend using a group email address (e.g. agency_finance_team@agency.gov.sg) for transferability.

  2. (Optional) For webhook registration, share the webhook URL with the PaySG team.

You will need to share the following information with PaySG (team@pay.gov.sg):

  • Payment service ID

  • Email address for API key

  • (optional) Webhook URL

  • For agencies with DBS PayNow integrations:

    1. Payment service ID

    2. Agency UEN

    3. DBS account number

    4. DBS API key (provided by DBS)

    5. DBS organisation ID (provided by DBS)

You will receive the following resources from PaySG:

  • API key

  • (optional) Webhook secret

pay.gov.sg