Reference Information

This section contains reference information that is useful when integrating with
Oracle NetSuite
.

Testing Endpoints

Follow these steps to verify the test and live endpoint URLs to be used by the integration.
  1. Go to
    Customization
    >
    Lists, Records, and Fields
    > click
    Record Types
    .
  2. Under Record Types, click
    List
    of the
    Payment API Configuration
    record type.
  3. Verify that the test and live endpoint URLs are correct. If any changes are required, confirm with the company team, and update them in the custom record.
  4. You can also check the SuiteApp version on the bottom of the
    Oracle NetSuite
    Configuration Screen. This helps easily identify the version that you currently use.
  5. To check the SuiteApp version, go to
    Cybersource
    Integration >
    SuiteApp Configuration
    . Click
    SuiteApp Configuration
    .
Reference Information

Reason Codes for
Oracle NetSuite

The following table describes the reason codes that are returned by
Oracle NetSuite
.
Reason Codes
Reason Code
Description
100
Successful transaction.
101
Decline: The request is missing one or more fields.
102
Decline: One or more fields in the request contains invalid data.
104
Decline: The
merchantReferenceCode
sent with this authorization request matches the
merchantReferenceCode
of another authorization request that you sent in the last 15 minutes.
110
Partial amount was approved.
150
Error: General system failure.
151
Error: The request was received but there was a server timeout. This error does not include timeouts between the client and the server.
152
Error: The request was received, but a service did not finish running in time.
200
Soft Decline: The authorization request was approved by the issuing bank but flagged by Cybersource because it did not pass the Address Verification Service (AVS) check.
201
Decline: The issuing bank has questions about the request. You do not receive an authorization code programmatically, but you might receive one verbally by calling the processor.
202
Decline: Expired card. You might also receive this if the expiration date you provided does not match the date the issuing bank has on file.
The
ccCreditService
does not check the expiration date; instead, it passes the request to the payment processor. If the payment processor allows issuance of credits to expired cards, Cybersource does not limit this functionality.
203
Decline: General decline of the card. No other information provided by the issuing bank.
204
Decline: Insufficient funds in the account.
205
Decline: Stolen or lost card.
207
Decline: Issuing bank unavailable.
208
Decline: Inactive card or card not authorized for card-not-present transactions.
209
Decline: Card verification number (CVN) did not match.
210
Decline: The card has reached the credit limit.
211
Decline: Invalid Card Verification Number (CVN).
220
Decline: Generic decline.
221
Decline: The customer matched an entry on the processor's negative file.
222
Decline: Customer's account is frozen.
230
Soft Decline: The authorization request was approved by the issuing bank but flagged by Cybersource because it did not pass the Card Verification Number (CVN) check.
231
Decline: Invalid account number.
232
Decline: The card type is not accepted by the payment processor.
233
Decline: General decline by the processor.
234
Decline: There is a problem with your Cybersource merchant configuration.
235
Decline: The requested amount exceeds the originally authorized amount. This can occur if you try to capture an amount larger than the original authorization amount.
236
Decline: Processor failure.
237
Decline: The authorization has already been reversed.
238
Decline: The transaction has already been settled.
239
Decline: The requested transaction amount must match the previous transaction amount.
240
Decline: The card type sent is invalid or does not correlate with the credit/debit card number.
241
Decline: The referenced request ID is invalid for all follow-on transactions.
242
Decline: The request ID is invalid. You requested a capture, but there is no corresponding, unused authorization record. This can occur if there was not a previously successful authorization request or if the previously successful authorization has already been used in another capture request.
243
Decline: The transaction has already been settled or reversed.
246
Decline: The capture or credit is not voidable because the capture or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided.
247
Decline: You requested a credit for a capture that was previously voided.
248
Decline: The boleto request was declined by your processor.
250
Error: The request was received, but there was a timeout at the payment processor.
251
Decline: The pinless debit card's use frequency or maximum amount per use has been exceeded.
254
Decline: Account is prohibited from processing stand-alone refunds.
400
Soft Decline: Fraud score exceeds threshold.
450
Apartment number missing or not found.
451
Insufficient address information.
452
House/Box number not found on street.
453
Multiple address matches were found.
454
P.O. Box identifier not found or out of range.
455
Route service identifier not found or out of range.
456
Street name not found in postal code.
457
Postal code not found in database.
458
Unable to verify or correct address.
459
Multiple address matches were found (international).
460
Address match not found (no reason given).
461
Unsupported character set.
475
The cardholder is enrolled in Payer Authentication. Please authenticate the cardholder before continuing with the transaction.
476
Encountered a Payer Authentication problem. Payer could not be authenticated.
480
The order is marked for review by Decision Manager.
481
The order has been rejected by Decision Manager.
490
Your aggregator or acquirer is not accepting transactions from you at this time.
491
Your aggregator or acquirer is not accepting this transaction.
520
Soft Decline: The authorization request was approved by the issuing bank but declined by Cybersource based on your Smart Authorization settings.
700
The customer matched the Denied Parties List.
701
Export
bill_country/ship_country
match.
702
Export email_country match.
703
Export
hostname_country/ip_country
match.
Reference Information

Export Execution Logs

You can use the Execution Logs Saved Search feature of
Oracle NetSuite
to analyze logs. Go to
Cybersource Integration
>
SuiteApp Configuration
>
Export Logs
. The Execution Logs will be downloaded.
Reference Information

Support

If you require support with the SuiteApp, contact GlobalPartnerSolutionsCS@visa.com and provide these details:
  • Steps to recreate the issue.
  • SuiteApp version. Go to
    Cybersource
    Integration>
    SuiteApp Configuration
    . Click
    SuiteApp Configuration
    . Find the version on the page footer.
  • Export and share the logs. Go to
    Cybersource
    Integration >
    SuiteApp Configuration
    >
    SuiteApp Configuration
    >
    Export Logs
    . The Execution Logs file is now downloaded in your local system. Include the date and time of occurrence of the issue while sharing the logs.
  • Business Center
    merchant ID.
  • Oracle NetSuite
    transaction ID,
    Business Center
    request ID.
  • Payment event screenshots with raw request and raw response visible.
  • Payment processing profile screenshots.
  • Invoicing configuration screenshots (if applicable).
  • Reporting set up screenshots (if applicable)
  • Summary of the issue.
Reference Information