Scheme reference data

This functionality allows you to continue a recurring payment sequence that was originally started using a different Payment Service Provider than Trust Payments. The scheme reference data submitted provides a link to the payment history between your business and the customer.

  About Visa scheme reference data

The scheme reference data required by Visa in Recurring and other types of Merchant Initiated Transaction (MIT) authorisation requests is called the Visa Transaction Identifier (Transaction ID).

The Visa Transaction ID is a unique identifier for each original authorisation request, which is a numeric value of up to 15 digits in length included in the Visa authorisation response returned, following the initial Customer Initiated Transaction authorisation submitted when the cardholder first signed up to the recurring or MIT agreement.

Example of a Visa Transaction ID: 987654321234567

Trust Payments require the Visa Transaction ID to be provided in the above format.


  About Mastercard scheme reference data

The scheme reference data required by Mastercard in Recurring and other types of Merchant Initiated Transaction (MIT) authorisation requests is called the Mastercard Trace ID.

The Mastercard Trace ID is a combination of the Mastercard Financial Network Code, Banknet Reference Number and Banknet Settlement Date included in the Mastercard authorisation response returned, following the initial Customer Initiated Transaction authorisation submitted when the cardholder first signed up to the recurring or MIT agreement.

Example of a Mastercard Trace ID: "MCCABC1XY0101  "

Positions 1-3 = “MCC” = Financial Network Code
Positions 4-9 = “ABC1XY” = Banknet Reference Number
Positions 10-13 = “0101” = Banknet Settlement Date
Positions 14-15 = space filled

Trust Payments require the Mastercard Trace ID to be provided in the following format: "MCCABC1XY   0101"

Positions 1-3 = “MCC” = Financial Network Code
Positions 4-9 = “ABC1XY” = Banknet Reference Number
Positions 10-12 = “ ” = space filled
Positions 13-16 = Banknet Settlement Date

 

Requirements

  • Before you proceed, you will need to contact our Support Team and request scheme reference data functionality is enabled on your site reference(s).
  • This is functionality is only supported if you are processing payments with TRU Acquiring.

 

Submit request with scheme reference data

Request example

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",
"currencyiso3a": "GBP",
"baseamount": "1050",
"orderreference": "My_Order_123",
"pan": "4111111111111111",
"expirydate": "12/2020",
"schemereferencedata": "123456789012345",
"subscriptiontype": "RECURRING",
"subscriptionnumber": "2",
"credentialsonfile": "2"
}

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

 

Request field specification

An extra field is required in this use case:

  Field Format Description
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-required.png schemereferencedata
XPath: /operation/schemereferencedata

If Mastercard scheme:

  • Alphanumeric (max length 16)
    • Positions 1-3 = Financial Network Code
    • Positions 4-9 = Banknet Reference Number
    • Positions 10-12 = space filled
    • Positions 13-16 = Banknet Settlement Date

If Visa scheme:

  • Numeric (15)
    e.g. 123456789012345
Scheme reference data provided by your previous Payment Service Provider (PSP) following the initial payment in the sequence. This must be submitted unmodified.
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.

 

Handling the response

The scheme reference data will be returned in the response:

  Field Format Description
table-returned.png schemereferencedata
XPath: /operation/schemereferencedata

If Mastercard scheme:

  • Alphanumeric (max length 16)
    • Positions 1-3 = Financial Network Code
    • Positions 4-9 = Banknet Reference Number
    • Positions 10-12 = space filled
    • Positions 13-16 = Banknet Settlement Date

If Visa scheme:

  • Numeric (15)
    e.g. 123456789012345

Scheme reference data associated with this transaction, as returned by the card issuer.

Note: In subsequent recurring payments, you must continue to submit the original scheme reference data that was submitted in the request.

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