Skip to main content

Secure remote payments

Casestanding instructionindustry practicesecure remote payment
Secure remote payment--present
Secure remote payment as standing instruction CIT- recurring initial
- unscheduled initial
-present
Secure remote payment as standing instruction MIT- recurring subsequent
- unscheduled subsequent
-optionally present
Secure remote payment as industry practice MIT-- delayed_charges
- no_show
- reauthorization
- resubmission
optionally present
note
  • For MIT transactions the secure remote payment block is optional. In case it is sent, only the mandatory fields need to be provided.
  • For more information on how to fill in the credential on file information, please check the credential on file section.

Secure remote payment

Shopper makes a purchase on merchants website based on tokenized card (Apple Pay, Google Pay, etc.).

FieldValue
secureRemotePaymentpresent

Secure remote payment as standing instruction CIT

Cardholder authorizes the merchant to store the account data to pull funds from his account automatically at regular intervals for the goods and services provided to them on an ongoing basis. The amount could be fixed or variable.

FieldValue
secureRemotePaymentpresent
standingInstruction.type- recurring
- unscheduled
standingInstruction.modeinitial

Secure remote payment as standing instruction MIT

Merchant pulls funds using the account previously stored. Used typically in subscriptions of VOD (fixed amount) or phone company billing (variable amount).

FieldValue
secureRemotePaymentoptionally present
standingInstruction.type- recurring
- unscheduled
standingInstruction.modesubsequent

Secure remote payment as industry practice MIT

For more information on industry practice values for MIT transactions, please check the merchant initiated transactions section.

FieldValue
secureRemotePaymentoptionally present
industryPractice.type- delayed_charges
- no_show
- reauthorization
- resubmission