Overview

The subMethod class is used in different request methods to access the following advanced 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 the customer details needed to register a new customer in your system, based on the customer details collected by the APM provider.

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

APM Recurring Billing

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

APM Providers Offering a “Recurring Billing” Service

APM	Parameter
PayPal – Billing Agreement	subMethod: "ReferenceTransaction"
Post Finance – Alias Registration	subMethod: "AliasRegistration"
Skrill – Skrill1Tap	subMethod: "Skrill1Tap"

For Checkout SDK

Send the initial payment as a checkout() request, and include the savePM: true parameter to display a “Save my details for future use” checkbox for each payment method in the Payment Methods list. (Note: Do not include a subMethod parameter in the checkout() request.)

When a customer chooses a payment method from the Payment Methods list and selects the “Save my details for future use” checkbox, then the payment method details are stored.
If the payment method is an APM that supports the direct server-to-server payment option for subsequent recurring/re-bill payments, then the transaction is marked as the “initial transaction” in a “Recurring Billing” arrangement for that customer and payment method.

For an example, see the Perform a Checkout Payment topic.

For Web SDK and REST API

• For Web SDK:
  Send the initial payment as a regular redirect-based createPayment() request and include the relevant paymentOption.subMethod.subMethod parameter, listed in the APM Providers for Recurring Billing table above.
• This performs the initial payment and also registers the recurring billing agreement with the APM.
  For an example see the APM Recurring Billing topic.
  
  Subsequent recurring billing payment requests are only performed using REST API (see below).

• For REST API:
  For both the initial and subsequent /payment requests, include the relevant paymentOption.subMethod.subMethod parameter, listed in the APM Providers for Recurring Billing table above.
  For an example, see the Initiate APM Payment topic.

Customer Registration via APM

The following APM providers offer a service to supply you with the customer details needed to register a new customer in your system, based on the customer details collected by the APM provider:

APM Providers Offering a “Customer Registration via APM” Service

APM	Parameter
PayPal	subMethod: "QuickRegistration"
Trustly	subMethod: "PayNPlay"

For Checkout SDK

Send a checkout() payment request and include this parameter:

subMethod:["PayNPlay","QuickRegistration"] //customer registration APM providers

For an example, see the Perform a Checkout Payment topic.

For Web SDK and REST API

• For Web SDK:
  Send a createPayment() request as a regular redirect-based request and include the relevant paymentOption.subMethod.subMethod parameter, listed in the APM Providers for Customer Registration table above.
  This performs the payment with the APM and also returns all the customer details needed for you to register the new customer in your system.
  For an example, see the Customer Registration via APM topic.
• For REST API:
  Send a /payment request and include the relevant paymentOption.subMethod.subMethod parameter, listed in the APM Providers for Customer Registration table above.
  For an example, see the Initiate APM Payment topic.