Cybersource
United States / global: read transaction details.
Match provider records to your invoices, orders and finance workflows without moving funds.
Source actions
1
Destination actions
0
Data types
1
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
transactions
- Read transaction detailsSource
Read existing Cybersource transaction metadata; card and payer details are omitted.
Authentication
Cybersource merchant HTTP-signature key
Plans and access
An approved provider account with API access and the required read scopes. Availability depends on the merchant country, product, permissions and provider agreement.
Test environment
Use dedicated provider test credentials where available; credential-backed validation is pending.
Rate limits
Provider/account-specific limits apply. HTTP 429 and Retry-After are handled with bounded retries.
Provider events
Provider events are not ingested by this adapter. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Transaction Details lookup only, using an existing request ID. No transaction-search feed or payment writes.
- HTTP-signature key must have reporting access. Credential-backed validation pending.