Payments Developer Guide {#payments-about-guide} ================================================ This section describes how to use this guide and where to find further information. Audience and Purpose : This guide is written for application developers who want to use the `Simple Order API` to integrate payment card processing into an order management system. Implementing the `Visa Acceptance Solutions` payment services requires software development skills. You must write code that uses the API request and response fields to integrate the credit card services into your existing order management system. Conventions : These statements appear 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. Recent Revisions to This Document {#payment-doc-revisions} ========================================================== 24.09 ----- Multiple Partial Captures : Added multiple partial captures. See [Multiple Partial Captures](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-capture-multi-intro.md ""). Split Shipments Processing : Added split shipments processing. See [Split Shipments Processing](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-split-ship-intro.md ""). 24.08 ----- This revision contains only editorial changes and no technical updates. 24.07 ----- Pre-Authorizations : Added pre-authorization processing. See [Pre-Authorizations](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-pre-auth-intro.md ""). 24.06 ----- Credit Authorizations on Follow-On Credits : Added credit authorization information to [Follow-On Credits](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-refund-intro.md ""). Credit Authorizations on Stand-Alone Credits : Added credit authorization information to [Stand-Alone Credits](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-credit-intro.md ""). 24.05 ----- 24.04 ----- Relaxed Requirements for Address Data and Expiration Date : Added a new section [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-intro/payments-features-intro/payments-relax-reqs-intro.md ""). 24.03 ----- Timeout Authorization Reversals : Added an important note about the wait time before requesting a timeout authorization reversal. See [Timeout Authorization Reversals](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-timeout-auth-reversals-intro.md ""). : Added an important note about the wait time before requesting a timeout authorization reversal. See [Timeout Authorization Reversals](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-timeout-auth-reversals-intro.md ""). 24.02 ----- Follow-on Credits : The time limit for follow-on credits has been updated. See these topics: * [Credits](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-intro/payments-services-intro/payments-intro-processing-credit.md "") in the section on follow-on credits. * [Timeout Authorization Reversals](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-timeout-auth-reversals-intro.md ""). * [Follow-On Credits](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-refund-intro.md ""). * [Timeout Voids for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-timeout-void-intro.md ""). 24.01 ----- Processing Payments Using Credentials : Updated the Mastercard Standing Order Payments and the Mastercard Subscription Payments to include `TMS` information. See [Mastercard Standing Order Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mit-stand-order-intro.md "") and [Mastercard Subscription Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mc-subscription-intro.md ""). Timeout Reversals : Added timeout authorization reversals. See [Timeout Authorization Reversals](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-timeout-auth-reversals-intro.md ""). Timeout Voids : Added timeout voids. See [Timeout Voids for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-timeout-void-intro.md ""). 23.10 ----- This revision contains only editorial changes and no technical updates. 23.09 ----- This revision contains only editorial changes and no technical updates. 23.08 ----- This revision contains only editorial changes and no technical updates. 23.07 ----- Added notes about merchants in India not being permitted to store PANs. For details, see [Authorizations with Payment Network Tokens](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/pnt-auth-intro.md ""). Introduction to Payments {#payments-intro} ========================================== This introduction provides the basic information that you will need to successfully process payment transactions. It also provides an overview of the payments industry and provides workflows for each process. With `Visa Acceptance Solutions` payment services, you can process payment cards (tokenized or non-tokenized), digital payments such as Apple Pay and Google Pay, and customer ID transactions. You can process payments across the globe and across multiple channels with scalability and security. `Visa Acceptance Solutions` supports a large number of payment cards and offers a wide choice of gateways and financial institutions, all through one connection. Financial Institutions and Payment Networks {#cc-banks-overview} ================================================================ Financial institutions and payment networks enable payment services. These entities work together to complete the full payment cycle. Merchant Financial Institutions (Acquirers) {#cc-banks-acquiring} ================================================================= A merchant financial institution, also known as an *acquirer*, offers accounts to businesses that accept payment cards. Before you can accept payments, you must have a merchant account from an acquirer. Your merchant account must be configured to process card-not-present, card-present, or mail-order/telephone-order (MOTO) transactions. If excessive chargebacks or fraudulant changes occur, these actions might be taken: * You might be required to change your business processes to reduce the number chargebacks, fraud, or both. * Your acquiring institution might increase your discount rate. * Your acquiring institution might revoke your merchant account. Contact your sales representative for information about products that can help prevent fraud. Customer Financial Institutions (Issuers) {#cc-banks-issuing} ============================================================= A customer financial institution, also known as an issuer, provides payment cards to and underwrites lines of credit for their customers. The issuer provides monthly statements and collects payments. The issuer must follow the rules of the payment card companies to which they belong. Payment Networks {#cc-cards-card-companies} =========================================== Payment networks manage communications between acquiring financial institutions and issuing financial institutions. They also develop industry standards, support their brands, and establish fees for acquiring institutions. Some payment networks, such as Visa, Mastercard, and UnionPay International, are trade associations that do not issue cards. Issuers are members of these associations, and they issue cards under license from the association. Other networks, such as Discover and American Express, issue their own cards. Before you process cards from these companies, you must sign agreements with them. Payment Processors {#payments-intro-processors} =============================================== Payment processors connect with acquirers. Before you can accept payments, you must register with a payment processor. Your payment processor assigns one or more merchant IDs (MIDs) to your business. These unique codes identify your business during payment transactions. This table lists the processors and corresponding card types that are supported for payment services. Only the card types explicitly listed here are supported. | Payment Processor | Supported Card Types | Notes | |-------------------|--------------------------------------------------------------------------------|-------| | `Elavon Americas` | Visa, Mastercard, American Express, JCB, Diners Club, Discover, China UnionPay | | [Payment Processors and Supported Card Types] Card Types {#cc-cards-types-and-payment-methods} ================================================ You can process payments with these kinds of cards: * Credit cards * Debit cards Credit Cards {#payments-intro-credit-cards} =========================================== Cardholders use credit cards to borrow money from issuing banks to pay for goods and services offered by merchants that accept credit cards. Debit Cards {#payments-intro-debit-cards} ========================================= A debit card is linked to a cardholder's checking account. A merchant who accepts the debit card can deduct funds directly from the account. Transaction Types {#cc-transactions-overview} ============================================= This topic provides information about transaction types that are supported by your processor, such as card-present, card-not-present, and international transactions. Card-Not-Present Transactions {#cc-transactions-card-not-present} ================================================================= When a customer provides a card number, but the card and the customer are not physically present at the merchant's location, the purchase is known as a *card-not-present transaction*. Typical card-not-present transactions are internet and phone transactions. Card-not-present transactions pose an additional level of risk to your business because the customer's identification cannot be verified. You can reduce that risk by using features such as the Address Verification System (AVS) and Card Verification Numbers (CVNs). The AVS and CVNs provide additional protection from fraud by verifying the validity of the customer's information and notifying you when discrepancies occur. Authorizations with Card Verification Numbers {#payment-auth-cvn-intro} ======================================================================= Card verification numbers (CVNs) are a required feature for the authorization service. The CVN is printed on a payment card, and only the cardholder can access it. The CVN is used in card-not-present transactions as a verification feature. Using the CVN helps reduce the risk of fraud. CVNs are not included in payment card track data and cannot be obtained from a card swipe, tap, or dip. CVNs must not be stored after authorization. > In Europe, Visa mandates that you not include a CVN for mail-order transactions and not record a CVN on any physical format such as a mail-order form. Endpoint {#payment-auth-cvn-intro_d7e16} ---------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. CVN Locations and Terminology {#payment-auth-cvn-locations} =========================================================== For most cards, the CVN is a three-digit number printed on the back of the card, to the right of the signature field. For American Express, the CVN is a four-digit number printed on the front of the card above the card number. #### Figure: CVN Locations ![Image depicting the location of the CVN on the back of most cards and the front of an American Express card.](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/payments/images/CVV_Location.svg/jcr:content/renditions/original) Each payment card company has its own name for the CVN value: * American Express and Discover call it the *Card Identification Number* (CID). * JCB calls it the *Card Authentication Value* (CAV2). * Mastercard calls it the *Card Validation Code* (CVC2). * Visa calls it the *Card Verification Value* (CVV2). `Token Management Service` {#payments-intro-tms-overview} ========================================================= The `Token Management Service` (`TMS`) tokenizes, securely stores, and manages customer and payment data. `TMS` enables you to: * Securely store a customer's payment details and their billing and shipping addresses. * Create a network token of a customer's payment card. {#payments-intro-tms-overview_ul_4} `TMS` simplifies your PCI DSS compliance. `TMS` passes back to you tokens that represent this data. You then store these tokens in your environment and databases instead of customer payment details. **`TMS` Token Types** * Customer --- Stores the buyer's email address and the merchant's account ID for that buyer plus any other custom fields. * Shipping Address --- Stores a shipping address for a specific customer. * Instrument Identifier --- Stores either a payment card number or a bank account number and routing number This resource creates either: * An Instrument Identifier token using details of a payment card or an ACH bank account. * A payment network token using the details of a payment card; also uses the card expiration date and billing address, which are pass-through only fields. {#payments-intro-tms-overview_ul_5} * Payment Instrument --- Stores a Payment Instrument using an Instrument Identifier token. It does not store the card number and cannot exist without an associated Instrument Identifier. It stores: * Card expiration date * Billing address {#payments-intro-tms-overview_ul_2} You can also choose to store this information yourself instead and store only the card number or bank account and routing number in an Instrument Identifier object. * Customer Payment Instrument --- Creates and stores a payment instrument for a specific customer ID and an Instrument Identifier token. **`TMS` Features** * Create, retrieve, update, and delete tokens. * Set a default payment instrument and shipping address for a customer. * Process follow-on payment transactions with token IDs. * Create and update tokens through bundled payment transactions. Due to mandates from the Reserve Bank of India, Indian merchants cannot store personal account numbers (PAN). Use network tokens instead. For more information on network tokens, see the Network Tokenization section of the [` Token Management Service ` Guide.](https://developer.visaacceptance.com/docs/vas/en-us/tms/developer/ctv/rest/tms/tms-overview.md "") Payment Services {#payment-services-intro} ========================================== Various services are used to process payments. These services enable customers to purchase goods and services. They also enable merchants to receive payments from customer accounts, to provide refunds, and to void transactions. Authorizations {#payment-processing-auth} ========================================= An authorization confirms that a payment card account holds enough funds to pay for a purchase. Authorizations can be made online or offline. Micropayment Authorizations {#payments-intro-processing-auth-micropayment} ========================================================================== Micropayments are payments for less than one unit in the transaction's currency. For `Elavon Americas`, `Visa Acceptance Solutions` supports micropayment authorizations for these payment cards: * American Express (in the US only) * Diners Club (in the US only) * Discover (in the US only) * JCB (in the US only) * Mastercard (in the US only) * Visa (in the US only) Online Authorizations {#payments-processing-auth-online} ======================================================== Online authorizations provide immediate confirmation of funds availability. The customer's financial institution also reduces the amount of credit available in the customer's account, setting aside the authorized funds for the merchant to capture at a later time. Authorizations for most payment cards are processed online. Typically, it is safe to start fulfilling the order when you receive an authorization confirmation. An online authorization confirmation and the subsequent hold on funds expire after a specific length of time. Therefore it is important to capture funds in a timely manner. The issuing bank sets the expiration time interval, but most authorizations expire within 5 to 7 days. The issuing bank does not inform `Visa Acceptance Solutions` when an authorization confirmation expires. By default, the authorization information for each transaction remains in the `Visa Acceptance Solutions` database for 180 days after the authorization date. To capture an authorization that expired with the issuing bank, you can resubmit the authorization request. Offline Authorizations {#payment-processing-auth-offline} ========================================================= Online transactions require an internet connection. In situations where the internet is not available, for example, due to an outage, merchants can continue to take credit card payments using offline transactions. An offline authorization is an authorization request for which you do not receive an immediate confirmation about the availability of funds. Offline authorizations have a higher level of risk than online transactions because they do not confirm funds availability or set aside the funds for later capture. Further, it can take up to 5 days to receive payment confirmations for offline transactions. To mitigate this risk, merchants may choose to fulfill orders only after receiving payment confirmation. Incremental Authorizations {#payment-processing-auth-incremental} ================================================================= Incremental authorizations are useful when a customer adds products and services to a purchase. After a successful initial authorization, you can request subsequent authorizations and request one capture for the initial authorization and the incremental authorizations. The incremental authorization service is not the same as the incremental authorization scenario for a merchant-initiated transaction. Scenario for the Incremental Authorization Service {#payments-processing-basic-auth-inc-scenario} ================================================================================================= This sequence is an example of how incremental authorizations work: 1. The customer reserves a hotel room for two nights at a cost of 200.00 per night. You request an authorization for 400.00. The authorization request is approved. 2. The customer orders dinner through room service the first night. You request an incremental authorization of 50.00 for the dinner. 3. The customer decides to stay an extra night. You request an incremental authorization of 200.00 for the additional night. 4. The customer uses items from the mini-bar. The cost of the mini-bar items is 50.00. You request an incremental authorization of 50.00. 5. When the customer checks out, they sign a receipt for 700.00, which is the total of all costs incurred. 6. You request a capture for 700.00. Pre-Authorizations {#payments-intro-pre-auths} ============================================== A pre-authorization enables you to authorize a payment when the final amount is unknown. It is typically used for lodging, auto rental, e-commerce, and restaurant transactions. For a pre-authorization: * The authorization amount must be greater than zero. * The authorization must be submitted for capture within 30 calendar days of its request. * When you do not capture the authorization, you must reverse it. In the U.S., Canada, Latin America, and Asia Pacific, Mastercard charges an additional fee for a pre-authorization that is not captured and not reversed. In Europe, Russia, Middle East, and Africa, Mastercard charges fees for all pre-authorizations. * Chargeback protection is in effect for 30 days after the authorization. Payment Network Token Authorizations {#payments-intro-processing-auth-pnt} ========================================================================== You can integrate authorizations with payment network tokens into your existing order management system. For an incremental authorization, you do not need to include any payment network tokenization fields in the authorization request because `Visa Acceptance Solutions` obtains the payment network tokenization information from the original authorization request. Authorization Workflow {#payments-intro-processing-auth-workflow} ================================================================= This image and description show the authorization workflow: ![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/payments/images/Authorization2.svg/jcr:content/renditions/original) 1. The customer purchases goods or services from the merchant using a payment card. 2. You send an authorization request over secure internet connection to `Visa Acceptance Solutions`. When the customer buys a digitally delivered product or service, you can request both the authorization and the capture at the same time. When the customer buys a physically fulfilled product, do not request the capture until you ship the product. 3. `Visa Acceptance Solutions` validates the order information then contacts your payment processor and requests authorization. 4. The processor sends the transaction to the payment card company, which routes it to the issuing bank for the customer's payment card. Some card companies, including Discover and American Express, act as their own issuing banks. 5. The issuing bank approves or declines the request. * If funds are available, the issuing bank reserves the amount of the authorization request and returns an authorization approval to `Visa Acceptance Solutions`. * If the issuing bank denies the request, it returns an authorization denial to `Visa Acceptance Solutions`. {#payments-intro-processing-auth-workflow_ul_smg_gg5_rbc} 6. `Visa Acceptance Solutions` runs its own tests then tells you whether the authorization succeeded. Sales {#payment-intro-processing-sales} ======================================= A sale is a bundled authorization and capture. Some processors and acquirers require a sale transaction instead of using separate authorization and capture requests. For other processors and acquirers, you can request a sale instead of a separate authorization and capture when you provide the goods or services immediately after taking an order. There are two types of sale processing: dual-message processing and single-message processing. Dual-Message Processing {#payments-intro-processing-sales-dual} =============================================================== Dual-message processing is a two-step process. The authorization is processed first. If the authorization is successful, the capture is processed immediately afterward. The response includes the authorization and the capture information. If the authorization is declined, the capture is not processed, and the response message includes only the authorization information. Partial Authorizations {#payments-intro-processing-sales-dual-partialauth} ========================================================================== All debit and prepaid card processors as well as a limited number of credit card processors support partial authorizations when dual-message processing is in place. When partial authorization is enabled, the issuing financial institution can approve a partial amount when the balance on the card is less than the requested amount. When a partial amount is authorized, the capture is not processed. The merchant can then use a second card to cover the balance, adjust the total cost, or void the transaction. Single-Message Processing {#payment-processing-sales-single} ============================================================ Single-message processing treats the authorization and capture as a single transaction. There are important differences between dual-message processing and single-message processing: * Single-message processing treats the request as a full-financial transaction, and with a successful transaction, funds are immediately transferred from the customer account to the merchant account. * Authorization and capture amounts must be the same. * Some features cannot be used with single-message processing. Authorization Reversals {#payments-intro-processing-reversal} ============================================================= The authorization reversal service releases the hold that an authorization placed on a customer's payment card funds. Each card-issuing financial institution has its own rules for deciding whether an authorization reversal succeeds or fails. When a reversal fails, contact the card-issuing financial institution to learn whether there is a different way to reverse the authorization. If your processor supports authorization reversal after void (ARAV), you can reverse an authorization after you void the associated capture. If your processor does not support ARAV, you can use the authorization reversal service only for an authorization that has not been captured and settled. An authorization reversal is a follow-on transaction that uses the request ID returned from an authorization. The main purpose of a follow-on transaction is to link two transactions. The request ID links the follow-on transaction to the original transaction. The authorization request ID is used to look up the customer's billing and account information in the `Visa Acceptance Solutions` database. You are not required to include those fields in the full authorization reversal request. The original transaction and follow-on transaction are linked in the database and in `Business Center`. You cannot perform an authorization reversal if a transaction is in a review state, which can occur if you use a fraud management service. You must reject the transaction prior to authorization reversal. For more information, see the fraud management documentation in ` Business Center `. Captures {#payment-processing-captures} ======================================= A capture is a follow-on transaction to an authorization. It is used to transfer the authorized funds from the customer's account to the merchant account. To link the authorization transaction to the capture transaction, you include a request ID in your capture request. This request ID is returned to you in the authorization response. Captures are typically not performed in real time. They are placed in a batch file and sent to the processor, and the processor settles all of the captures at one time. In most cases, these batch files are sent and processed outside of the merchant's business hours. It usually takes 2 to 4 days for the acquiring financial institution to deposit the funds into the merchant account. When fulfilling only part of a customer's order, do not capture the full amount of the authorization. Capture only the cost of the delivered items. When you deliver the remaining items, request a new authorization, and then capture the new authorization. It is not possible to perform a capture if a transaction is in a review state, which can occur if you use a fraud management service. You must accept the transaction prior to capture. For more information, see the fraud management documentation in ` Business Center `. Capture Workflow {#payment-processing-captures-workflow} ======================================================== The capture workflow begins when you send a request for a capture. 1. The merchant sends a request for a capture to `Visa Acceptance Solutions`. 2. For online captures, `Visa Acceptance Solutions` validates the order information then sends an online capture to the payment processor. For offline captures, `Visa Acceptance Solutions` stores the capture request in a batch file and sends the batch file to the payment processor after midnight. 3. The processor validates the request and forwards it to the issuing bank. 4. The issuing bank transfers funds to the acquiring bank. Credits {#payments-intro-processing-credit} =========================================== Credits are payment refunds from a merchant to the cardholder after a cardholder pays for a product or service and that payment is captured by the merchant. When a credit request is successful, the issuer transfers funds from the merchant bank (acquirer) account to the customer's account. It typically takes 2 to 4 days for the acquirer to transfer funds from your merchant account. You should carefully control access to the credit service. Do not request this service directly from your customer interface. Instead, incorporate this service as part of your customer service process. This process reduces the potential for fraudulent transactions. There are two basic types of credits: follow-on credits and stand-alone credits. Follow-On Credits ----------------- Follow-on credits, also known as *refunds*, use the capture request ID to link the refund to a specific transaction. This request ID is returned during the capture request (also known as a *settlement*) and is used in all subsequent refunds associated with the original capture. The request ID links the transaction to the customer's billing and account information, so you are not required to include those fields in the credit request. However, when you combine a request for a refund with a request for another service, such as the tax calculation service, you must provide the customer's billing and account information. Unless otherwise specified, refunds must be requested within 180 days of a settlement. You can request multiple refunds against a single capture. To perform multiple refunds, use the same request ID in each request. Stand-Alone Credits ------------------- Stand-alone credits are not tied to an original transaction. Stand-alone credits do not have a time restriction, and they can be used to issue refunds more than 180 days after a transaction settlement. Credit Workflow {#payments-intro-processing-credit-workflow} ============================================================ The credit workflow begins when you send a request for a credit. A credit does not happen in real time. All of the credit requests for a day are typically placed in a file and sent to the processor as a single *batch* transaction. In most cases, the batch transaction is settled overnight. 1. The merchant sends a request for a credit to `Visa Acceptance Solutions`. 2. For online credits, `Visa Acceptance Solutions` validates the order information then sends an online credit to the payment processor. For offline credits, `Visa Acceptance Solutions` stores the credit request in a batch file and sends the batch file to the payment processor after midnight. 3. The processor validates the request and forwards it to the acquiring bank. 4. The acquiring bank transfers funds to the issuing bank. Voids {#payments-intro-processing-void} ======================================= A void cancels a capture or credit request that was submitted but not yet processed by the processor. Capture and credit requests are usually submitted once a day. A void request is declined when the capture or credit request has already been sent to the processor. After a void is processed, you cannot credit or capture the funds. You must perform a new transaction to capture or credit the funds. Further, when you void a capture, a hold remains on the authorized funds. If you are not going to re-capture the authorization, you should request an authorization reversal to release the hold on the unused funds. A void uses the capture or credit request ID to link the transactions. The authorization request ID is used to look up the customer's billing and account information, so there is no need to include those fields in the void request. You cannot perform a follow-on credit against a capture that has been voided. Payment Features {#payments-features-intro} =========================================== You can apply features to different payment services to enhance the customer payment processing experience. This section includes an overview of these features: * [Debit and Prepaid Card Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-intro/payments-features-intro/payments-debit-prepaid-intro.md "") * [Payer Authentication](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-intro/payments-features-intro/payments-processing-pa-intro.md "") * [Processing Payments Using Credentials](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro.md "") * [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-intro/payments-features-intro/payments-relax-reqs-intro.md "") Debit and Prepaid Card Payments {#payments-debit-prepaid-intro} =============================================================== Debit cards are linked to a cardholder's checking account. A merchant who accepts the debit card can deduct funds directly from the linked cardholder's account. You can process debit cards using these services: * Credit card services * PIN debit services * Partial authorizations, which are a special feature available for debit cards * Balance inquiries, which are a special feature available for debit cards Related Information ------------------- * See [Standard Payment Processing](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro.md "") for information that shows you how to use credit card services. * See [Debit and Prepaid Card Processing](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-debit-prepaid-process-intro.md "") for information that shows you how to process authorizations that use a debit or prepaid card. Payer Authentication {#payment-processing-pa-intro} =================================================== Payer authentication is run before a transaction is submitted for authorization. Most of the time payer authentication is bundled with authorization so that after payer authentication happens, the transaction is automatically submitted for authorization. Payer authentication and authorization can be configured to occur as separate operations. This section shows you how to run payer authentication as a separate process and pass the payer authentication data when seeking authorization for a transaction. Payer authentication consists of a two-step verification process that adds an extra layer of fraud protection during the payment process. During transactions, the transaction device, location, past purchasing habits, and other factors are analyzed for indications of fraud. This process collects customer data during the transaction from at least two of these three categories: * **Something you have**: A payment card or a payment card number * **Something you know**: A password or pin * **Something you are**: Facial recognition or fingerprint Each of these payment card companies has its own payer authentication product: * **Discover**: ProtectBuy * **JCB**: J/Secure * **Mastercard**: Identity Check * **Visa**: Visa Secure Payer authentication can be used to satisfy the Strong Customer Authentication (SCA) requirement of the Payment Services Directive (PSD2). SCA applies to the European Economic Area (EEA) and the United Kingdom. SCA requires banks to perform additional checks when customers make payments to confirm their identity. Related Information {#payment-processing-pa-intro_section_rb2_vbs_5xb} ---------------------------------------------------------------------- * See [Payer Authentication Processing](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-pa-process-intro.md "") for information about how to process payments with payer authentication. {#payment-processing-pa-intro_ul_r3s_vbs_5xb} Relaxed Requirements for Address Data and Expiration Date in Payment Transactions {#payments-relax-reqs-intro} ============================================================================================================== With relaxed requirements for address data and the expiration date, not all standard payment request fields are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. Related Information ------------------- * See [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md "") for information about how to process payments with relaxed requirements for address data and expiration date. Introduction to Credentialed Transactions {#credentials-intro} ============================================================== Credentialed transactions are transactions that involve either storing a customer's payment credentials for future transactions or using a customer's already stored payment credentials. When processing a credentialed transaction, you must indicate the type of credentialed transaction and the reason for the transaction. Credentialed transactions are also known as *credential-on-file* (COF) transactions. There are several types of credentialed transactions: * **Customer-Initiated Transactions (CITs):** Any transaction a customer is actively participating in such as making a card-present payment, completing an online checkout, or by using a stored credential. CIT transactions can store of the customer's credentials in your system for future CITs or merchant-initiated transactions. * **Merchant-Initiated Transactions (MITs):** Any transaction a merchant initiates without the customer's participation such as an industry practice transaction or a standing instruction transaction. * **Industry Practice Transactions:** MITs that are performed as subsequent transactions to a CIT because the initial transaction could not be completed in one transaction. Not every industry practice transaction involves a stored credential. If a stored credential is used only for one transaction, that transaction is not considered a credentialed transaction. * **Standing Instruction Transactions:** MITs that are performed to follow agreed-upon instructions from the customer for the provision of goods and services. Supported Services ------------------ These are the supported merchant-initiated services: * Delayed Authorization * Mastercard Standing Order Transactions * Mastercard Subscription Transactions * No-Show Transactions * Reauthorization * Recurring Transactions * Resubmission * Unscheduled Credentials-on-File Transactions The service determines the reason for the credentialed transaction. Standard Payment Processing {#payment-processing-basic-intro} ============================================================= This section shows you how to process various authorization, capture, credit, and sales transactions. Basic Authorizations {#payments-processing-basic-auth-intro} ============================================================ This section provides the information you need in order to process a basic authorization. Endpoint {#payments-processing-basic-auth-intro_d7e16} ------------------------------------------------------ Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Declined Authorizations {#payments-intro-processing-auth-decline} ================================================================= If an authorization is declined, you can use response categories to help you decide whether to retry or block a declined transaction. These response fields provide additional information: * ccAuthReply_paymentInsightsInformation_responseInsightsCategory * ccAuthReply_paymentInsightsInformation_responseInsightsCategoryCode These fields are available starting in the XML schema version 1.193. Category codes have possible values (such as `01`) each of which corresponds to a category that contains a description. You cannot retry this category code and category: * `01 ISSUER_WILL_NEVER_APPROVE` {#payments-intro-processing-auth-decline_ul_wxl_1yx_f5b}For these values, you can retry the transaction a maximum of 15 times over a period of 30 days: * `02 ISSUER_CANNOT_APPROVE_AT_THIS_TIME` * `03 ISSUER_CANNOT_APPROVE_WITH_THESE_DETAILS`: Data quality issue. Revalidate data prior to retrying the transaction. * `04 GENERIC_ERROR` * `97 PAYMENT_INSIGHTS_INTERNAL_ERROR` * `98 OTHERS` * `99 PAYMENT_INSIGHTS_RESPONSE_CATEGORY_MATCH_NOT_FOUND` {#payments-intro-processing-auth-decline_ul_zf4_4yx_f5b} Required Fields for Processing a Basic Authorization {#payments-processing-basic-auth-required} =============================================================================================== Use these required fields for processing a basic authorization. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing a Basic Authorization {#payments-processing-basic-auth-ex-so} ============================================================================================== Request ```keyword billTo_city=Ann Arbor billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_postalCode=48104-2201 billTo_state=MI billTo_street1=201 S. Division St. card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true merchant_id=npr_paymentech merchant_referenceCode=TC42703-1 purchaseTotals_currency=usd purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` requestID=6629977932421985593067 decision=ACCEPT reasonCode=100 merchantReferenceCode=TC42703-1 purchaseTotals_currency=usd ccAuthService_reconciliationID=57953165A7YFPS77 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-09-12T154953Z ccAuthReply_paymentNetworkTransactionID=123456789619999 ``` Response to a Declined Request ``` requestID=6629977932421985593067 merchantReferenceCode=Merchant_REF decision=REJECT ccAuthReply_avsCode=Y ccAuthReply_avsCodeRaw=Y ccAuthReply_paymentNetworkTransactionID=111222 ccAuthReply_transactionID=111222 ccAuthReply_paymentInsightsInformation_responseInsightsCategory= ISSUER_CANNOT_APPROVE_WITH_THESE_DETAILS ccAuthReply_paymentInsightsInformation_responseInsightsCategoryCode=03 ccAuthReply_processorResponse=183 ccAuthReply_reasonCode=233 ``` Authorizations with Line Items {#payment-processing-basic-auth-lineitem-intro} ============================================================================== This section shows you how to process an authorization with line items. The main difference between a basic authorization and an authorization that includes line items is that the purchaseTotals_grandTotalAmount field, which is included in a basic authorization, is substituted with one or more line items that are included in the item_#_ fields, starting with the item_0_ fields. Fields Specific to this Use Case -------------------------------- These fields are required for each line item that you use: item_#_unitPrice : item_#_quantity : item_#_productCode : item_#_productSKU : Optional when item_#_productCode is set to `default`, `shipping_only`, `handling_only`, or `shipping_and_handling` item_#_productName : Optional when item_#_productCode is set to `default`, `shipping_only`, `handling_only`, or `shipping_and_handling` {#payment-processing-basic-auth-lineitem-intro_dl_ht4_hlx_rxb} At a minimum, you must include the item_#_unitPrice field in order to include a line item in an authorization. When this field is the only field included in the authorization, the system sets: * item_#_productCode: `default` * item_#_quantity: `1` For example, these three line items are valid. ``` item_0_unitPrice=10.00 item_1_unitPrice=5.99 item_1_quantity=3 item_1_productCode=shipping_only item_2_unitPrice=29.99 item_2_quantity=3 item_2_productCode=electronic_good item_2_productSKU=12384569 item_2_productName=receiver ``` Endpoint {#payment-processing-basic-auth-lineitem-intro_d7e16} -------------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Optional Line Item Fields {#payment-processing-basic-auth-lineitem-inst-ops-so} =============================================================================== These fields can be used to provide more line item information. For more information on each field, see the field reference guide: * item_#_alternativeTaxID * item_#_buyerRegistration * item_#_commodityCode * item_#_DiscountAmount * item_#_discountIndicator * item_#_discountRate * item_#_nationalTax * item_#_orderAcceptanceCity * item_#_orderAcceptanceCountry * item_#_orderAcceptancePostalCode * item_#_orderAcceptanceState * item_#_orderOriginCity * item_#_orderOriginCountry * item_#_orderOriginPostalCode * item_#_orderOriginState * item_#_otherTax_#_passengerFirstName * item_#_otherTax_#_passengerLastName * item_#_productCode * item_#_productDescription * item_#_productName * item_#_productSKU * item_#_quantity * item_#_shippingDestinationType * item_#_taxAmount * item_#_taxRate * item_#_taxTypeApplied * item_#_taxTypeCode * item_#_totalAmount * item_#_unitPrice Required Fields for Processing an Authorization with Line Items {#payments-processing-basic-auth-lineitem-required} =================================================================================================================== Use these required fields for processing an authorization that includes line items. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : : Required when billTo_personalID is included in the request. purchaseTotals_currency purchaseTotals_grandTotalAmount : Either purchaseTotals_grandTotalAmount or item_#_unitPrice must be included in the request. Simple Order Example: Processing an Authorization with Line Items {#payements-processing-basic-auth-lineitem-ex-so} =================================================================================================================== Request ```keyword billTo_city=Palo Alto billTo_country=US billTo_email=null@vas.com billTo_firstname=Julia billTo_lastname=Fernandez billTo_postalCode=94053 billTo_state=CA billTo_street1=123 Main St. card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true dcc_dccIndicator=1 merchant_id=MID23 merchant_referenceCode=Merchant_REF purchaseTotals_currency=usd item_0_unitPrice=10.00 item_1_unitPrice=5.99 item_1_quantity=3 item_1_productCode=shipping_only item_2_unitPrice=29.99 item_2_quantity=3 item_2_productCode=electronic_good item_2_productSKU=12384569 item_2_productName=receiver purchaseTotals_exchangeRate=0.91 purchaseTotals_originalAmount=107.33 purchaseTotals_originalCurrency=eur ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=usd cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=117.94 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Authorizations with Payment Network Tokens {#pnt-std-auth-intro} ================================================================ This section shows you how to successfully process an authorization with payment network tokens. > Due to mandates from the Reserve Bank of India, Indian merchants cannot store personal account numbers (PAN). Use network tokens instead. For more information on network tokens, see [Network Tokenization](https://developer.visaacceptance.com/docs/vas/en-us/tms/developer/ctv/rest/tms/tms-net-tkn-onboard.md "") in the *` Token Management Service ` Developer Guide*. Endpoint {#pnt-std-auth-intro_d50e16} ------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Authorizations with Payment Network Tokens {#pnt-std-req-fields} ==================================================================================== Use these required fields for processing an authorization with payment network tokens. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo.email : billTo.firstName : billTo.lastName : billTo.street1 : ccAuthService.networkTokenCryptogram : paymentNetworkToken.transactionType : purchaseTotals.currency : purchaseTotals.grandTotalAmount : token.expirationMonth : token.expirationYear : Optional Fields for Authorizations with Payment Network Tokens {#pnt-std-optional-fields} ========================================================================================= billTo.city : billTo.country : billTo.email : billTo.firstName : billTo.lastName : billTo.postalCode : Required only for transactions in the U.S. and Canada. billTo.state : Required only for transactions in the U.S. and Canada. billTo.street1 : card.accountNumber : Set to the token value that you received from the token service provider. card.cardType : It is strongly recommended that you send the card type even if it is optional for your processor. Omitting the card type can cause the transaction to be processed with the wrong card type. card.expirationMonth : Set to the token expiration month that you received from the token service provider. card.expirationYear : Set to the token expiration year that you received from the token service provider. ccAuthService.cavv : For 3-D Secure in-app transactions for Visa and JCB, set to the 3-D Secure cryptogram. Otherwise, set to the network token cryptogram. ccAuthService.commerceIndicator : ccAuthService.networkTokenCryptogram : ccAuthService.run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals.currency : purchaseTotals.grandTotalAmount or item_#.unitPrice : paymentNetworkToken.transactionType : paymentNetworkToken.requestorID ucaf.authenticationData : For Mastercard requests, set this field to the Identity Check cryptogram. ucaf.collectionIndicator : For Mastercard requests, set the value to `2`. Simple Order API Example: Authorizations with Payment Network Tokens {#pnt-ex-so} ================================================================================= Request ``` <requestMessage> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>16.00</grandTotalAmount> </purchaseTotals> <card> <accountNumber>4111111111111111</accountNumber> <expirationMonth>12</expirationMonth> <expirationYear>2031</expirationYear> </card> <ccAuthService run="true"> <networkTokenCryptogram>qE5juRwDzAUFBAkEHuWW9PiBkWv=</networkTokenCryptogram> </ccAuthService> <paymentNetworkToken> <transactionType>1</transactionType> </paymentNetworkToken> </requestMessage> ``` Successful Response ``` <soap:Body> <c:replyMessage> <c:merchantReferenceCode>Postman-1684858432</c:merchantReferenceCode> <c:requestID>6848584316126969103007</c:requestID> <c:decision>ACCEPT</c:decision> <c:reasonCode>100</c:reasonCode> <c:purchaseTotals> <c:currency>USD</c:currency> </c:purchaseTotals> <c:ccAuthReply> <c:reasonCode>100</c:reasonCode> <c:amount>16.00</c:amount> <c:authorizationCode>888888</c:authorizationCode> <c:avsCode>X</c:avsCode> <c:avsCodeRaw>I1</c:avsCodeRaw> <c:authorizedDateTime>2023-05-23T16:13:51Z</c:authorizedDateTime> <c:processorResponse>100</c:processorResponse> <c:reconciliationID>78849228NHPFQCKD</c:reconciliationID> <c:paymentNetworkTransactionID>123456789619999</c:paymentNetworkTransactionID> </c:ccAuthReply> <c:card> <c:cardType>001</c:cardType> </c:card> </c:replyMessage> </soap:Body> ``` Authorizations with a Card Verification Number {#payments-auth-cvn-procedure} ============================================================================= This section shows you how to process an authorization with a Card Verification Number (CVN). CVN Results ----------- The response includes a raw response code and a mapped response code: * The raw response code is the value returned by the processor. This value is returned in the ccAuthReply_cvCodeRaw field. Use this value only for debugging purposes; do not use it to determine the card verification response. * The mapped response code is the pre-defined value that corresponds to the raw response code. This value is returned in the ccAuthReply_cvCode field. Even when the CVN does not match the expected value, the issuing bank might still authorize the transaction. You will receive a CVN decline, but you can still capture the transaction because it has been authorized by the bank. However, you must review the order to ensure that it is legitimate. Settling authorizations that fail the CVN check might have an impact on the fees charged by your bank. Contact your bank for details about how card verification management might affect your discount rate. When a CVN decline is received for the authorization in a sale request, the capture request is not processed unless you set the businessRules_ignoreCVResult field to `true`. CVN Results for American Express : A value of `1` in the ccAuthReply_cvCode field indicates that your account is not configured to use card verification. Contact customer support to have your account enabled for this feature. CVN Results for Discover : When the CVN does not match, Discover refuses the card and the request is declined. The reply message does not include the ccAuthReply_cvCode field, which indicates that the CVN failed. CVN Results for Visa and Mastercard : A CVN code of `D` or `N` causes the request to be declined with a reason code value of `230`. You can still capture the transaction, but you must review the order to ensure that it is legitimate. `Visa Acceptance Solutions`, not the issuer, assigns the CVN decline to the authorization. You can capture any authorization that has a valid authorization code from the issuer, even when the request receives a CVN decline. When the issuer does not authorize the transaction and the CVN does not match, the request is declined because the card is refused. You cannot capture the transaction. Fields Specific to this Use Case {#payments-auth-cvn-procedure_section_ylk_2qx_rxb} ----------------------------------------------------------------------------------- Include this field with a standard authorization request when processing an authorization with a CVN: * card_cvNumber {#payments-auth-cvn-procedure_ul_zlk_2qx_rxb} Endpoint {#payments-auth-cvn-procedure_d7e16} --------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing an Authorization with a Card Verification Number {#payments-auth-cvn-required} ============================================================================================================= Use these required fields for processing an authorization that includes a Card Verification Number (CVN). > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_cvNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : Optional Fields for Processing an Authorization with a Card Verification Number {#payments-auth-cvn-optional} ============================================================================================================= You can use these optional fields to include additional information when processing an authorization with a card verification number. businessRules_ignoreCVResult : card_cvIndicator : Simple Order Example: Processing an Authorization with a Card Verification Number {#payements-auth-cvn-ex-so} ============================================================================================================= Request ``` ccAuthService_run=true merchantID=Napa Valley Vacations merchantReferenceCode=482046C3A7E94F5 billTo_firstName=John billTo_lastName=Doe billTo_street1=1295 Charleston Rd. billTo_city=Mountain View billTo_state=CA billTo_postalCode=94043 billTo_country=US billTo_phoneNumber=650-965-6000 billTo_email=jdoe@example.com item_0_unitPrice=49.95 item_0_quantity=1 purchaseTotals_currency=USD card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 card_cvNumber=999 card_cardType=001 ``` Response to a Successful Request ``` requestID=0305782650000167905080 decision=ACCEPT reasonCode=100 merchantReferenceCode=482046C3A7E94F5 purchaseTotals_currency=USD ccAuthReply_reconciliationID=ABCDE12345FGHIJ67890 ccAuthReply_cardCategory=F^ ccAuthReply_cardGroup=0 ccAuthReply_reasonCode=100 ccAuthReply_amount=49.95 ccAuthReply_authorizationCode=123456 ccAuthReply_avsCode=Y ccAuthReply_avsCodeRaw=YYY ccAuthReply_processorResponse=A ccAuthReply_paymentNetworkTransactionID=3312345 ``` Zero Amount Authorizations {#payment-processing-basic-zero-auth-intro} ====================================================================== Authorizing a payment for a zero amount shows whether a payment card account is valid and whether the card is lost or stolen. You cannot capture a zero amount authorization. This section provides the information that you need in order to process a zero amount authorization. Processor-Specific Information ------------------------------ `Elavon Americas` : AVS and CVN are supported. : Card types: American Express, China UnionPay, Diners Club, Discover, JCB, Mastercard, Visa Endpoint {#payment-processing-basic-zero-auth-intro_d7e16} ---------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Zero Amount Authorization {#payments-processing-basic-zero-auth-required} ========================================================================================================== Use these required fields for processing a zero amount authorization. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Simple Order Example: Processing a Zero Amount Authorization {#payements-processing-basic-zero-auth-ex-so} ========================================================================================================== Request ```keyword billTo_city=Sao Paulo billTo_country=BR billTo_email=null@vas.com billTo_firstname=Julia billTo_lastname=Fernandez billTo_postalCode=01310-000 billTo_state=SP billTo_street1=R. Augusta card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true merchant_id=MID23 merchant_referenceCode=Merchant_REF purchaseTotals_currency=mxn purchaseTotals_grandTotalAmount=0 ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=0 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Pre-Authorizations {#payments-processing-pre-auth-intro} ======================================================== This section provides the information you need in order to process a pre-authorization. A pre-authorization enables you to authorize a payment when the final amount is unknown. It is typically used for lodging, auto rental, e-commerce, and restaurant transactions. For a pre-authorization: * The authorization amount must be greater than zero. * The authorization must be submitted for capture within 30 calendar days of its request. * When you do not capture the authorization, you must reverse it. In the U.S., Canada, Latin America, and Asia Pacific, Mastercard charges an additional fee for a pre-authorization that is not captured and not reversed. In Europe, Russia, Middle East, and Africa, Mastercard charges fees for all pre-authorizations. * Chargeback protection is in effect for 30 days after the authorization. Endpoint {#payments-processing-pre-auth-intro_d7e16} ---------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Pre-Authorization {#payments-processing-pre-auth-required} =========================================================================================== Use these required fields for processing a pre-authorization. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing a Pre-Authorization {#payments-processing-pre-auth-ex-so} ========================================================================================== Request ```keyword billTo_city=Ann Arbor billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_postalCode=48104-2201 billTo_state=MI billTo_street1=201 S. Division St. card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true merchant_id=npr_paymentech merchant_referenceCode=TC42703-1 purchaseTotals_currency=usd purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` requestID=6629977932421985593067 decision=ACCEPT reasonCode=100 merchantReferenceCode=TC42703-1 purchaseTotals_currency=usd ccAuthService_reconciliationID=57953165A7YFPS77 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-09-12T154953Z ccAuthReply_paymentNetworkTransactionID=123456789619999 ``` Response to a Declined Request ``` requestID=6629977932421985593067 merchantReferenceCode=Merchant_REF decision=REJECT ccAuthReply_avsCode=Y ccAuthReply_avsCodeRaw=Y ccAuthReply_paymentNetworkTransactionID=111222 ccAuthReply_transactionID=111222 ccAuthReply_paymentInsightsInformation_responseInsightsCategory= ISSUER_CANNOT_APPROVE_WITH_THESE_DETAILS ccAuthReply_paymentInsightsInformation_responseInsightsCategoryCode=03 ccAuthReply_processorResponse=183 ccAuthReply_reasonCode=233 ``` Final Authorization Indicator {#payments-final-auth-indicator} ============================================================== The purpose of this feature is to ensure that unused funds are reversed, so that customer's funds are available again when an order is not fulfilled. For an authorization with an amount greater than zero, indicate whether the authorization is a final authorization, a pre-authorization, or an undefined authorization. You can set a default authorization type in your account. To set the default authorization type in your account, contact customer support. Chargeback protection is in effect for seven days after the authorization. Supported Services ------------------ * Authorization * Incremental authorization Supported Card Types {#payments-final-auth-indicator_lcr-process-prereq} ------------------------------------------------------------------------ * Maestro (International) * Maestro (UK Domestic) * Mastercard Requirements for Final Authorizations {#payments-final-auth-indicator-final-auth} ================================================================================= For a final authorization: * The authorization amount must be greater than zero. * The authorization amount must be the final amount that the customer agrees to pay. * The authorization should not be cancelled after it is approved except when a system failure occurs. * The authorization must be submitted for capture within seven calendar days of its request. * The capture amount and currency must be the same as the authorization amount and currency. Pre-Authorizations {#payments-final-auth-indicator-preauth} =========================================================== A pre-authorization enables you to authorize a payment when the final amount is unknown. It is typically used for lodging, auto rental, e-commerce, and restaurant transactions. For a pre-authorization: * The authorization amount must be greater than zero. * The authorization must be submitted for capture within 30 calendar days of its request. * When you do not capture the authorization, you must reverse it. In the U.S., Canada, Latin America, and Asia Pacific, Mastercard charges an additional fee for a pre-authorization that is not captured and not reversed. In Europe, Russia, Middle East, and Africa, Mastercard charges fees for all pre-authorizations. * Chargeback protection is in effect for 30 days after the authorization. Unmarked Authorizations {#payments-final-auth-indicator-unmarked-auth} ====================================================================== An authorization is unmarked when the default authorization type is not set in your account and you do not include the authIndicator field in the authorization request. To set the default authorization type in your account, contact customer support. Unmarked authorizations are supported only in the US, Canada, Latin America, and Asia Pacific. They are not supported in Europe, Russia, Middle East, and Africa. `Visa Acceptance Solutions` does not set a mark or indicator for the type of authorization in the request that is sent to the processor. **`Elavon Americas`:** Supported for Mastercard only. Your acquirer processes an unmarked authorization as a final authorization, a preauthorization, or an undefined authorization. Contact your acquirer to learn how they process unmarked authorizations. Requirements for Unmarked Authorizations {#payments-final-auth-indicator-unmarked-auth2} ======================================================================================== For an unmarked authorization: * The authorization amount must be greater than zero. * The authorization amount can be different from the final transaction amount. Undefined Authorizations {#payments-final-auth-undef-auth} ========================================================== An authorization is undefined when you set the default authorization type in your account to undefined and do not include the authIndicator field in the authorization request. To set the default authorization type in your account, contact customer support. Undefined authorizations are supported only in the U.S., Canada, Latin America, and Asia Pacific. They are not supported in Europe, Russia, Middle East, and Africa. Chargeback protection is in effect for seven days after the authorization. Requirements for Undefined Authorizations {#payments-final-auth-indicator-undef-auth2} ====================================================================================== For an undefined authorization: * The authorization amount must be greater than zero. * The authorization amount can be different from the final transaction amount. * The authorization should not be cancelled after it is approved except when a system failure occurs. * The authorization must be submitted for capture within seven calendar days of its request. * When you do not capture the authorization, you must reverse it; otherwise, Mastercard charges an additional fee for the transaction. Required Fields for Final Authorizations {#payments-final-auth-indicator-required} ================================================================================== Use these required fields for final authorizations and preauthorizations. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). authIndicator : Set the value to `0` for preauthorizations, or to `1` for final authorizations. Do not include this field for unmarked or undefined authorizations. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Simple Order Example: Final Authorizations {#payments-final-auth-indicator-ex-so} ================================================================================= Request ```keyword <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.{{WSDLVersion}}"> <merchantID>testrest</merchantID> <billTo> <firstName>John</firstName> <lastName>Doe</lastName> <street1>1295 Charleston Road</street1> <city>Mountain View</city> <state>CA</state> <postalCode>94043</postalCode> <country>US</country> <email>test@vas.com</email> </billTo> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>1.02</grandTotalAmount> </purchaseTotals> <card> <accountNumber>4111111111111111</accountNumber> <expirationMonth>12</expirationMonth> <expirationYear>2023</expirationYear> <cardType>001</cardType> </card> <ccAuthService run="true"/> <authIndicator>1</authIndicator> </requestMessage> ``` Response to a Successful Request ``` <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.142"> <c:merchantReferenceCode>Postman-1691009216</c:merchantReferenceCode> <c:requestID>6910092160816328603011</c:requestID> <c:decision>ACCEPT</c:decision> <c:reasonCode>100</c:reasonCode> <c:purchaseTotals> <c:currency>USD</c:currency> </c:purchaseTotals> <c:ccAuthReply> <c:reasonCode>100</c:reasonCode> <c:amount>1.02</c:amount> <c:authorizationCode>888888</c:authorizationCode> <c:avsCode>X</c:avsCode> <c:avsCodeRaw>I1</c:avsCodeRaw> <c:authorizedDateTime>2023-08-02T20:46:56Z</c:authorizedDateTime> <c:processorResponse>100</c:processorResponse> <c:reconciliationID>78194788VKQUQO9Q</c:reconciliationID> <c:paymentNetworkTransactionID>123456789619999</c:paymentNetworkTransactionID> </c:ccAuthReply> <c:card> <c:cardType>001</c:cardType> </c:card> <c:pos> <c:terminalID>111111</c:terminalID> </c:pos> </c:replyMessage> ``` Authorization Reversals {#payments-processing-basic-auth-reversal-intro} ======================================================================== This section provides the information you need in order to process an authorization reversal. Reversing an authorization releases the hold on the customer's payment card funds that the issuing bank placed when processing the authorization. Endpoint {#payments-processing-basic-auth-reversal-intro_d7e64} --------------------------------------------------------------- Set the ccAuthReversalService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing an Authorization Reversal {#payments-processing-basic-auth-reversal-required-fields} =================================================================================================================== ccAuthReversalService_authRequestID : Set this field to the request ID that was included in the authorization response message. ccAuthReversalService_run : Set the value to `true`. merchantReferenceCode : merchantTransactionIdentifier : purchaseTotals_currency : purchaseTotals_grandTotalAmount : The amount of the reversal must be the same as the authorization amount that was included in the authorization response message. Do not use the amount that was requested in the authorization request message. Simple Order Example: Processing an Authorization Reversal {#payments-processing-basic-auth-reversal-ex-so-nvp} =============================================================================================================== Request ``` ccAuthReversalService_authRequestID=6522033834410167772169 ccAuthReversalService_run=true merchantReferenceCode=482046C3A7E94F5BD1FE3C66C merchantTransactionIdentifier=Napa Valley Vacations purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=49.95 ``` Response to a Successful Request ``` requestID=1019827520348290570293 merchantReferenceCode=482046C3A7E94F5BD1FE3C66C decision=ACCEPT reasonCode=100 ccAuthReversalReply_amount=49.95 purchaseTotals_currency=USD ccAuthReversalReply_reasonCode=100 ccAuthReversalReply_reconciliationID=1094820975023470 ``` Timeout Authorization Reversals {#payments-timeout-auth-reversals-intro} ======================================================================== When you do not receive a response message after sending an authorization request, this feature enables you to reverse the authorization that you requested. Wait 60 seconds before requesting a timeout authorization reversal. Include the merchantTransactionIdentifier field in the original request for an authorization. The value of the merchant transaction ID must be unique for 180 days. When the original transaction fails, the response message for the reversal request includes these fields: * originalTransaction_amount * originalTransaction_reasonCode Requirements ------------ Unless your processor supports authorization reversal after void (ARAV), timeout authorization reversals are supported only for authorizations that have not been captured and settled. Required Fields for Processing a Timeout Authorization Reversal {#payments-timeout-auth-reversal-required-fields} ================================================================================================================= Use these required fields for processing a timeout authorization reversal. ccAuthReversalService_authRequestID : Set this field to the request ID that was included in the authorization response message. ccAuthReversalService_run : Set the value to `true`. merchantReferenceCode : merchantTransactionIdentifier : Identifier that links the reversal request to the original request. purchaseTotals_currency : purchaseTotals_grandTotalAmount : The amount of the reversal must be the same as the authorization amount that was included in the authorization response message. Do not use the amount that was requested in the authorization request message. Simple Order Example: Processing a Merchant-Initiated Authorization Reversal {#payments-timeout-auth-reversal-ex-so-nvp} ======================================================================================================================== Request ``` ccAuthReversalService_authRequestID=6522033834410167772169 ccAuthReversalService_run=true merchantReferenceCode=482046C3A7E94F5BD1FE3C66C merchantTransactionIdentifier=987654321 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=49.95 ``` Response to a Successful Request ``` requestID=1019827520348290570293 merchantReferenceCode=482046C3A7E94F5BD1FE3C66C decision=ACCEPT reasonCode=100 ccAuthReversalReply_amount=49.95 purchaseTotals_currency=USD ccAuthReversalReply_reasonCode=100 ccAuthReversalReply_reconciliationID=1094820975023470 ``` Sales {#payments-processing-basic-sale-intro} ============================================= This section provides the information you need in order to process a sale transactions. A sale combines an authorization and a capture into a single transaction. Endpoint {#payments-processing-basic-sale-intro_d7e161} ------------------------------------------------------- Set the ccAuthService_run field to `true`, and the ccCaptureService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Sale {#payments-processing-basic-sale-reqfields} ================================================================================= billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_cardType : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : ccAuthService_run : Set the value to `true`. ccCaptureService_run : Set the value to `true`. merchantID : purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing a Sale {#payments-processing-basic-sale-ex-so-nvp} =================================================================================== Request ``` ccAuthService_run=true ccCaptureService_run=true merchantID=Napa Valley Vacations merchantReferenceCode=482046C3A7E94F5 billTo_firstName=John billTo_lastName=Doe billTo_street1=1295 Charleston Rd. billTo_city=Mountain View billTo_state=CA billTo_postalCode=94043 billTo_country=US billTo_phoneNumber=650-965-6000 billTo_email=jdoe@example.com item_0_unitPrice=49.95 item_0_quantity=1 purchaseTotals_currency=USD card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 card_cardType=001 ``` Response to a Successful Request ``` requestID=0305782650000167905080 decision=ACCEPT reasonCode=100 merchantReferenceCode=482046C3A7E94F5 purchaseTotals_currency=USD ccAuthReply_reconciliationID=ABCDE12345FGHIJ67890 ccAuthReply_cardCategory=F^ ccAuthReply_cardGroup=0 ccAuthReply_reasonCode=100 ccAuthReply_amount=49.95 ccAuthReply_accountBalance=50.05 ccAuthReply_authorizationCode=123456 ccAuthReply_avsCode=Y ccAuthReply_avsCodeRaw=YYY ccAuthReply_processorResponse=A ccAuthReply_paymentNetworkTransactionID=3312345 ccCaptureReply_amount=49.95 ccCaptureReply_reasonCode=100 ccCaptureReply_reconciliationID=1094820975023470 ``` Captures {#payments-processing-basic-capture-intro} =================================================== This section provides the information you need in order to capture an authorized transaction. Endpoint {#payments-processing-basic-capture-intro_d7e88} --------------------------------------------------------- Set the ccCaptureService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Capturing an Authorization {#payments-processing-basic-capture-required-fields} =================================================================================================== Use these required fields for capturing an authorization. ccCaptureService_authRequestID : ccCaptureService_run : merchantID : merchantReferenceCode : Set the value to `merchant_ref_number` value used in corresponding authorization request. purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Capturing an Authorization {#payments-processing-basic-capture-ex-so-nvp} =============================================================================================== Request ``` ccCaptureService_authRequestID=6629978499572480812782 ccCaptureService_run=true merchantID=npr_paymentech merchantReferenceCode=TC42703-1 purchaseTotals_grandTotalAmount=100.00 ``` Response to a Successful Request ``` ccCaptureReply_amount=100.00 ccCaptureReply_requestDateTime=2022-09-12T173947Z decision=ACCEPT merchantReferenceCode=TC42703-1 purchaseTotals_currency=USD requestID=6630043878211258349460 ``` Multiple Partial Captures {#payments-processing-capture-multi-intro} ==================================================================== This section shows you how to process multiple partial captures for an authorization. This feature enables you to request multiple partial captures for one authorization. A multiple partial capture allows you to incrementally settle authorizations over time. Ensure that the total amount of all the captures does not exceed the authorized amount. Endpoint {#payments-processing-capture-multi-intro_d7e88} --------------------------------------------------------- Set the ccCaptureService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing Multiple Partial Captures {#payment-processing-capture-multiple-reqfields} ========================================================================================================= ccCaptureService_authRequestID : ccCaptureService_run : ccCaptureService_sequence : For the final capture request, set this field and ccCaptureService_totalCount to the same value. ccCaptureService_totalCount : When you do not know the total number of captures that you are going to request, set this field to at least one more than the ccCaptureService_sequence field until you reach the final capture. For the final capture request, set this field and ccCaptureService_sequence to the same value. merchantID : merchantReferenceCode : Set the value to `merchantReferenceCode` value used in corresponding authorization request. purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing Multiple Partial Captures {#payments-processing-multi-capture-ex-so} ===================================================================================================== Request ``` ccCaptureService_authRequestID=6744978508916643203008 ccCaptureService_run=true ccCaptureService_sequence=2 ccCaptureService_totalCount=5 merchantID=npr_paymentech merchantReferenceCode=Postman-1674497851 purchaseTotals_grandTotalAmount=1.01 purchaseTotals_currency=USD ``` Response to a Successful Request ``` merchantReferenceCode=Postman-1674497851 requestID=6630043878211258349460 decision=ACCEPT reasonCode=100 purchaseTotals_currency=USD ccCaptureReply_reasonCode=100 ccCaptureReply_requestDateTime=2023-01-23T18:17:31Z ccCaptureReply_amount=1.01 ccCaptureReply_reconciliationID=76016263ND3MGETD ``` Forced Captures {#payments-forced-captures} =========================================== This feature allows merchants to process authorizations obtained through an organization other than `Visa Acceptance Solutions`. For example, a merchant might call their processor to request a manual authorization, at which point they can request a forced capture of the authorization. A manual authorization cannot be captured for more than the original authorization amount, and the authorization expires after seven days. Supported Services ------------------ * Authorization Required Fields for Forced Captures {#payments-forced-capture-required} ======================================================================= Use these required fields for processing forced captures. authIndicator : Set the value to `0` for preauthorizations, or to `1` for final authorizations.. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Simple Order Example: Forced Captures {#payments-forced-auth-ex-so} =================================================================== Request ```keyword <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.{{WSDLVersion}}"> <merchantID>testrest</merchantID> <billTo> <firstName>John</firstName> <lastName>Doe</lastName> <street1>1295 Charleston Road</street1> <city>Mountain View</city> <state>CA</state> <postalCode>94043</postalCode> <country>US</country> <email>test@vas.com</email> </billTo> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>1.02</grandTotalAmount> </purchaseTotals> <card> <accountNumber>4111111111111111</accountNumber> <expirationMonth>12</expirationMonth> <expirationYear>2023</expirationYear> <cardType>001</cardType> </card> <ccAuthService run="true"> <authType>verbal</authType> <verbalAuthCode>ABC123</verbalAuthCode> </ccAuthService> </requestMessage> ``` Response to a Successful Request ``` <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Timestamp-576203304"> <wsu:Created>2023-08-08T16:45:33.955Z</wsu:Created> </wsu:Timestamp> </wsse:Security> </soap:Header> <soap:Body> <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.142"> <c:merchantReferenceCode>Postman-1691513134</c:merchantReferenceCode> <c:requestID>6915131335966844703009</c:requestID> <c:decision>ACCEPT</c:decision> <c:reasonCode>100</c:reasonCode> <c:purchaseTotals> <c:currency>USD</c:currency> </c:purchaseTotals> <c:ccAuthReply> <c:reasonCode>100</c:reasonCode> <c:amount>1.02</c:amount> <c:authorizationCode>ABC123</c:authorizationCode> <c:authorizedDateTime>2023-08-08T16:45:33Z</c:authorizedDateTime> </c:ccAuthReply> <c:card> <c:cardType>001</c:cardType> </c:card> <c:pos> <c:terminalID>111111</c:terminalID> </c:pos> </c:replyMessage> </soap:Body> </soap:Envelope> ``` Follow-On Credits {#payments-processing-basic-refund-intro} =========================================================== This section provides the information you need in order to process a follow-on credit, which is linked to a capture or sale. You must request a follow-on credit within 180 days of the authorization. When your account is enabled for credit authorizations, also known as purchase return authorizations, `Visa Acceptance Solutions` authenticates the card and customer during a credit request. Every credit request is automatically authorized. Credit authorization results are returned in these response fields: * ccCreditReply_authorizationCode * ccCreditReply_paymentNetworkTransactionID * ccCreditReply_processorResponse When you request a void for the credit and the credit is voided. If your account is enabled for credit authorizations, the credit authorization is also reversed. Endpoint {#payments-processing-basic-refund-intro_d7e137} --------------------------------------------------------- Set the ccCreditService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Follow-On Credit {#payments-processing-basic-refund-required-fields} ===================================================================================================== Use these required fields for processing a follow-on credit. ccCreditService_captureRequestID : ccCreditService : Set the value to `true`. For example `ccCreditService run="true"`. merchantID : merchantReferenceCode : Set to merchantReferenceCode value used in corresponding capture request. purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing a Follow-On Credit {#payments-processing-basic-refund-ex-so-nvp} ================================================================================================= Request ``` <merchantID>merchantID</merchantID> <merchantReferenceCode>merchantRefCode</merchantReferenceCode> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>1.01</grandTotalAmount> </purchaseTotals> <ccCreditService run="true"> <captureRequestID>captureRequestID</captureRequestID> </ccCreditService> ``` Response to a Successful Request ``` <c:merchantReferenceCode>Postman-1666641056</c:merchantReferenceCode> <c:requestID>6666410568976150003010</c:requestID> <c:decision>ACCEPT</c:decision> <c:reasonCode>100</c:reasonCode> <c:purchaseTotals> <c:currency>USD</c:currency> </c:purchaseTotals> <c:ccCreditReply> <c:reasonCode>100</c:reasonCode> <c:requestDateTime>2022-10-24T19:50:57Z</c:requestDateTime> <c:amount>1.01</c:amount> <c:reconciliationID>6691571329CM5P99</c:reconciliationID> <c:authorizationCode>831111</c:authorizationCode> <c:processorResponse>00</c:processorResponse> <c:paymentNetworkTransactionID>222222222222222</c:paymentNetwork> </c:ccCreditReply> ``` Stand-Alone Credits {#payments-processing-basic-credit-intro} ============================================================= This section shows you how to process a stand-alone credit, which is not linked to a capture or sale. There is no time limit for requesting a stand-alone credit. When your account is enabled for credit authorizations, also known as purchase return authorizations, `Visa Acceptance Solutions` authenticates the card and customer during a credit request. Every credit request is automatically authorized. Credit authorization results are returned in these response fields: * ccCreditReply_authorizationCode * ccCreditReply_paymentNetworkTransactionID * ccCreditReply_processorResponse When you request a void for the credit and the credit is voided. If your account is enabled for credit authorizations, the credit authorization is also reversed. Endpoint {#payments-processing-basic-credit-intro_d7e112} --------------------------------------------------------- Set the ccCreditService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Stand-Alone Credit {#payments-processing-basic-credit-required-fields} ======================================================================================================= Use these required fields for processing a stand-alone credit. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccCreditService : Set the value to `true`. For example `ccCreditService run="true"`. merchantID : merchantReferenceCode : Set to merchantReferenceCode value used in corresponding capture request. purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing a Stand-Alone Credit {#payments-processing-basic-credit-ex-so} =============================================================================================== Request ```keyword <billTo> <firstName>John</firstName> <lastName>Doe</lastName> <street1>1295 Charleston Road</street1> <city>Mountain View</city> <state>CA</state> <postalCode>94043</postalCode> <country>US</country> <email>null@vas.com</email> </billTo> <card> <accountNumber>4111111111111111</accountNumber> <expirationMonth>12</expirationMonth> <expirationYear>2023</expirationYear> </card> <merchantID>lrsebctest</merchantID> <merchantReferenceCode>Postman-1666381004</merchantReferenceCode> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>1.01</grandTotalAmount> </purchaseTotals> <ccCreditService run="true"/> ``` Response to a Successful Request ``` <c:merchantReferenceCode>Postman-1666374834</c:merchantReferenceCode> <c:requestID>6663748348516429203007</c:requestID> <c:decision>ACCEPT</c:decision> <c:reasonCode>100</c:reasonCode> <c:purchaseTotals> <c:currency>USD</c:currency> </c:purchaseTotals> <c:ccAuthReply> <c:reasonCode>100</c:reasonCode> <c:amount>1.01</c:amount> <c:authorizationCode>888888</c:authorizationCode> <c:avsCode>X</c:avsCode><c:avsCodeRaw>I1</c:avsCodeRaw> <c:authorizedDateTime>2022-10-21T17:53:54Z</c:authorizedDateTime> <c:processorResponse>100</c:processorResponse> <c:reconciliationID>66737280B9CGUCCP</c:reconciliationID> <c:paymentNetworkTransactionID>123456789619999</c:paymentNetworkTransactionID> </c:ccAuthReply> <c:card> <c:cardType>001</c:cardType> </c:card> <c:pos> <c:terminalID>111111</c:terminalID> </c:pos> ``` Voids {#payments-processing-basic-void-intro} ============================================= This section describes how to void a capture or credit that was submitted but not yet processed by the processor. Endpoint {#payments-processing-basic-void-intro_d7e191} ------------------------------------------------------- **Void a Capture** **Void a Credit** Set the VoidService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Void {#payments-processing-basic-void-required-fields} ======================================================================================= merchantID : merchantReferenceCode : voidService_voidRequestID : Set this field to the request ID that was included in the authorization response message. voidService_run : Set the value to `true`. Simple Order API Example: Processing a Void {#payments-processing-basic-void-ex-so-nvp} ======================================================================================= Request ``` merchantID=Napa Valley Vacations merchantReferenceCode=482046C3A7E94F5 voidService_run voidService_voidRequestID=6522033834410167772169 ``` Response to a Successful Request ``` requestID=0305782650000167905080 decision=ACCEPT reasonCode=100 merchantReferenceCode=482046C3A7E94F5 purchaseTotals_currency=USD ccAuthReply_reconciliationID=ABCDE12345FGHIJ67890 ccAuthReply_cardCategory=F^ ccAuthReply_cardGroup=0 ccAuthReply_reasonCode=100 ccAuthReply_amount=49.95 ccAuthReply_accountBalance=50.05 ccAuthReply_authorizationCode=123456 ccAuthReply_avsCode=Y ccAuthReply_avsCodeRaw=YYY ccAuthReply_processorResponse=A ccAuthReply_paymentNetworkTransactionID=3312345 ``` Timeout Voids for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit {#payments-timeout-void-intro} ========================================================================================================= When you do not receive a response message after requesting a capture, sale, or credit, this feature enables you to void the transaction that you requested. Include the merchantTransactionIdentifier field in the original request for a capture, sale, follow-on credit, or stand-alone credit. The value of the merchant transaction ID must be unique for 180 days. When the original transaction fails, the response message for the reversal request includes these fields: * originalTransaction_amount * originalTransaction_reasonCode Endpoint {#payments-timeout-void-intro_d7e247} ---------------------------------------------- Required Fields for Processing a Timeout Void for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit {#payments-timeout-void-required-fields} =================================================================================================================================================== merchantID : merchantReferenceCode : merchantTransactionIdentifier : Identifier that links the reversal request to the original request. voidService_voidRequestID : Set this field to the request ID that was included in the authorization response message. voidService_run : Set the value to `true`. Simple Order Example: Processing a Timeout Void for a Capture, Sale, Follow-on Credit, or Stand-Alone Credit {#payments-timeout-void-ex-so-others} ================================================================================================================================================== Request ``` merchantID=Napa Valley Vacations merchantReferenceCode=482046C3A7E94F5 voidService_run voidService_voidRequestID=6522033834410167772169 ``` Response to a Successful Request ``` requestID=0305782650000167905080 decision=ACCEPT reasonCode=100 merchantReferenceCode=482046C3A7E94F5 purchaseTotals_currency=USD ccAuthReply_reconciliationID=ABCDE12345FGHIJ67890 ccAuthReply_cardCategory=F^ ccAuthReply_cardGroup=0 ccAuthReply_reasonCode=100 ccAuthReply_amount=49.95 ccAuthReply_accountBalance=50.05 ccAuthReply_authorizationCode=123456 ccAuthReply_avsCode=Y ccAuthReply_avsCodeRaw=YYY ccAuthReply_processorResponse=A ccAuthReply_paymentNetworkTransactionID=3312345 ``` Debit and Prepaid Card Processing {#payments-debit-prepaid-process-intro} ========================================================================= This section shows you how to process authorizations that use a debit or prepaid card. Related Information ------------------- * See [Debit and Prepaid Card Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-intro/payments-features-intro/payments-debit-prepaid-intro.md "") for a description of the debit or prepaid card transactions you can process. Processing Debit and Prepaid Authorizations {#payments-debit-prepaid-auth-intro} ================================================================================ This section shows you how to process an authorization using debit and prepaid cards. Endpoint {#payments-debit-prepaid-auth-intro_d7e16} --------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing Debit and Prepaid Authorizations {#payments-processing-debit-prepaid-auth-required} ================================================================================================================== Use these required fields for processing debit and prepaid authorizations. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Optional Field for Processing Debit and Prepaid Authorizations {#concept_i1y_bnd_g5b} ===================================================================================== You can use this optional field to include additional information when processing debit and prepaid authorizations. linkToRequest : Set this field to the request ID that was returned in the response message from the original authorization request. Simple Order Example: Processing Debit and Prepaid Authorizations {#payements-debit-prepaid-auth-ex-so} ======================================================================================================= Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_postalCode=40500 billTo_state=CA billTo_street1=901 Metro Center Blvd card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2031 ccAuthService_run=true merchant_id=pa_ctv_sg101 merchantReferenceCode=rts_6595481893301034778276 purchaseTotals_currency=usd purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` additionalData=ABC ccAuthReply_amount=100.00 ccAuthReply_avsCode=Y ccAuthReply_authorizationCode=831000 ccAuthReply_processorResponse=00 ccAuthReply_authorizedDateTime=2022-08-30T165039Z ccAuthReply_avsCodeRaw=Y ccAuthReply_cavvResponseCode=2 ccAuthReply_cavvResponseCodeRaw=2 ccAuthReply_merchantAdviceCode=01 ccAuthReply_merchantAdviceCodeRaw=M001 ccAuthReply_paymentNetworkTransactionID=016153570198200 ccAuthReply_reconciliationReferenceNumber=224216876457 apAuthReply_reconciliationID=6618782389070178232890 card_cardType=001 payerAuthEnrollReply_cardTypeName=VISA purchaseTotals_currency=usd merchantReferenceCode=rts_6595481893301034778276 receiptNumber=876457 requestID=6618782389070178232890 ``` Enabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-part-auth-intro} =========================================================================================== Partial authorizations and balance responses are special features that are available for debit cards and prepaid cards. This section shows you how to enable partial authorizations for a specific transaction. You must use version 1.52 or later of the XML schema to implement partial authorizations or balance responses. Field Specific to this Use Case ------------------------------- Include this field in addition to the fields required for a standard authorization request: * Indicate that this request is a partial authorization. Set the `ccAuthService_partialAuthIndicator` to `true`. Endpoint {#payments-debit-prepaid-part-auth-intro_d7e16} -------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Enabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-part-auth-required} ================================================================================================================== Use these required fields for enabling debit and prepaid partial authorizations. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_partialAuthIndicator : Set the value to `true`. ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Optional Field for Enabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-part-auth-optional} ================================================================================================================= You can use these optional fields to include additional information when enabling debit and prepaid partial authorizations. linkToRequest : Set this field to the request ID that was returned in the response message from the original authorization request. Simple Order Example: Enabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-part-auth-ex-so} ================================================================================================================= Request ```keyword billTo_street1=201 S. Division St billTo_city=Ann Arbor billTo_country=US billTo_state=MI billTo_postalCode=48104-2201 billTo_email=test@vas.com billTo_firstname=John billTo_lastname=Deo card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=5555555555554444 ccAuthService_partialAuthIndicator=true merchant_id=pa_ctv_sg101 merchantReferenceCode=TC50171_3 purchaseTotals_currency=usd purchaseTotals_grandTotalAmount=1000.00 ``` Response to a Successful Request ``` apCaptureService_authRequestID=6618807769750178232890 apAuthReply_reconciliationID=6618807769750178232890 card_cardType=002 ccAuthReply_amount=1000.00 ccAuthReply_avsCode=Y ccAuthReply_authorizationCode=831000 ccAuthReply_authorizedDateTime=2022-08-30T173257Z ccAuthReply_avsCodeRaw=Y ccAuthReply_cavvResponseCode=2 ccAuthReply_cavvResponseCodeRaw=2 ccAuthReply_merchantAdviceCode=01 ccAuthReply_merchantAdviceCodeRaw=M001 ccAuthReply_processorResponse=00 ccAuthReply_reconciliationReferenceNumber=224217876503 ccCreditReply_paymentNetworkTransactionID=MCC9689130830 merchantReferenceCode=TC50171_3 payerAuthEnrollReply_cardTypeName=MASTERCARD purchaseTotals_currency=usd receiptNumber=876503 requestID=6618807769750178232890 ``` Disabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-disable-part-auth-intro} ==================================================================================================== This topic shows you how to successfully disable partial authorizations for specific transactions. Field Specific to this Use Case {#payments-debit-prepaid-disable-part-auth-intro_section_brd_jvn_sxb} ----------------------------------------------------------------------------------------------------- Include this field in addition to the fields required for a standard authorization request: * Indicate that this request is not a partial authorization. Set the `ccAuthService_partialAuthIndicator` to `false`. {#payments-debit-prepaid-disable-part-auth-intro_ul_crd_jvn_sxb} Endpoint {#payments-debit-prepaid-disable-part-auth-intro_d7e16} ---------------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Field for Disabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-disable-part-auth-required} ========================================================================================================================== Use these required fields for disabling debit and prepaid partial authorizations. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_partialAuthIndicator : Set the value to `false`. ccAuthService_run : Set the value to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Optional Field for Disabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-disable-part-auth-optional} ========================================================================================================================== You can use this optional field to include additional information when disabling debit and prepaid partial authorizations. linkToRequest : Set this field to the request ID that was returned in the response message from the original authorization request. Simple Order Example: Disabling Debit and Prepaid Partial Authorizations {#payments-debit-prepaid-disable-part-auth-ex-so} ========================================================================================================================== Request ```keyword billTo_street1=201 S. Division St billTo_city=Ann Arbor billTo_country=US billTo_state=MI billTo_postalCode=48104-2201 billTo_email=test@vas.com billTo_firstname=John billTo_lastname=Deo card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=5555555555554444 ccAuthService_partialAuthIndicator=false merchant_id=pa_ctv_sg101 merchantReferenceCode=TC50171_3 purchaseTotals_currency=usd purchaseTotals_grandTotalAmount=1000.00 ``` Response to a Successful Request ``` apCaptureService_authRequestID=6643889552520668668655 apAuthReply_reconciliationID=6643889552520668668655 card_cardType=002 ccAuthReply_amount=1000.00 ccAuthReply_avsCode=Y ccAuthReply_authorizationCode=831000 ccAuthReply_authorizedDateTime=2022-09-28T173257Z ccAuthReply_avsCodeRaw=Y ccAuthReply_cavvResponseCode=2 ccAuthReply_cavvResponseCodeRaw=2 ccAuthReply_merchantAdviceCode=01 ccAuthReply_merchantAdviceCodeRaw=M001 ccAuthReply_processorResponse=00 ccAuthReply_reconciliationReferenceNumber=227118876340 ccCreditReply_paymentNetworkTransactionID=MCC8605090928 merchantReferenceCode=TC50171_3 payerAuthEnrollReply_cardTypeName=MASTERCARD purchaseTotals_currency=usd receiptNumber=876340 requestID=6618807769750178232890 ``` Payer Authentication Processing {#payment-processing-pa-process-intro} ====================================================================== This section shows you how to process authorizations that use these payer authentication methods: * **American Express**: SafeKey * **JCB**: J/Secure * **Mastercard**: Identity Check * **Visa**: Visa Secure {#payment-processing-pa-process-intro_ul_dqz_xll_5xb} Providing Payer Authentication Information for Authorization {#concept_hr5_jnj_hxb} =================================================================================== The values that are returned from payer authentication must be provided when seeking authorization for the transaction. Authentication information that is not included when considering authorization may cause the transaction to be refused or downgraded and prevent the normal liability shift from occurring. The level of security in payer authentication is denoted by the two digit Electronic Commerce Indicator (ECI) that is assigned to the transaction. These digital values have text equivalents which are assigned to the e_commerce_indicator field. The America Express, Diners, Discover, UPI, and Visa card brands use 05, 06, and 07 digit values to express the authentication level for a 3-D Secure transaction. | ECI Value | Meaning | Visa | Diners | Discover | UPI | Amex | |:----------|--------------------------------------------|:---------------------|:-------------|:---------------|:-----------------------|:---------------| | `05` | Authenticated | vbv | pb | dipb | up3ds | aesk | | `06` | Attempted authentication with a cryptogram | vbv_attempted | pb_attempted | dipb_attempted | up3ds_attempted | aesk_attempted | | `07` | Internet, not authenticated | vbv_failure/internet | internet | internet | up3ds_failure/internet | internet | [Text Values for ECI Values] Mastercard and Maestro cards use 00, 01, 02, 06, and 07 digit values to indicate the authentication level of the transaction. | ECI Value | Meaning | Mastercard/Maestro | |:----------|:------------------------------------------------------------------|:-------------------| | `00` | Internet, not authenticated | spa/internet | | `01` | Attempted authentication | spa | | `02` | Authenticated | spa | | `06` | Exemption from authentication or network token without 3‑D Secure | spa | | `07` | Authenticated merchant-initiated transaction | spa | [Mastercard/Maestro Text Values for ECI Values] The payer authentication response contains other information that needs to be passed on for successful authorization. Be sure to include these fields when requesting a separate authorization: * ccAuthService_directoryServerTransactionID (Mastercard, Maestro, UPI only) * ccAuthService_eciRaw * ccAuthService_paresStatus * ccAuthService_paSpecificationVersion * payerAuthEnrollReply_ucafAuthenticationData (Mastercard/Maestro only) * payerAuthValidateReply_ucafCollectionIndicator(Mastercard/Maestro only) * ccAuthService_cavv * ccAuthService_xid American Express SafeKey {#cc-pa-amex-intro} ============================================ American Express SafeKey is the authentication service in the American Express card network that uses the 3-D Secure protocol to validate customers at checkout. When you request an authorization using a supported card type and a supported processor, you can include payer authentication data in the request. Before implementing payer authentication for American Express SafeKey, contact customer support to have your account configured for this feature. Fields Specific to the American Express SafeKey Use Case -------------------------------------------------------- These API fields are required specifically for this use case. ccAuthService_cavv : Required when payer authentication is successful. ccAuthService_commerceIndicator : Set this field to one of these values: * `aesk`: Successful authentication (3-D Secure value of `05`). * `aesk_attempted`: Authentication was attempted (3-D Secure value of `06`). * `internet`: Authentication failed or was not attempted (3-D Secure value of `07`). {#cc-pa-amex-intro_ul_onm_fn1_jxb} Endpoint {#cc-pa-amex-intro_d7e16} ---------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing an Authorization Using American Express SafeKey {#payments-processing-pa-amex-reqfields} ======================================================================================================================= These fields must be included in a request for an authorization with American SafeKey. The values for these fields are in the response from the payer authentication validate service. When you request the payer authentication validate and authorization services together, the data is automatically passed from one service to the other. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. ccAuthService_cavv : ccAuthService_commerceIndicator : Set this field to one of these values: * `aesk`: Successful authentication (3-D Secure value of `05`). * `aesk_attempted`: Authentication was attempted (3-D Secure value of `06`). * `internet`: Authentication failed or was not attempted (3-D Secure value of `07`). {#payments-processing-pa-amex-reqfields_ul_pvn_kn1_jxb} ccAuthService_eciRaw : Required when the payer authentication validation service returns a raw ECI value. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Either purchaseTotals_grandTotalAmount or item_#_unitPrice must be included in the request. Optional Field for Processing an Authorization Using American Express SafeKey {#payments-processing-pa-amex-optfields} ====================================================================================================================== This field is optional in a request for an authorization with American Express SafeKey. The value for this field is in the response from the payer authentication validate service. When you request the payer authentication validate and authorization services together, the data is automatically passed from one service to the other. ccAuthService_xid : Simple Order Example: Processing an Authorization Using American Express SafeKey {#payements-processing-pa-amex-ex-so} ====================================================================================================================== Request ```keyword billTo_city=Sao Paulo billTo_country=BR billTo_email=null@vas.com billTo_firstname=Julia billTo_lastname=Fernandez billTo_postalCode=01310-000 billTo_state=SP billTo_street1=R. Augusta card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true ccAuthService_cavv=ABCDEFabcdefABCDEFabcdef0987654321234567 ccAuthService_commerceIndicator=aesk merchant_id=MID23 merchant_referenceCode=Merchant_REF purchaseTotals_currency=mxn purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` merchantReferenceCode=Merchant_REF request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 purchaseTotals_currency=mxn ccAuthReply_cardCategory=F ccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_reasonCode=100 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` JCB J/Secure {#payments-processing-pa-jcb-intro} ================================================ JCB J/Secure is the authentication service in the JCB card network that uses the 3-D Secure protocol to validate customers at checkout. When you request an authorization using a supported card type and a supported processor, you can include payer authentication data in the request. The payer authentication services enable you to add payer authentication support to your website without running additional software on your server. Before implementing payer authentication for JCB J/Secure, contact customer support to have your account configured for this feature. Fields Specific to the JCB J/Secure Use Case -------------------------------------------- These API fields are required specifically for this use case. ccAuthService_cavv : Required when payer authentication is successful. ccAuthService_xid : Required when payer authentication is successful. ccAuthService_eciRaw : Required when the payer authentication validation service returns a raw ECI value. ccAuthService_commerceIndicator : Set this field to one of these values: * `js`: Successful authentication for a JCB card (3-D Secure value of `05`). * `js_attempted`: Authentication was attempted for a JCB card (3-D Secure value of `06`). * `js_failure`: or `internet`: Authentication failed or was not attempted for a JCB card (3-D Secure value of `07`). {#payments-processing-pa-jcb-intro_ul_kx5_plz_3xb} Endpoint {#payments-processing-pa-jcb-intro_d7e16} -------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing an Authorization Using JCB J/Secure Authentication {#payments-processing-pa-jcb-reqfields} ========================================================================================================================= Use these required fields to process an authorization using JCB J/Secure authentication. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_cavv : Required when payer authentication is successful. Otherwise, this field is optional. ccAuthService_commerceIndicator : Set this field to one of these values: * `js`: Successful authentication for a JCB card (3-D Secure value of `05`). * `js_attempted`: Authentication was attempted for a JCB card (3-D Secure value of `06`). * `js_failure`: Authentication failed or was not attempted for a JCB card (3-D Secure value of `07`). {#payments-processing-pa-jcb-reqfields_ul_a2g_5lz_3xb} ccAuthService_xid : merchant_referenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : Simple Order Example: Processing an Authorization Using JCB J/Secure Authentication {#payements-processing-pa-jcb-ex-so} ======================================================================================================================== Request ```keyword billTo_city=Sao Paulo billTo_country=BR billTo_email=null@vas.com billTo_firstname=Julia billTo_lastname=Fernandez billTo_postalCode=01310-000 billTo_state=SP billTo_street1=R. Augusta card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2026 ccAuthService_run=true ccAuthService_cavv=ABCDEFabcdefABCDEFabcdef0987654321234567 ccAuthService_commerceIndicator=js ccAuthService_xid=MID23 merchant_referenceCode=Merchant_REF purchaseTotals_currency=mxn purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` merchantReferenceCode=Merchant_REF request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 purchaseTotals_currency=mxn ccAuthReply_cardCategory=F ccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_reasonCode=100 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Mastercard Identity Check {#payments-processing-pa-mc-intro} ============================================================ Mastercard Identity Check is the authentication service in the Mastercard card network that uses the 3-D Secure protocol in online transactions to authenticate customers at checkout. Mastercard Identity Check generates a unique, 32-character transaction token, called the account authentication value (AAV) each time a Mastercard Identity Check-enabled account holder makes an online purchase. The AAV binds the account holder to a specific transaction. Mastercard Identity Check transactions use the universal cardholder authentication field (UCAF) as a standard to collect and pass AAV data. Before implementing payer authentication for Mastercard Identity Check, contact customer support to have your account configured for this feature. Fields Specific to the Mastercard Identity Check Use Case --------------------------------------------------------- These API fields are required specifically for this use case. : Set this field to the transaction ID returned by Mastercard Identity Check during the authentication process. : Set this field to the Mastercard Identity Check version returned by Mastercard Identity Check during the authentication process. ucaf_collectionIndicator : Set to the last digit of the raw ECI value returned from authentication. For example, if ECI=02, this value should be 2. : Set this field to one of these values: * `spa`: Successful authentication (3-D Secure value of `02`). * `spa`: Authentication was attempted (3-D Secure value of `01`). * `spa` or `internet`: Authentication failed or was not attempted (3-D Secure value of `00`) {#payments-processing-pa-mc-intro_ul_a2g_5lz_3xb} Endpoint {#payments-processing-pa-mc-intro_d7e16} ------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing an Authorization Using Mastercard Identity Check {#payments-processing-pa-mc-reqfields} ====================================================================================================================== Use these required fields to process an authorization using Mastercard Identity Check. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set the value to `true`. ccAuthService_cavv : ccAuthService_commerceIndicator : Set this field to one of these values: * `spa`: Successful authentication (3-D Secure value of `02`). * `spa`: Authentication was attempted (3-D Secure value of `01`). * `spa` or `internet`: Authentication failed or was not attempted (3-D Secure value of `00`). {#payments-processing-pa-mc-reqfields_ul_a2g_5lz_3xb} ccAuthService_directoryServerTransactionID : ccAuthService_paSpecificationVersion : mercahnt_id : merchant_referenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : ucaf_collectionIndicator : Set to the last digit of the raw ECI value returned from authentication. For example, if ECI=02, this value should be 2. {#payments-processing-pa-mc-reqfields_dl_pcx_hzz_3xb} Simple Order Example: Processing an Authorization Using Mastercard Identity Check {#payements-processing-pa-mc-ex-so} ===================================================================================================================== Request ```keyword billTo_city=Sao Paulo billTo_country=BR billTo_email=null@vas.com billTo_firstname=Julia billTo_lastname=Fernandez billTo_postalCode=01310-000 billTo_state=SP billTo_street1=R. Augusta card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true ccAuthService_cavv=ABCDEFabcdefABCDEFabcdef0987654321234567 ccAuthService_commerceIndicator=spa ccAuthService_paSpecificationVersion=1 merchant_id=MID23 merchant_referenceCode=Merchant_REF ucaf_collectionIndicator=1 purchaseTotals_currency=mxn purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` merchantReferenceCode=Merchant_REF request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 purchaseTotals_currency=mxn ccAuthReply_cardCategory=F ccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_reasonCode=100 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Visa Secure {#payments-processing-pa-visa-intro} ================================================ Visa Secure is the authentication service in the Visa card network that uses the 3-D Secure protocol to authenticate customers at checkout. This authentication is a two-step process. First, the cardholder is authenticated by 3-D Secure. Then, the transaction is authorized based on the 3-D Secure evaluation. This section explains how to authorize a card payment based on the 3-D Secure evaluation. Before implementing Visa Secure, contact customer support to have your account configured for this feature. Fields Specific to the Visa Secure Use Case ------------------------------------------- These API fields are required specifically for this use case. ccAuthService_commerceIndicator : Set the value to `vbv` for a successful authentication (3-D Secure value of `05`), `vbv_attempted` if authentication was attempted but did not succeed (3-D Secure value of `06`), or `vbv_failure` if authentication failed (3-D Secure value of `07`). ccAuthService_cavv : Required when payer authentication is successful. Endpoint {#payments-processing-pa-visa-intro_d7e16} --------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing an Authorization Using Visa Secure {#payments-processing-pa-visa-reqfields} ========================================================================================================== Use these required fields to process an authorization using Visa Secure. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_cavv : This field is required when payer authentication is successful. Otherwise, this field is optional. ccAuthService_commerceIndicatorv : Set the value of this field to one of these values: * `vbv`: Successful authentication (EMV 3-D Secure value of `05`). * `vbv_attempted`: Authentication was attempted (EMV 3-D Secure value of `06`). * `vbv_failure`: or `internet`: Authentication failed or was not attempted (EMV 3-D Secure value of `07`) {#payments-processing-pa-visa-reqfields_ul_kx5_plz_3xb} ccAuthService_run : Set the value of this field to `true`. ccAuthService_xid : merchant_referenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : Simple Order Example: Processing an Authorization Using Visa Secure {#payements-processing-pa-visa-ex-so} ========================================================================================================= Request ``` billTo_city=Sao Paulo billTo_country=BR billTo_email=julia@example.com billTo_firstname=Julia billTo_lastname=Fernandez billTo_postalCode=01310-000 billTo_state=SP billTo_street1=R. Augusta card_accountNumber=41111111XXXXXXXX card_expirationMonth=12 card_expirationYear=2023 ccAuthService_run=true ccAuthService_cavv=ABCDEFabcdefABCDEFabcdef0987654321234567 ccAuthService_commerceIndicator=vbv ccAuthService_xid=MID23 merchant_referenceCode=Merchant_REF purchaseTotals_currency=mxn purchaseTotals_grandTotalAmount=100 ``` Response to a Successful Request ``` merchantReferenceCode=Merchant_REF request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 purchaseTotals_currency=mxn ccAuthReply_cardCategory=F ccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_reasonCode=100 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Relaxed Requirements for Address Data and Expiration Date in Payment Transactions {#payments-relax-reqs} ======================================================================================================== With relaxed requirements for address data and the expiration date, not all standard payment request fields are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. Requirements {#payments-relax-reqs-reqs} ======================================== You must contact customer support in order to enable relaxed requirements for address data and expiration date. Services {#payments-relax-reqs-services} ======================================== Relaxed requirements for address data and expiration date are supported for these services: * Authorization * Capture * Stand-alone credit * Subscription create * Subscription update Relaxed Fields {#payments-relax-reqs-fields} ============================================ When relaxed requirements for address data and expiration date are enabled for your ` Visa Acceptance Solutions ` account, and your service request does not include one or more of the fields in the following list, you increase the risk of declined transactions and fraud depending on your location, your processor, and the cardholder's issuing bank. It is your responsibility to determine whether a field is required for the transaction you are requesting. For example, an issuing bank can decline an authorization request for a recurring transaction with a Visa Europe card if the expiration date is incorrect, invalid, or missing. If you do not provide the correct expiration date for a recurring transaction the authorization request may be declined. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : When you include this field in your request, you must also include billTo_country billTo_state : billTo_street1 : card_expirationMonth : When you include this field in your request, you must also include card_expirationYear. : This field is required for payment network token transactions and subscription creation requests. card_expirationYear : When you include this field in your request, you must also include card_expirationMonth. : This field is required for payment network token transactions and subscription creation requests. Split Shipments Processing {#payments-processing-basic-split-ship-intro} ======================================================================== Split shipments enable you to split an order into multiple shipments with multiple captures. You can use this feature when a customer orders a product that is not yet available. *Multiple partial captures* and *split shipments* are not the same feature. The processor provides the multiple partial captures feature, while `Visa Acceptance Solutions` provides the split shipment feature. Requirements for Using Split Shipments -------------------------------------- The requirements for using split shipments are you must use and contact customer support to have your account configured for this feature. Authorizing a Sale for a Product Not Yet Available {#payments-processing-basic-split-ship-one-auth-sale-intro} ============================================================================================================== When the customer purchases a product that is not yet available, you can request an authorization and a sale. First request an authorization to ensure that funds are available. After the product becomes available, ship the product and request a sale. `Visa Acceptance Solutions` then links the follow-on authorization to the first authorization, and then links to the capture request. #### Figure: Authorizing a Sale for a Product not yet Available ![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/payments/images/payments-ss-scenario-one.svg/jcr:content/renditions/original) **Step 1: Requesting an authorization** Request an authorization to ensure that funds are available before the product is available for immediate shipment. The authorization request requires no additional fields or requirements than a basic authorization. **Step 2: Processing a sale** When the product becomes available, ship the product and request a sale. The follow-on authorization requires you to submit a sale request that includes the requestID field in addition to the basic fields required for every sale request. The requestID field in an authorization request triggers the split-shipment functionality. Set the field to the value from the requestID field from the first authorization's response. **Field Specific to authorizing a sale for a product not yet available:** First Authorization Response Message: `requestID=SWVdPS5IM` Follow-on Authorization Request: `linkToRequest=SWVdPS5IM` **Step 3: `Visa Acceptance Solutions` attempts to link the follow-on authorization request to the first authorization** * If the value is valid, the follow-on authorization is linked to the original authorization in the `Business Center` and in reports. * If the value is not valid, the follow-on authorization is not linked to the original authorization in the `Business Center` and in reports. {#payments-processing-basic-split-ship-one-auth-sale-intro_ul_nvp_44z_wwb} **Step 4: `Visa Acceptance Solutions` links the capture request** * If the value for the follow-on authorization was valid, all three transactions (first authorization, follow-on authorization, capture) are linked together in the `Business Center` and in reports. * If the value for the follow-on authorization was not valid, the second authorization and capture are linked to each other in the `Business Center` and in reports, but they are not linked to the first authorization. {#payments-processing-basic-split-ship-one-auth-sale-intro_ul_sv2_q4z_wwb} Related Information {#payments-processing-basic-split-ship-one-auth-sale-intro_section_yqz_c11_xxb} --------------------------------------------------------------------------------------------------- * See [Basic Authorizations](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-auth-intro.md "") for information on how to process a basic authorization. * See [Sales](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-sale-intro.md "") for information on how to process a sale. {#payments-processing-basic-split-ship-one-auth-sale-intro_ul_rxj_d11_xxb} Processing Two Authorizations and a Capture for Multiple Products {#payments-processing-basic-split-ship-two-auth-cap-intro} ============================================================================================================================ When the customer purchases a product that is not yet available, you can request two authorizations and a capture. First request an authorization to ensure that funds are available, and then ship the available products. After the remaining products become available, request follow-on authorization to ensure funds are still available. Ship the remaining products, and request a capture. `Visa Acceptance Solutions` links the follow-on authorization to the first authorization and the capture request to the other transactions. #### Figure: Processing Two Authorizations and a Capture for Multiple Products ![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/payments/images/payments-ss-scenario-two.svg/jcr:content/renditions/original) **Step 1: Requesting an authorization** Request an authorization to ensure that funds are available for one or more of the products that are available for immediate shipment. The authorization request requires no additional fields or requirements than a basic authorization. **Step 2: Requesting a follow-on authorization** After the product becomes available, request a follow-on authorization to ensure that funds are still available. The follow-on authorization request must include the requestID field in addition to the basic fields required for every authorization request. The requestID field in an authorization request triggers the split shipment functionality. Set the field to the value from the requestID field from the first authorization's response. **Field specific to requesting a follow-on authorization request:** First Authorization Response Message: `requestID=SWVdPS5IM` Follow-on Authorization Request: `linkToRequest=SWVdPS5IM` **Step 3: `Visa Acceptance Solutions` attempts to link the follow-on authorization request to the first authorization** * If the value is valid, the follow-on authorization is linked to the original authorization in the `Business Center` and in reports. * If the value is not valid, the follow-on authorization is not linked to the original authorization in the `Business Center` and in reports. {#payments-processing-basic-split-ship-two-auth-cap-intro_ul_nvp_44z_wwb} **Step 4: Requesting a capture** You ship the product and request a capture. The capture request must include the request ID in addition to the basic fields required as any capture request. **Field Specific to Processing a Capture after a Requesting a Follow-on Authorization:** Follow-on Authorization Response Message: `requestID=sl39cmdSlkJ` Capture Request: `authRequestID=sl39cmdSlkJ` **Step 5: `Visa Acceptance Solutions` attempts to link the capture request to the other transactions** * If the authRequestID value for the capture is valid, all three transactions (first authorization, follow-on authorization, capture) are linked together in the `Business Center` and in reports. * If the authRequestID value for the capture is not valid, the follow-on authorization and capture are linked to each other in the `Business Center` and in reports, but they are not linked to the first authorization. Related Information ------------------- * See [Basic Authorizations](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-auth-intro.md "") for information on how to process a basic authorization. * See [Captures](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-capture-intro.md "") for information on how to process a capture. {#payments-processing-basic-split-ship-two-auth-cap-intro_ul_pwx_n11_xxb} Processing an Authorization and Two Captures for Multiple Products {#concept.dita_10d7a64c-c2fe-4325-92a2-ae879f72e0ab} ======================================================================================================================= When the customer orders multiple products and one is not available, you must request an authorization to ensure funds are available. You ship the products that are available and request a capture for the amount of the shipped products. When the remaining product becomes available, ship the product and request a follow-on capture for the amount of the product. `Visa Acceptance Solutions` performs a system-generated authorization for the follow-on capture request. `Visa Acceptance Solutions` then links the capture request. You receive the status of the follow-on capture request and its associated system-generated authorization. #### Figure: Processing an Authorization and Two Captures for Multiple Products ![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/payments/images/payments-ss-scenario-three.svg/jcr:content/renditions/original) **Step 1: Requesting an authorization** Request an authorization to ensure that funds are available for one or more products that are available for immediate shipment. The authorization request requires no additional fields or requirements other than a basic authorization. **Step 2: Requesting a capture** Ship the available product and request a capture while you wait for the remaining product to become available. The capture request requires only the basic fields as any capture request. **Step 3: Requesting a follow-on capture** When the remaining product becomes available, ship it and request a capture for that amount. The capture request requires only the basic fields as any capture request. **Step 4: `Visa Acceptance Solutions` performs a system-generated authorization** `Visa Acceptance Solutions` performs a system-generated authorization for the follow-on capture request and link it to the original authorization in the `Business Center` and in reports. `Visa Acceptance Solutions` processes the capture request as a split shipment request because your account is already enabled for split shipments. **Step 5: `Visa Acceptance Solutions` attempts to link the capture request to the other transactions** The capture is linked to the authorizations in the `Business Center` and in reports through the request IDs as with any capture. All four transactions (first authorization, system-generated authorization, first capture, follow-on capture) are linked together in the `Business Center` and in reports. **Step 6: `Visa Acceptance Solutions` provides the status** The status of the follow-on capture request and its associated system-generated authorization becomes available. Related Information {#concept.dita_10d7a64c-c2fe-4325-92a2-ae879f72e0ab_section_hll_s11_xxb} -------------------------------------------------------------------------------------------- * See [Basic Authorizations](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-auth-intro.md "") for information on how to process a basic authorization. * See [Captures](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-processing-basic-intro/payments-processing-basic-capture-intro.md "") for information on how to process a capture. {#concept.dita_10d7a64c-c2fe-4325-92a2-ae879f72e0ab_ul_ill_s11_xxb} Processing Payments Using Credentials {#credentials-processing-intro} ===================================================================== This section provides the information you need in order to process payments using credentials. Customer-Initiated Transactions with Credentials on File {#credentials-cit-intro} ================================================================================= A customer-initiated transaction (CIT) is a transaction initiated by the customer. There are two types of CITs: * Customer transactions during which the credentials are stored for future **customer**-initiated transactions. * Customer transactions during which the credentials are stored for future **merchant**-initiated transactions. Customers can initiate a CIT at a merchant payment terminal, through an online purchase transaction, or by making a purchase using a previously stored credential. `Business Center` ----------------- You can create a new customer-initiated transaction in the `Business Center` by going to the One-Time Payments section and requesting a new authorization. When you have entered the customer's information, you can store the customer's credentials with the customer's permission in the Payment Information section. By doing so, you can perform merchant-initiated transactions for payments that the customer has pre-approved. For more information on how to perform a MIT in the `Business Center`, see [Merchant-Initiated No-Show Transactions with PAN](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-noshow-intro/credentials-mit-noshow-intro.md ""). Storing Customer Credentials with a CIT and PAN {#credentials-cit-storing-intro} ================================================================================ Before you can perform a merchant-initiated transaction (MIT) or a customer-initiated transaction (CIT) with credentials-on-file (COF), you must store the customer's credentials for later use. Further, before you can store the user's credentials, you must get the customer's consent to store their private information. This is also known as establishing a relationship with the customer. Endpoint {#credentials-cit-storing-intro_d10e16} ------------------------------------------------ Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Storing Customer Credentials During a CIT {#credentials-cit-storing-required} ================================================================================================= Use these required fields for storing customer credentials during a customer-initiated transaction. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthFirst : Set to `true`. {#credentials-cit-storing-required_dl_v5p_mwl_bwb} Simple Order Example: Storing Customer Credentials During a CIT {#credentials-cit-storing-ex-so} ================================================================================================ Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuthFirst=True ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Using Stored Customer Credentials During a CIT {#credentials-cit-using-intro} ============================================================================= After customers store their credentials on file, they can recall these credentials to use with subsequent transactions. Endpoint {#credentials-cit-using-intro_d10e16} ---------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Retrieving Customer Credentials During a Customer-Initiated Transaction {#credentials-cit-using-required} ============================================================================================================================= Use these required fields to retrieve customer credentials during a customer-initiated transaction. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthStoredCredential : Set to `true`. {#credentials-cit-using-required_dl_kxm_lwl_bwb} Card-Specific Required Field for Retrieving Customer Credentials During a CIT {#credentials-install-mit-card-type} ================================================================================================================== Discover -------- Discover requires the authorization amount from the original transaction in addition to the above required fields. subsequentAuthOriginalAmount : Mastercard ---------- Mastercard requires a reason code in addition to the above required fields. subsequentAuthReason : Set to `9`. Simple Order Example: Retrieving Customer Credentials During a CIT {#credentials-cit-using-ex-so} ================================================================================================= Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuthStoredCredential=True ``` {#credentials-cit-using-ex-so_codeblock_bzb_nn1_45b} Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-cit-using-ex-so_codeblock_czb_nn1_45b} Delayed Transaction {#credentials-delay-intro} ============================================== Delayed charge transaction is performed to process a supplemental account charge after original services have been rendered and respective payment has been processed. This section describes how to process a merchant-initiated delayed transaction, also known as a delayed charge, using these payment types: * [Merchant-Initiated Delayed Transaction with PAN](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-delay-intro/credentials-delay-mit-pan-intro.md "") Merchant-Initiated Delayed Transaction with PAN {#credentials-delay-mit-pan-intro} ================================================================================== Delayed charge transaction is performed to process a supplemental account charge after original services have been rendered and respective payment has been processed. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover{#credentials-delay-mit-pan-intro_d9e204} {#credentials-delay-mit-pan-intro_d9e204} * Mastercard{#credentials-delay-mit-pan-intro_d9e207} {#credentials-delay-mit-pan-intro_d9e207} * Visa{#credentials-delay-mit-pan-intro_d9e210} {#credentials-delay-mit-pan-intro_d9e210} Endpoint {#credentials-delay-mit-pan-intro_d10e16} -------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Merchant-Initiated Delayed Transaction {#credentials-delay-mit-pan-req-fields} =============================================================================================================== Use these required fields to process a merchant-initiated delayed transaction. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency purchaseTotals_grandTotalAmount : subsequentAuth : Set to `true`. {#credentials-delay-mit-pan-req-fields_dl_ksr_jwl_bwb} subsequentAuthReason : Set to `2`. : Required only for Discover, Mastercard, and Visa. subsequentAuthTransactionID : * American Express: set to the transaction ID from the original transaction. * Discover: set to the transaction ID from the original transaction. * Visa: set to the last successful transaction ID. {#credentials-delay-mit-pan-req-fields_dl_qqg_nr1_45b} Card-Specific Required Field for Processing a Merchant-Initiated Transactions {#credentials-mit-common-intro-card} ================================================================================================================== Discover -------- The listed card requires an additional field: subsequentAuthOriginalAmount : Provide the original transaction amount. Simple Order Example: Processing a Merchant-Initiated Delayed Authorization Transaction {#credentials-delay-mit-pan-ex-so} ========================================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=2 ``` {#credentials-delay-mit-pan-ex-so_codeblock_nnf_fp1_45b} Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-delay-mit-pan-ex-so_codeblock_onf_fp1_45b} No-Show Transactions {#credentials-noshow-intro} ================================================ A no-show authorization occurs when a merchant charges a customer after the customer makes a reservation, and does not show up to claim the reservation. In this situation, the customer is charged an agreed upon fee for not showing up as expected. This section describes how to process a merchant-initiated no-show transaction using these payment types: * [Merchant-Initiated No-Show Transactions with PAN](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-noshow-intro/credentials-mit-noshow-intro.md "") Merchant-Initiated No-Show Transactions with PAN {#credentials-mit-noshow-intro} ================================================================================ A no-show authorization occurs when a merchant charges a customer after the customer makes a reservation, and does not show up to claim the reservation. In this situation, the customer is charged an agreed upon fee for not showing up as expected. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover{#credentials-mit-noshow-intro_d9e204} {#credentials-mit-noshow-intro_d9e204} * Mastercard{#credentials-mit-noshow-intro_d9e207} {#credentials-mit-noshow-intro_d9e207} * Visa{#credentials-mit-noshow-intro_d9e210} {#credentials-mit-noshow-intro_d9e210} Endpoint {#credentials-mit-noshow-intro_d10e16} ----------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing Merchant-Initiated No-Show Charges {#credentials-mit-noshow-required} ==================================================================================================== Use these required fields to process a merchant-initiated no-show charges transaction. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount subsequentAuthReason : Set to `4`. : Required only for Discover, Mastercard, and Visa. subsequentAuth : Set to `true`. subsequentAuthTransactionID : * American Express: set to the transaction ID from the original transaction. * Discover: set to the transaction ID from the original transaction. * Visa: set to the last successful transaction ID. {#credentials-mit-noshow-required_dl_gwq_2wl_bwb} Optional Field for Processing Merchant-Initiated No-Show Charges {#credentials-mit-noshow-optional} =================================================================================================== You can use these optional fields to include additional information when authorizing a request for an MIT no-show charge: subsequentAuthStoredCredential : If the payment information is COF information, Set to `true`. Simple Order Example: Processing Merchant-Initiated No-Show Transactions {#credentials-mit-noshow-ex-so} ======================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=4 ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Reauthorization Transaction {#credentials-reauth-intro} ======================================================= A reauthorization occurs when the completion or fulfillment of the original order or service extends beyond the authorized amount time limit. There are two common reauthorization scenarios: * Split or delayed shipments by a retailer * Extended car rentals, hotel stays, or cruise line bookings This section describes how to process a reauthorization transaction using these payment methods: * [Merchant-Initiated Reauthorization Transactions with PAN](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-reauth-intro/credentials-mit-reauth-intro.md "") Merchant-Initiated Reauthorization Transactions with PAN {#credentials-mit-reauth-intro} ======================================================================================== A reauthorization occurs when the completion or fulfillment of the original order or service extends beyond the authorized amount time limit. There are two common reauthorization scenarios: * Split or delayed shipments by a retailer * Extended car rentals, hotel stays, or cruise line bookings Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover{#credentials-mit-reauth-intro_d9e204} {#credentials-mit-reauth-intro_d9e204} * Mastercard{#credentials-mit-reauth-intro_d9e207} {#credentials-mit-reauth-intro_d9e207} * Visa{#credentials-mit-reauth-intro_d9e210} {#credentials-mit-reauth-intro_d9e210} Endpoint {#credentials-mit-reauth-intro_d10e16} ----------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing Merchant-Initiated Reauthorized Transactions {#credentials-mit-reauth-required} ============================================================================================================== Use these required fields to process a merchant-initiated reauthorization transaction. > When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see [Relaxed Requirements for Address Data and Expiration Date in Payment Transactions](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/payments-relax-reqs.md ""). billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthReason : Set to `3`. : Required only for Discover and Visa. subsequentAuth : Set to `true`. subsequentAuthTransactionID : * American Express: set to the transaction ID from the original transaction. * Discover: set to the transaction ID from the original transaction. * Visa: set to the last successful transaction ID. {#credentials-mit-reauth-required_dl_e4b_hwl_bwb} Simple Order Example: Processing a Merchant-Initiated Reauthorized Transaction {#credentials-mit-reauth-ex-so} ============================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=3 ``` {#credentials-mit-reauth-ex-so_codeblock_bfg_cp1_45b} Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-mit-reauth-ex-so_codeblock_cfg_cp1_45b} Resubmission Transaction {#credentials-resub-intro} =================================================== A resubmission transaction is used when a merchant resubmits an authorization to recover an outstanding debt from the customer. A common scenario is when a card was initially declined due to insufficient funds, but the goods or services were already delivered to the customer. This section describes how to process a resubmission transaction using these payment types: * [Merchant-Initiated Resubmission Transaction with PAN](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-resub-intro/credentials-mit-resub-intro.md "") Merchant-Initiated Resubmission Transaction with PAN {#credentials-mit-resub-intro} =================================================================================== A resubmission transaction is used when a merchant resubmits an authorization to recover an outstanding debt from the customer. A common scenario is when a card was initially declined due to insufficient funds, but the goods or services were already delivered to the customer. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover{#credentials-mit-resub-intro_d9e204} {#credentials-mit-resub-intro_d9e204} * Mastercard{#credentials-mit-resub-intro_d9e207} {#credentials-mit-resub-intro_d9e207} * Visa{#credentials-mit-resub-intro_d9e210} {#credentials-mit-resub-intro_d9e210} Endpoint {#credentials-mit-resub-intro_d10e16} ---------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Processing a Merchant-Initiated Resubmitted Transaction {#credentials-mit-resub-required} ============================================================================================================= Use these required fields to process a merchant-initiated resubmitted transaction. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthReason : Set to `1`. : Required only for Discover, Mastercard, and Visa. subsequentAuth : Set to `true`. subsequentAuthTransactionID : * American Express: set to the transaction ID from the original transaction. * Discover: set to the transaction ID from the original transaction. * Visa: set to the last successful transaction ID. {#credentials-mit-resub-required_dl_pwc_gwl_bwb} Simple Order Example: Processing a Merchant-Initiated Resubmitted Transaction {#credentials-mit-resub-ex-so} ============================================================================================================ Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=install merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthReason=1 ``` {#credentials-mit-resub-ex-so_codeblock_ujl_v41_45b} Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-mit-resub-ex-so_codeblock_vjl_v41_45b} Recurring Payments {#credentials-recur-intro} ============================================= A recurring payment is a credentials-on-file (COF) transaction in a series of payments that you bill to a customer for a fixed amount at regular intervals that do not exceed one year between transactions. The series of recurring payments is the result of an agreement between you and the customer for the purchase of goods or services that are provided at regular intervals. Recurring payments are also known as *subscriptions*. Mastercard uses standing order and subscription payments instead of recurring payments. See [Mastercard Standing Order Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mit-stand-order-intro.md "") and [Mastercard Subscription Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mc-subscription-intro.md ""). Recurring Billing Service for Recurring Payments ------------------------------------------------ Do not use this document for the Recurring Billing service. Customer-Initiated Recurring Payment with PAN {#credentials-recur-cit-pan-intro} ================================================================================ A recurring payment is a credentials-on-file (COF) transaction in a series of payments that you bill to a customer at a fixed amount, at regular intervals that do not exceed one year between transactions. The series of recurring payments is the result of an agreement between you and the customer for the purchase of goods or services that are provided at regular intervals. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover * Visa Mastercard uses standing order and subscription payments instead of recurring payments. See [Mastercard Standing Order Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mit-stand-order-intro.md "") and [Mastercard Subscription Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mc-subscription-intro.md ""). Recurring Billing Service for Recurring Payments ------------------------------------------------ > Do not use this document for the Recurring Billing service. Address Verification Service for Recurring Payments --------------------------------------------------- If your processor supports the Address Verification Service (AVS), then the AVS should verify every authorization request. `Visa Acceptance Solutions` recommends checking the AVS's results for the first recurring payment to ensure that the payment information is accurate and to reduce the risk of fraud. You must determine how to handle the AVS results for any subsequent recurring payments that are not the same as the already-verified billing address information from the first recurring payment. Endpoint {#credentials-recur-cit-pan-intro_d10e16} -------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Successful Response ------------------- You must store the *network transaction ID* from the successful response message to include in subsequent MIT authorization requests in order to associate the CIT to the MIT. The network transaction ID is the ccAuthReply_paymentNetworkTransactionID field value. Store the *network transaction ID* , which is the ccAuthReply_paymentNetworkTransactionID field value, from the successful response message. You must include the network transaction ID in subsequent MIT authorization requests in order to associate the CIT to the MIT. Required Fields for Authorizing a Customer-Initiated Recurring Payment with PAN Using Simple Order API {#credentials-recur-cit-pan-reqfields} ============================================================================================================================================= Use these required fields to request an initial customer-initiated recurring payment. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : Set to `internet`, a payer authentication value, or `MOTO`. ccAuthService_firstRecurringPayment : Set to `true`. ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthFirst : Set to `true`. subsequentAuth : Set to `false`. {#credentials-recur-cit-pan-reqfields_dl_j2j_ldt_5wb} Simple Order Example: Authorizing a Customer-Initiated Recurring Payment with a PAN {#credentials-recur-cit-pan-ex-so} ====================================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=internet merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=false subsequentAuthFirst=true ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-recur-cit-pan-ex-so_codeblock_u3n_wtw_v5b} Merchant-Initiated Recurring Payments with PAN {#credentials-recur-mit-pan-intro} ================================================================================= After the initial recurring payment (CIT), subsequent recurring payments are merchant-initiated transactions (MITs). Prerequisites ------------- The first transaction in a recurring payment is a customer-initiated transaction (CIT). Before you can perform a subsequent merchant-initiated transaction (MIT), you must store the customer's credentials for later use. Before you can store the customer's credentials, you must get their consent to store their private information. This is also known as establishing a relationship with the customer. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover * Visa Mastercard uses standing order and subscription payments instead of recurring payments. See [Mastercard Standing Order Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mit-stand-order-intro.md "") and [Mastercard Subscription Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mc-subscription-intro.md ""). Address Verification Service for Recurring Payments --------------------------------------------------- If your processor supports the Address Verification Service (AVS), then the AVS should verify every authorization request. `Visa Acceptance Solutions` recommends checking the AVS's results for the first recurring payment to ensure that the payment information is accurate and to reduce the risk of fraud. You must determine how to handle the AVS results for any subsequent recurring payments that are not the same as the already-verified billing address information from the first recurring payment. Replacing Expiration Dates -------------------------- If the customer's card-on-file is going to expire before a scheduled subsequent recurring payment, your processor may allow you to replace the expiration date with the date 12/2099. Do not replace a card's expiration date if the card is not expired. Using this replacement expiration date does not guarantee a successful authorization request. It is your responsibility to know if your processor supports this feature. Not all issuing banks support the 12/2099 expiration date and may decline the authorization request. To include this date in the authorization request, use these fields and values. card_expirationMonth : Set to `12`. card_expirationYear : Set to `99`. Endpoint {#credentials-recur-mit-pan-intro_d10e16} -------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Authorizing a Merchant-Initiated Recurring Payment {#credentials-recur-mit-pan-reqfields} ============================================================================================================= Use these required fields to authorize subsequent recurring payments. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : Set to `recurring`. ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthReason : Set to `7`. subsequentAuth : Set to `true`. subsequentAuthStoredCredential : Set to `true`. subsequentAuthTransactionID {#credentials-recur-mit-pan-reqfields_dl_n45_1wl_bwb} Card-Specific Required Fields for Authorizing Subsequent Recurring Payments {#credentials-recur-mit-card-type} ============================================================================================================== Some card companies require additional information when making authorizations with stored credentials. Discover -------- Include the authorization amount from the original transaction in this field: subsequentAuthOriginalAmount : Mastercard ---------- Mastercard supports subscription and standing order payments instead of recurring payments. See [Mastercard Subscription Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mc-subscription-intro.md "") and [Mastercard Standing Order Payments](/docs/vas/en-us/payments/developer/elavonamericas/so/payments/credentials-processsing-intro/credentials-mit-stand-order-intro.md ""). Simple Order Example: Authorizing a Merchant-Initiated Recurring Payment {#credentials-recur-mit-pan-ex-so} =========================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_commerceIndicator=recurring merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthOriginalAmount=100.00 //This field is for Discover only. subsequentAuthReason=7 subsequentAuthStoredCredential=true subsequentAuthTransactionID=23976974322 ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-recur-mit-pan-ex-so_codeblock_vjl_v41_45b} Mastercard Standing Order Payments {#credentials-mit-stand-order-intro} ======================================================================= A standing order payment is a recurring COF transaction that is a variable amount at a regular interval, such as a utility bill, not to exceed one year between transactions. The series of recurring payments is the result of an agreement between you and the customer for the purchase of goods or services that are provided at regular intervals. Mastercard Initial CIT Standing Order Payment {#credentials-mit-cit-stand-order-initial-intro} ============================================================================================== The first transaction in a standing order payment is a customer-initiated transaction (CIT). Before you can perform a subsequent merchant-initiated transaction (MIT), you must store the customer's credentials for later use. Before you can store the user's credentials, you must get the customer's consent to store their private information. This process is also known as establishing a relationship with the customer. Endpoint {#credentials-mit-cit-stand-order-initial-intro_d10e16} ---------------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Successful Response ------------------- You must store the *network transaction ID* from the successful response message to include in subsequent MIT authorization requests in order to associate the CIT to the MIT. The network transaction ID is the ccAuthReply_paymentNetworkTransactionID field value. Store the *network transaction ID* , which is the ccAuthReply_paymentNetworkTransactionID field value, from the successful response message. You must include the network transaction ID in subsequent MIT authorization requests in order to associate the CIT to the MIT. Required Fields for Authorizing Initial CIT Standing Order Payments {#credentials-mit-stand-order-initial-reqfields} ==================================================================================================================== Use these required fields to authorize initial customer-initated standing order payments. billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : Set to `internet`. ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthFirst : Set to `true`. subsequentAuthReason : Set to `8`. subsequentAuth : Set to `customer`. {#credentials-mit-stand-order-initial-reqfields_dl_z2l_zvl_bwb} Simple Order Example: Authorizing Initial CIT Standing Order Payments {#credentials-mit-stand-order-initial-ex-so} ================================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=internet merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuthFirst=True subsequentAuthReason=8 ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Mastercard Subscription Payments {#credentials-mc-subscription-intro} ===================================================================== A subscription payment is a recurring COF transaction that is processed at a fixed amount at regular intervals not to exceed one year between transactions. The series of recurring payments is the result of an agreement between you and the customer for the purchase of goods or services that are provided at regular intervals. Mastercard CIT Initial Subscription Payment {#credentials-mc-subscription-cit-pan-intro} ======================================================================================== The first transaction in a subscription payment is a customer-initiated transaction (CIT). Before you can perform a subsequent merchant-initiated transaction (MIT), you must store the customer's credentials for later use. Before you can store the user's credentials, you must get the customer's consent to store their private information. This process is also known as establishing a relationship with the customer. Endpoint {#credentials-mc-subscription-cit-pan-intro_d10e16} ------------------------------------------------------------ Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Successful Response ------------------- You must store the *network transaction ID* from the successful response message to include in subsequent MIT authorization requests in order to associate the CIT to the MIT. The network transaction ID is the ccAuthReply_paymentNetworkTransactionID field value. Store the *network transaction ID* , which is the ccAuthReply_paymentNetworkTransactionID field value, from the successful response message. You must include the network transaction ID in subsequent MIT authorization requests in order to associate the CIT to the MIT. Required Fields for Authorizing CIT Initial Subscription Payments {#credentials-mc-subscription-cit-pan-req-fields} =================================================================================================================== billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : Set to `recurring`. ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthFirst : Set to `true`. subsequentAuthReason : Set to `7`. subsequentAuth : Set to `customer`. {#credentials-mc-subscription-cit-pan-req-fields_dl_ixz_wvl_bwb} Simple Order Example: Authorizing Initial CIT Subscription Payments {#credentials-mc-subscription-cit-pan-ex-so} ================================================================================================================ Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=internet merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuthFirst=true subsequentAuthReason=7 ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Unscheduled COF Payments {#credentials-ucof-intro} ================================================== An unscheduled credentials-on-file (COF) transaction uses stored payment information for a fixed or variable amount that does not occur regularly. An account top-up is one kind of unscheduled COF. Customer-Initiated Unscheduled COF Payment with PAN {#credentials-mit-cit-ucof-initial-intro} ============================================================================================= An unscheduled credentials-on-file (COF) transaction uses stored payment information for a fixed or variable amount that does not occur regularly. An account top-up is one kind of unscheduled COF. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover{#credentials-mit-cit-ucof-initial-intro_d9e204} {#credentials-mit-cit-ucof-initial-intro_d9e204} * Mastercard{#credentials-mit-cit-ucof-initial-intro_d9e207} {#credentials-mit-cit-ucof-initial-intro_d9e207} * Visa{#credentials-mit-cit-ucof-initial-intro_d9e210} {#credentials-mit-cit-ucof-initial-intro_d9e210} Endpoint {#credentials-mit-cit-ucof-initial-intro_d10e16} --------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Successful Response ------------------- You must store the *network transaction ID* from the successful response message to include in subsequent MIT authorization requests in order to associate the CIT to the MIT. The network transaction ID is the ccAuthReply_paymentNetworkTransactionID field value. Store the *network transaction ID* , which is the ccAuthReply_paymentNetworkTransactionID field value, from the successful response message. You must include the network transaction ID in subsequent MIT authorization requests in order to associate the CIT to the MIT. Required Fields for Authorizing Initial CIT Unscheduled COF Payments {#credentials-mit-ucof-initial-reqfields} ============================================================================================================== These fields are required in a subsequent authorization request for an initial unscheduled COF payment: billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : Set to `internet`, `MOTO`, or a payer authentication value. ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthFirst : Set to `true`. subsequentAuth : Set to `false`. {#credentials-mit-ucof-initial-reqfields_dl_wwc_5vl_bwb} Simple Order Example: Authorizing Initial CIT Unscheduled COF Payments {#credentials-mit-ucof-initial-ex-so} ============================================================================================================ Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_run=true ccAuthService_commerceIndicator=internet merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=false subsequentAuthFirst=True ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` Merchant-Initiated Unscheduled COF Payments with PAN {#credentials-mit-unsched-subsequent-intro} ================================================================================================ After the initial CIT unscheduled COF payment, subsequent unscheduled COF transactions are merchant-initiated transactions (MITs). Prerequisites ------------- The first transaction in an unscheduled COF payment is a customer-initiated transaction (CIT). Before you can perform a subsequent merchant-initiated transaction (MIT), you must store the customer's credentials for later use. Before you can store the user's credentials, you must get the customer's consent to store their private information. This process is also known as establishing a relationship with the customer. Supported Card Types -------------------- These are the supported card types for processing credentialed transactions: * Discover{#credentials-mit-unsched-subsequent-intro_d9e204} {#credentials-mit-unsched-subsequent-intro_d9e204} * Mastercard{#credentials-mit-unsched-subsequent-intro_d9e207} {#credentials-mit-unsched-subsequent-intro_d9e207} * Visa{#credentials-mit-unsched-subsequent-intro_d9e210} {#credentials-mit-unsched-subsequent-intro_d9e210} Endpoint {#credentials-mit-unsched-subsequent-intro_d10e16} ----------------------------------------------------------- Set the ccAuthService_run field to `true`. Send the request to `https://ics2ws.ic3.com/commerce/1.x/transactionProcessor`. Required Fields for Authorizing Subsequent MIT Unscheduled COF Payments {#credentials-mit-unsched-reqfields} ============================================================================================================ These fields are required in a subsequent authorization request for a subsequent unscheduled COF payment: billTo_city : billTo_country : billTo_email : billTo_firstName : billTo_lastName : billTo_postalCode : billTo_state : billTo_street1 : card_accountNumber : card_expirationMonth : card_expirationYear : ccAuthService_commerceIndicator : Set to `internet`. ccAuthService_run : Set to `true`. merchantID : merchantReferenceCode : purchaseTotals_currency : purchaseTotals_grandTotalAmount : subsequentAuthReason : Set to `10`. : Required only for American Express, Discover, and Mastercard. subsequentAuthStoredCredential : Set to `true`. subsequentAuth : Set to `true`. subsequentAuthTransactionID {#credentials-mit-unsched-reqfields_dl_tsj_svl_bwb} Simple Order Example: Authorizing Subsequent MIT Unscheduled COF Payments {#credentials-mit-unsched-ex-so} ========================================================================================================== Request ```keyword billTo_city=Foster City billTo_country=US billTo_email=null@vas.com billTo_firstname=John billTo_lastname=Smith billTo_state=CA billTo_postalCode=94404 billTo_street1=201 S. Division St. card_expirationMonth=12 card_expirationYear=2031 card_accountNumber=4111111111111111 ccAuthService_commerceIndicator=internet merchantId=pa_ctv_sg101 merchantReferenceCode=33557799 purchaseTotals_currency=USD purchaseTotals_grandTotalAmount=100.00 subsequentAuth=true subsequentAuthOriginalAmount=100.00 //This field is for Discover only. subsequentAuthStoredCredential=true subsequentAuthTransactionID=23976974322 ``` Response to a Successful Request ``` additional_processor_response=e1cdcafc-cdbb-4ef7-8788-a1234e844805 request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 merchantReferenceCode=Merchant_REF purchaseTotals_currency=mxn cardCategory=FccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2022-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222 ``` {#credentials-mit-unsched-ex-so_codeblock_vjl_v41_45b}