General Scope
Incoming Bank Transfers include all inbound payments—SEPA Credit Transfers (SCT), SEPA Instant Credit Transfers (SCT Inst), and non-SEPA (cross-border) transfers—directed to Wallets or Accounts held with us.
We act as the Beneficiary Payment Service Provider (PSP) and is responsible for ensuring that payments correctly addressed to IBANs issued by us are received, validated, and credited in accordance with applicable EU and Maltese law, including:
- Directive (EU) 2015/2366 (PSD2);
- Regulation (EU) No 260/2012 (SEPA Regulation);
- EPC SEPA Credit Transfer and SEPA Instant Credit Transfer Rulebooks; and
- Regulation (EU) 2024/1623 (on Instant Payments and Verification of Payee).
Our role is limited to:
- receiving and processing the payment message via SEPA or corresponding networks;
- conducting all required sanctions, AML/CFT, and fraud checks; and
- crediting the Wallet corresponding to the IBAN issued by us.
Receipt and Credit Timing
i. SEPA Credit Transfers (SCT)
We will credit funds to the Wallet Holder’s Wallet no later than the end of the Business Day following the day on which funds are received in our settlement account, in accordance with Article 87(1) PSD2 and Section 5.6 of the EPC SEPA Credit Transfer Rulebook.
ii. SEPA Instant Credit Transfers (SCT Inst)
We support SEPA Instant execution when:
- the Beneficiary IBAN is active;
- the IBAN is not restricted, blocked, or subject to limitations under Article 3.2 (Transaction Limits), Article 3.4 (Blocking or Refusal), or any judicial, regulatory, or sanctions-related order; and
- the transfer meets the scheme and liquidity thresholds set by the SEPA Instant framework.
If the Beneficiary IBAN is subject to an active limitation, such as a regulatory freeze, antifraud block, or internal transaction restriction, the payment will be declined or queued for standard SEPA processing.
Funds for SEPA Instant payments shall be made available immediately upon receipt confirmation, subject to these conditions and technical availability under EPC SCT Inst Rulebook Section 5.3.
iii. Non-SEPA Transfers
For cross-border payments outside SEPA, we credit funds upon receipt and validation through its correspondent network.
Value dating corresponds to the date our account with its correspondent is credited.
Verification of Payee (VoP) for SEPA Incoming Transfers
i. Provision of VoP Service
We provide Verification of Payee (VoP) capability to Originator PSPs and their customers (Originators) to verify that the Beneficiary Name corresponds to the Wallet Holder Name linked to the IBAN issued by us.
This functionality complies with Regulation (EU) 2024/1623, PSD2 Articles 86–88, and EPC VoP Standard (Version 1.1, 2024).
ii. VoP Outcomes and Impact on Liability
Result: Match
Description: Full correspondence between Beneficiary Name and Wallet Holder Name for the IBAN.
Our Action: Payment credited without delay.
Liability Allocation: We assumes Beneficiary PSP responsibility under PSD2 Art. 86(2).
Result: Close Match
Description: Minor differences (abbreviations, punctuation, or formatting).
Our Action: Originator PSP must seek confirmation from its customer before execution.
If executed despite a “Close Match,” liability rests with the Originator PSP.
Liability Allocation: We bear no liability if the Originator or Originator PSP executes despite a “Close Match” alert.
Result: No Match
Description: Beneficiary Name does not correspond to the IBAN Holder Name.
Our Action: If executed despite a “No Match,” liability rests with the Originator PSP.
Liability Allocation: We bear no liability if the Originator or Originator PSP executes despite a “No Match” alert.
Result: Verification Not Available
Description: Originator PSP does not support VoP or fails to perform it.
Our Action: We credit according to IBAN data received. Liability lies with the Originator PSP under PSD2 Article 88(1) and Regulation (EU) 2024/1623 Article 7(3).
Liability Allocation: We bear no liability if the Originator or Originator PSP do not verify the IBAN correspondence to Beneficiary name and still executed the payment.
Result: Service Not Available
Description: Temporary VoP system outage
Our Action: If the payment is executed, we bears no liability for incorrect beneficiary identification; responsibility remains with the Originator PSP.
Liability Allocation: We bear no liability if the Originator or Originator PSP executes despite a “Verification Not Available” alert.
Compliance and Screening
All incoming payments are subject to real-time AML/CFT and sanctions screening, as required under:
- the Prevention of Money Laundering and Funding of Terrorism Regulations (PMLFTR);
- Directive (EU) 2015/849 (AMLD IV) and subsequent amendments; and
- EU Restrictive Measures Regulations (EU 269/2014, EU 833/2014) and related instruments.
We may delay or block an incoming transfer pending screening or verification. Such delay or non-crediting does not constitute a breach under PSD2 Article 83(3).
Returns, Recalls, and Reversals
i. Return by us
We may return or reverse an incoming transfer SEPA SCT Credit transfer where:
- IBAN are incorrect;
- the payment contravenes AML/CFT, sanctions, or regulatory obligations; or
- instructed to do so by a competent authority, intermediary, or correspondent bank.
ii. Recall by Originator PSP
A recall of an already executed SEPA payment may be processed only in accordance with the EPC SEPA Credit Transfer Rulebook Section 4.3.3.
We execute the recall only if the Beneficiary (Wallet Holder) has provided explicit consent to return the funds.
If such consent is not obtained within the prescribed timeframe (currently 10 Business Days under EPC standards), We will refuse the recall and notify the Originator PSP accordingly.
Where funds have already been withdrawn, converted, or otherwise disposed of, we bear no liability for non-recovery.
iii. Notification of Return or Recall
We will notify the Wallet Holder of any return, reversal, or recall via Trusted and Secure Communication Channels, unless prohibited by law or regulatory order.
iv. Exchange Rate Adjustments
For returned or recalled non-EUR transfers, the conversion rate applicable on the day of reversal shall apply, in accordance with Article 2.11 – Exchange Rates and Currency Conversion, and the Wallet Holder shall bear any rate difference.
Liability Framework
i. Correctly Executed Transfers
Our obligation ends once the payment is credited to the Wallet corresponding to the IBAN provided in the payment order, in compliance with PSD2 Article 88(1).
We are not responsible for mismatches between IBAN and Beneficiary Name, nor for payments sent by an Originator PSP that did not use or disregarded VoP results.
ii. Originator PSP Responsibility
If the Originator PSP has not implemented, offered, or performed VoP verification prior to execution, or has executed despite a “Close Match” “No Match” or “Verification Not Available” result, it bears full liability for any misdirected payment, sharing it between them and Originator under Regulation (EU) 2024/1623 Article 7 and PSD2 Article 88(1).
iii. Our Errors
If we incorrectly credit funds to a Wallet not corresponding to the IBAN indicated in the received payment message, wel correct the error and restore the Wallet Holder’s balance without undue delay per PSD2 Article 89(1).
Termination of Responsibility
Our execution responsibility concludes when:
- the payment is credited to the Wallet corresponding to the specified IBAN;
- compliance, sanctions, and VoP checks (where applicable) are complete; and
- the transaction confirmation is made available through the Wallet interface or Trusted and Secure Communication Channels.
Subsequent disputes concerning incorrect payee data, non-performed VoP verification, or Originator PSP negligence shall be resolved between the Originator and the Originator PSP, without recourse to us.
Scope of Responsibility for Payments to Card Number
i. Nature of the Service
This provision governs payments initiated by the Wallet Holder to a payment card number issued under the VISA or Mastercard network (“Payment to Card Number”). The service enables the transfer of funds from the Wallet Holder’s selected Wallet to a Beneficiary Card using the relevant international card processing network.
ii. Initiation and Input Requirements
The Wallet Holder shall, through the Application (APP), select the source Wallet from which the transfer is to be made and provide the required Beneficiary Card credentials, including the card number and expiry date.
Where the Beneficiary Card does not belong to the Wallet Holder, the Wallet Holder must additionally provide the Beneficiary’s full name and address, in accordance with anti-money laundering and counter-terrorism financing (AML/CFT) requirements and card scheme rules.
iii. Processing and Settlement
Upon submission and authorisation of the Payment to Card Number, the transaction is executed in Real-Time through the corresponding card processing network (VISA or Mastercard). The authorised amount is transmitted and made available in the Beneficiary Card’s currency as a network authorisation, temporarily increasing the Beneficiary Card’s available balance.
Final settlement and posting of the transaction are completed by the Beneficiary Bank in accordance with the operational and settlement procedures prescribed by the respective card scheme.
iv. Currency and Conversion Responsibility
All Payments to Card Numbers initiated from Wallets are transmitted by us in Euro (EUR), unless otherwise indicated in the Application.
If the Beneficiary Card or the Beneficiary Bank operates in a currency other than EUR, the currency conversion is performed by the Beneficiary Bank or its acquirer. We bear no responsibility for the conversion process, exchange rate applied, or any resulting amount received by the Beneficiary.
In accordance with Article 45(1)(h) of PSD2 and Regulation (EU) 2019/518, the Beneficiary Bank is solely responsible for displaying or otherwise making available the applicable exchange rate and any associated conversion charges to the Beneficiary.
v. Liability and Scope of Responsibility
Our responsibility shall be strictly limited to the accurate and secure transmission of the authorised payment order to the VISA or Mastercard network.
Once the transaction has been transmitted and acknowledged by the network, our execution obligation is considered fully discharged.
All subsequent responsibilities—including settlement, posting, crediting, and any foreign exchange applied—rest solely with the Beneficiary Bank or its acquiring institution, in accordance with Articles 86 and 88 of Directive (EU) 2015/2366 (PSD2) and the Mastercard/VISA Transaction Processing Rules.
vi. Right of Refusal and Compliance Controls
We reserve the right to refuse, suspend, or delay execution of a Payment to Card Number where:
- the transaction or the Beneficiary is suspected of money laundering, terrorist financing, fraud, sanctions evasion, or other unlawful conduct;
- the Beneficiary Bank or its jurisdiction is subject to sanctions or regulatory restrictions; or
- the transaction otherwise breaches these Terms and Conditions, AML/CFT requirements, or card scheme rules.
vii. Notification and Assistance
Unless prohibited by law, we will notify the Wallet Holder of any refusal, delay, or suspension of the Payment to Card Number and provide reasonable assistance for clarification or dispute resolution. Such communication shall occur through Trusted and Secure Communication Channels, as defined herein, and in compliance with Article 88(2) of PSD2 and the Central Bank of Malta Directive No. 1.
Scope of Responsibility for Top-up Using Codes
i. Nature of the Service
This Article governs the process of crediting a Wallet by means of Top-up Codes, as defined in the Definitions section. Top-up Codes are unique, single-use credentials issued through authorised retail or partner networks of us, each representing a predefined transaction type and monetary value.
ii. Initiation and Authentication
The Wallet Holder initiates the top-up by entering the Top-up Code within the “Top-up by Codes” section of the Application (APP).
Upon successful entry, we perform Strong Customer Authentication (SCA) pursuant to Article 97 of Directive (EU) 2015/2366 (PSD2) to confirm the Wallet Holder’s authorisation to execute the transaction.
Entry of a valid Top-up Code constitutes:
- a legally binding payment instruction by the Wallet Holder (as Ordinator) to us; and
- the explicit authorisation for us to credit the same Wallet Holder (as Beneficiary) with the amount predefined for that Top-up Code.
iii. Execution and Crediting
Once validated, we execute the crediting transaction in Real-Time, making the corresponding amount immediately available in the Wallet.
The transaction is recorded in the Wallet Holder’s transaction history and reflected in the next Statement (see Article 2.12 – Statements).
Each Top-up Code is single-use and cannot be altered, cancelled, or reused once redeemed.
iv. Currency and Conversion
All Top-up Codes are denominated in Euro (EUR), unless expressly specified otherwise at issuance.
If the Wallet is denominated in a currency other than EUR, the corresponding amount will be converted using our prevailing exchange rate at the time of processing, in accordance with Article 2.11 – Exchange Rates and Currency Conversion.
AML/CFT and Record Preservation
In compliance with the Prevention of Money Laundering and Funding of Terrorism Regulations (S.L. 373.01), Directive (EU) 2024/1640 (AMLD VI), Directive (EU) 2018/843 (AMLD V), and Chapter 373 (Prevention of Money Laundering Act in Malta), CBM Directive No. 1, we shall:
- conduct ongoing monitoring and screening of Top-up transactions;
- identify and verify the Ordinator and Beneficiary of each Top-up transaction, even when both roles are performed by the same Wallet Holder; and
- preserve all relevant transaction data, including the Top-up Code identifier, time of execution, value, and Wallet Holder identification, for the minimum statutory retention period prescribed by Maltese law.
We may suspend or reject a top-up if we suspect misuse, fraud, money laundering, or terrorist financing, or if the transaction violates regulatory or internal risk controls.
Limitations of Liability
Our responsibility is strictly limited to validating and executing the top-up transaction upon receipt of a valid Top-up Code.
We shall not be liable for:
- the loss, theft, or unauthorised disclosure of Top-up Codes once distributed through retail or partner networks;
- delays, failures, or errors attributable to third-party distributors; or
- transactions resulting from Top-up Codes obtained or used fraudulently.
In such cases, we will provide reasonable assistance to competent authorities in accordance with Articles 73–75 of PSD2 and CBM Directive No. 1.
Refunds and Expiry
Top-up Codes are non-refundable once redeemed unless non-execution results from a verified technical fault attributable to us.
Unredeemed Top-up Codes expire either upon the lapse of their stated validity period or twelve (12) months from issuance, whichever is earlier.
Compliance with Tariffs and Limits
All Top-up by Codes transactions are subject to the Tariff of Charges and the applicable operational and regulatory limits set out in Article 3.2 – Transaction Limits, including anti-fraud and AML thresholds.