Paytia portal · Payment rules

Paytia portal · Payment rules

Managing Payment Rules


Payment rules let you attach your own business logic to the checkout. A rule watches for a condition — a card type, a country, a payment amount, a service key — and, when it matches, takes an action: show or hide a payment button, add a management fee, apply a fee plan, or route the payment through a chosen gateway. Rules are built from two reusable ingredients you create first — Payment plans (fee-by-amount tables) and BIN groups (card-matching groups) — then combined in the rule builder.
A · Build the ingredients
Payment plans · BIN groups
B · Create the rule
When this happens › Do this
C · The result
Fee & buttons at checkout

01 · Open the Payment rules dashboard
/ Manage payments › Payment rules

Go to Manage payments › Payment rules. Every rule on the account is listed here, showing the condition (When this happens), the action (Do this) and the rule’s Case type. The three buttons top-right are your starting points: Create Payment rules, Manage Plan and Create Bin Group.

→ Order Build your Payment plans and BIN groups first (steps 02–03) — the rule builder in step 04 lets you pick them by name, so they need to exist before you create the rule that uses them.


02 · Create a Payment Plan (fee by amount)
/ Payment rules › Manage Plan › Payment plan

A Payment plan is a table of amount bands, each with a flat fee. When a rule applies a plan, Paytia finds the band the payment total falls into and adds that fee as a management charge. Click Manage Plan on the dashboard, then Add Plan. A single plan can hold several bands — here Card Payment charges £10 up to £500, £15 to £1,000 and £20 to £2,500.

Paytia — Payment Plan
Payment plan table showing Bank payment and Card Payment plans with From, To and Fee bands
Paytia — Add Plan
Add Plan modal with Plan name, From amount, To amount and Fee fields
→ Tip Use the + button to add more bands to the same plan before saving. Keep bands continuous (e.g. the next band starts at 501.00) so every amount lands in exactly one band.
03 · Create a BIN Group (match cards)
/ Payment rules › Bin groups

A BIN group matches cards by their characteristics — Card Type, Card Brand, Card Category or Card Country — so a rule can react to “commercial credit cards” or “UK Amex” without you listing individual BINs. Click Create Bin Group on the dashboard, then Add Group. Each condition is a Field / Operator / Value triple, joined with AND or OR.

Paytia — Bin groups
Bin groups table showing Commercial Credit Cards and UK AMEX Cards with their field conditions
Paytia — Add group
Add group modal with Group name and Field, Operator, Value conditions joined by AND
/ BIN group field reference

Field — the card attribute to test: Card Type (Credit / Debit / Charge Card), Card Brand (Visa, Amex…), Card Category (Personal / Commercial) or Card Country.

Operator — Equals (=) or Not Equals (!=).

AND / OR — the joiner between conditions. AND means every condition must match; OR means any one is enough.

+ Add — appends another condition. Use the red bin to remove one. Save to store the group.

04 · Create the Payment rule
/ Payment rules › Create Payment rules

Now tie it together. Click Create Payment rules. Name the case, choose where it applies (Select Type), define the trigger under When this happen, and pick the outcome under Do this. The panel on the left previews the rule as a When this happens → Take this action flow.

Paytia — Create Payment rule
Create Payment rule screen with the When this happens to Take this action flow on the left and the rule form on the right

The Choose value dropdown is the trigger, and the Do this › Select value dropdown is the action:

When this happen — Choose value
Choose value dropdown listing Amount, Account number, Billing country, Shipping country, Payment method selection, Currency Code, Service_type and BIN groups
Do this — Select value
Do this dropdown listing Add Fee, Plan, Payment gateway, Payment method configuration, Hide payment method and Show payment method
/ Rule field reference

Select Type — where the rule runs: Checkout API, ACA User Interface (agent capture), or Both.

Choose value (the trigger) — Amount, Account number, Billing country, Shipping country, Payment method selection, Currency Code, Service_type, or any BIN group you created in step 03.

Add condition — the comparison: Equals / Not equals / Greater than / Less than / ≥ / ≤ for values, or If Match for a BIN group. Use the + to stack several conditions.

Do this (the action) — Add Fee (flat amount), Plan (apply a payment plan), Payment gateway (route to a processor), Payment method configuration, Hide payment method, or Show payment method.

! Add Fee vs Plan Add Fee applies one flat charge whatever the amount. Plan applies the banded fee table from step 02, so the charge scales with the payment total. Pick Plan when the fee should vary by amount.
05 · What the customer sees
/ Checkout · Order summary

When a rule matches at checkout, the effect appears in the customer’s Order summary. Below, the entered card triggers the Commercial Credit Cards rule, so Paytia shows the additional fee and folds it into the amount to pay — the £17.50 subtotal plus a £6.00 rule fee gives the £23.50 total.

Paytia — Checkout order summary
Customer order summary showing subtotal, card entry and an additional fee of six pounds bringing the total to twenty three pounds fifty
→ Note If the rule instead hides or shows a payment method, the customer simply sees fewer or different payment buttons — no fee line appears.
/ At a glance
Ingredients first, then the rule.
Create your fee plans and BIN groups, then a rule joins a condition to an action and applies it at checkout.
/ Setup checklist
✓  Payment plan(s) created
✓  BIN group(s) created
✓  Rule named & type chosen
✓  When-this-happens condition set
✓  Do-this action selected & saved
/ Need help?
Paytia support.
If a rule doesn’t fire, check the Case type matches where you’re testing (Checkout API vs ACA) and that the plan or BIN group it points to still exists.

    • Related Articles

    • Adding custom fields to capture more payment information

      How do I add fields to send additional custom values to Paytia and a payment gateway? Note: Custom fields is an additional licence. If you require this please contact sales@paytia.com Paytia has now introduced Custom fields as an additional licence ...

    • Paytia API services

      API Services Playtia provides REST API services, allowing our customers and system integrators to programatically control the Paytia transaction processing service from their own web/database applications. Paytia have three versions of API services ...

    • Paytia Proxy Gateway

      Technical Overview, Configuration, and Test Guide 1. Overview The Paytia Proxy Gateway is a flexible payment gateway that enables organisations to securely pass captured payment data from their environment to third-party systems using a fully ...

    • Paytia API exception handling

      Paytia API Exception Handling The Paytia API services provide status update webhooks to track processes and status changes. These updates include standard API posts as well as exception handling for telephony-related processes. Below are details ...

    • Webhooks sent from Paytia to API users for the payment capture IVR flow

      Paytia IVR webhook flow The initial post into Paytia will return a URL for the Paytia iframe. If you do not want to use the iframe you can ignore that response post ‘url’ value. Note: Paytia will maintain the reference_id value throughout the payment ...