1. Trust Payments
  2. TRU Connect
  3. Webservices API

Recurring payments

Avatar
Michael Buckley

This page explains how to process recurring payments.

  The following content assumes you have obtained the necessary PCI certification to process and submit sensitive cardholder data in the request to our Webservices API.
Read this article to learn more.

  In order to process recurring payments, your merchant ID must be capable of processing recurring or continuous authority payments. If in doubt, we strongly recommend contacting your bank for clarification.

 

Process overview

  1. Customer enters their card details on your secure website.
  2. When the customer clicks "Pay", your system has been configured to process an initial request with either type THREEDQUERY then AUTH or THREEDQUERY then ACCOUNTCHECK. We refer to this as the parent request.
  3. Three days prior to processing a new payment, your system manually submits a scheme update request using our Webservices API, to check if the customer’s payment details are still up-to-date.
  4. When the next payment is due, your system manually processes a child request using our Webservices API, which inherits the previously-stored payment, billing and delivery details and seeks authorisation for a new payment.
  5. Your system can manually submit scheme update and child requests at various intervals to process new payments. The customer will only be debited after a new child request is submitted.

 

  Benefits

  • Payment details need only be entered by the customer once, at time of purchase.
  • Process repeat payments for customers without needing to store their card details on your own system for future use. Payment details are stored securely on our servers.
  • A recurring payment is only processed when a request has been submitted by your system. This allows for greater control over when payments are processed, as you are able to define your own interval between each payment.

  Alternative solution: Subscriptions

Our subscription solution allows you to submit a single request and we will process recurring payments automatically at regular intervals.

Click here to learn more.

 

1. Parent request

This section describes the initial request your system will need to process. You can inherit the payment details submitted in this request in subsequent recurring payments.

 

Process overview

The parent request submitted can either be type THREEDQUERY then AUTH or THREEDQUERY then ACCOUNTCHECK. You will need to read the two workflows below and choose the request type that best suits your business requirements:

Learn about THREEDQUERY then AUTH flow

3-D Secure authentication is performed.
Checks are performed on the card and billing address.
The first payment is processed immediately.

  1. Customer enters their card details and agrees to a subscription.
  2. A combined THREEDQUERY then AUTH request is processed. All payment, billing and delivery details submitted in the request are stored securely in our records for future use.
  3. 3-D Secure authentication is performed.
  4. We will then contact the acquiring bank to perform AVS and Security Code Checks, before seeking authorisation for the payment. Funds are reserved immediately on the customer’s bank account.
  5. Your system receives a response that includes the outcome of the request. The response returned contains a unique transaction reference.
  6. To process the second payment at the next interval agreed with the customer, your system manually submits another AUTH request using our Webservices API (that follows the specification described in “3. Child request” below).
Learn about THREEDQUERY then ACCOUNTCHECK flow

  Not supported using our hosted Payment Pages solution.

3-D Secure authentication is performed.
Checks are performed on the card and billing address.
Does not process the first payment immediately.

Account Checks are supported for merchants with a Trust Payments acquiring account. If you are using a different acquiring bank, you will need to contact our Support Team to check this workflow is supported before proceeding.

  1. Customer enters their card details and agrees to a subscription.
  2. A combined THREEDQUERY then ACCOUNTCHECK request is processed. All payment, billing and delivery details submitted in the request are stored securely in our records for future use.
  3. 3-D Secure authentication is performed.
  4. We will contact the acquiring bank to perform AVS and Security Code Checks. Funds are NOT reserved on the customer’s bank account.
  5. Your system receives a response that includes the results of the checks performed. The response returned contains a unique transaction reference.
  6. To process the first payment at the next interval agreed with the customer, your system manually submits an AUTH request using our Webservices API (that follows the specification described in “3. Child request” below).

 

Configuration of parent request

Expand the relevant section below to learn how to configure the parent request using your preferred interface.

Parent request using the Payment Pages

  Payment Pages is our fully-hosted checkout solution. If you are unfamiliar with our Payment Pages solution, click here to learn more and get started.

  The THREEDQUERY then ACCOUNTCHECK flow is not supported using our hosted Payment Pages solution.

The THREEDQUERY then AUTH flow is performed by processing a standard, 3-D Secure authenticated transaction using Payment Pages, with additional fields included in the POST, as described below.

<html>
  <head>
  </head>
  <body>
    <!--YOUR HTML-->
    <form method="POST" action="<DOMAIN>/process/payments/choice">
      <input type="hidden" name="credentialsonfile" value="1">
      <input type="hidden" name="currencyiso3a" value="USD">
      <input type="hidden" name="mainamount" value="100.00">
      <input type="hidden" name="sitereference" value="test_site12345">
      <input type="hidden" name="sitesecurity" value="hee879a9ab97753b3a768925d50842f10e19fea03fef0b820026b6df92d415866">
      <input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
      <input type="hidden" name="stprofile" value="default">
      <input type="hidden" name="subscriptionnumber" value="1">
      <input type="hidden" name="subscriptiontype" value="RECURRING">
      <input type="hidden" name="version" value="2">
      <input type="submit" value="Pay">
    </form>
  </body>
</html>

Replace <DOMAIN> with a supported domain. Click here for a full list.

 

Field specification

  Field Format Description
table-optional.png accounttypedescription Alpha (20)

The correct account type value for the parent request is dependent on your account configuration. We recommend contacting our Support Team for advice on which account type values to submit when processing recurring payments. These values are supported:

  • “ECOM” – e-commerce
  • “MOTO” – Mail or Telephone Order
    (Note that 3-D Secure authentication is not supported for MOTO transactions)
table-required.png mainamount Numeric (14)

The amount associated with this request in main units, with decimal places being separated by commas/decimal point. e.g. £10.99 would be submitted as “10.99” and ¥246 would be submitted as “246”.

This amount will be immediately reserved on the customer’s bank account.

This value will be inherited in all child requests that inherit from this parent request, unless the field is manually overridden.
table-required.png credentialsonfile Numeric (1) Visa and Mastercard have mandated that you must obtain cardholder consent before storing card details for future use. Following this, you must appropriately identify credentials that are to be stored for later, by assigning a Credentials on File (CoF) flag to signify this. For this reason, you must always submit credentialsonfile with value “1” in the parent request.

If you are processing a new recurring payments sequence using previously-stored credentials, you must still submit credentialsonfile = 1 in the parent request, to indicate the credentials will be stored to process future child payments in this sequence.
table-required.png currencyiso3a Alpha (3) The transaction currency. This must remain the same in all future child requests processed that inherit from this parent request.
table-required.png sitereference Alphanumeric
& underscore (50)		 The site reference relates to your individual account which you received on setup. If you do not know your site reference, please contact our Support Team.
table-required.png sitesecurity

Site security hash

 Used to submit the request site security hash in the POST.
table-required.png sitesecuritytimestamp

Date YYYY-MM-DD hh:mm:ss 

 As accurately as possible, the timestamp that reflects when the customer’s payment session was initiated. The customer will have 3 hours from the specified time to complete the payment.

Additional considerations:

  • The timestamp value must be in UTC.
  • The timestamp value must NOT be in the future.
table-required.png stprofile

Alphanumeric (20)

  • Lowercase letters only.
  • Punctuation and spaces not permitted.
 Used to specify the styling used to render the Payment Pages. When using the default appearance, this is set to “default”.
Click here for further information.
table-required.png subscriptionnumber Numeric (5) Submit “1” to denote the first request in the recurring sequence.

In each subsequent child request, the number submitted must be incremented by 1. For example the second request is “2”, the third is “3”, etc.
table-conditional.png subscriptionfinalnumber Numeric (5)

This is used to set the number of payments to be processed over the course of the subscription.

Note: This field is required for certain acquiring banks on the US platform when the subscriptiontype is “INSTALLMENT” (otherwise the field is optional). Contact our Support Team for further information.
table-required.png subscriptiontype Alpha (11)

This is the type of subscription:

“RECURRING” is for when the customer is making a recurring payment for a new product/service each time.

“INSTALLMENT” is for when a customer is purchasing a single order over several installments. Installments are supported for merchants with a Trust Payments acquiring account. If you are using a different acquiring bank, you will need to contact our Support Team to check this feature is supported before proceeding.

Note: If the subscription type is “INSTALLMENT” and you are processing payments on the US platform, certain acquiring banks also require the field subscriptionfinalnumber is submitted. Contact our Support Team for further information.

 

Response

You will need to ensure your system stores the transactionreference field returned in the browser redirect at the end of the checkout session (if configured), and/or the URL notification (if configured), as this must be referenced in the child request that is submitted later.

Parent request using the JavaScript Library

  Our JavaScript Library provides resources to help you quickly build your own streamlined checkout solution on the web. If you are unfamiliar with our JavaScript Library solution, click here to learn more and get started.

  • Both the [“THREEDQUERY”,”AUTH”] and [“THREEDQUERY”,”ACCOUNTCHECK”] parent requests follow a similar specification to that of a standard payment processed using our JavaScript Library, but are subject to different requirements when employed as part of a recurring payments solution.
  • These changes are made within the payload of the JWT.
  • Refer to the example and field specification below for further information.
{
  "payload":{
    "accounttypedescription":"ECOM",
    "baseamount":"1050",
    "credentialsonfile":"1",
    "currencyiso3a":"GBP",
    "requesttypedescriptions":["THREEDQUERY","AUTH"]
    "sitereference":"test_site12345",
    "subscriptionnumber":"1",
    "subscriptiontype":"RECURRING",
  },
  "iat":1559033849,
  "iss":"jwt.user"
}

 

Field specification

  Field Format Description
table-required.png accounttypedescription Alpha (20)

The correct account type value for the parent request is dependent on your account configuration. We recommend contacting our Support Team for advice on which account type values to submit when processing recurring payments. These values are supported:

  • “ECOM” – e-commerce
  • “MOTO” – Mail or Telephone Order
    (Note that 3-D Secure authentication is not supported for MOTO transactions)
table-required.png baseamount Numeric (13)

The amount associated with this request in base units, with no commas or decimal points. e.g. £10.99 would be submitted as “1099” but ¥246 would be submitted as “246”.

  • For an initial [“THREEDQUERY”,”AUTH”] request: This amount will be immediately reserved on the customer’s bank account.
  • For an initial [“THREEDQUERY”,”ACCOUNTCHECK”] request: No funds are reserved on the customer’s bank account.

This value will be inherited in all child requests that inherit from this parent request, unless the field is manually overridden.
table-required.png credentialsonfile Numeric (1) Visa and Mastercard have mandated that you must obtain cardholder consent before storing card details for future use. Following this, you must appropriately identify credentials that are to be stored for later, by assigning a Credentials on File (CoF) flag to signify this. For this reason, you must always submit credentialsonfile with value “1” in the parent request.

If you are processing a new recurring payments sequence using previously-stored credentials, you must still submit credentialsonfile = 1 in the parent request, to indicate the credentials will be stored to process future child payments in this sequence.

The value submitted here is returned in the response JWT.
table-required.png currencyiso3a Alpha (3) The transaction currency. This must remain the same in all future child requests processed that inherit from this parent request.
table-required.png requesttypedescriptions List The request types to be processed.
For the parent, this should be either [“THREEDQUERY”,”AUTH”] or  [“THREEDQUERY”,”ACCOUNTCHECK”]
table-required.png sitereference Alphanumeric
& underscore (50)		 The site reference relates to your individual account which you received on setup. If you do not know your site reference, please contact our Support Team.
table-required.png subscriptionnumber Numeric (5) For the parent [“THREEDQUERY”,”AUTH”] or  [“THREEDQUERY”,”ACCOUNTCHECK”] request: Submit “1”.

In each subsequent child request, the number submitted must be incremented by 1. For example the second request is “2”, the third is “3”, etc.
table-conditional.png subscriptionfinalnumber Numeric (5)

This is used to set the number of payments to be processed over the course of the subscription.

Note: This field is required for certain acquiring banks on the US platform when the subscriptiontype is “INSTALLMENT” (otherwise the field is optional). Contact our Support Team for further information.
table-required.png subscriptiontype Alpha (11)

This is the type of subscription:

“RECURRING” is for when the customer is making a recurring payment for a new product/service each time.

“INSTALLMENT” is for when a customer is purchasing a single order over several installments. Installments are supported for merchants with a Trust Payments acquiring account. If you are using a different acquiring bank, you will need to contact our Support Team to check this feature is supported before proceeding.

Note: If the subscription type is “INSTALLMENT” and you are processing payments on the US platform, certain acquiring banks also require the field subscriptionfinalnumber is submitted. Contact our Support Team for further information.

 

Response

The response JWT returned follows the same specification as when processing a standard payment. Of particular importance, your system will need to store the transactionreference returned, as this must be referenced in the child request that is submitted later. Click here to learn about decoding the JWT response.

Parent request using the Mobile SDK

  Our Mobile SDK provides resources to help you quickly build a streamlined checkout solution into your mobile app. If you are unfamiliar with our Mobile SDK solution, click here to learn more and get started.

  • Both the [“THREEDQUERY”,”AUTH”] and [“THREEDQUERY”,”ACCOUNTCHECK”] parent requests follow a similar specification to that of a standard payment processed using our Mobile SDK, but are subject to different requirements when employed as part of a recurring payments solution.
  • These changes are made within the payload of the JWT.
  • Refer to the example and field specification below for further information.
{
  "payload":{
    "accounttypedescription":"ECOM",
    "baseamount":"1050",
    "credentialsonfile":"1",
    "currencyiso3a":"GBP",
    "requesttypedescriptions":["THREEDQUERY","AUTH"]
    "sitereference":"test_site12345",
    "subscriptionnumber":"1",
    "subscriptiontype":"RECURRING",
    "termurl":"https://payments.securetrading.net/process/payments/mobilesdklistener",
  },
  "iat":1559033849,
  "iss":"jwt.user"
}

 

Field specification

  Field Format Description
table-required.png accounttypedescription Alpha (20)

The correct account type value for the parent request is dependent on your account configuration. We recommend contacting our Support Team for advice on which account type values to submit when processing recurring payments. These values are supported:

  • “ECOM” – e-commerce
  • “MOTO” – Mail or Telephone Order
    (Note that 3-D Secure authentication is not supported for MOTO transactions)
table-required.png baseamount Numeric (13)

The amount associated with this request in base units, with no commas or decimal points. e.g. £10.99 would be submitted as “1099” but ¥246 would be submitted as “246”.

  • For an initial [“THREEDQUERY”,”AUTH”] request: This amount will be immediately reserved on the customer’s bank account.
  • For an initial [“THREEDQUERY”,”ACCOUNTCHECK”] request: No funds are reserved on the customer’s bank account.

This value will be inherited in all child requests that inherit from this parent request, unless the field is manually overridden.
table-required.png credentialsonfile Numeric (1) Visa and Mastercard have mandated that you must obtain cardholder consent before storing card details for future use. Following this, you must appropriately identify credentials that are to be stored for later, by assigning a Credentials on File (CoF) flag to signify this. For this reason, you must always submit credentialsonfile with value “1” in the parent request.

If you are processing a new recurring payments sequence using previously-stored credentials, you must still submit credentialsonfile = 1 in the parent request, to indicate the credentials will be stored to process future child payments in this sequence.

The value submitted here is returned in the response JWT.
table-required.png currencyiso3a Alpha (3) The transaction currency. This must remain the same in all future child requests processed that inherit from this parent request.
table-required.png requesttypedescriptions List The request types to be processed.
For the parent, this should be either [“THREEDQUERY”,”AUTH”] or  [“THREEDQUERY”,”ACCOUNTCHECK”]
table-required.png sitereference Alphanumeric
& underscore (50)		 The site reference relates to your individual account which you received on setup. If you do not know your site reference, please contact our Support Team.
table-required.png subscriptionnumber Numeric (5) For the parent [“THREEDQUERY”,”AUTH”] or  [“THREEDQUERY”,”ACCOUNTCHECK”] request: Submit “1”.

In each subsequent child request, the number submitted must be incremented by 1. For example the second request is “2”, the third is “3”, etc.
table-conditional.png subscriptionfinalnumber Numeric (5)

This is used to set the number of payments to be processed over the course of the subscription.

Note: This field is required for certain acquiring banks on the US platform when the subscriptiontype is “INSTALLMENT” (otherwise the field is optional). Contact our Support Team for further information.
table-required.png subscriptiontype Alpha (11)

This is the type of subscription:

“RECURRING” is for when the customer is making a recurring payment for a new product/service each time.

“INSTALLMENT” is for when a customer is purchasing a single order over several installments. Installments are supported for merchants with a Trust Payments acquiring account. If you are using a different acquiring bank, you will need to contact our Support Team to check this feature is supported before proceeding.

Note: If the subscription type is “INSTALLMENT” and you are processing payments on the US platform, certain acquiring banks also require the field subscriptionfinalnumber is submitted. Contact our Support Team for further information.
table-required.png termurl URL (1024)

This URL is used to instruct the card issuer where to send the customer’s browser after they have been authenticated on the card issuer’s ACS. You must submit the following URL in this field when performing 3-D Secure:

https://payments.securetrading.net/process/payments/mobilesdklistener

 

Response

The response JWT returned follows the same specification as when processing a standard payment. Of particular importance, your system will need to store the transactionreference returned, as this must be referenced in the child request that is submitted later. Click here to learn about decoding the JWT response.

 

  Your progress

After following the instructions above, you should now be ready to manually process repeat payments using our Webservices API. You can take the transactionreference returned in the response JWT and include this in subsequent child requests.

 

2. Scheme update

Whenever a participating card issuer re-issues a customer’s card, they submit the new account number and expiry date to the Visa Account Updater (VAU) or Mastercard’s Automatic Billing Updater (ABU) systems, as appropriate. In the days preceding a recurring payment, you can manually submit a SCHEMEUPDATE request to Trust Payments using our Webservices API, and we will contact the VAU and ABU to check for updates. If the payment credentials have been updated, we will store the new details and these will be used in future recurring payments.

 

Benefits

  Reduced disruption when customers are issued new cards, increasing rate of successful transactions.

  Customers do not have to update their payment details on your site to make future payments.

  Customers are not required to take any action to ensure subscriptions continue as normal.

  We strongly recommend that merchants processing high volume recurring transactions enable Scheme updates.

We only support this functionality with supported acquiring banks.

This functionality must be enabled on your site reference(s) before it can be used. Please contact our Support Team to discuss enabling Scheme updates.

 

Here's how it works:

  • If a scheme update request is submitted prior to processing a child request, and we successfully retrieve updated payment credentials from the VAU or ABU, the subsequent child request described below will be processed using these new details.
  • If a scheme update request is submitted prior to processing a child request, and the payment credentials are already up-to-date, the subsequent child request described below will be processed using the existing details stored.
  • If you do not submit a scheme update, the child request described below will be processed using the existing details stored.

  Click here for our full scheme updates documentation.
(This will open in a new tab)

 

3. Child request

  This section describes the subsequent recurring payment. This section assumes the parent request described earlier has already been processed.

  Before processing a child request, you must ensure that the parent request has completed successfully. Investigate any issues raised and if assistance is required, contact our Support Team.

About declines: Mastercard has mandated that in cases where a recurring payment has been declined by the card issuer, your system must not retry the request more than once per day for the next 31 days. After this period has passed, your system must not send further requests for the affected customer.

 

Process overview

  1. Your system requests that a new payment is processed, by manually submitting an AUTH request using our Webservices API, which includes the transactionreference of the parent AUTH or ACCOUNTCHECK.

  For those using our JavaScript Library or Mobile SDK to process the parent request, the subsequent response JWT returned will also contain the transactionreference of the THREEDQUERY. You must not submit this in the child request. Instead, you must only submit the transactionreference value associated with the parent AUTH or ACCOUNTCHECK.

  1. We contact the acquiring bank to seek authorisation for the payment, using the billing and delivery details inherited from the parent AUTH/ACCOUNTCHECK. (Your system does not need to re-submit these details)
  2. Your system receives an AUTH response, including the results of the request.

 

Request

The request type submitted for the child request must be “AUTH” (submitted in the requesttypedescriptions field). The AUTH child request follows a similar specification to a standard AUTH request, but is subject to different requirements when employed as part of a recurring payments solution. Refer to the example and field specification below for further information.

Python PHP cURL Raw JSON Raw XML
#!/usr/bin/python
import securetrading

stconfig = securetrading.Config()
stconfig.username = "webservices@example.com"
stconfig.password = "Password1^"
st = securetrading.Api(stconfig)

auth = {
  "sitereference": "test_site12345",
  "requesttypedescriptions": ["AUTH"],
  "accounttypedescription": "RECUR",
  "parenttransactionreference": "12-3-4567",
  "baseamount": "1050",
  "subscriptiontype": "RECURRING",
  "subscriptionnumber": "2",
  "credentialsonfile": "2"
}

strequest = securetrading.Request()
strequest.update(auth)
stresponse = st.process(strequest) #stresponse contains the transaction response

Replace <DOMAIN> with a supported domain. Click here for a full list.

 

  The example above assumes that the previous request was the first to be processed, therefore the subscriptionnumber is assigned value “2”. Subsequent child requests are processed with the same structure, incrementing this number each time (i.e. next payment in sequence would be “3”, then “4” and so on).

  Field Format Description
table-required.png accounttypedescription
XPath: /operation/accounttypedescription		 Alpha (20) This must be set to “RECUR”.
table-optional.png baseamount
XPath: /billing/amount		 Numeric (13)

The amount associated with the child payment in base units, with no commas or decimal points. e.g. £10.99 would be submitted as “1099” but ¥246 would be submitted as “246”.

If you don’t submit this field, the amount processed will be inherited from the preceding parent request.
table-required.png credentialsonfile
XPath: /operation/credentialsonfile		 Numeric (1)

This is required for Visa and Mastercard transactions where the merchant is utilising Credentials on File (CoF).

Submit “2” in this field to indicate the payment is using previously-stored credentials.
table-optional.png currencyiso3a
XPath: /billing/amount/@currencycode		 Alpha (3) If submitted, this must be the same currency used in the parent request.

If not submitted, this value is inherited from the parent request.
table-required.png parenttransactionreference
XPath: /operation/parenttransactionreference		 Alphanumeric
& hyphens (25)		 You must submit the transactionreference value of the AUTH or ACCOUNTCHECK returned in the response JWT of the initial parent request.

You must not submit the transactionreference value associated with the THREEDQUERY.
table-required.png requesttypedescriptions
XPath: /@type		 Alpha (20) You must submit “AUTH”, as shown in the request example.
table-required.png sitereference
XPath: /operation/sitereference		 Alphanumeric
& underscore (50)		 The site reference relates to your individual account which you received on setup. If you do not know your site reference, please contact our Support Team.
table-required.png subscriptionnumber
XPath: /billing/subscription/number		 Numeric (5)

This is used to identify a payment’s position within a sequence of recurring transactions.

For each subsequent payment, the number submitted should be incremented by 1 (without gaps).

e.g. 2nd transaction is “2”, 3rd is “3”, then “4” etc.

(You should only increment this number if the previous recurring payment request was successful)

We do not impose limits on the number of payments made against a card.
table-required.png subscriptiontype
XPath: /billing/subscription/@type		 Alpha (11)

This is the type of subscription:

“RECURRING” is for when the customer is making a recurring payment for a new product/service each time.

“INSTALLMENT” is for when a customer is purchasing a single order over several installments. Installments are supported for merchants with a Trust Payments acquiring account. If you are using a different acquiring bank, you will need to contact our Support Team to check this feature is supported before proceeding.

 

Response

The response returned follows the same specification as a standard AUTH response, with the exception of the additional field acquireradvicecode that can be returned (see the field specification below for further information).

 

Field specification

  Field Format Description
table-returned.png accounttypedescription
XPath: /operation/accounttypedescription		 Alpha (20) Account type “RECUR” will be returned.
table-conditional.png acquireradvicecode
XPath: /acquireradvicecode		 Numeric (1)

A numeric value returned from the acquiring bank, which is used to indicate whether further payments can be processed. A full mapping of these values can be found in the “Additional notes” section at the bottom of this page.

Only returned if supported by your acquiring bank.
table-returned.png baseamount
XPath: /billing/amount		 Numeric (13)

The amount associated with the child payment in base units, with no commas or decimal points. e.g. £10.99 would be submitted as “1099” but ¥246 would be submitted as “246”.

We recommend checking this amount matches the value you are expecting. The amount returned here reflects the amount the customer will be debited on the child payment.
table-returned.png credentialsonfile
XPath: /operation/credentialsonfile		 Numeric (1) If the credentialsonfile field has been submitted in the request and it is supported by the acquirer processing the transaction, it is returned in the response.
table-returned.png currencyiso3a
XPath: /billing/amount/@currencycode		 Alpha (3)

The currency of the transaction.

Click here for a full list of available currencies.
table-returned.png parenttransactionreference
XPath: /operation/parenttransactionreference		 Alphanumeric
& hyphens (25)		 The transaction reference of the parent transaction.
table-returned.png requesttypedescription
XPath: /@type		 Alpha (20) Request type “AUTH” will be returned.

  Mastercard has mandated that in cases where a recurring payment has been declined by the card issuer, you must not retry more than once per day for the next 31 days. After this period has passed, your system must not send further requests for the affected customer.

  Summary

Following the instructions above, your system should now be able to manually process repeat payments using our Webservices API, without needing to re-submit any of the customer’s billing or payment credentials. As always, we strongly recommend thoroughly testing your solution to ensure recurring payments are being processed as expected, before performing live payments on your production system. Please read on for additional information you may find useful when developing a recurring payments solution.

 

Additional notes

Below are some additional notes to consider when processing recurring payments.

 

Acquirer advice code mapping

The acquirer advice code is a numeric value returned if supported by your acquiring bank, indicating if further payments can be processed. The codes are mapped as follows:

Code Description Action
0

N/A

(Mastercard only)

 No action required
1

“New account information available”

The bank has reason to believe that the customer’s card details are out-of-date (e.g. the expiry date has passed).

(Mastercard only)

 Please check with the customer that their card details are still correct. This field is advisory and we will allow you to re-process even if the card details are not updated, however the acquiring bank may not accept the payment. You may find it useful to contact your bank in such cases for clarification.
2 “Cannot approve at this time” Try again later. If you are continuing to have difficulties, please contact your acquiring bank.
4 “Do not try again” Do not process further recurring transactions.
8 “Payment blocked by card scheme”

 

3-D secure liability shift

By processing the first AUTH with 3-D Secure, the subsequent recurring payments may also be covered by the benefits of the schemes, depending on your acquirer. Please contact your bank for further information on recurring payments and 3-D Secure.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Articles in this section

See more