Versions Compared

Old Version 1

changes.mady.by.user Miles Graves

Saved on

compared with

New Version 2

changes.mady.by.user Ada Li

Saved on

Key

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

You can automate risk reviews for Partitions partitions (Facilitator portfolio), Divisions 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 will walk walks you through the steps to leverage Policies policies to automate your risk Decisions decisions within your portfolio.

image-20240202-225651.png

Objective

Configure a Policy 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

Warnings will provide insight or advice to avoid issues related to risk, visibility, and overall product performance during this use case.

Note

Warning: Some Policy “Stages” policy stages are not compatible with specific Decision Actions, the Portal decision actions. The portal will identify if your configuration is invalid with your Policy Stagepolicy stage.

Note

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

Tips

Tips will provide suggestions to streamline or better prepare you to apply this use case tutorial.

Tip

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

Additional Resources

Create a Policy

1. Access the Policies page.

Step 1:

  1. Click the PLUS icon next to Risk in the left

-hand

  1. navigation panel to open a drop-down menu.

Step 2:

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

2. Add your new Policy.

Step 1:

  1. Click

the

  1. ADD POLICY

button

  1. in the upper-right corner.

Step 2:

  1. Enter a

Name

  1. name for the

Policy

  1. policy.

Step 3:

  1. Select the

Stage

  1. stage for the

Policy

  1. policy to apply:

Expand
titleClick here to see all available Policy 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.

Step 3:

  1. Select the

Target

  1. target of the

Policy

  1. policy:

    • Partition

-

    • : Your entire Facilitator portfolio

.

    • Divisions

-

    • : A Referrer

Portfolio

    • portfolio

    • Merchants

-

    • : A specific Merchant or Referrer entity

.

Step 4:

  1. Select the

Status

  1. status of the

Policy

  1. policy:

    • Active

-

    • : The

Policy

    • policy is actively applied.

    • Inactive

-

    • : The

Policy

    • policy will not be applied until changed to Active.

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

3. Set your first Decision.

Step 1:

  1. Click

the

  1. Add Decision

button

  1. in the upper-right corner.

Step 2:

  1. Select a

Decision

  1. decision from the available risk services. Then, click Next.

Step 3:

  1. Add

Sub

  1. sub-

Decisions

  1. decisions with applicable Subtypes, Operators, and Values for the

Decision

  1. decision type. Then, click Next.

Step 4:

  1. (Optional) Add any

Rules

  1. rules desired using the same parameter types used in

Step 3

  1. the previous step to further refine the decision action trigger.

Step 5:

  1. Click

the

  1. Create

button

  1. to finish adding the

Decision

  1. decision.

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

4. Add more Decisions with Dependencies and Failover Dependencies

Step 1:

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

Step 2:

  1. (Optional) Select your first

Decision

  1. decision from the Dependencies drop-down.

    • This

Dependency

    • dependency will require this new second

Decision

    • decision to rely on the original first

Decision

    • decision to return the expected response before initiating the action.

Step 3:

  1. (Optional) Select your first (or another)

Decision

  1. decision from the Failover drop-down.

    • This Failover Dependency outlines another

Decision

    • decision (the first) to resort to if this

Decision

    • decision fails for the designated Fail Reason.

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

Next Steps

Once you’ve configured After configuring your automated risk policies for your portfolio, review the following guides for related topics:

Conclusion

You’ve now successfully configured a Policy policy to automate your risk review for Merchant Boarding boarding or transaction processing actions and status changes. You can repeat these steps to refine your Policy 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: