Cybersource
Keep Cybersource in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
37 ways to read, 7 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Cybersource, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create TMS customerApproval by rule
- Create draft invoiceApproval by rule
- Get report definitionRead
Example flow
- Cybersource · Get report definitionDone
- Cybersource · Create TMS customerNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Cybersource.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Cybersource
- Cybersource's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Cybersource (Visa) test account before you go live.
For developers
Technical detail
Cybersource transactions, reports, chargebacks, retrievals, interchange, recurring billing, payment links, webhooks and Account Updater (read); customers, invoices, plans and links (write).
Cybersource (Visa) API docs- Source actions
- 37
- Destination actions
- 7
- Data types
- 25
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account updater batches2
- Get Account Updater batch statusSource
Status and totals of one Account Updater batch.
- List Account Updater batchesSource
Account Updater batches with status and totals.
Chargeback summaries1
- List chargeback summariesSource
Chargeback counts per account and period.
Chargebacks1
- List chargeback detailsSource
Chargebacks and retrievals in a period, with reason, amount and response due date.
Conversion details1
- List decision conversionsSource
Decision Manager review outcomes: original and new decision per transaction.
Customers3
- Create TMS customerDestinationNot retried automaticallyApproval before production
Create a Token Management customer record without payment details. Nothing is charged.
- Get TMS customerSource
A Token Management customer with default instrument and shipping address IDs.
- Update TMS customerDestinationProvider duplicate protectionApproval before production
Update customer details, merchant-defined fields, or the default payment instrument or shipping address.
Interchange details1
- List interchange clearing detailsSource
Interchange clearing level, rates, interchange and billback amounts per transaction.
Invoice settings1
- Get invoice settingsSource
Invoicing or Pay by Link settings: display name, currency, language and reminders.
Invoices4
- Create draft invoiceDestinationNot retried automaticallyApproval before production
Create an invoice in DRAFT status. Nexra never sends or publishes it; the customer pays only after you send it from Cybersource.
- Get invoiceSource
One invoice with customer, line items, amounts and payment link.
- List invoicesSource
Invoices with status, amounts, due date and payment link.
- Update invoiceDestinationProvider duplicate protectionApproval before production
Replace an unpaid invoice's details. The invoice number cannot change, and Nexra never sends it.
Net fundings1
- List net funding summariesSource
Conveyed, settled and funded totals for purchases, refunds, fees and chargebacks.
Notification of changes1
- List notifications of changeSource
ACH notifications of change (NOC codes) per transaction in a period.
Payment batch summaries1
- List payment batch summariesSource
Sales and credit counts and amounts per currency and payment type in a period.
Payment instruments2
- Get customer payment instrumentSource
One tokenized payment instrument with card type, expiry and billing address.
- List customer payment instrumentsSource
Tokenized payment instruments on a customer; card numbers are never returned.
Payment links3
- Create payment linkDestinationNot retried automaticallyApproval before production
Create a Pay by Link purchase or donation link. No money moves until the customer pays on Cybersource's hosted page.
- Get payment linkSource
One Pay by Link link.
- List payment linksSource
Pay by Link links with status, amounts and line items.
Plans4
- Create recurring billing planDestinationNot retried automaticallyApproval before production
Create a Recurring Billing plan (DRAFT unless ACTIVE is chosen). A plan bills nobody until a subscription is created on it, which Nexra does not do.
- Get recurring billing planSource
One Recurring Billing plan.
- List recurring billing plansSource
Recurring Billing plans by code, status or name.
- Update recurring billing planDestinationProvider duplicate protectionApproval before production
Change a plan's name, description or (increase) its billing cycles.
Purchase refund details1
- List purchase and refund detailsSource
Purchases and refunds in a period with settlement, authorization, settlement status and fee details per request.
Report definitions2
- Get report definitionSource
One report definition with its attributes, formats and default settings.
- List report definitionsSource
Report types the account can subscribe to, with formats and defaults.
Report subscriptions2
- Get report subscriptionSource
One scheduled report subscription by report name.
- List report subscriptionsSource
Scheduled report subscriptions on the account.
Reports2
- Get reportSource
Report metadata: definition, format, frequency, status, period and fields.
- List available reportsSource
Generated reports you are subscribed to, filtered by time, name or status.
Retrieval summaries1
- List retrieval summariesSource
Retrieval request counts per account and period.
Retrievals1
- List retrieval detailsSource
Retrieval requests in a period with reason, amount and response due time.
Secure files1
- List secure filesSource
Files available on Secure File Share (reports and statements) in a date range.
Shipping addresses2
- Get customer shipping addressSource
One shipping address stored on a TMS customer.
- List customer shipping addressesSource
Shipping addresses stored on a TMS customer.
Subscriptions2
- Get recurring billing subscriptionSource
One Recurring Billing subscription (read only).
- List recurring billing subscriptionsSource
Recurring Billing subscriptions by code, status, customer or reference.
Transactions2
- Read transaction detailsSource
Read a Cybersource transaction by request ID: status, applications, amounts, processor and masked card details.
- Search transactionsSourceIncremental
Transaction Search by merchant reference, customer ID, submitted-time range or a Cybersource query.
Webhooks2
- Get webhookSource
One webhook subscription (security configuration is not mapped).
- List webhooksSource
Webhook subscriptions for an organization (security configuration is not mapped).
Access and limits
- Authentication
- Cybersource merchant HTTP-signature key
- Plans and access
- A Cybersource merchant (or transacting account under a portfolio) with a REST shared-secret key. Reporting, Transaction Search, Token Management and Invoicing must each be enabled for the merchant; some depend on the portfolio configuration.
- Test environment
- Create a sandbox account at developer.cybersource.com and use apitest.cybersource.com.
- Rate limits
- Cybersource does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries; customer and invoice creates are not repeated automatically.
- Pagination
- Transaction search, purchase and refund details, payment instruments, shipping addresses and invoices use offset and limit. Report summaries return the whole period.
- Provider events
- Cybersource Webhooks deliver transaction, token, invoice and decision events to a registered endpoint. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Intentional exclusions: payments, authorizations, captures, reversals, refunds, credits, voids, payouts, payment instrument or instrument identifier writes, tokenization, network-token enrollment and payment credentials, BIN lookup, capture contexts, sending, publishing or cancelling invoices, report and report-subscription creation, creating, updating, cancelling, suspending or reactivating Recurring Billing subscriptions, plan activation and deactivation, payment link updates, Account Updater batch creation and reports, webhook writes and security keys, tax calculation, boarding, and every delete.
- Recurring Billing plan updates change only name, description and billing cycles; amounts, periods and applyTo are never sent. New plans default to DRAFT.
- Notifications of change never map routing numbers, account numbers or consumer names; webhooks never map security configuration; Secure File Share and Account Updater reports are listed but not downloaded.
- Notification of Change reports (bank routing and account numbers) and report file downloads are not mapped.
- Invoices are created and updated only as drafts; Nexra never sends them.
- Card BIN, expiry on transactions, billing addresses on transactions and device data are not mapped.
Developer reference
- Create the Cybersource (Visa) credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Cybersource, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/cybersource and the Connections API.