Payment Configuration
Receiving and Sending Payment Methods Configurations
1. Receiving Payment Configuration
Overview
The Receiving Payment Configuration facilitates the payment-receiving process by defining the payment methods that will be included in the contract. This ensures that all payment-related configurations are standardized and aligned with the requirements of the merchant transaction.
Integration with Business Units (BUs)
The configuration can be linked to a Merchant Business Unit (BU).
Based on this linkage, the provider determines which specific configurations apply to the data.
Set Up a New Receiving Payment Configuration
Step 1: Define the Configuration
Navigate to the Payment Configuration Module.
Create a new configuration by selecting Receiving as the configuration type.
Specify the Provider Business Unit (BU) associated with this configuration.
Step 2: Specify Approved Payment Methods
Define the payment methods that will be allowed for contracts under this configuration.
Only the payment methods specified here will be available in the contract.
Set up a Receiving Payment Mapping
Step 1: Choose the Relevant Payment Configuration
Select the Receiving Payment Configuration created earlier.
Step 2: Apply the Configuration
Specify on whom this configuration will be applied. This includes:
Business Unit: Select the relevant Business Unit.
Company: Choose the specific company.
Widget: If applicable, select the widget.
Ensure the selected configuration aligns with the payment methods approved in the Payment Configuration.
Checkout Process for Receiving Configuration
During the checkout phase, the user finalizes the payment by selecting an appropriate payment method from the predefined Payment Cards. This process ensures that only approved payment methods, as defined in the Payment Configuration, are used.
The user has two options:
Select Payment Card: Select a card from the list of previously added and approved payment cards.
Add a New Payment Card: If the desired card is not available, the user can add a new card from the set of allowed payment methods defined in the configuration.
2. Issuing Payment Configuration
Overview
The Issuing Payment Configuration is designed to facilitate the process of transaction fulfillment by defining the required fields and configurations for Issuing virtual credit card payments. This ensures that all payment-related configurations are standardized and aligned with the requirements of the transaction client.
Important Note: In order for AirPlus virtual credit card issuning to be visable, the Merchent needs to have a Reciving Payment Config that include a MasterCard payment method. This is a prerequisite for processing AirPlus payments.
Integration with Business Units (BUs)
The configuration is linked to a Client Business Unit (BU).
Based on this linkage, the client determines which specific configurations apply to the data.
Steps to Set Up a New Issuing Payment Configuration
Step 1: Define the Configuration
Navigate to the Payment Configuration Module.
Create a new configuration by selecting Issuing as the configuration type.
Specify the Client Business Unit (BU) associated with this configuration.
Step 2: Configure AirPlus Fields
Define the fields required for AirPlus payments. These fields include:
Accounting Unit (AE)
Accounting Code (AK)
Order Number (AU)
Departure Date (BD)
Department Code (DS)
Internal Account (IK)
Cost Center (KS)
Employee Number (AE)
Project Number (PR)
Destination (R2)
For each field, specify whether it is:
Mandatory: Must be filled by the user.
Optional: This can be filled by the user but is not required.
Not Used: The field will not appear in the configuration.
3. Company Data Field Mapping
The Company Data Field Mapping must be configured to ensure seamless integration with Issuing Payment Configuration. This involves mapping the fields in the system to the corresponding fields in the Issuing Payment Configuration.
Steps to Configure Company Data Field Mapping:
Navigate to the Company Data Field Mapping section.
Map each field in the system to its corresponding field in the AirPlus configuration. For example:
Map the Accounting Unit (AE) in the system to the Accounting Unit in AirPlus.
Map Cost Center (KS) in the system to Cost Center in AirPlus.
Ensure that all mandatory fields are properly mapped to avoid errors during the checkout process.
4. Checkout Process for AirPlus Payments
During the checkout phase, the user completes the payment process by filling in the required AirPlus fields. This process ensures that all mandatory fields are filled, and the payment is processed seamlessly.
Steps to Complete the Payment:
Select Reporting:
The user selects Reporting to display all the fields required for the Issuing payment card + required fields missing by any reporting requirements.
Fields marked as Not Used will not appear in the form.
Fill in Mandatory Fields:
The user fills in all fields marked as Mandatory.
Optional fields can be filled if needed.
Submit Payment:
Once all mandatory fields are filled, the user submits the payment.
The system validates the fields and processes the payment using AirPlus.
Last updated
