1. To record the subscribers' payment details, you should redirect them to Paypage, sending the transaction data in the request (amount, currency, etc.), as well as the subscriber ID (merchantWalletId field).
2. Mercanet displays the payment page, the subscriber provides their payment details, then confirms.
3. Mercanet makes a 3-D Secure verification.
4. Mercanet makes anti-fraud checks.
5. Mercanet sends an authorisation request to the Acquirer.
6. Mercanet records the transaction in the back office.
7. If the transaction is approved Mercanet records the subscriber payment details in the wallet.
8. Mercanet displays the payment receipt page with a confirmation message that the subscriber payment method has been registered.
9. Mercanet returns the manual and automatic responses containing the transaction details, including the result of the subscriber registration in the wallet.
10. Mercanet may or may not send the transaction for collection, depending on the parameters that you have configured in the payment request.

Make a classic payment Paypage request as described in the connector guide.

However, the following field should be valued as follows:

For subscriptions with cards only (DSP2 obligation, see chaining documentation for more information), the following fields have a special behaviour and have to be filled in like this:

Mercanet returns a typical Paypage manual and automatic response.

The fields related to subscriber enrollment are as follows:

You manage the data entry for payment methods on your website.

1. Step 1: You send a request to Mercanet to verify the payment method before enrolling the customer.
   • The 3-D secure authentication to verify that the customer is the cardholder of CB, Visa, Mastercard, Amex, Bancontact cards.
   • Anti-fraud checks that you have configured according to your business rules (e.g. foreign cards, commercial cards, etc.).
   • Authorisation request to the acquirer to verify that the card is still valid (not stolen, lost etc.).
     1. Mercanet records the transaction.
     2. Mercanet may or may not send the transaction for remittance to the acquirer, depending on the elements provided in the request.
   • Mercanet sends you the results of the payment methods verification.

2. Step 2: Once the payment method has been verified, you send a second request to Mercanet to register the payment method in the wallet.

3. Mercanet returns the payment method registration response.

The sequence described above applies to the Amex, and Bancontact means of payment.

Use the methods below, depending on the verification level of the payment method to be enrolled.

CB, Visa, Mastercard, Bancontact, Oney, AMEX cards

Please refer to one of the Office (M2M) guides corresponding to the selected connector (JSON or SOAP), as well as the Payment methods guides, to learn how to populate the request, depending on your business requirements.

When receiving the answer, before analysing it and following the advice in the table below, check the seal. The recalculated seal must be identical to the seal received.

CardOrder, cardValidateAuthenticationAndOrder and directDebitOrder methods

Use the methods below, depending on the payment method to be enrolled. The merchantWalletId field contains the customer ID.

Carte CB, Visa, Mastercard, Bancontact, Oney, Amex

Please refer to the adequate Office (M2M) guide, as well as the Payment methods guides, to learn how to populate the request, depending on your business requirements.

You format a Office Batch file using the WalletOrder method.

Each WalletOrder registration contains:

1. You send the file to Sips via FTPS or SFTP.
2. Mercanet retrieves the subscriber payment details stored in the wallet.
3. Mercanet executes the anti-fraud checks that you configured for your store.
4. Mercanet sends the authorisation requests to acquirers.
5. Mercanet stores the transaction in the back office.
6. Mercanet formats the response file and sends it to you.
7. In the evening, Mercanet sends the payment collection of accepted transactions.

Please consult the Office Batch XML or Office Batch CSV guides to find out more about implementation (file structure, description of records, file transfer, error management etc.).

To generate a recurring subscription payment using the walletOrder method, you should complete the following fields:

Please refer to Office Batch XML or Office Batch CSV Guides to learn how to complete the other fields for the request, depending on your business requirements.

For payments with cards, the fields below have a particular behaviour and should be valued like this:

The Office Batch solution allows batch payments to be made.

You format a Office Batch file using the walletCredit method.

Each walletCredit record contains:

• The ID of the subscriber to be debited (merchantWalletOrderId field)
• The transaction data (amount, order reference etc.).

1. You send the file to Mercanet via FTPS or SFTP.
2. Mercanet retrieves the subscriber payment details stored in the wallet.
3. Mercanet sends the authorisation requests to acquirers.
4. Mercanet stores the transaction in the back office.
5. Mercanet formats the response file and sends it to you.
6. In the evening, Mercanet sends the payment collection of accepted transactions.

Please consult the Office Batch XML or Office Batch CSV guides to find out more about implementation (file structure, description of records, file transfer, error management etc.).

To generate a recurring subscription payment using the walletCredit method, you should complete the following fields:

Please refer to Office Batch XML Office Batch CSV guides to learn how to complete the other fields for the request, depending on your professional requirements.

The Walletpage interface allows the subscriber to autonomously manage his wallet. The following features are available:

• consulting the contents of a subscriber account
• editing the payment mean of a subscriber account (alias only)
• removing a subscriber account

All management features are available to the user by default. However, it is possible to reduce the scope of these features, by indicating the list of features required in the walletActionNameList field.

For the wallet management you should populate the fields below:

Please refer to the Walletpage guide corresponding to the selected connector (JSON, POST or SOAP) to learn how to populate the request, depending on your business requirements.

The "Wallet" service of the Office (M2M) interface allows the merchant to manage the wallet contents of his customers. The following features are available:

• Obtaining the complete content of a subscriber account.
• Obtaining details of a payment mean contained in a subscriber account.
• Creating a new subscriber account.
• Deleting a subscriber account.
• Deleting a payment method from a subscriber account.

Using the Office (M2M) or Office Batch interfaces, you need to manage the wallet management pages to allow your subscribers to manage their accounts.

Office (M2M) allows you to view customer details through a getWalletData request.

• Setting the request
  To view the content of a wallet with the getWalletData method, you should populate the fields below:

  Field	Value
  merchantWalletID	Customer identifier

  Please refer to the Office (M2M) guide corresponding to the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

• Analysing the response

  Status	Response fields	Action to take
  Customer found in the wallet database	walletReponseCode = 00 walletPaymentMeanDataList filled with the payment methods recorded in the wallet	The customer exists in the wallet. Analyse the walletPaymentMeanDataList field to access the customer payment method details paymentMeanBrand paymentMeanId maskedPAN PANExpiryDate
  Customer not found in the wallet database	walletReponseCode = 25	The account has been deleted or was not created.
  Other refusals	walletReponseCode = xx	Please refer to the Office (M2M) guide corresponding to the selected connector (JSON or SOAP) to analyse the Mercanet response.

Office (M2M) allows you to modify the alias of a customer payment method via the updatePaymentMean request.

• Setting the request
  To modify a payment method via the updatePaymentMean request, you should populate the fields below:

  Field	Value setting
  merchantWalletID	Customer identifier
  paymentMeanId	Sequence number of the payment method
  paymentMeanAlias	New payment method alias

Please refer to the Office (M2M) guide corresponding to the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

• Analysing the response

Office (M2M) allows you to delete a customer via the signOff request.

• Setting the request

To delete a wallet with the signOff method, you should populate the fields below:

Please refer to the Office (M2M) guide corresponding the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

• Analysing the response