Enter a type and click search.




Results for Magento\AuthorizenetCardinal\Gateway\Validator\VirtualTransactionValidator

File: vendor/magento/module-authorizenet-cardinal/etc/di.xml

<virtualType name="Magento\AuthorizenetCardinal\Gateway\Validator\VirtualTransactionValidator"
             type="Magento\Payment\Gateway\Validator\ValidatorComposite">
    <arguments>
        <argument name="chainBreakingValidators" xsi:type="array">
            <item name="general" xsi:type="boolean">
                true
            </item>
        </argument>
        <argument name="validators" xsi:type="array">
            <item name="general" xsi:type="string">
                AuthorizenetAcceptjsTransactionValidator
            </item>
            <item name="cavv_response" xsi:type="string">
                Magento\AuthorizenetCardinal\Gateway\Validator\CavvResponseValidator
            </item>
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual Magento\AuthorizenetCardinal\Gateway\Validator\VirtualTransactionValidator object that it should return a Magento\Payment\Gateway\Validator\ValidatorComposite object.

This configuration tells the Object Manager that when a user wants a Magento\AuthorizenetCardinal\Gateway\Validator\VirtualTransactionValidator object that the following arguments should be used in the foo object's constructor.

  • $chainBreakingValidators = [...items...];
  • $validators = [...items...];

File: vendor/magento/module-authorizenet-cardinal/etc/di.xml

<virtualType name="AuthorizenetAcceptjsAuthorizeCommand">
    <arguments>
        <argument name="validator" xsi:type="object">
            Magento\AuthorizenetCardinal\Gateway\Validator\VirtualTransactionValidator
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This configuration tells the Object Manager that when a user wants a AuthorizenetAcceptjsAuthorizeCommand object that the following arguments should be used in the foo object's constructor.