Initiating a General Payment

These are the step a user must take to initiate a payment regardless of the payment type or payment schema:

Open the FintechOS Portal using the credentials given.
Insert the SMS code you received on your phone.
Choose the Business Unit, i.e. the customer for whom the transaction is made. This screen is available for those users who have access to multiple customers with only one set of credentials.
HINT
A user can have access to multiple customers (which could be multiple companies' account(s), the user's own account(s), etc.)
Insert the OTP code sent via SMS.
From the homepage, click Payments on the footer
or select an account by clicking View Account, then click Payments.

The Make a Payment page is displayed. On this page, depending on the beneficiary IBAN, payer account, amount, payment currency and BIC/SWIFT and other mandatory fields, the system verifies the checks explained below and returns a list of payment schemas from which the user must choose from or one schema, which then is displayed as the title.

Fill in the following fields for a new payment:

Fields	Type	Description
FROM	Lookup	Select the current account from where to send the amount by clicking on the drop-down arrow. It displays all the accounts: the alias of the accounts and the IBAN/account number for the accounts without an alias. HINT The accounts displayed are the accounts for which the user has at least the right for Account Balance & Details according to Back-Office Administration. This field is automatically filled with the account number only when the payment was initiated from the Account details page.
Available Balance	Numeric	This field is displayed once the FROM account has been chosen. It displays the amount available for the specifically chosen bank account.
On behalf of (Ultimate Payer)	Text	This field is displayed in the case of small value domestic payments, with the exception of budget payments.
TO	Lookup	The user can: search and select a saved payment template or search and select a saved beneficiary.
Or add new recipient
Beneficiary	Text	Insert the name of the recipient. Field valid for: SEPA Credit Transfers Payments (case I) SEPA EUR Instant (case H) TARGET2 Small Value Payments Local Currency Instant Payments. Insert the name of the actual beneficiary in the case of sending funds to a company.
Account	Text	Insert the destination bank account. In the case of an IBAN: Depending on the structure of the IBAN, the types of payments are displayed. The system validates the format of the IBAN, if the system recognizes the IBAN, it automatically fills in the Beneficiary field and the Beneficiary Bank. After the values are displayed, they become read-only. There is a default maximum length available for the Account. The length is set using the script FTOS_IB_GetPaymentFieldsLengthBySchema. See for details. In the case of an account number, there is no validation done on the format of the number. When the account number is inserted, the type of payment is determined and the title of the page changes to display the name of the type of payment schema.
Beneficiary Bank	Text	This field is read-only. The bank is identified using the IBAN (B, C, D, E, F, G, H, I, J cases) or the BIC/SWIFT code for case A.
Beneficiary Address	Text	Insert the address of the receiver.
BIC or SWIFT	Text	Insert the code BIC or SWIFT. The identified BIC/SWIFT is made from: the IBAN inputted by the user or manually inputted by the user for SWIFT (Initializing a Non-SEPA SWIFT Payment). The system searches for 11 characters identified BIC/SWIFT, and if a value cannot be perfectly matched, it searches for the first 8 characters. If the code inserted is found within the entity FTOS_IB_BICSWIFT, but the account inserted is not an IBAN format, the system displays a toast message informing the customer that they need to insert an IBAN.
Beneficiary Bank Country	Text	Insert the country of the destination bank in the cases of Case A (SWIFT) Case H (SEPA Instant EUR) Case I (SEPA Credit Transfer Payments EUR) Case J (TARGET2).
Payment Details
Amount	Numeric	Insert the amount you wish to send to the person/company.
Currency	Lookup	The currency of the amount being transferred. The list is authentically ordered. For budget payments, the currency is by default the local currency.
Total amount paid in FROM account currency including commissions	Numeric	It is read-only. It is displayed only after all the mandatory fields are completed. The value is in the currency of the account from which the sum is sent. If the selected payment currency is different than the currency of the FROM account, then the Total amount is calculated with the exchange rates in place at the moment of payment and displayed in the currency of the FROM account.
Commissions	Numeric	The value of the commissions charged by the bank. It is displayed only after all the mandatory fields are completed.
FX Rate	Numeric	The value of the exchange rate in case the currency of the payment is not the currency of the FROM account. It is displayed only after all the mandatory fields are completed. The rates applied are: BuyNonCash (foreign currency to local currency) SellNonCash (local currency to foreign currency).
Execution Date	Date Time	Schedule the payment by selecting a date. From the calendar only the first date available is the current day, followed by the day after and so on up until 90 days, see Processor Settings for details.
Details	Text	Insert a description for the payment such as an invoice number.
Category Purpose	Option set	Select a value from the drop-down. This field is displayed for: SEPA Credit Transfers Payments (case I) SEPA EUR Instant (case H) TARGET2 Small Value Payments LCY Instant Payments It is mandatory only for the local currency instant payments.
Payment Type	Boolean	Select the type of payment.
Details of Charges	Option set	It is displayed for: Non-SEPA Foreign Currency Payment (case A) TARGET2 EUR payments (case J): if the beneficiary country is outside of the EU the customer should be able to choose from all three charges if the beneficiary country is in the EU, the default value is SHA SEPA Instant (H) - SHA value pre-selected and it is not editable SEPA Payments (I) - SHA value pre-selected and it is not editable. Choose between: SHA The user pays the bank's outgoing transfer charge. The beneficiary bank receives the payment minus the correspondent (intermediary) bank charges. OUR The user pays all transfer charges. BEN The user does not pay any charge. The beneficiary bank receives the payment minus all transfer charges. Available for SWIFT payments only.. If the country is in the EU, only SHA and OUR can be selected.
Settlement Date	Option set	It is displayed only for SWIFT payments. It is the date when the funds arrive in the account of the beneficiary: If the country is in European Union, only SHA and OUR are displayed and can be selected If the country is outside European Union all 3 values are displayed. Choose between: SAME Same day transfer (it becomes un-available if the cut-off hour is passed), TOM The transaction is sent to the beneficiary on the working day after the user has instructed the trade. (execution date +1, in the case the execution date is not holiday), SPOT This is usually the default payment type within foreign exchange. It means your payment is settled and sent to your recipient 2 days after the trade is instructed. (execution date +2, in the case the execution date is not holiday).
Save as Payment Template	Boolean	By ticking this field, the payment is saved and a new field is displayed Payment Template Name.
Payment Template Name	Text	Insert the name of the payment template.
Save Contact Details	Boolean	By ticking this field, the beneficiary is saved and a new field is displayed Beneficiary Template Name.
Beneficiary Template Name	Text	Insert the name of the beneficiary template.
Visible?	Boolean	Check this box to mark whether or not the other users can see this template.
Fields available for the saved recipients
Amount	Numeric	Insert the amount you wish to send to the person/company.
Payment Date	Date	The date when the payment is executed.
Payment Details	Text area	Insert the details for the payment.

The payment has the status Initiated. For details, see Business Workflows Processor. The system calls the custom method validateAgnosticPayment (found within the server automation script libraries FTOS_IB_Payments and FTOS_IB_Payments.Custom).

Click Review Payment. By clicking that button, if applicable, the payment template and the beneficiary template are saved. The page Review Payment Details is displayed. It contains the read-only data:

Field	Description
From	The source account.
To	The beneficiary name and account.
Available balance	The sum available in the FROM account.
Total	The total amount to be paid in the currency of the source account. Total amount to be debited is calculated based on the equivalent amount in payer account currency + fee.
Payment amount	The amount to be transferred.
Payment type	The type of payment: Non-SEPA SWIFT Payments Intra-BankOwn Account Foreign Exchange Intra-BankOther customer from the same financial institution Instant Payments High-value domestic payments OR Urgency Small value domestic payments SEPA Instant SEPA Payments TARGET2.
Execution Date	The date when the amount arrives in the account of the beneficiary.
Payment reason	The reason for the transfer.

Based on the business workflow FTOS_IB_Payment_Flow the status changes to Authorization required (Authorization required, Authorized, Pending Available Balance, Sent to corebanking, Executed, Rejected) the system does not allow to change of data from the fields in the entity FTOS_IB_Payment, except the execution date.

To proceed, click Confirm. To cancel, click Back.

NOTE
If the user who initiated the payment has authorization rights as well, they are able to sign through Strong Customer Authentication

Strong customer authentication (SCA) is a requirement of EU Revised Directive on Payment Services (PSD2) on payment service providers within European Economic Area. The requirement ensures that electronic payments are performed with multi-factor authentication, to increase the security of electronic payments.[1] Physical card transactions already commonly have what could be termed strong customer authentication in EU (Chip and PIN), but this has not generally been true for Internet transactions across EU prior to the implementation of the requirement,[1] and many contactless card payments do not use a second authentication factor.. If not, the payment must be authorized by a user who can. That flow continues as described in Authorizing a Payment.

If the user has the rights, the page Terms & Conditions is displayed informing you that you need to insert an OTP sent via SMS to authorize the payment. Click Send.
A pop-up window is displayed informing you to sign the payment by inserting the code. There are six boxes where to insert each letter of the OTP. To verify the OTP inserted, click Authorize.
If the code was not sent, click Re-send code.
If you have trouble seeing the code, click Call me.
Before changing the status to Authorized, for single signatures, the beneficiary account is one of the own accounts of the customer. The transfer is rejected, if the account is an own account and the system sends a notification by mail to the help desk address in the bank.
A confirmation message is displayed for the single signature A payment authorization that requires only one validation by a user (confimration by inserting the OTP sent via SMS). scenario. If it is the case to be a joint signature, there is the message The payment has been posted in the Order List for the joint authorized Approver to sign. Click Home to return to the Homepage. The payment Id is in the status Authorized.
If the code inserted was wrong, then the user is directed to the page Wrong authorization code with the following message: You have 4 remaining retries. If you want to try again, click Send. If you want to try again later, select Try again and you will be directed to the Homepage. The payment will remain initiated, and you will be able to sign it for the Order List.
Click Send to reinitiate the signature process.
Click the Try later button to save the payment and re-initiate it from the List of Orders and Multiple Authorizations of a Payment.
NOTE
Every two minutes, the scheduled job named FTOS_IB_PaymentsQueue runs to send the payment to Core Banking after it has been authorized by all the persons needed and its status is Authorized.

Malicious Attack

If the payment failed due to the reason that the payer account inactivated or does not belong to the user the screen displays the following message: There was a problem processing your payment, please try again later.

Click Home to return to the Homepage. The payment Id is in status Rejected.

An email is sent to the bank to inform them that the payment might have been a malicious attack.

IMPORTANT!
Transfers from a current account to a deposit or savings account are not a payment, and therefore it is not covered in this chapter.