List of terms commonly found when using Curlec services.
Terms | Descriptions |
Application Programming Interface (API) | A form of communication between applications that allow merchants to integrate with Curlec services. |
Authorisation | A process whereby customers complete a mandate or Instant Pay form to permit merchants to collect recurring or one-off payments, respectively. A RM1 FPX fee is charged when authorising a mandate. |
Auto Collection | A function that automatically generates and uploads payment collection (CFT) files to the bank according to the recurring collection settings configured on the mandate. |
Auto Retry | A function performed by our system to re-attempt an unsuccessful collection on behalf of the customer's bank by automatically generating a new collection file. The number of retry iterations is capped at 99 but it is recommended to be kept below 20. |
Bank Retry | An action performed by the customer's bank to re-attempt an unsuccessful collection by automatically generating a new collection file on the next working day. The number of retry iterations is capped at 4 for most banks, but not all banks offer this function. |
Batch upload | A function that allows merchants to create multiple mandates or payment collections by uploading an Excel template to the portal. |
Card payments | A payment method that allows merchants to collect recurring or one-off payments from their customers via credit/debit cards. |
Collection File (CFT) | A file uploaded to the merchant bank’s folder as an instruction for payment collection. A collection file can contain one or more collection items. |
Date Period | The period, starting from the effective date, at which a mandate cannot be terminated. It is a rule that applies to a specific mandate or all mandates, as determined by the settings. |
Direct Debit | A payment method that allows merchants to collect recurring payments from their customers’ bank accounts directly, without going through card processing networks such as MasterCard or Visa. |
Down payment | A function that allows merchants to collect initial payments from customers when setting up a mandate. |
Effective date | The date when a mandate becomes active. This can be set when completing the mandate form. |
Enrolment report (ENRP) | A report that contains customer’s bank details, sent to us by the merchant’s bank at most 2 days after a mandate is approved. |
Expiry date | The date when a mandate will be terminated. Collections cannot be made from this date onwards. A mandate can be set to have no expiry date. |
Financial Process Exchange (FPX) | An online payment gateway that allows real time payments using a current account/savings account (CASA) or FPX Credit Card account. |
Instant Pay | A payment method that allows merchants to instantly collect one-off payments from customers via FPX or card payment gateways. |
Mandate | An authorisation form given by customers for allowing merchants to directly collect payments from their customers’ bank accounts or direct/credit cards. |
| PayNet | The national payments network and shared central infrastructure for Malaysia’s financial markets. |
Portal | An online dashboard that allows merchants to access Curlec services such as creating a mandate, generating payment collections, monitoring day-to-day transactions and more. |
| Response date | The date when we receive the ENRP file from the bank. The response date will be 1-2 days after the transaction date. |
Response (RES) report | A file returned by the merchant’s bank that updates the status of collection, it is typically received 1-2 working day(s) after the collection file is uploaded to the bank. |
Scheduled Collection | A function that automatically schedules collections according to the recurring collection settings configured on the mandate, while also providing a preview of upcoming collections. |
Subscriptions | A function that allows merchants to pre-set recurring payment plans for customers to subscribe to in their mandate form. |
Transaction date | The date when a customer has made the RM1 payment to authorise a mandate. |
Tokenisation | A process that replaces sensitive debit/credit card data with a unique identification code during the recurring card payment transactions for greater security purposes. |
Two-factor authentication (2-FA) | An additional layer of security to the login process, making it harder for attackers to gain access to our merchants’ accounts. |