Skip to login Skip to content
Developer Cybersource Logo

Getting started

Find tailored resources to kickstart your integration

API Reference

Use our live console to test and start building with our APIs

 

Accept payments

Online or In-person payment acceptance made easy

Technology partners

Register to get onboard our sandbox environment as a Tech partner or explore our pre-built integrations

Resources

Create seamless scalable payment experiences with interactive tools and detailed documentation

Documentation hub

Explore developer guides and best practices for integration with our platform

SDKs

Get pre-built samples to build or customize your integrations to fit your business needs

Demo hub

Access to variety of our product demos 

Testing

Signup for sandbox and use testing resources before going live

Sandbox signup

Create a sandbox to test our APIs

 

Testing guide

Guide with sandbox testing instructions and processor specific testing trigger data

Response codes

Understand all different error codes that REST API responds with

Support

Find resources and guidance to build, test, and deploy on our platform

Frequently asked questions

Find answers to commonly-asked questions about our APIs and platform

Contact us

Connect with our team of experts to troubleshoot or go-live to Production

Developer community

Connect and share with community of developers 

 

AI Assistant

Menu
API Overview
  • Card Present Connect | Electric Vehicle Charging Developer Guide
    • Recent Revisions to This Document
    • VISA Platform Connect: Specifications and Conditions for Resellers/Partners
  • Introduction to Electric Vehicle Charging
    • Supported Card Types and Entry Modes
    • Prerequisites
    • Validation and Certification
      • Message-Level Validation
      • EMV Level 3 Certification
    • Card-Present Transaction Risk Control Requirements
  • Electric Vehicle Charging Transaction Scenarios
    • Pre-Pay Transaction Scenario
    • Post-Pay Transaction Scenario
    • Flexible Transaction Scenario
      • Prerequisites for the Flexible Transaction Scenario
  • Electric Vehicle Charging Payment Services
    • Electric Vehicle Charging EMV and Card Data
    • Electric Vehicle Charging Transaction Descriptions
    • Authentication Requirements for Incremental Authorizations in Europe
    • Authorization for Visa Pre-Pay
      • Required Fields for Authorization for Visa Pre-Pay
      • REST Example: Authorization for Visa Pre-Pay
    • Capture for Visa Pre-Pay EMV
      • Required Fields for Capture for Visa Pre-Pay EMV
      • REST Example: Capture for Visa Pre-Pay EMV
    • Sale for Mastercard Post-Pay
      • Required Fields for Sale for Mastercard Post-Pay
      • REST Example: Sale for Mastercard Post-Pay
    • Authorization for Visa Flexible
      • Required Fields for Authorization for Visa Flexible
      • REST Example: Authorization for Visa Flexible
    • Incremental Authorization for Visa Flexible
      • Required Fields for Incremental Authorization for Visa Flexible
      • REST Example: Incremental Authorization for Visa Flexible
    • Capture for Visa Flexible EMV
      • Required Fields for Capture for Visa Flexible EMV
      • REST Example: Capture for Visa Flexible EMV
  • Documentation hub
  • Ev-charging
  • Card Present Connect | Electric Vehicle Charging Developer Guide
    • Recent Revisions to This Document
    • VISA Platform Connect: Specifications and Conditions for Resellers/Partners
  • Introduction to Electric Vehicle Charging
    • Supported Card Types and Entry Modes
    • Prerequisites
    • Validation and Certification
      • Message-Level Validation
      • EMV Level 3 Certification
    • Card-Present Transaction Risk Control Requirements
  • Electric Vehicle Charging Transaction Scenarios
    • Pre-Pay Transaction Scenario
    • Post-Pay Transaction Scenario
    • Flexible Transaction Scenario
      • Prerequisites for the Flexible Transaction Scenario
  • Electric Vehicle Charging Payment Services
    • Electric Vehicle Charging EMV and Card Data
    • Electric Vehicle Charging Transaction Descriptions
    • Authentication Requirements for Incremental Authorizations in Europe
    • Authorization for Visa Pre-Pay
      • Required Fields for Authorization for Visa Pre-Pay
      • REST Example: Authorization for Visa Pre-Pay
    • Capture for Visa Pre-Pay EMV
      • Required Fields for Capture for Visa Pre-Pay EMV
      • REST Example: Capture for Visa Pre-Pay EMV
    • Sale for Mastercard Post-Pay
      • Required Fields for Sale for Mastercard Post-Pay
      • REST Example: Sale for Mastercard Post-Pay
    • Authorization for Visa Flexible
      • Required Fields for Authorization for Visa Flexible
      • REST Example: Authorization for Visa Flexible
    • Incremental Authorization for Visa Flexible
      • Required Fields for Incremental Authorization for Visa Flexible
      • REST Example: Incremental Authorization for Visa Flexible
    • Capture for Visa Flexible EMV
      • Required Fields for Capture for Visa Flexible EMV
      • REST Example: Capture for Visa Flexible EMV
On This Page

Required Fields for Authorization for Visa Pre-Pay

clientReferenceInformation.code
clientReferenceInformation.comments
Set the value to
Pre-Pay Auth
.
clientReferenceInformation.partner.developerId
Cybersource
provides the value for this field.
clientReferenceInformation.partner.solutionId
Cybersource
provides the value for this field.
clientReferenceInformation.partner.thirdPartyCertificationNumber
Cybersource
provides the value for this field.
clientReferenceInformation.transactionId
merchantInformation.transactionLocalDateTime
orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount
paymentInformation.card.type
pointOfSaleInformation.catLevel
Set this value to
2
.
pointOfSaleInformation.emv.cardSequenceNumber
pointOfSaleInformation.emv.tags
pointOfSaleInformation.entryMode
pointOfSaleInformation.terminalCapability
pointOfSaleInformation.terminalId
This field is required when within project scope. Merchant configuration must support multiple terminal IDs. Otherwise,
Cybersource
uses the default terminal ID in the merchant configuration.
pointOfSaleInformation.terminalPinCapability
Set this value to
0
.
pointOfSaleInformation.trackData
processingInformation.authorizationOptions.authIndicator
Set the value to
1
.
processingInformation.commerceIndicator
Set the value to
retail
.

Related Information

  • API field reference guide for the REST API
Previous topic
Next topic
Back to top

Visa

Cybersource.com

Terms + conditions

Cookie policy

Privacy notice

Your privacy rights

© 2024 Cybersource. All rights reserved. All brand names and logos are the property of their respective owners, are used for identification purposes only, and do not imply product endorsement or affiliation with Cybersource.