TRANXACT.AI Help
Accounting › UPI Collection

Payment Engines

The UPI rail, the apps on it (Google Pay, PhonePe, Paytm, BHIM) and the gateways that route it. An app is a package hint, not a separate integration.

Where to find it

  1. Module: Accounting
  2. Group: Close & Compliance
  3. Section: UPI Collection
  4. Screen: Payment Engines

Address in the console: /india/payment-engines

List · 9 columns · 18 fields on its form · 3 of them required · 1 action

What the list shows

These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.

ColumnKindField name
CodeCodecode
NameTextname
KindStatusengine_kind
CollectYes or nosupports_collect
RefundsYes or nosupports_refund
CeilingAmountmax_amount
EnvironmentStatusenvironment
DefaultYes or nois_default
ActiveYes or nois_active

The form

What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.

FieldTypeChoicesNotes
Code required Text
Name required Text
Kind required Choice upi_app, upi_psp, gateway, netbanking, card, wallet, nach, bharat_qr
Android package Text
iOS scheme Text
Intent links Yes or no
Collect requests Yes or no
QR Yes or no
Mandates Yes or no
Refunds Yes or no
Merchant id Text
Endpoint Text
Environment Choice sandbox, production
Ceiling per payment Number
Default Yes or no
Active Yes or no
Order Number
Notes Long text

What you can do here

Set webhook secret

On each row of the list.

The secret the PSP signs its callbacks with. Stored sealed; only its last four characters are shown again.

Asks for: Webhook secret*

* required

The rules that apply here

Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:

Beside it in UPI Collection