Skip to main content
Cybersource is a Visa solution that provides comprehensive card processing solutions globally. The platform supports card payments with advanced features like delayed capture, over-capture, partial refunds, network tokenization, and digital wallet integration across multiple currencies and countries.

Setup

Please follow the common Cybersource instructions to get set up with CyberSource. Some Cybersource features need to be enabled by their support team to be used/tested:
  • 3-D Secure - Needs to be activated on your merchant ID, using the external 3DS server
  • Tokenization - Needs to be activated on your merchant ID, ensuring support for both Instrument Identifiers and Payment Instruments is added
  • Metadata - You must define Merchant Defined Data Fields via the Terminal Settings on the Cybersource dashboard. Metadata keys must be integers or they are ignored. These keys are mapped to your merchant-defined data fields
  • Cybersource Decision Manager - Must be turned off within the Payment Configuration options of the merchant account for the connector to work as expected. If this feature is required, please use the Cybersource Decision Manager Anti-Fraud Connector

Capabilities

Supported countries

Supported currencies

Integration

To accept card payments with CyberSource, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which automatically routes the payment to your configured CyberSource connection based on your Flow rules or explicit payment_service_id parameter.

Testing

For test scenarios and additional card numbers, refer to the CyberSource testing documentation or contact your CyberSource representative.