Stored Credentials
- Customer-Initiated Transactions with Credentials on File
- Industry Practice Transactions
- Standing Instructions Transactions
  - Requirements for Standing Instruction Transactions
  - Recurring Billing for Recurring Payments

Transaction Matrix for Industry Practice and Standing Instructions
- Initial Transactions
- Subsequent Transactions

Customer-Initiated Transactions with Credentials on File
- Storing Customer Credentials with a Customer-Initiated Transaction
  - Required Fields for Storing Customer Credentials During a Customer-Initiated Transaction
  - REST Example: Storing Customer Credentials During a Customer-Initiated Transaction
- Using Stored Customer Credentials During a Customer-Initiated Transaction
  - Required Fields for Retrieving Customer Credentials During a Customer-Initiated Transaction
    - Card-Specific Required Field for Retrieving Customer Credentials During a Customer-Initiated Transaction
  - REST Example: Retrieving Customer Credentials During a Customer-Initiated Transaction

Merchant-Initiated Delayed Transaction
- Required Fields for Processing a Merchant-Initiated Delayed Transaction
  - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
- REST Example: Processing a Merchant-Initiated Delayed Authorization Transaction

Merchant-Initiated Incremental Transaction
- Required Fields for Processing Merchant-Initiated Incremental Transactions
  - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
- REST Example: Processing Merchant-Initiated Incremental Transactions

Merchant-Initiated Reauthorization Transactions
- Required Fields for Processing Merchant-Initiated Reauthorized Transactions
  - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
- REST Example: Processing a Merchant-Initiated Reauthorized Transaction

Merchant-Initiated Resubmission Transaction
- Required Fields for Processing a Merchant-Initiated Resubmitted Transaction
  - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
- REST Example: Processing a Merchant-Initiated Resubmitted Transaction

Merchant-Initiated No-Show Transactions
- Required Fields for Processing Merchant-Initiated No-Show Charges
  - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
- Optional Field for Processing Merchant-Initiated No-Show Charges
- REST Example: Processing Merchant-Initiated No-Show Transactions

Recurring Payments
- Recurring Billing for Recurring Payments
- Initial CIT Recurring Payment with a PAN
  - Required Fields for Authorizing Initial Recurring Payments Using REST API
  - REST Example: Authorizing an Initial CIT Recurring Payment with a PAN
- Initial CIT Recurring Payment with an Instrument Identifier
  - Required Fields for Authorizing Initial Recurring Payments with an Instrument Identifier
  - REST Example: Authorizing an Initial Recurring Payment with an Instrument Identifier
- Initial CIT Recurring Payment with a Customer ID
  - Required Fields for Authorizing Initial Recurring Payments with a Customer ID
  - REST Example: Authorizing an Initial Recurring Payments with a Customer ID
- Subsequent MIT Recurring Payments
  - Required Fields for Authorizing Subsequent Recurring Payments
    - Card-Specific Required Fields for Authorizing Subsequent Recurring Payments
    - credentials-mit-common-intro-country
  - REST Example: Authorizing Subsequent Recurring Payments
- Subsequent MIT Recurring Payments with an Instrument Identifier
  - Required Fields for Authorizing Subsequent Recurring Payments with Instrument Identifier
    - Card-Specific Required Fields for Authorizing Subsequent Recurring Payments
  - REST Example: Authorizing Subsequent Recurring Payments with an Instrument Identifier
- Subsequent MIT Recurring Payments with a Customer ID
  - Required Fields for Authorizing Subsequent Recurring Payments with a Customer ID
    - Card-Specific Required Fields for Authorizing Subsequent Recurring Payments
  - REST Example: Authorizing Subsequent Recurring Payments with a Customer ID

Mastercard Standing Order Payments
- Mastercard Initial CIT Standing Order Payment
  - Required Fields for Authorizing Initial CIT Standing Order Payments
  - REST Example: Authorizing Initial CIT Standing Order Payments

Mastercard Subscription Payments
- Mastercard CIT Initial Subscription Payment
  - Required Fields for Authorizing CIT Initial Subscription Payments
  - REST Example: Authorizing Initial CIT Subscription Payments

Unscheduled COF Payments
- Initial CIT Unscheduled COF Payment
  - Required Fields for Authorizing Initial CIT Unscheduled COF Payments
  - REST Example: Authorizing Initial CIT Unscheduled COF Payments
- Subsequent MIT Unscheduled COF Payments
  - Required Fields for Authorizing Subsequent MIT Unscheduled COF Payments
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
    - credentials-mit-common-intro-country
  - credentials-mit-unsched-optfields
  - REST Example: Authorizing Subsequent MIT Unscheduled COF Payments

On This Page

REST API | Barclays

Required Fields for Authorizing Subsequent Recurring Payments

Use these required fields to authorize subsequent recurring payments.

orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount
orderInformation.billTo.address1
orderInformation.billTo.administrativeArea
orderInformation.billTo.country
orderInformation.billTo.email
orderInformation.billTo.firstName
orderInformation.billTo.lastName
orderInformation.billTo.locality
orderInformation.billTo.phoneNumber
orderInformation.billTo.postalCode
paymentInformation.card.expirationMonth
paymentInformation.card.expirationYear
paymentInformation.card.number
processingInformation.authorizationOptions.initiator.merchantInitiatedTransaction. previousTransactionID
processingInformation.authorizationOptions.initiator.storedCredentialUsed: Set to
true
.
processingInformation.authorizationOptions.initiator.type: Set to
merchant
.
processingInformation.commerceIndicator: Set to
recurring
.
processingInformation.initiator.merchantInitiatedTransaction.reason: Set to
7
.

Back to top