Payssion, Duitku and TriPay Modules

17 views Markdown

Set up Payssion, Duitku or TriPay and enable the payment methods approved for your merchant account.

Reaching the Screen

Open Settings → Financial → Payment Gateways → All Modules and select a provider’s payment method.

Examples: {admin}/modules/payment?module=Payssion_pixbr, {admin}/modules/payment?module=Duitku_cc, {admin}/modules/payment?module=Tripay_cc.

What Is on the Screen

There is no shared provider settings screen. Each child method has its own credentials and status. Changes to one method do not configure its siblings.

The installed families contain 75 Payssion, 22 Duitku and 15 TriPay methods. These include wallets, bank accounts, retail payments and cards. Installed methods are not necessarily available to your account.

Before You Configure It

Register with the provider, complete merchant approval and obtain credentials for the chosen environment. Request activation of each desired channel. Use HTTPS and a publicly reachable payment callback.

Confirm the Existing API Is Accepted

Payssion uses the older v1/form integration, while current documentation describes v2. Duitku still signs with MD5; current documentation marks MD5 obsolete and requires HMAC-SHA256. Obtain compatibility confirmation before enabling either family.

Fields

Payssion

Payssion - API KeyRequired; initially blank. Obtain an API key for the legacy integration.
Payssion - Secret KeyRequired; initially blank. Use the matching Secret Key; a v2 key alone is insufficient.
Test ModeOff initially. Uses one generic sandbox method for all channels. Its old sandbox URL uses HTTP; verify secure-browser compatibility first.

Duitku

Duitku Merchant CodeRequired; initially blank. Project merchant code from the Duitku portal.
Duitku API KeyRequired; initially blank. API key from the same project and environment.
Duitku EndpointRequired. Default: https://passport.duitku.com/webapi; sandbox: https://sandbox.duitku.com/webapi. No separate test switch.
Duitku Expiry PeriodDefaults to 1440 minutes. Set a positive duration within the method’s limit, no more than 1440.

TriPay

Mode IntegrasiDefaults to Sandbox. Production enables real transactions.
Merchant CodeRequired; initially blank. Merchant identifier for the selected mode.
API KeyRequired; initially blank. API Key for that merchant and mode.
Private KeyRequired even in sandbox; initially blank. Merchant Private Key signs requests and verifies notifications.
Masa AktifChoose 1–14 days. Blank or zero uses one day.
Tipe CheckoutChoose REDIRECT. All 15 current methods redirect even when DIRECT is selected.
Verifikasi Data CallbackBlank/disabled initially. Aktif adds an API status check; enable for Production. Signature verification always remains mandatory.

Status, fees, amount limits and country restrictions follow Payment Modules.

Tasks

Configure the Provider

  1. For Payssion, obtain the approved legacy API/Secret Key pair. For Duitku, open the matching sandbox or production project and copy its Merchant Code and API Key.
  2. For TriPay sandbox, open API & Integrasi → Simulator → Merchant → Detail. For live credentials, use Merchant → Opsi → Edit.
  3. Enter matching credentials in the selected WISECP method. Enable Status and click Save Changes.
  4. For TriPay, save WISECP’s complete generated Callback URL in the merchant’s callback setting. The module does not include it in transaction requests.

Enable Child Methods

  1. Check channel availability in the provider account. For TriPay use the merchant’s Channel Pembayaran settings in the matching mode.
  2. Configure each approved child method separately. For multiple TriPay channels on one merchant, verify that the registered callback processes each channel correctly.
  3. Open Payment Gateways → Initial → Enabled Module Selection, select those methods and click Save Changes.
  4. Create integer-IDR invoices for Duitku and TriPay. Payssion requires the selected channel’s supported currency. Shared conversion does not adjust these requests.

Test and Track Payment

  1. As the invoice’s client, select a method and click Pay Now. Test success, cancellation, expiry and delayed notification with approved sandbox credentials.
  2. Compare the provider reference, amount, currency and invoice record. Payssion checks signed notifications; Duitku rechecks transaction status; TriPay requires a signed PAID event.
  3. A browser return does not prove payment. Investigate waiting or partial payments in both systems before retrying or manually recording payment.
  4. After compatibility and channel tests pass, save live credentials and environment settings separately for each enabled method.

Refund and Reconcile

Duitku and TriPay have no gateway refund operation. Payssion’s legacy refund function does not receive the current invoice payment structure correctly. Arrange refunds with the provider and confirm completion.

Record the external result at {admin}/invoices/detail?id={invoice}. Use Summary → Change Status → Refunded and Update Status without requesting another gateway refund.

Things to Watch

Payssion partial payment can leave the invoice unpaid; an overpayment does not automatically create extra credit. Reconcile actual received amounts. Duitku MIGS has no credential-code field in this form; confirm compatibility before enabling it.

These modules do not provide WISECP card storage, automatic payment, subscriptions, installment selection or a connection-test button. Keep credentials available while notifications are pending.

Required Privileges

Settings require Modules → Payment Gateways (MODULES_PAYMENT_SETTINGS). Invoice changes require Billing → Edit (INVOICES_OPERATION).

Was this helpful?

Thanks for your feedback!

Still Need Help?

Our support team is here around the clock for anything you can't find above.

Contact Us Open a Ticket

We use cookies to keep you signed in, remember your language and currency, and improve the site. Cookie Policy