{{variable.MSD}}{{variable.IPG_MonriOnline1}}

Introduction

{{variable.IPG_MonriOnline}} [{{variable.IPG_MonriOnline1}}] provides online payment services for your web shop solution.

Requirements

Requirement	Details
Account on test environment	Contact Monri Sales and/or support for more details
Access to documentation	{{variable.IPG_TechnicalDocumentation}}
Additional information	If you don’t have any information yet please contact our sales ecomm-prodaja@monri.com

Please select what type of integration will be used if not already defined with our key account manager.

Types of integrations by your use-case:

Type of transactions:

{{glossary.MD-Pay Authorization}} - First step of two-step authorization. In this step fund are ‘only’ reserved on the buyers/users account. Authorization is also known as pre-authorization.
Purchase - Direct payment authorization where funds are immediately transferred form buyer's card to the merchants acquiring bank account.
Capture - Second possible step of the two-step authorization. Funds are now transferred form buyer's card to the merchants acquiring bank account. Capture is also known as post-authorization.
Refund - Funds are returned/refunded to the buyer/card user.
Void - Second possible step of the the two-step authorization.

NOTE: For more information about transaction types please refer to: Transaction Types

Technical integrations:

Redirect
Components
Mobile (Monri SDK)
- Android
- iOS
PayByLink API integration
Lightbox
Supported frameworks used for cross-platform mobile app development: Flutter, React Native, Ionic

{{glossary.MD-Pay Callback}} & Webhooks
Installments
Discounts (BIN or Card targeted)
Customers module
Limitations on initial {{glossary.MSD-IPG request}}:
- Custom attributes
- Rules
Custom parameters

Features that can only be set by the Monri support agent:

Monri tokenization
Note: one time setup needed from Monri side for test and production alike
Discounts
Web-Hooks (back-off response mechanism for different authorization steps)
- For declined transactions (3DS decline is not included)
- For all other steps: approved or declined transactions for refund, void, authorization; tokenized card transactions
  Additional
  Add all other statuses. Consider creating a snapshot of every possible variation with additional explanations.
  Example:
  transaction:refund:approved - Your configured endpoint will receive information for an approved refund transaction.

For any information regarding business side or something in the process is not clear, please contact our sales at {{variable.IPG_SalesContactEmail}}.