Skip to main content

Payment Links

Payment Links are the simplest way to accept payments. Instead of embedding a button on your website, you generate a URL that redirects the user to a hosted Sticitt checkout page.

This is ideal for:

  • Sending invoices via SMS, WhatsApp, or Email.
  • Platforms with no frontend (e.g., backend-only automation).
  • Quick "No-Code" integration testing.

Base URLs

Like the API, Payment Links exist in both Test and Production environments.

EnvironmentBase URL
Test (Sandbox)https://link-test.sticitt.co.za/
Productionhttps://link.sticitt.co.za/

Best for: Invoices, Orders, and Secure Transactions.

This method links to a pre-created Payment Object. It is secure because the amount and details are locked by your server, and you can track the status via Webhooks.

How to construct

  1. Create a payment via the API (POST /v3/payments).
  2. Receive the paymentId (e.g., da9df1fc-83e7...).
  3. Append it to the base URL as a query parameter.

Format: {BaseURL}/?paymentId={paymentId}

Example: https://link-test.sticitt.co.za/?paymentId=da9df1fc-83e7-40aa-8cf3-13d76fc3c802

Redirect

To return the user to your site after payment, ensure you set the paymentSuccessfulReturnUrl field when you create the payment object via the API.


Best for: Ad-hoc payments, Donations, or generic "Pay Me" links.

You can create a valid payment link without calling the API at all. You simply pass your Merchant ID and details as query parameters.

Parameters

ParameterRequired?Description
merchantId✅ YesYour unique Merchant UUID.
reference❌ NoA reference string (e.g., Invoice-001).
amount❌ NoThe amount in cents (e.g., 12300 = R123.00). If omitted, the user will be asked to enter an amount.

How to construct

Append the parameters to the base URL.

Format: {BaseURL}/?merchantId={guid}&reference={ref}&amount={cents}

Example (Fixed Amount): https://link-test.sticitt.co.za/?merchantId=2a0ed44b-b928-4bfe-bad0-116fa360ba59&reference=MyRef&amount=12300

Example (Open Amount): https://link-test.sticitt.co.za/?merchantId=2a0ed44b-b928-4bfe-bad0-116fa360ba59

User enters the amount themselves.

Use Case Restriction

Static payments are not recommended for e-commerce or services where fulfillment verification is required. Use them only for simple, low-risk scenarios like donations. See Create Static Payments section for more details.