XML Unscheduled recurring master

Request

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754652001" timeStamp="2025-06-24T11:44:12.001+03:00"><SaleRequest><Authentication><Mid>0101118297</Mid></Authentication><OrderInfo><OrderId>1750754595780</OrderId><OrderDesc></OrderDesc><OrderAmount>6.0</OrderAmount><Currency>EUR</Currency><Var6>rcauto=false</Var6></OrderInfo><PaymentInfo><PayMethod>visa</PayMethod><CardPan>4016360000000010</CardPan><CardExpDate>2512</CardExpDate><CardCvv2>756</CardCvv2><CardHolderName>Test</CardHolderName><RecurringIndicator>R</RecurringIndicator><RecurringParameters><ExtRecurringfrequency>7</ExtRecurringfrequency><ExtRecurringenddate>20300623</ExtRecurringenddate></RecurringParameters><ThreeDSecure><EnrollmentStatus>Y</EnrollmentStatus><AuthenticationStatus>Y</AuthenticationStatus><CAVV>AJkBAUhZRwAAAAJsl4NFdUBiUAk=</CAVV><XID>VlBPUzM0MDMxNzEtY2I0OTAyMDA=</XID><ECI>05</ECI><Protocol>3DS2.2.0</Protocol><Attribute name="TDS2.dsTransID">7205089f-7de2-50ab-8000-00000a4ef19d</Attribute></ThreeDSecure></PaymentInfo></SaleRequest></Message><Digest>J8EzVPX4nTUMlvFuYwlX1WDCizbO7sfKAYeW1gQlKpY=</Digest></VPOS>

Canonicalized

<Message xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" messageId="M1750754652001" timeStamp="2025-06-24T11:44:12.001+03:00" version="2.1"><SaleRequest><Authentication><Mid>0101118297</Mid></Authentication><OrderInfo><OrderId>1750754595780</OrderId><OrderDesc></OrderDesc><OrderAmount>6.0</OrderAmount><Currency>EUR</Currency><Var6>rcauto=false</Var6></OrderInfo><PaymentInfo><PayMethod>visa</PayMethod><CardPan>4016360000000010</CardPan><CardExpDate>2512</CardExpDate><CardCvv2>756</CardCvv2><CardHolderName>Test</CardHolderName><RecurringIndicator>R</RecurringIndicator><RecurringParameters><ExtRecurringfrequency>7</ExtRecurringfrequency><ExtRecurringenddate>20300623</ExtRecurringenddate></RecurringParameters><ThreeDSecure><EnrollmentStatus>Y</EnrollmentStatus><AuthenticationStatus>Y</AuthenticationStatus><CAVV>AJkBAUhZRwAAAAJsl4NFdUBiUAk=</CAVV><XID>VlBPUzM0MDMxNzEtY2I0OTAyMDA=</XID><ECI>05</ECI><Protocol>3DS2.2.0</Protocol><Attribute name="TDS2.dsTransID">7205089f-7de2-50ab-8000-00000a4ef19d</Attribute></ThreeDSecure></PaymentInfo></SaleRequest></Message>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754652001" timeStamp="2025-06-24T11:44:12.592+03:00"><SaleResponse><OrderId>1750754595780</OrderId><OrderAmount>6.0</OrderAmount><Currency>EUR</Currency><PaymentTotal>6.0</PaymentTotal><Status>CAPTURED</Status><TxId>92639558728581</TxId><PaymentRef>144196</PaymentRef><RiskScore>0</RiskScore><Description>OK, CAPTURED response code 00</Description><Attribute name="EXTACQUIRERID">026</Attribute></SaleResponse></Message><Digest>bPVcSUDzgBmVOEs6AFNRY2Nvnf5LkcUul02Y7RvOv8s=</Digest></VPOS>

XML Unscheduled Recurring child – Same amount as master

Request

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754253118" timeStamp="2025-06-24T11:37:33.118+03:00"><RecurringOperationRequest><Authentication><Mid>0101118297</Mid></Authentication><TransactionInfo><OrderId>O250624113138</OrderId></TransactionInfo><Operation>RecurringChild</Operation></RecurringOperationRequest></Message><Digest>PdcPZ1GsM2VQdpd/qjJ0QD86HPr4xNPn5fNfU8hOXe4=</Digest></VPOS>

Canonicalized

<Message xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" messageId="M1750754253118" timeStamp="2025-06-24T11:37:33.118+03:00" version="2.1"><RecurringOperationRequest><Authentication><Mid>0101118297</Mid></Authentication><TransactionInfo><OrderId>O250624113138</OrderId></TransactionInfo><Operation>RecurringChild</Operation></RecurringOperationRequest></Message>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754253118" timeStamp="2025-06-24T11:37:35.844+03:00"><RecurringOperationResponse><OrderId>O250624113138/2</OrderId><OrderAmount>47.0</OrderAmount><Currency>EUR</Currency><PaymentTotal>47.0</PaymentTotal><Status>CAPTURED</Status><TxId>92639558728481</TxId><Sequence>2</Sequence><PaymentRef>144187</PaymentRef><RiskScore>0</RiskScore><Description>OK, CAPTURED response code 00</Description><Attribute name="EXTACQUIRERID">026</Attribute></RecurringOperationResponse></Message><Digest>HZMCSV/1oqFzv+GURieViqQX/PTIqKe6MpXmb0OyO1I=</Digest></VPOS>

XML Unscheduled Recurring child – Different amount than master

Request

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754465043" timeStamp="2025-06-24T11:41:05.043+03:00"><RecurringOperationRequest><Authentication><Mid>0101118297</Mid></Authentication><TransactionInfo><OrderId>O250624113138</OrderId></TransactionInfo><Operation>RecurringChild</Operation><OrderInfo><OrderId>O250624113138</OrderId><OrderDesc></OrderDesc><OrderAmount>19.0</OrderAmount><Currency>EUR</Currency></OrderInfo></RecurringOperationRequest></Message><Digest>Gv/jUoHrNFfbOLgHFrokgtgKDp6wSoNfoOG9Moyjax0=</Digest></VPOS>

Canonicalized

<Message xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" messageId="M1750754465043" timeStamp="2025-06-24T11:41:05.043+03:00" version="2.1"><RecurringOperationRequest><Authentication><Mid>0101118297</Mid></Authentication><TransactionInfo><OrderId>O250624113138</OrderId></TransactionInfo><Operation>RecurringChild</Operation><OrderInfo><OrderId>O250624113138</OrderId><OrderDesc></OrderDesc><OrderAmount>19.0</OrderAmount><Currency>EUR</Currency></OrderInfo></RecurringOperationRequest></Message>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754465043" timeStamp="2025-06-24T11:41:05.962+03:00"><RecurringOperationResponse><OrderId>O250624113138/3</OrderId><OrderAmount>19.0</OrderAmount><Currency>EUR</Currency><PaymentTotal>19.0</PaymentTotal><Status>CAPTURED</Status><TxId>92639558728531</TxId><Sequence>3</Sequence><PaymentRef>144191</PaymentRef><RiskScore>0</RiskScore><Description>OK, CAPTURED response code 00</Description><Attribute name="EXTACQUIRERID">026</Attribute></RecurringOperationResponse></Message><Digest>scYvskhcyMPTZwLeWY3l0sP0w+hnznypacPsj1BFe+A=</Digest></VPOS>

XML Payment Link Unscheduled recurring master

Request

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754849682" timeStamp="2025-06-24T11:47:29.682+03:00"><PaymentLinkRequest><Authentication><Mid>0101118297</Mid></Authentication><OrderInfo><OrderId>1750754653599</OrderId><OrderDesc></OrderDesc><OrderAmount>11.0</OrderAmount><Currency>EUR</Currency><PayerEmail>simos.siatis@worldline.com</PayerEmail><Var6>rcauto=false</Var6></OrderInfo><PaymentInfo><RecurringIndicator>R</RecurringIndicator><RecurringParameters><ExtRecurringfrequency>7</ExtRecurringfrequency><ExtRecurringenddate>20300623</ExtRecurringenddate></RecurringParameters></PaymentInfo><TxType>PAYMENT</TxType><LinkValidityDays>5</LinkValidityDays><MailLinkIfValidMail>true</MailLinkIfValidMail></PaymentLinkRequest></Message><Digest>gc39EQIvSf3Z+H+Sw/UECwv5Yf52OUD586RcsYqH8EE=</Digest></VPOS>

Canonicalized

<Message xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" messageId="M1750754849682" timeStamp="2025-06-24T11:47:29.682+03:00" version="2.1"><PaymentLinkRequest><Authentication><Mid>0101118297</Mid></Authentication><OrderInfo><OrderId>1750754653599</OrderId><OrderDesc></OrderDesc><OrderAmount>11.0</OrderAmount><Currency>EUR</Currency><PayerEmail>simos.siatis@worldline.com</PayerEmail><Var6>rcauto=false</Var6></OrderInfo><PaymentInfo><RecurringIndicator>R</RecurringIndicator><RecurringParameters><ExtRecurringfrequency>7</ExtRecurringfrequency><ExtRecurringenddate>20300623</ExtRecurringenddate></RecurringParameters></PaymentInfo><TxType>PAYMENT</TxType><LinkValidityDays>5</LinkValidityDays><MailLinkIfValidMail>true</MailLinkIfValidMail></PaymentLinkRequest></Message>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><VPOS xmlns="http://www.modirum.com/schemas/vposxmlapi41" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"><Message version="2.1" messageId="M1750754849682" timeStamp="2025-06-24T11:47:29.938+03:00"><PaymentLinkResponse><OrderId>1750754653599</OrderId><OrderAmount>11.0</OrderAmount><Currency>EUR</Currency><PaymentTotal>11.0</PaymentTotal><Status>EXECWAIT</Status><TxId>92639558728641</TxId><Description>OK, link created mailed</Description><PaymentLink>https://ecommerce-test.cardlink.gr/vpos/Paylink/46ae3ffc1279e8b8dc029ffd5d1fd40d</PaymentLink><LinkMailed>true</LinkMailed></PaymentLinkResponse></Message><Digest>Csw70m83QL8E5GVfNGWXcc822el/qQ6RUNPn6cTBXG0=</Digest></VPOS>

Mass Payments

This manual describes the execution of unscheduled recurring child transactions through mass file in Cardlink Payment Gateway.

Mass file creation

The mass file should have the below format.

Name of the mass file: We recommend the name of the file to have the following format: MerchantID+YYYYMMDD+3digitsserialNumber.txt
For example: 6111111120170525001.txt
The name could also be alphanumeric.

Mass file structure:

The mass file should have specific layout to be executed successfully. The layout should be as follows:

File Header
Detailed Record
Detailed Record
Detailed Record
File Trailer

Note: File Header and File Trailer should be unique for each file. Detailed Record lines can be as many as the merchant wishes, based on the amount of the transactions that need to be executed. In order for the file to be uploaded successfully, its size should not exceed 16MB.

The below table shows all the required and the optional elements a mass file should have.

Name of the field	Required (R) Optional (O)	Type	Description
FileHeader
COS_HEAD_ID	R	CHAR (01)	HEADER ID (ALWAYS EQUALS TO “0”)
COS_SEIRNO	R	CHAR (07)	08YYNNN   SERIAL NUMBER OF THE FILE
COS_HEADFIL1	R	CHAR (02)	EQUAL TO “08”
COS_CRDATE	R	NUMERIC (9(06))	CREATION DATE OF THE FILE (YYMMDD)
COS_CODECOSMO	R	CHAR (02)	EQUAL  TO “08”
COS_ONOMETAIR	R	CHAR (20)	MERCHANT NAME (SPACES UP TO 20 CHARS IF NAME IS SHORTER)
COS_CODENUMBER	R	CHAR (02)	ALWAYS EQUALS TO “36”
COS_ONOMBANK	R	CHAR (20)	WORLDLINE (SPACES UP TO 20 CHARS)
COS_HEADFIL2	R	CHAR (08)	ALWAYS EQUALS TO “00000000”
COS_MCODE	R	CHAR(30)	MERCHANT ID variable length number right space padded to 30 chars, e.g. « 9999999                      «
COS_HEADFIL3	R	CHAR (02)	EQUAL TO “08”
COS_HMSYN	R	NUMERIC (9(06))	TRANSACTION DATE (YYMMDD)
COS_CURRCODE	R	CHAR (03)	TRANSACTION CURRENCY CODE (EUR)
COS_HEADFIL4	R	CHAR (14)	FILLER (14 SPACES)
DetailRecord
COS_DETAIL_ID	R	CHAR (01)	DETAIL RECORD ID (ALWAYS EQUALS TO “3”
COS_KATMA	R	NUMERIC (9(03))	ISSUER BANK BRANCH CODE (000)
COS_ARKART	R	CHAR (19)	19 SPACES
COS_SUBSCR	R	CHAR (19)	19 SPACES
COS_EXPDAT	R	NUMERIC (9(04))	4 SPACES
COS_DETFIL1	R	CHAR (01)	FILLER 1 (1 SPACE)
COS_ARLOGAR	R	CHAR (16)	16 SPACES
COS_DETFIL2	R	CHAR (18)	FILLER 2 (18 SPACES)
COS_POSO	R	NUMERIC (9(07)V99)	TRANSACTION AMOUNT  (in cents) The format is 7digits (amount in Euros) + 2digits (Cents), e.g.   10.56Euros COS_POSO=000001056
COS_DETFIL3	R	CHAR (02)	EQUAL TO “08”
COS_HMEGKR	R	NUMERIC (9(07))	AUTHORIZATION DATE  (YYYMMDD) equal to COS_HMSYN It is the date that the merchants would like the  transactions to be authorized and settled. The format is YYYMMDD, e.g. for 2013 05 15 COS_HMEGKR=1130515 (Year 2013 is 113)
COS_KATOXSYMF	R	NUMERIC (9)	9 random digits
COS_CODEAPOR	R	CHAR (01)	TRANSACTION COMPLETION CODE Always Space in input file
trType	R	CHAR (01)	Recurring child =’r’ For recurring child COS_ARKART  and COS_EXPDAT shall be space and orderid must be orderid of valid and successful initial recurring.
Separator	R	CHAR(01)	#NAME?
orderid	R	CHAR (50)	Similar to VPOS (redirection, XML) please refer to https://developer.cardlink.gr/api-product/redirect/ or https://developer.cardlink.gr/api-product/direct/ Order id must be unique per record of each mass file.
Separator	R	CHAR(01)	#NAME?
orderDesc	O	Char(128)	Similar to VPOS (redirection, XML) please refer to https://developer.cardlink.gr/api-product/redirect/ or https://developer.cardlink.gr/api-product/direct/
Separator	R	CHAR(01)	#NAME?
extInstallmentoffset	O	CHAR (03)	NOT USED WITH RECURRING CHILD
Separator	R	CHAR(01)	#NAME?
extInstallmentperiod	O	CHAR (03)	NOT USED WITH RECURRING CHILD
Separator	R	CHAR(01)	#NAME?
var1	O	CHAR(255)	Similar to VPOS (redirection, XML) please refer to https://developer.cardlink.gr/api-product/redirect/ or https://developer.cardlink.gr/api-product/direct/
Separator	R	CHAR(01)	#NAME?
Var2	O	CHAR(255)	Similar to VPOS (redirection, XML) please refer to https://developer.cardlink.gr/api-product/redirect/ or https://developer.cardlink.gr/api-product/direct/
Separator	R	CHAR(01)	#NAME?
Var3	O	CHAR(255)	Similar to VPOS (redirection, XML) please refer to https://developer.cardlink.gr/api-product/redirect/ or https://developer.cardlink.gr/api-product/direct/
Separator	R	CHAR(01)	#NAME?
TrailerRecord
COS_TRAILLER_ID	R	CHAR (01)	TRAILER RECORD ID (ALWAYS EQUALS TO “9”
COS_TOTTRANS	R	NUMERIC (9(05))	TOTAL NUMBER OF TRANSACTIONS = TOTAL NUMBER OF DETAIL RECORDS
COS_TOTAMNT	R	NUMERIC (9(10)V99)	TOTAL TRANSACTIONS AMOUNT (in cents) The format is 10digits (amount in Euros) + 2digits (Cents)
COS_TRAILFIL1	R	CHAR (79)	FILLER 3  (79 SPACES)
COS_ARXEIO	R	CHAR (03)	EQUAL TO “DPF”

Mass file upload and execution

How to upload a file in Cardlink Payment Gateway

In the landing page of Back Office tool we choose “Upload new mass payments file”.

 

We will then be transferred to a page asking to choose the file we want to upload.

 

Once we choose the file we press “Start upload”.

 

After the successful completion of the uploading, we will be transferred to the below page.

 

Mass file execution steps

File upload: During the upload, the layout of the file is checked and if there are no issues, the upload is completed successfully. Otherwise, it turns to “Upload error".

File import: During that step, the transactions data are being checked. If those data are invalid, then the file cannot be imported and turns to status “Import error”. Error details provide further details about the error.

 

File execution: Given that upload and import have been completed successfully, then the actual execution of each transaction takes place.

Executed file download: After the completion of the execution step, we are able to download the respective csv file containing all the executed transactions.

 

 

When each step occurs

A mass file can be uploaded whenever a user wishes to.

The import of the file takes place every hour at :10.
For example, a file that has been uploaded at 9:05, the import will occur at 9:10. If the upload takes place at 9:14, the import will be made at 10:10.

The execution of the file takes place every hour at :45.
For example, if file has been uploaded at 9:10, it will be executed at 9:45.

Introduction

The below guide describes Payment Links functionality.

General

Payment Links allow merchants to execute e-commerce transactions, without any technical integration with Cardlink’s payment gateway. For that purpose, merchant uses the Back Office tool where the Payment Links are created and/or sent.

Payment Links are ideal for accepting payments through:

• Sales through phone or e-mail
• Sales through other channels (social media, SMS, Viber etc.)

How Payment Links work in 4 steps:

1. Merchant agrees with the customer to proceed with a transactions for a specific amount, using a Paymene Link the customer will receive through the desired channel (e-mail, Viber, etc.)
2. Merchant creates the Payment Link through Back Office toole.
3. As a final step, merchant chooses whether to send the Payment Link through e-mail or copy it and send it in a different way.
4. Customer receives the Payment Link, opens it and is redirected to the respective payment page, in which he/she completes the transaction.

Getting started with the creation of the Payment Link

Log in to the back office tool using the credentials sent to you and choose “Make Mail/Telephone order (Mo/To)”.

 

Send the Payment Link to the customer

There are 2 options for that:

1. Send it directly to an e-mail address through back office tool
2. Create (Generate) Payment Link and copy it to send it with a different way, using your template

Send Payment Link directly to e-mail

To send the Payment Link directly to an e-mail follow the below steps:

1.When in “Make Mail/Telephone order (Mo/To)” menu, fill in all the below necessary fields:

1. Transaction type: Always “Recurring payment”
2. Order Id: Keep the prefilled value.
3. Order Amount
4. Recurring data: Fill in fields Frequency and End date. Checkbox “Disable auto recurring” has to be checked if the transaction is for a standing order (unscheduled recurring).
5. Payer email

And any other optional field you desire.

2.In “Paylink validity” field, you can set the days the link will remain active

3.Click on “Send payment link”.

4.In the pop up window press “Confirm”

5.The Payment Link has been sent to your customer

Note: Supported languages are English and Greek. You can choose the language through “Payment language” field.

Cardlink’s e-mail template

The e-mail that is sent to your customer looks like the below.

 

Merchant name, URL, amount and order id are dynamically filled in.

Create (Generate) Payment Link and manual dispatch

In order to manually send the Payment Link using a different channel and/or template, follow the below steps.

1.When in “Make Mail/Telephone order (Mo/To)” menu, fill in all the below necessary fields:

1. Transaction type: Always “Recurring payment”
2. Order Id: Keep the prefilled value.
3. Order Amount
4. Recurring data: Fill in fields Frequency and End date. Checkbox “Disable auto recurring” has to be checked if the transaction is for a standing order (unscheduled recurring).
5. Payer email

And any other optional field you desire.

 

2.In “Paylink validity” field, you can set the days the link will remain active

3.Click on “Generate payment link”

 

4.In the pop up window press “Confirm”

 

5.In the next pop up window press “Copy”

 

6.Paste the link to any other means you desire to send it to your customer

How to handle Payment Links

You are able to cancel or resend an already created Payment Link.

Cancel a Payment Link

In case you want to cancel a Payment Link so your customer will not be able to use it:

1. Find and select the respective transaction in back office tool
2. Click at “Paylink cancel”

 

3. The Payment Link has now been cancelled and cannot be used

Resend a Payment Link

If you have directly sent through e-mail a payment link to your customer, you can resend it:

1. Find and select the respective transaction in back office tool
2. Click at “Paylink resend”
3. The Payment Link has been resent to your customer

 

Payment Link transaction results

You can always be informed regarding the status of a Payment Link transaction with the below ways:

1. Through “VPOS transactions” section in back office tool
2. By receiving a notification e-mail after a successful Payment Link transaction
3. Directly to your system if you have a site and have set confirm/cancel URLs.

Find a transaction in Back Office tool

In order to find a Payment Link transaction, go to “VPOS Transactions” section and choose “Payment Link: option in field “Input Channel”.

 

You can easily check the Payment Link transaction’s status from the transactions menu, as per below.

 

Payment Link transaction’s status

A Payment Link transaction can (normally) get one of the following statuses.

STATUS	DESCRIPTION
EXECWAIT	Customer has not opened the Payment Link yet
PREPROCESS	Payment Link is open and payment page has appeared
PREPROCESS-TIMEDOUT	Transaction lifetime (30 minutes) has passed. Transaction has not been canceled
CANCELLED	Transaction is canceled by the customer
INWALLET	A digital wallet has been opened to complete the transaction
EXECWAIT-TIMEDOUT	The Payment Link has expired without having been opened

Receive response message directly to your system

If you have a website, then you can set respective URLs to receive online the response message when a payment link transaction is completed.
To achieve that, your system should be able to handle the response messages as described at https://developer.cardlink.gr/api-product/redirect/ (table “Return message POST to inform merchant shop about payment success or failure”).

 

Success / Fail pages

If you have not set your own return pages, then the default pages the customer will return to are as follows.

 

 

More features

Tokenization

 

If the merchant has set specific return URLs and the MID is respectively configured, then the customer’s card can be saved (Tokenization) and a token value can be returned to the success URL.

The next time the same customer will make a purchase through the e-shop, then that token could be used for faster check out.

Note that the token cannot be used in a future payment link transaction.

Merchant has the option to cancel a recurring scheme.

For both scheduled and unscheduled recurring schemes, there are 2 common ways to cancel.

1. By pressing “Cancel recurring" within the master recurring transaction through back office tool.
2. Through XML API. You may find the respective documentation at https://developer.cardlink.gr/api-product/direct/.

Important: Once a master recurring is cancelled, no other child transaction can be executed.

Especially for unscheduled recurring, given that child transactions are merchant initiated, a type of cancelation would be to stop sending child transactions to the payment gateway for a specific master transaction.

The second category of recurring transactions is the unscheduled recurring transactions or standing orders.

The initiation of a scheduled recurring scheme is made with the execution of a master recurring transaction that will necessarily go through 3D authentication process. For that purpose, the master transaction can be performed using any of the below methods.

• Redirection
• Payment Link
• Direct integration

At that initial transaction, merchant sets an indicative frequency of the subsequent (child) transactions and end date of their execution. The respective fields are mandatory for a recurring transaction and cannot be omitted.

Along with those parameters, it is necessary to also send value “rcauto=false" within a var parameter of the request, usually at var6. That value is crucial for the payment gateway not to automatically execute the subsequent (child) transactions.

Redirection: https://developer.cardlink.gr/api-product/redirect/
Payment Link: https://developer.cardlink.gr/uat/documentation_categories/recurring/#Recurring-through-Payment-Link
Direct integration: https://developer.cardlink.gr/api-product/direct/ and https://developer.cardlink.gr/api-product/modirum-mpi-merchant-interface-v4/ (requires log in)

Master transaction needs to be successful for the recurring scheme to be established.

Given that the payment gateway does not automatically execute the child transactions, each of them need to be initiated from the merchant.
There are 2 options to achieve that:

1. Through XML API. Check that option when activating unscheduled recurring transactions in the test app. You may find the respective documentation at https://developer.cardlink.gr/api-product/direct/
2. Through mass file. Check that option when activating unscheduled recurring transactions in the test app. That will send a notification to our customer support who will create a test user for the back office tool of the payment gateway, through which you will upload each file. You may find the respective documentation at https://developer.cardlink.gr/uat/documentation_categories/recurring/#Mass-files. You can also download a sample mass file here

If a subsequent transaction is rejected, then the merchant needs to initiate it again with one of the above ways.

Unscheduled recurring transactions that were initially executed more than 18 months ago (in production environment), are passed their end date and they have no child transaction for more than 18 months, are cleaned up from the database, are no longer visible or accessible and no new child transaction can be initiated.

The first category of recurring transactions is the scheduled recurring transactions or subscriptions.

The initiation of a scheduled recurring scheme is made with the execution of a master recurring transaction that will necessarily go through 3D authentication process. For that purpose, the master transaction can be performed using any of the below methods.

• Redirection
• Payment Link
• Direct integration

At that initial transaction, merchant sets the frequency of the subsequent (child) transactions and the end date of their execution.

The respective documentation of each method can be found at:

Redirection: https://developer.cardlink.gr/api-product/redirect/
Payment Link: https://developer.cardlink.gr/uat/documentation_categories/recurring/#Recurring-through-Payment-Link
Direct integration: https://developer.cardlink.gr/api-product/direct/ and https://developer.cardlink.gr/api-product/modirum-mpi-merchant-interface-v4/ (requires log in)

Master transaction needs to be successful for the recurring scheme to be established.

Each child transaction will be automatically executed through the payment gateway based on the originally set frequency and until the originally set end date.
The amount of each child transaction is the same as the on of the master transaction and cannot be altered.

In case a child transaction is rejected, the payment gateway proceeds with 2 more retries within the same day. The attempts are made at 07:00, 15:00 and 23:00. If all 3 attempts are rejected, then that specific sequence of the recurring scheme is abandoned and payment gateway will process the next one based on the frequency.

Merchant has two options to receive a response message of each child transaction:

1. To a URL that will be set in the field “Recurring notify url" of the test app.
2. Through webhooks. Up to 5 URLs can be set to receive the XML response message. Configuration can be made through “Enable Webhooks" section of the test app.
   
   Note: The above configuration is not automatically set to the respective production MID when activated.

Scheduled recurring transactions that were initially executed more than 18 months ago (in production environment) and are passed their end date, are cleaned up from the database and are no longer visible and accessible.

Payment gateway supports recurring transactions, allowing merchants of specific industries to perform future charges in their customer’s card, after having mutually agreed to do so.

Such cases could be a subscription to a service or a store or an agreement with a service provider for bill payments.

Recurring payments cannot co-exist with installments. Also, they are not compatible with digital wallets (Apple Pay/Google Pay), meaning that such wallets will not be available to complete a recurring transaction.

An established recurring scheme could either be executed at a specific frequency and with a specific amount (scheduled recurring – subsciptions) or at a frequency and/or with amount that will vary each time (unscheduled recurring – standing order).

In each case, the initial recurring transaction, must go through 3D authentication process.

The initial transaction cannot be refunded/voided in order for the subsequent transactions to be executed.

Token is not necessary for the execution of a subsequent (child) recurring transaction, so there is no need for tokenization (store card) during the initial (master) recurring transaction.