API PAY-IN TRANSACTION

Request

The Pay-In API enables merchants to initiate payment collection transactions from customers. This API supports various payment methods for secure and efficient money collection in the Philippine market.

Request Path:

sandbox: https://sandbox-gateway.smilepayz.com/v2.0/transaction/pay-in
production: https://gateway.smilepayz.com/v2.0/transaction/pay-in

Header Parameters

Field	Required	Type	Description
Content-Type	M	String	HTTP content type specification Fixed value: application/json Required for proper request parsing
X-TIMESTAMP	M	String	ISO 8601 datetime format with timezone offset Format: yyyy-MM-ddTHH:mm:ss±HH:mm Example: 2020-12-17T10:55:00+08:00 Note: Must be current server time within ±5 minutes
X-SIGNATURE	M	String	Digital signature for request authentication See Signature Generation
X-PARTNER-ID	M	String	Unique merchant identifier assigned by the platform Format: Alphanumeric string Used for merchant authentication and transaction routing Please enter merchantID

Body Parameters

Field	Required	Type	Description
orderNo	M	String(32)	Unique transaction identifier Format: Alphanumeric string (numbers and letters only) Length: 6-32 characters Used for transaction tracking and reference
purpose	M	String(64)	Transaction purpose or description Format: UTF-8 encoded string Maximum length: 64 characters Used for transaction identification and reporting
merchant	M	Object	Merchant information container Contains merchant identification and business details See Merchant Model
merchantId	M	String	Unique merchant identifier assigned by the platform Format: Alphanumeric string Used for merchant authentication and transaction routing
merchantName	O	String	Merchant business name or display name Format: UTF-8 encoded string Used for merchant identification and reporting
subMerchantId	O	String	Sub-merchant identifier for multi-level merchant structures Format: Alphanumeric string Used for sub-merchant identification and reporting
subMerchantName	O	String	Sub-merchant business name or display name Format: UTF-8 encoded string Used for sub-merchant identification and reporting
money	M	Object	Transaction amount details with currency specification Contains transaction amount and currency information See Money Model
currency	M	String	ISO 4217 currency code specification Fixed value: PHP (Philippine Peso) Determines payment processing rules and settlement currency
amount	M	Number	Transaction amount in smallest currency unit Format: Integer value Example: 20000 represents PHP 20000 Range: 100-999999999
paymentMethod	O	String	Payment method used for transaction processing Format: Predefined payment method codes Examples: GCASH, PAY_MAYA, BPI_BANK Indicates the actual payment channel used See Payment Method List
expiryPeriod	O	Number	Transaction expiration time in seconds Format: Integer value Default: 3600 (1 hour) Maximum: 86400 (24 hours) Used to set transaction validity period
redirectUrl	O	String(256)	Customer redirect URL after payment completion Format: Valid HTTP/HTTPS URL Maximum length: 256 characters Used to redirect customers after payment processing
callbackUrl	O	String(256)	Webhook notification URL for transaction status updates Format: Valid HTTP/HTTPS URL Maximum length: 256 characters Used for real-time transaction status notifications

Example Body – Transaction Request:

Content-type: application/json
X-TIMESTAMP: 2020-12-17T10:55:00+08:00
X-SIGNATURE: 7MHd9v5/m9JeqmDZVwWBZUZ5J5...7120QnFEny7Qm7uQR1G0TWCh10fsU6nVxiRoeoQ==
X-PARTNER-ID: 20001

{
    "merchant": {
        "merchantId": "20011"
    },
    "money": {
        "amount": 20000,
        "currency": "PHP"
    },
    "orderNo": "200110edbb466abb04682968b40",
    "paymentMethod": "GCASH",
    "purpose": "Payment for online purchase",
    "redirectUrl": "https://www.example.com/success"
}

Response

HTTP Response

Field	Required	Type	Description
Content-Type	M	String	HTTP response content type specification Fixed value: application/json Indicates JSON response format
X-TIMESTAMP	M	String	ISO 8601 datetime format with timezone offset Format: yyyy-MM-ddTHH:mm:ss±HH:mm Example: 2020-12-17T10:55:00+08:00

Body Parameters

Field	Required	Type	Description
code	M	String	API response status code indicating operation result Format: Two-digit string Success: "00", Error: Other codes Used for programmatic response handling
message	M	String	Human-readable response status description Format: UTF-8 encoded string Provides detailed information about the operation result Localized based on request language
tradeNo	O	String	Internal transaction reference number for system tracking Format: System-generated alphanumeric string Used for internal transaction management and support
orderNo	M	String	Unique transaction identifier provided in the request Format: Alphanumeric string Same as the orderNo provided in the request Used for transaction tracking and reference
merchant	M	Object	Merchant information container Contains merchant identification and business details See Merchant Model
merchantId	M	String	Unique merchant identifier assigned by the platform Format: Alphanumeric string Used for merchant authentication and transaction routing
merchantName	O	String	Merchant business name or display name Format: UTF-8 encoded string Used for merchant identification and reporting
subMerchantId	O	String	Sub-merchant identifier for multi-level merchant structures Format: Alphanumeric string Used for sub-merchant identification and reporting
subMerchantName	O	String	Sub-merchant business name or display name Format: UTF-8 encoded string Used for sub-merchant identification and reporting
money	M	Object	Transaction amount details with currency specification Contains confirmed transaction amount and currency See Money Model
currency	M	String	ISO 4217 currency code specification Fixed value: PHP (Philippine Peso) Determines payment processing rules and settlement currency
amount	M	Number	Transaction amount in smallest currency unit Format: Integer value Example: 20000 represents PHP 20000 Range: 100-999999999
transactionTime	M	String	Transaction completion timestamp Format: yyyy-MM-ddTHH:mm:ss Example: 2020-12-17T10:55:00+08:00 Used for transaction timing and audit
channel	M	Object	Payment channel information container Contains payment method and processing details See Channel Model
status	O	String	Current transaction processing status Format: Predefined status codes Examples: PROCESSING, SUCCESS, FAILED, CANCELLED Indicates the current state of the transaction See Status Model

Content-type: application/json
X-TIMESTAMP: 2020-12-17T10:55:00+08:00

{
    "channel": {
        "additionalInfo": {
            "paymentUrl": "https://wpay.gpayment.net/api/payment_direct/redirect/ptpayd14302662"
        },
        "paymentMethod": "GCASH",
        "paymentUrl": "https://gateway.smilepayz.com/cashier/#/loading?tradeNo=1812003025061909313195096"
    },
    "code": "00",
    "merchant": {
        "accountNo": "11820011202403071031",
        "merchantId": "20011",
        "merchantName": "bradytest123www"
    },
    "message": "Successful",
    "money": {
        "amount": 20000,
        "currency": "PHP"
    },
    "orderNo": "20011563d9094aa7d4d9e9b933bb",
    "status": "PROCESSING",
    "tradeNo": "1812001125042115424463245",
    "transactionTime": "2025-06-19T10:31:33+08:00"
}

Notification

HTTP Request

Field	Required	Type	Description
Content-Type	M	String	HTTP request content type specification Fixed value: application/json Indicates JSON request format
X-TIMESTAMP	M	String	ISO 8601 datetime format with timezone offset Format: yyyy-MM-ddTHH:mm:ss±HH:mm Example: 2020-12-17T10:55:00+08:00
X-SIGNATURE	M	String	Digital signature for notification authentication See Callback Signature Verification

Body Parameters

Field	Required	Type	Description
orderNo	M	String	Merchant transaction identifier Format: Alphanumeric string Same as the orderNo provided in the original request Used for transaction identification and verification
tradeNo	M	String	Internal transaction reference number for system tracking Format: System-generated alphanumeric string Used for internal transaction management and support
merchantId	M	String	Unique merchant identifier assigned by the platform Format: Alphanumeric string Used for merchant authentication and transaction routing
merchantName	M	String	Merchant business name or display name Format: UTF-8 encoded string Used for merchant identification and reporting
subMerchantId	O	String	Sub-merchant identifier for multi-level merchant structures Format: Alphanumeric string Used for sub-merchant identification and reporting
subMerchantName	O	String	Sub-merchant business name or display name Format: UTF-8 encoded string Used for sub-merchant identification and reporting
paymentMethod	M	String	Payment method used for transaction processing Format: Predefined payment method codes Examples: GCASH, PAY_MAYA, BPI_BANK Indicates the actual payment channel used
transactionTime	M	String	Transaction completion timestamp Format: yyyy-MM-ddTHH:mm:ss Example: 2020-12-17T10:55:00+08:00 Used for transaction timing and audit
money	M	Object	Transaction amount details with currency specification Contains confirmed transaction amount and currency See Money Model
currency	M	String	ISO 4217 currency code specification Fixed value: PHP (Philippine Peso) Determines payment processing rules and settlement currency
amount	M	Number	Transaction amount in smallest currency unit Format: Integer value Example: 20000 represents PHP 20000 Range: 100-999999999
status	M	String	Final transaction processing status Format: Predefined status codes Examples: SUCCESS, FAILED, CANCELLED Indicates the final state of the transaction See Status Model

Return

Important Response

Notification Response: Please return only the string SUCCESS to acknowledge receipt of the notification

{
  "merchantId": "20001",
  "merchantName": "test",
  "money": {
    "amount": 100000,
    "currency": "PHP"
  },
  "orderNo": "2000102900000000000001",
  "status": "SUCCESS",
  "tradeNo": "181200012410241325417215",
  "transactionTime": "2020-12-17T10:55:00+08:00"
}

SUCCESS