Overview

The subMethod class is used in different request methods to access the following special APM features:

• APM Recurring Billing – Specific APM providers offer a direct server-to-server payment option for subsequent recurring/re-bill payments, thereby eliminating the need for the customer to be involved.
• Customer Registration via APM – Specific APM providers offer a service to supply you with all the customer details needed to register a new customer in your system, based on the customer’s registration details entered by the customer, during registration with that APM provider.

You can invoke these APM features from the Nuvei platforms, as described below.

subMethod for Checkout SDK

The subMethod parameter is used to access these special APM features, in different ways, as described in the sections below:

APM Recurring Billing

Include the savePM: true parameter, needed in the initial request.
For an example see the Checkout() Payment section.

Customer Registration via APM

Include this parameter in both the initial and subsequent payment requests:
subMethod: ["PayNPlay","QuickRegistration"] // Array of the APM providers who support the Customer Registration feature.
For an example see the Checkout() Payment section.

subMethod for Web SDK and REST API

You can invoke these APM payments using these request methods:

• For Web SDK:
  Use a createPayment() request, and include the subMethod parameter.
  For an example see the Create a “Redirect” APM Payment section.
• For REST API:
  Use a /payment request, and include the subMethod parameter.
  For an example see the Initiate APM Payment section.

The subMethod parameter is used to access these special APM features, in different ways, as described in the sections below:

• APM Recurring Billing – for createPayment() and /Payment
• Customer Registration via APM – for createPayment() and /Payment

APM Recurring Billing

APM recurring billing payments are done in two stages:

1. Send the initial payment request as a regular redirect-based payment request, and include the "subMethod" parameter.
   This will perform the initial payment and also register the recurring billing agreement with the APM.
2. Subsequent recurring payment requests can then be sent using direct server-to-server payment requests, and must include the "subMethod" parameter.

The following APM providers support direct server-to-server recurring payment requests.

When sending recurring payment requests to these APM provides, include these parameters, for both the initial and subsequent payment requests:

• For PayPal – Billing Agreement: Set subMethod: "ReferenceTransaction"
• For Post Finance – Alias Registration: Set subMethod: "AliasRegistration"
• For Skrill – Skrill1Tap: Set subMethod: "skrill1Tap"

Customer Registration via APM

Specific APM providers offer a service to supply you with all the customer details needed to register a new customer in your system, based on the customer’s registration details, entered during registration with that APM provider.

When sending payment requests to these APM provides, include these parameters, for both the initial and subsequent payment requests:

• For PayPal: Set the subMethod to "QuickRegistration"
• For Trustly: Set the subMethod to "PayNPlay"