Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can automate risk reviews for partitions (Facilitator portfolio), divisions (Referrer portfolios), or Merchants to trigger various actions using Payrix and third-party risk services to perform many different types of reviews automatically. This tutorial walks you through the steps to leverage policies to automate your risk decisions within your portfolio.

image-20240202-225651.png

Objective

Configure a policy to automate risk reviews in your portfolio for transaction processing or Merchant boarding.


Audience

  • Facilitators

  • Referrers

Environment

  • Portal (Sandbox)

  • Portal (Production)


Prerequisites

Info

Prerequisites:

  • You must have a fully boarded Payrix account to perform any of the actions described in the use case guides.

Warnings

Note

Warning: Some policy stages are not compatible with specific decision actions. The portal will identify if your configuration is invalid with your policy stage.

Note

Warning: Risk decisions and notifications will not work outside of the Payrix gateway. If you have questions, contact your relationship manager.

Tips

Tip

Tip: You can apply policies to your business model in multiple ways. Due to the complex nature of the product, this use case does not cover all decision types. Visit Understanding Policies - Risk for more details on each specific Policy Decision.

Additional Resources


Create a Policy

1.

Access the Policies

page.

Page

  1. Click the PLUS icon next to Risk in the left navigation panel to open a drop-down dropdown menu.

  2. Click Policies in the Risk drop-down dropdown menu to open the Policies page.

2.

Add

your new

Your New Policy

.

  1. Click ADD POLICY in the upper-right corner.

  2. Enter aname for the policy.

  3. Select thestage for the policy to apply:

Expand
titleClick here to see all available policy stages.
  • Create Entity: When an entity is created

  • Pre-board: When the entity is created, but not yet boarded

  • Underwriting: When an entity is being risk-reviewed for boarding

  • Post-board: After the entity has passed risk review and completed boarding

  • transaction: For any transaction processing event

  • Activation: When a payment terminal is activated in a payment transaction

  • Auth: When a credit card is authorized for a transaction

  • Post-Auth: After a credit card has already been authorized for a transaction

  • Capture: When a credit card payment is captured

  • Refund: When a transaction refund is issued

  • E-Check: When an eCheck transaction is processed

  • Change Review: When a bank account change request occurs from an entity

  1. Select the target of the policy:

    • Partition: Your entire Facilitator portfolio

    • Divisions: A Referrer portfolio

    • Merchants: A specific Merchant or Referrer entity

  2. Select thestatus of the policy:

    • Active: The policy is actively applied.

    • Inactive: The policy will not be applied until changed to Active.

Result: Your policy is now created and ready to be configured with decisions.

3.

Set

your first

Your First Decision

.

  1. Click Add Decision in the upper-right corner.

  2. Select a decision from the available risk services. Then, click Next.

  3. Add sub-decisions with applicable Subtypes, Operators, and Values for the decision type. Then, click Next.

  4. (Optional) Add any rules desired using the same parameter types used in the previous step to further refine the decision action trigger.

  5. Click Create to finish adding the decision.

Result: Your first policy decision is created, allowing you to create additional decisions to further refine the policy trigger criteria using the original decision as a dependency.

4.

Add

more

More Decisions with Dependencies and Failover Dependencies

  1. Repeat Steps 1-4 above. Then, click Next.

  2. (Optional) Select your first decision from the Dependencies drop-down dropdown menu.

    • This dependency will require this new second decision to rely on the original first decision to return the expected response before initiating the action.

  3. (Optional) Select your first (or another) decision from the Failover drop-downdropdown menu.

    • This Failover Dependency outlines another decision (the first) to resort to if this decision fails for the designated Fail Reason.

Result: You’ve created a secondary decision within your policy to further refine when it will take the set action, using your first decision’s response as the condition for whether or not to apply the second decision before the policy takes effect. You’ve also added a contingency plan for what this second decision should do if it fails for your given reason. Your policy is now configured.


Next Steps

After configuring your automated risk policies for your portfolio, review the following guides for related topics:


Conclusion

You’ve successfully configured a policy to automate your risk review for Merchant boarding or transaction processing actions and status changes. You can repeat these steps to refine your policy as much as needed and automate as many aspects of Merchant boarding or transaction processing as you’d like.


References

Click the links or items below to access any of the following pages: