SenangPay icon

SenangPay

Generate SenangPay payment URL, query transaction, or manage recurring payments

Actions4

Generate Payment URL

AI-generated

Overview

This node generates a SenangPay payment URL for processing payments, queries transaction status, generates recurring payment URLs, or processes recurring payment callbacks. It is useful for automating payment workflows, such as creating payment links for customers, checking payment status, and handling recurring payments in e-commerce or subscription services.

Use Case Examples

  1. Generate a payment URL for a customer to complete a transaction with specified amount, order ID, and customer details.
  2. Query the status of a specific transaction using its order ID.
  3. Generate a recurring payment URL for subscription-based services.
  4. Process callback data from SenangPay to verify recurring payment status.

Properties

Name Meaning
Detail Description or details about the payment transaction.
Amount The payment amount to be charged, with a minimum value of 2 and precision of 2 decimal places.
Order ID Unique identifier for the order or transaction.
Name Customer's name associated with the payment.
Email Customer's email address.
Phone Customer's phone number.
Timeout Timeout duration in seconds for the payment URL validity; 0 means no timeout.

Output

JSON

  • paymentUrl - The generated SenangPay payment URL for the transaction.
  • qrLink - A QR code URL representing the payment URL for easy scanning.

Dependencies

  • Requires SenangPay API credentials including merchant ID and secret key.

Troubleshooting

  • Ensure the merchant ID and secret key credentials are correctly configured to avoid authentication errors.
  • Verify that the amount is at least 2 and formatted correctly to prevent validation errors.
  • Check that the order ID is unique and properly set to avoid conflicts.
  • If the hash validation fails during recurring callback processing, the callback data will be rejected with an 'invalid hash' error; ensure the secret key and data integrity are correct.

Links

Discussion