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
  • 1. Introduction
  • 2. Create a payment service
  • 3. Whitelisting
  • 4. API keys
  • 5. Test out our endpoints

Was this helpful?

  1. Start an API integration

Get started

PreviousResourcesNextEndpoints

Last updated 1 month ago

Was this helpful?

PaySG APIs allows agencies to integrate the platform into their software systems. The API follows REST semantics, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. We do not provide SDKs.

Backwards compatibility is maintained within each major version of the API (/v1, /v2). However, new fields might be added as more features are developed on PaySG platform.

1. Introduction

Ensure that the onboarding steps in have been completed.

The rest of this guide walks you through setting up your integration with PaySG.

2. Create a payment service

To begin, follow our and create a payment service on our testing environment (). All .gov.sg email addresses can do so without needing to create an account.

3. Whitelisting

If you are a vendor, please request for your agency counterpart to contact us to whitelist your email addresses for access to our staging environment.

4. API keys

Provide our team with the relevant gov.sg email addresses to receive an API key. This email address must have been used to log in to PaySG's or before, so that it is associated with a user.

Staging API keys have the prefix paysg_stag_ while the live API keys have the prefix paysg_live_. Payments should be tested on the staging environment using

To make authenticated requests, provide an x-api-key: <key> header to the request.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

5. Test out our endpoints

Refer to our to send your first request.

this section
payment service guide
staging.pay.gov.sg
staging (test) environment
live environment
dummy credit card numbers.
documentation on endpoints