Tulus API Playground

Interactive sandbox for testing both Tulus and SnapNPay payment integration. See the Callback Reference for the full list of POST parameters, status codes, and signature verification your server will receive after a payment.

API Overview: The API is logically grouped into two main categories:

  1. Payment Orders - Create and manage payment transactions
  2. Payment Reports - Query and retrieve transaction reports

Authentication can be done using a user account and API key for secure and flexible access.

Payment Order Example

Note: API Key is optional but recommended to sign and lock in the payment amount.

Current Order Configuration

Array
(
    [agency] => SNAPNPAY
    [refNo] => test6a0a1ff5b712c~881225-08-1234~12 
 Jalan Foo~#Sample RefNo
    [amount] => 2.00
    [email] => [email protected]
    [returnUrl] => https://developers.snapnpay.my/sdk/example/receipt.php?just=1&a=test
    [cancelUrl] => 
    [utm_source] => sdk
    [utm_medium] => dev
    [utm_campaign] => sdk_demo
    [utm_term] => tulus sdk
    [utm_content] => 
    [pref_method] => 
    [pref_bank] => 
    [extra_data] => 
)
Production - Live payments
UAT - MEPS Dev Environment
Unique identifier for this payment order. Can include extra data appended with ~
Amount in RM. Min: RM 2.00 for FPX B2B, RM 1.00 for FPX B2C (after charges)
Valid email address for receipt delivery
Your assigned agency code
Callback URL after payment completion
Optional. URL to redirect the user if they cancel at the Tulus checkout page before the request is submitted to the bank/FPX. Once the request has been sent onwards, cancellations/failures return via returnUrl instead.

UTM Tracking Parameters

e.g., instagram, facebook
e.g., email, cpc
e.g., spring_sale
e.g., pay zakat
e.g., logolink

Advanced Options

[ALPHA] e.g., fpx/b2b1
[ALPHA] e.g., ABB0235 for Affin Bank B2B
Internal debug use only
POST to https://pay.tulus.my/

Payment Reports API

Obtain from reports.tulus.my via "Copy AuthToken to Clipboard"
Agency code for report filtering