On This Page

Required Fields for Processing a Sale with
Cybersource
 Decryption

As a best practice, include these
REST API
 fields in your request for a combined authorization and capture (sale) transaction with the
Cybersource
 decryption implementation of Apple Pay.
Depending on your processor, your geographic location, and whether the relaxed address verification system (RAVS) is enabled for your account, some of these fields might not be required. It is your responsibility to determine whether an API field can be omitted from the transaction you are requesting.
Format of the encrypted payment data.
Set the value to
RklEPUNPTU1PTi5BUFBMRS5JTkFQUC5QQVlNRU5U
 for Apple Pay.
Encoding method used to encrypt the payment data.
Set the value to
Base64
 for Apple Pay.
For card-present transactions: set the value to the encrypted payment data.
Set the value to
true
 for a sale transaction (to include a capture with the authorization).
Type of transaction. Some payment card companies use this information when determining discount rates. Possible values:
  • aesk
    :   American Express SafeKey authentication.
  • dipb
    :   Discover card type.
  • internet
    :   Default value for authorizations. E-commerce order placed from a website.
  • js
    :   JCB J/Secure authentication.
  • spa
    :   Mastercard Identity Check authentication.
  • 111
    :   Visa Secure authentication
Set the value to
001
 to identify Apple Pay as the digital payment solution.