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 | Mass Transit Developer Guide
    • Recent Revisions to This Document
  • Introduction to Card Present Connect | Mass Transit
    • Rider Benefits
    • Transit System Benefits
    • Mass Transit Terminology
    • Mass Transit Prerequisites
    • Mass Transit Transactions
      • Single Fare
      • Aggregated
      • Debt Recovery
      • Stand Alone Credit
    • First Ride Risk
      • First Ride Risk Eligibility Reason Codes
    • Test Cards
    • EMV Data Elements and Tags
  • Mass Transit Transaction Workflows
    • Single Fare Workflow
    • Aggregated Fare Workflow
    • Additional Workflows
      • Debt Recovery Workflows
  • Mass Transit Payment Services Using TMS Tokens
    • Pre-Authorization with a Token
      • Required Fields for a Pre-Authorization with a Token Using the REST API
      • REST Example: Pre-Authorization with a Token Using the REST API
    • Mass Transit Tap-Initiated Sale for Debt Recovery with a Token
      • Required Fields for a Tap-Initiated Sale for Debt Recovery with a Token Using the REST API
      • REST Example: Performing a Tap-Initiated Sale for Debt Recovery with a Token
    • Mass Transit Merchant-Initiated Sale for Debt Recovery with a Token
      • Required Fields for a Merchant-Initiated Sale for Debt Recovery with a Token Using the REST API
      • REST Example: Performing a Merchant-Initiated Sale for Debt Recovery with a Token
  • Mass Transit Follow-On Payment Services
    • Capture an Authorization
      • Required Fields for a Mass Transit Capture
      • REST Example: Capturing a Pre-Authorization
    • Authorization Reversal
      • Required Fields for a Mass Transit Authorization Reversal
      • REST Example: Reversing a Mass Transit Authorization
    • Refund
      • Required Fields for a Mass Transit Refund
      • REST Example: Refunding a Capture
    • Voiding a Capture
      • Required Fields for Voiding a Capture
      • REST Example: Voiding a Capture
    • Credit with a Token
      • Required Fields for a Credit with a Token Using the REST API
      • REST Example: Credit with a Token
  • Reference Information
  • Documentation hub
  • Mass-transit
  • Card Present Connect | Mass Transit Developer Guide
    • Recent Revisions to This Document
  • Introduction to Card Present Connect | Mass Transit
    • Rider Benefits
    • Transit System Benefits
    • Mass Transit Terminology
    • Mass Transit Prerequisites
    • Mass Transit Transactions
      • Single Fare
      • Aggregated
      • Debt Recovery
      • Stand Alone Credit
    • First Ride Risk
      • First Ride Risk Eligibility Reason Codes
    • Test Cards
    • EMV Data Elements and Tags
  • Mass Transit Transaction Workflows
    • Single Fare Workflow
    • Aggregated Fare Workflow
    • Additional Workflows
      • Debt Recovery Workflows
  • Mass Transit Payment Services Using TMS Tokens
    • Pre-Authorization with a Token
      • Required Fields for a Pre-Authorization with a Token Using the REST API
      • REST Example: Pre-Authorization with a Token Using the REST API
    • Mass Transit Tap-Initiated Sale for Debt Recovery with a Token
      • Required Fields for a Tap-Initiated Sale for Debt Recovery with a Token Using the REST API
      • REST Example: Performing a Tap-Initiated Sale for Debt Recovery with a Token
    • Mass Transit Merchant-Initiated Sale for Debt Recovery with a Token
      • Required Fields for a Merchant-Initiated Sale for Debt Recovery with a Token Using the REST API
      • REST Example: Performing a Merchant-Initiated Sale for Debt Recovery with a Token
  • Mass Transit Follow-On Payment Services
    • Capture an Authorization
      • Required Fields for a Mass Transit Capture
      • REST Example: Capturing a Pre-Authorization
    • Authorization Reversal
      • Required Fields for a Mass Transit Authorization Reversal
      • REST Example: Reversing a Mass Transit Authorization
    • Refund
      • Required Fields for a Mass Transit Refund
      • REST Example: Refunding a Capture
    • Voiding a Capture
      • Required Fields for Voiding a Capture
      • REST Example: Voiding a Capture
    • Credit with a Token
      • Required Fields for a Credit with a Token Using the REST API
      • REST Example: Credit with a Token
  • Reference Information
On This Page

Required Fields for a Mass Transit Capture

clientReferenceInformation.code
orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount

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.