Aller au contenu principal
Sur cette page

Cybersource Decision Manager returns an ACCEPT, REVIEW, or REJECT decision and a risk score from 0 to 99. DEUNA maps these results to its standard Low, Medium, and High risk tiers. This guide takes you from a Cybersource account to an active anti-fraud engine in eight steps.

Understand how Cybersource works with DEUNA#

Cybersource, a Visa solution, provides Decision Manager, a global fraud-management platform that uses insights from transactions across major card brands.

Capabilities

  • Visa global data network: Uses cross-merchant and cross-industry data to detect fraudulent patterns.
  • Advanced rules engine and machine learning: Combines merchant-specific business rules with machine-learning models.
  • Device fingerprinting and IP geolocation: Analyzes device, network, and location data to flag spoofing, proxies, and known fraudulent devices.
  • Omnichannel protection: Applies one fraud policy across web, mobile, in-app, and call-center transactions.

DEUNA standardizes Decision Manager decisions and scores as follows:

  • ACCEPT maps to Low Risk, and the transaction is processed immediately.
  • REVIEW maps to Medium Risk, and DEUNA triggers a 3-D Secure (3DS) step-up, waits for manual review in Cybersource, or both, depending on your configuration.
  • REJECT maps to High Risk, and the transaction is halted.

These are the default mappings. You can customize what triggers each tier to match your risk appetite.

Cybersource responseDEUNA risk levelDefault routing strategy
Decision ACCEPT and score 0-9🟢 Low RiskProcess through the preferred gateway.
Decision REVIEW and score 10-79🟡 Medium RiskWait for manual review, trigger 3DS, or both.
Decision REJECT and score 80-99🔴 High RiskDeny the transaction or route it to a specialized high-risk gateway.

Prerequisites#

You need an active Cybersource account with Decision Manager and a DEUNA Admin account with access to the test environment. Gather these values before you start:

SourceItemUsed in
CybersourceKeyStep 3
CybersourceMerchant IDSteps 2 and 3
CybersourceShared secretStep 3
CybersourceControl Panel username, password, and organization nameStep 1
DEUNAAdmin access to the test environmentSteps 3-7

1. Set up the test environment in Cybersource#

Complete this step in the Cybersource test Control Panel.

Create test users

  1. Go to Accounts and select Users.
  2. Select Create user.
  3. Create the users needed for testing.

Create simulation lists

Decision lists let you force an outcome by email address.

  1. Go to Decision Manager > Shared Configuration > Custom Lists.
  2. Create three lists:
    • Positive list: Emails that must always be accepted.
    • Review list: Emails that must go to manual review.
    • Negative list: Emails that must always be rejected.
  3. Add the test emails used in Test the integration to the corresponding lists.

:::info Mercado Pago tests The following testuser.com addresses are also accepted and are required for Mercado Pago tests:

  • test_aprove@testuser.com for the positive list
  • test_review@testuser.com for the review list
  • test_reject@testuser.com for the negative list :::

Create a profile

  1. Go to Decision Manager > Configuration > Profiles.
  2. Add a profile with centralized rules.

A preselected profile named A-Test is usually available and can be used instead.

Create and configure decision rules

Create one rule for each outcome:

  1. Go to Decision Manager > Configuration > Custom Rules.
  2. Select Add Rule.
  3. Configure the rules as follows:
FieldAcceptRejectReview
Rule NameAccept AlwaysReject AlwaysReview Always
DescriptionAccept AlwaysReject AlwaysReview Always
CategoryOther TestsOther TestsOther Tests
Core RuleSelectedSelectedSelected
DecisionAcceptRejectReview
Execution TimingBefore AuthBefore AuthBefore Auth
This rule is true ifAll conditions trueAll conditions trueAll conditions true
Order ElementEmail addressEmail addressEmail address
Comparison Opis equal tois equal tois equal to
Comparison valPositive ListNegative ListReview List
  1. Return to Custom Rules, select Edit Rule for each rule, and configure its profile behavior:
FieldAcceptRejectReview
Monitor
AcceptSelected
ReviewSelected
RejectSelected
Priority111
Execution TimingBefore AuthBefore AuthBefore Auth
  1. Select Update.

Configure the manual-review notification URL

Cybersource uses this URL to send manual-review decisions to DEUNA.

  1. Go to Decision Manager > Configuration > Extended settings > Developer settings.
  2. Turn on Enable order status notification.
  3. In Notification URL to receive notification, enter https://api.sandbox.deuna.io/post-transactions/cybersource.
  4. Select TEST URL.
  5. Under Notify for, select Reviewer decisions.
  6. Select UPDATE SETTINGS.

Create custom fields

Merchant-defined data (MDD) fields send order context to Decision Manager.

  1. Go to Decision Manager > Shared Configuration > Custom Fields.
  2. Select Add Custom Field.
  3. Create the fields that your rules use:
MDDNameTypeDescriptionExample
1Business LinestringPharmacy, restaurant, retail, or another line of business
2MerchantstringMerchant name
3Customer First NamestringFirst name or names, without last namesMario Alejandro
4Customer Last NamestringLast name or namesHernandez Gutierrez
5Customer StatestringStateTabasco
6Customer City or MunicipalitystringDelegation or municipalityCentro
7Customer Neighborhood/LocalitystringNeighborhood or settlementAtasta
8Customer Street and Number/FloorstringStreet and number, including the floor for buildings or interiorsCerrada de Revolucion 377
11Customer Postal CodestringPostal code86100
12Customer Mobile PhonenumberMobile phone number529932065236
13Store Registration MonthstringMonth when the customer registered in the storeJanuary
17Store Registration YearnumberYear when the customer registered in the store2022
18Guest or registered?stringYES for a guest or NO for a registered customerNO
19Customer Registration TimenumberNumber of days the customer has been registered90
21Items Purchased-Num ItemsnumberNumber of items in the cart1
22Most Expensive Item SKUstringMost expensive model in the cartROLEX 231
25Interest-free months purchase?stringYES for interest-free installments or NO otherwiseNO
26How many interest-free months?numberNumber of months; use 0 for a single payment3
28Discount PercentagenumberDiscount percentage on the total purchase0.2
29Discount code used?stringYES when a promotional code was used or NO otherwiseNO
31Loyalty points used?stringYES when points were used or NO otherwise; the value must come from the merchant's web or checkoutNO
32Delivery First NamestringFirst name or namesAlejandro Daniel
34Delivery Last NamestringLast name or namesValle Haya
35Delivery StatestringDelivery stateTabasco
36Delivery City or MunicipalitystringDelivery delegation or municipalityCentro
37Delivery Neighborhood/LocalitystringDelivery neighborhood or settlementAtasta
39Delivery Street and Number/FloorstringDelivery street and number, including the floorCerrada de Revolucion 377
40Delivery Postal CodestringDelivery postal code86100
41Delivery Mobile PhonestringMobile phone number529932065236
43Delivery DatedateDate in DD-MM-YYYY format30-11-2023
44Sales ChannelstringWeb, mobile, call center, or another channelweb
45Merchant AffiliationstringUnique merchant ID provided by the acquiring bank
46Order Day of WeekstringPurchase dayMonday
47-62Product 1-8: Brand and Model (subbrand)stringBrand in odd-numbered fields 47-61 and model in even-numbered fields 48-62ROLEX / 231

2. Configure device fingerprinting#

The device fingerprint is generated by a script that runs during checkout. It lets Cybersource identify the customer's device. The setup depends on how you connect to DEUNA.

  1. For the Payment Widget or a payment link, follow the Payment Widget instructions.
  2. For Direct API, follow the Direct API instructions.
  3. Add Cybersource to the providers object:
JavaScript
CYBERSOURCE: {
  cs_orgId: '<org_id>',
  cs_merchantId: '<merchant_id>'
}

Use the following values:

VariableDescriptionSandboxProduction
cs_orgId (org_id)Cybersource organization ID; it changes by environment1snn5n9wk8vif92e
cs_merchantId (merchant ID)Assigned by Cybersource for each storeYour merchant IDYour merchant ID
  1. For API integrations, send the output to DEUNA in anti_fraud_info.device.id when you create the payment.

3. Connect Cybersource in DEUNA Admin#

Complete this setup once per environment.

  1. In DEUNA Admin, turn on Test mode.
  2. Go to Connections, search for Cybersource, and select Connect.
  3. Enter the credentials and settings:
FieldValue
KeyKey provided by Cybersource
Merchant IDYour Cybersource merchant ID
Shared SecretShared secret provided by Cybersource
Environment (test, live)test for sandbox or live for production
Use "Review" status for 3DS (Yes or No)No, unless a REVIEW result should trigger 3DS; see Use REVIEW as a 3DS recommendation
Deactivate "ShipTo" object (Yes or No)Yes to remove ShipTo from the data sent to Cybersource; leave it empty or enter No to send ShipTo
  1. Select Connect.

Cybersource appears as a connected anti-fraud engine in the Connections list.

Exemple interactifUtilise des données fictives et n’effectue aucune requête API.
Production
Paiements

Connexions

Découvrez et gérez les intégrations de paiement, de portefeuille et antifraude.

Acme LATAM · Production
5 connexions fictivesMis à jour à l’instant
ConnexionsTypeStatutAction
AdyenPasserelle de paiementConnectée
WorldpayPasserelle de paiementConnectée
PayPalMoyen de paiementConnectée
Mercado PagoMoyen de paiementNon connectée
RiskifiedMoteur antifraudeNon connectée

:::info Manual review To hold Medium Risk orders for manual review, ask your DEUNA Technical Account Manager to confirm that manual review and automatic operation execution are enabled for the store and environment. :::

4. Map Merchant custom fields (MDDs) in DEUNA#

After creating the MDDs in Cybersource, map the corresponding order data to each MDD number. The mapping is stored in the merchant profile under merchant_custom_information.

Available sources include the billing_address, shipping_address, and items objects, metadata fields, constant values, and calculated values.

Set constant values

Use merchant_information for values that do not change between orders:

curl --location --request PUT 'https://api.stg.deuna.io/merchant/<merchant_id>/profile' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer <YOUR_ACCESS_TOKEN>' \
  --data '{
    "merchant_information": {
      "business_line": "ecommerce"
    }
  }'

Declare the MDD mapping

Send a second PUT request to the same endpoint. Each key is a DEUNA field, and each value is the corresponding Cybersource MDD number.

:::info Replacement behavior The request replaces the stored merchant_custom_information value. Always send the complete object, not only the fields you changed. :::

JSON
{
  "merchant_custom_information": {
    "installments": "37",
    "items_0_title": "22",
    "items_1_brand": "25",
    "items_1_title": "26",
    "billing_address": {
      "city": "4",
      "phone": "8",
      "zipcode": "7",
      "address2": "5",
      "last_name": "2",
      "first_name": "1",
      "state_name": "3"
    },
    "shipping_amount": "9",
    "shipping_address": {
      "city": "46",
      "phone": "50",
      "zipcode": "49",
      "address2": "47",
      "last_name": "44",
      "first_name": "43",
      "state_name": "45"
    },
    "payment_method": {
      "network_token_data": {
        "source": "97"
      }
    },
    "is_coupon_applied": "40",
    "is_installments_msi": "36",
    "get_total_quantity_products": "18",
    "get_max_unit_price_product_name": "19"
  }
}

Item fields follow the pattern items_<n>_title, items_<n>_brand, and items_<n>_description, where <n> is the item position starting at 0.

:::info APM and wallet orders For orders paid with APMs and wallets such as Google Pay or Apple Pay, it is very important to map this information as an MDD.

JSON
{
  "payment_method": {
    "network_token_data": {
      "source": "50"
    }
  }
}

:::

Map calculated values

You can map the following DEUNA-calculated keys to an MDD:

KeyDescriptionExample
is_coupon_appliedYES when a promotional code was used or NO otherwiseNO
is_installments_msiYES for interest-free installments or NO otherwiseNO
get_spanish_day_of_weekOrder day of the weekMonday
get_full_billing_addressBilling street and number, including the floor for buildings or interiorsCerrada de Revolucion 377
get_full_shipping_addressDelivery street and number, including the floorCerrada de Revolucion 377
get_channel_from_user_agentSales channel, such as web, mobile, or call center; read from the user agent for web and mobileweb
get_total_quantity_productsNumber of items in the cart1
get_total_discount_percentageDiscount percentage on the total purchase0.2
get_full_name_shipping_addressConcatenated first and last name from the shipping addressDiego Lora
get_full_name_billing_addressConcatenated first and last name from the billing addressSantiago Yepes
get_full_name_billing_address_uppercaseBilling full name in uppercaseSANTIAGO YEPES
get_max_unit_price_product_nameName of the most expensive item in the cartROLEX 231

Send and map metadata fields

To send your own fields as MDDs:

  1. Send the fields in the order's metadata object using the additional_data. prefix:
JSON
{
  "metadata": {
    "additional_data.account_name": "Nelson",
    "additional_data.identity_type": "DNI"
  }
}
  1. Map each field to its MDD number under merchant_custom_information.metadata. You can combine metadata with other sources such as merchant_information, email, and shipping_options:
JSON
{
  "merchant_custom_information": {
    "merchant_information": {
      "business_line": "22",
      "merchant_identifier": "1"
    },
    "metadata": {
      "additional_data.merchant_terminal": "2",
      "additional_data.account_name": "4",
      "additional_data.total_discount": "25"
    },
    "installments": "17",
    "billing_address": {
      "identification_type": "18",
      "identification": "19",
      "phone": "21"
    },
    "email": "20",
    "shipping_options": {
      "type": "26"
    },
    "get_full_name_billing_address_uppercase": "31"
  }
}

Use state and province codes for US and Canada billing

For billing addresses in the United States and Canada, send the state or province as its postal abbreviation:

  • United States (USPS): AL, AK, AS, AZ, AR, CA, CO, CT, DE, DC, FM, FL, GA, GU, HI, ID, IL, IN, IA, KS, KY, LA, ME, MH, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, MP, OH, OK, OR, PW, PA, PR, RI, SC, SD, TN, TX, UT, VT, VI, VA, WA, WV, WI, WY.
  • Canada (Canada Post): AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT.

5. Add Cybersource to your payment strategy#

  1. Go to Payment strategies.
  2. Find the rule where Cybersource should run and select Edit.
  3. Add Cybersource as the anti-fraud provider.
  4. Enable manual review.
  5. Enable automatic execution of operations.
  6. Select Activate.
Exemple interactifUtilise des données fictives et n’effectue aucune requête API.
Production
Paiements

Stratégies de paiement

Configurez le traitement par défaut et les règles de chaque flux de paiement.

Acme LATAM · Production

Traitement par défaut

Configurez le traitement par défaut et les règles de chaque flux de paiement.

RègleRoutageStatutAction
Traitement par défautAdyen → WorldpayActive

Règles spécifiques

Configurez le traitement par défaut et les règles de chaque flux de paiement.

1 règle fictiveProcesseurs de paiement
PrioritéRègleConditionsRoutageStatut
1Commandes de valeur élevéeMontant supérieur à 100 USDAdyen → WorldpayActive

Before activating the strategy, confirm how Medium Risk transactions should be handled. Depending on your configuration, these transactions are approved by the payment gateway and held for a manual decision in the Cybersource Control Panel, sent through 3DS, or both.

6. Use REVIEW as a 3DS recommendation#

You can optionally use a Cybersource REVIEW result to trigger 3DS instead of manual review.

Configure REVIEW for 3DS

  1. In the Cybersource connection credentials, enter Yes for Use "Review" status for 3DS.
  2. In DEUNA Admin, go to Merchant > Payment settings > General Fraud Settings.
  3. Turn on Enable Manual Review.

The Enable Manual Review setting must be on even though these orders do not enter a manual-review flow.

Understand the resulting behavior

When Cybersource returns REVIEW, DEUNA runs the 3DS flow instead of starting manual review.

StageFraud statusPayment statusUpdate sent to Cybersource
Cybersource returns REVIEW; 3DS is in progressPending 3DSPendingNone
3DS completes and the gateway processes the paymentApprovedAuthorized, Processing, or ProcessedCase changes from Review to Accept
3DS completes and the gateway denies the paymentDeniedDenied by the gatewayCase changes from Review to Reject

The fraud status remains Pending 3DS and the payment status remains Pending until the 3DS flow finishes and the payment is processed.

After the gateway returns its result, DEUNA notifies Cybersource to change the case from Review to its final status. The message includes the relevant 3DS fields, such as eci, cavv, ds_transaction_id, and par_status.

In sandbox, use review@deuna.com as billing_address.email to trigger REVIEW. When Use "Review" status for 3DS is set to Yes, DEUNA runs 3DS instead of manual review.

7. Test the integration#

  1. In DEUNA Admin, confirm that Test mode is on.
  2. Confirm that the Cybersource connection and payment strategy are active.
  3. Make test transactions using these values:
ScenarioFieldValue
Automatic approvalbilling_address.emailaccept@deuna.com
Automatic rejectionbilling_address.emailreject@deuna.com
Manual reviewbilling_address.emailreview@deuna.com

The testuser.com addresses from the simulation-list setup are also accepted.

  1. Open each order in DEUNA Admin and verify the Fraud section:
ScenarioExpected result
Automatic approvalLow risk
Automatic rejectionHigh risk
Manual review when manual review is disabledMedium risk
Manual review when manual review is enabledApproved by the payment gateway and pending a decision in Cybersource
Reviewer accepts in CybersourceApproved
Reviewer rejects in CybersourceRejected
Exemple interactifUtilise des données fictives et n’effectue aucune requête API.
Production
Paiements

Commandes

Trouvez un paiement puis ouvrez son contexte opérationnel.

Acme LATAM · Production
4 commandes fictivesMis à jour à l’instant
ID de commandeCrééeClientProcesseurMontantStatut
1 oct., 14:32sofia@example.comWorldpay128,40 $USApprouvés
1 oct., 14:18diego@example.comAdyen82,00 $USEn attente
1 oct., 13:54ana@example.comStripe246,90 $USRefusé
1 oct., 13:41marco@example.comWorldpay54,25 $USApprouvés

Resolve a manual-review case

  1. Save a payment strategy that sends Medium Risk transactions to manual review.
  2. In the Cybersource Control Panel, go to Decision Manager > Case Management > Cases.
  3. Search by date range or test order ID.
  4. Select the most recent attempt for the order. Each attempt generates a new request ID under the same order ID.
  5. Accept or reject the transaction.
  6. Return to DEUNA Admin and confirm that the order status changed.

For United States and Canada billing addresses, use the postal abbreviations listed in Use state and province codes for US and Canada billing.

8. Deploy to production#

Repeat the setup in production using production credentials and values.

Configure Cybersource production

  1. Sign in to the Cybersource production Control Panel.
  2. Create a production profile.
  3. Create the rules for acceptance, rejection, and manual review.
  4. Recreate the required MDDs.
  5. Set the notification URL to https://api.deuna.io/post-transactions/cybersource.
  6. Set the device-fingerprint cs_orgId to k8vif92e.

Configure DEUNA production

  1. Turn off Test mode in DEUNA Admin.
  2. Go to Connections and connect Cybersource with your production credentials and the live environment.
  3. Ask your DEUNA Technical Account Manager to confirm that manual review and automatic operation execution are enabled for the production store.
  4. Configure the payment gateways and activate the production payment strategy.
  5. Process a Medium Risk transaction to validate manual review or the configured 3DS behavior.