On This Page {#jumplink-list} [Markdown](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-about-guide.md) Filter FILTER BY TAG About This Guide {#sa-about-guide} ================================== This section describes how to use this guide and where to find further information. Audience and Purpose -------------------- This guide is written for resellers and merchants who want to customize and control their own customer checkout experience, including receipt and response pages. After the customization, you will have full control to store and control customer information before sending it to `Cybersource` to process transactions, and to use `Business Center` to review and manage all of your orders. Using the `Secure Acceptance` `Checkout API` requires moderate scripting skills. You must create a security script and modify your HTML form to pass order information to `Cybersource`. Conventions ----------- These special statements are used in this document: > An *Important* statement contains information essential to successfully completing a task or learning a concept. > A *Warning* contains information or instructions, which, if not heeded, can result in a security risk, irreversible loss of data, or significant cost in time or revenue or both. Customer Support ---------------- For support information about any service, visit the Support Center: Recent Revisions to This Document {#sa-checkout-doc-revisions} ============================================================== 25.08.01 -------- Updated the required browsers. See [Required Browsers](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/home-merch/sa-required-browsers.md ""). Updated the bill_to_address_state request field maximum length to 20. See [Request Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-request-fields.md ""). Updated the bill_to_company_name request field maximum length to 60. See [Request Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-request-fields.md ""). Updated the req_bill_to_address_state response field maximum length to 20. See [Response Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-response-fields.md ""). Updated the req_bill_to_company_name response field maximum length to 60. See [Response Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-response-fields.md ""). Added these new response fields. See [Response Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-response-fields.md ""). * payment_token_instrument_identifier_id * payment_token_instrument_identifier_new * payment_token_instrument_identifier_status 25.05.01 -------- Added China UnionPay test cards. See [Testing Transactions](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-test-view-txns/sa-testing-txns.md ""). Added the auth_trans_ref_no request field. See [Request Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-request-fields.md ""). 25.01 ----- Added information about China UnionPay cards that do not have a card verification number (CVN) and expiration date. See the Important note in [Adding Card Types and Currencies](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-payment-configuration/sa-payment-method-configuration/sa-add-card-types-currencies.md "") and [Reseller: Adding Card Types and Currencies](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-portfolio-reseller-mgmt/sa-payment-method-configuration-reseller/sa-add-card-types-curr-reseller.md ""). Updated information about test cards. See [Test and View Transactions](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-test-view-txns.md ""). Updated the auth_trans_ref_no, payer_authentication_eci, and payer_authentication_enroll_e_commerce_indicators response fields. See [Response Fields](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-wm-api-fields/sa-response-fields.md ""). 24.03 ----- This revision contains only editorial changes and no technical updates. Website Requirements {#sa-web-site-requirements} ================================================ Your website must meet these requirements: * It must have a shopping cart or customer order creation software. * It must contain product pages in one of the supported scripting languages. See [Sample Transaction Process Using JSP](/docs/cybs/en-us/sa/developer/all/sa-checkout/secure-acceptance/sa-samples-scripting-languages/sa-sample-txn-process-using-jsp.md ""). * The IT infrastructure must be Public Key Infrastructure (PKI) enabled to use SSL-based form POST submissions. * The IT infrastructure must be capable of digitally signing customer data before submission to `Secure Acceptance`. VISA Platform Connect: Specifications and Conditions for Resellers/Partners {#vpc-partner-reseller-disclaimer} ============================================================================================================== The following are specifications and conditions that apply to a Reseller/Partner enabling its merchants through Cybersource for Visa Platform Connect ("VPC") processing. Failure to meet any of the specifications and conditions below is subject to the liability provisions and indemnification obligations under Reseller/Partner's contract with Visa/Cybersource. 1. Before boarding merchants for payment processing on a VPC acquirer's connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer. 2. Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer. 3. Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer. 4. Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer. DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS OR OMISSIONS BY THE Visa Platform Connect ACQUIRER IN PROCESSING TRANSACTIONS. NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND CONDITIONS IMPOSED BY THE RELEVANT Visa Platform Connect ACQUIRER. RELATED TO THIS PAGE