E-Wallet Native Webhook

Money In Operation — This webhook fires when a customer completes an e-wallet payment, transferring funds into your SingaPay account.

Information

Method	Path	Format	Authentication
POST	`https://your-webhook-url/callback`	json	HMAC SHA512 Signature

SingaPay sends a POST request to your configured transaction_notif_url when a customer completes payment via e-wallet native checkout.

This webhook may share a callback URL with other event types. See Shared webhook endpoints for routing by event value.

Request Details

Headers

Field	Value	Type	Mandatory	Description
`Content-Type`	`application/json`	Alphabetic	Yes	Specifies JSON format for the request body
`User-Agent`	`SingaPaymentGateway/1.0`	Alphabetic	Yes	Identifies the source of the webhook
`Accept`	`application/json`	Alphabetic	Yes	Expected response format
`X-PARTNER-ID`	—	Alphanumeric	Yes	Your API Key from the merchant dashboard
`X-Signature`	—	Alphanumeric	Yes	HMAC SHA512 signature (128 chars) for request verification
`X-Timestamp`	—	Numeric	Yes	Unix timestamp in seconds when the request was sent
`Authorization`	`Bearer <random_token>`	Alphanumeric	Yes	System-generated random bearer token; used as a component in the signature

The Authorization token for e-wallet webhooks is a randomly generated string — not a user access token. This webhook is triggered by a payment notification (system event), not a user action. Extract the token as-is and use it in the string to sign. See How to Validate Signature below.

Body Parameters

number

required

HTTP Status Code. Example: 200

boolean

required

Indicates if the transaction was successful. Example: true

string

required

Event type identifier. Always "ewallet-native-transaction" for this webhook.

string

required

Event timestamp in format "d M Y H:i:s". Example: "26 Dec 2025 13:35:45"

object

required

Container for transaction, customer, and payment details.

Show data fields

object

required

Transaction details.

Show transaction fields

integer

required

Unique transaction ID. Example: 42

string

required

Merchant reference number used during checkout creation. Example: "INV-2026-001"

string

Optional merchant reference number for tracing. Example: "INV-2026-001"

string

required

Transaction type. Always "ewallet".

string

required

E-wallet vendor code. Example: "GOPAY", "OVO", "SHOPEEPAY"

string

required

Transaction status. Always "paid" for this webhook.

object

required

Net transaction amount after fees — credited to your balance.

Show amount fields

number

required

Net amount value. Example: 95000

string

required

ISO 4217 currency code. Example: "IDR"

object

required

Gross transaction amount — what the customer actually paid.

Show total_amount fields

number

required

Total amount value. Example: 100000

string

required

ISO 4217 currency code. Example: "IDR"

string

required

Timestamp when the transaction record was last updated. Example: "26 Dec 2025 13:35:43"

string

required

Timestamp when the payment was confirmed and processed. Example: "26 Dec 2025 13:35:45"

object

required

Customer details provided during checkout. All fields are optional depending on checkout creation data.

Show customer fields

string

Customer name. Example: "John Doe"

string

Customer email address. Example: "john@example.com"

string

Customer phone number. Example: "081234567890"

object

required

Payment method details.

Show payment fields

string

required

Payment method. Always "ewallet".

string

required

E-wallet vendor code — same as transaction.ewallet_vendor. Example: "GOPAY"

object

required

E-wallet specific payment information.

Show additional_info fields

number

required

Internal payment event ID for traceability. Example: 1042

string

Reference number from the e-wallet vendor. May be null depending on the provider’s API response.

Payload Example

Success

{
  "status": 200,
  "success": true,
  "event": "ewallet-native-transaction",
  "timestamp": "26 Dec 2025 13:35:45",
  "data": {
    "transaction": {
      "id": 42,
      "reff_no": "INV-2026-001",
      "merchant_reff_no": "INV-2026-001",
      "type": "ewallet",
      "ewallet_vendor": "GOPAY",
      "status": "paid",
      "amount": {
        "value": 95000,
        "currency": "IDR"
      },
      "total_amount": {
        "value": 100000,
        "currency": "IDR"
      },
      "post_timestamp": "26 Dec 2025 13:35:43",
      "processed_timestamp": "26 Dec 2025 13:35:45"
    },
    "customer": {
      "name": "John Doe",
      "email": "john@example.com",
      "phone": "081234567890"
    },
    "payment": {
      "method": "ewallet",
      "vendor": "GOPAY",
      "additional_info": {
        "payment_event_id": 1042,
        "vendor_reference_no": "PAY-XYZ-12345"
      }
    }
  }
}

Security and responses

Return HTTP 200 promptly after validating the request. For retry behavior, see Webhook retry mechanism. Verify every webhook using Security and signature validation. Use your configured callback path when building StringToSign. Handle duplicate deliveries idempotently using stable identifiers from the payload (for example transaction_id or reff_no).

E-Wallet Specific Notes

amount vs total_amount

total_amount is the gross amount the customer paid. amount is the net amount after fees — this is what gets credited to your balance. Always use total_amount for display to the customer and amount for reconciliation.

vendor_reference_no may be null

The vendor_reference_no field may be null depending on the e-wallet provider’s API response. Always handle null gracefully in your code — don’t assume it’s always populated.

Customer fields are optional

All customer fields (name, email, phone) are optional and depend on the data provided during checkout creation. Your handler should not assume any of these are present.

Timestamp format & timezone

Both post_timestamp and processed_timestamp use the format "d M Y H:i:s" (e.g. "26 Dec 2025 13:35:45") in Asia/Jakarta (WIB) timezone — not UTC.

Getting Started

Security

Accept Money

Send Money

Transaction Records

Money Accounts

Webhook

Information

Request Details

Headers

Body Parameters

Payload Example

Security and responses

E-Wallet Specific Notes

​Information

​Request Details

​Headers

​Body Parameters

​Payload Example

​Security and responses

​E-Wallet Specific Notes

Information

Request Details

Headers

Body Parameters

Payload Example

Security and responses

E-Wallet Specific Notes