Дерево страниц

Сравнение версий

Ключ

  • Эта строка добавлена.
  • Эта строка удалена.
  • Изменено форматирование.

Strong Customer Authentication (SCA) is a requirement form of multi-factor authentication required for merchants within the European Union collecting (EU) who collect credit card payments from clients also within the EU.   It is a form of mult-factor authentication that will be needed when attempting to charge an EU client's credit card through Ubersmith.  SCA is not required in cases where either the merchant or the customer are Payments that requires SCA can only be completed by the card holder.

Ubersmith integrates with a number of tokenized gateways that support SCA. SCA is not required for merchants or customers outside of the European Union.  SCA compliance is supported within Ubersmith by a number of tokenized gateway integrations. 

Processing

Client

Automatically Initiated Charges with SCA

  1. Within the client interface, initiate a credit card payment for an invoice.
    Image Removed
  2. If the bank requests SCA for a manual transaction, Ubersmith will open a popup presenting the challenge from the credit card gateway provider. Different gateways will display and require different things from the user depending on their individual processes.Image Removed
  3. If the payer completes the challenge successfully, they will be redirected to the invoice after the challenge is completed. 
  4. If the payer fails the challenge, they will be redirected back to the invoice to choose another payment method.

Signing Quotes with SCA

  • From the quote signature page, the client specifies they would like to pay their initial order total via credit card.  When the page is submitted and the quote is signed, the pre-authorization call is made to the gateway.Image Removed
  • If the bank requests SCA for the transaction, Ubersmith will open a popup

    Automated credit card charges, initiated by the daily invoicing script that trigger SCA challenges, emails your clients directing them to log into the Client Portal to complete the payment.

    Unlike other automatic transactions that fail, SCA-challenged transactions are not added to the Retry Queue because they require the payer’s intervention. These failed charges appear in the Charge Log with the message prefix [3DSecure 2.0]. The rest of the message varies depending on the provider.

    Image Added

    Processing User initiated charges with SCA

    1. Access the Invoices page.
    2. When marking the payment, If the bank requests SCA for the charge, an error displays and an email is sent to your client instructing them to log into Ubersmith’s Client Portal to complete the charge. Image Added

    Processing Client Initiated Charges with SCA

    1. From the Client Portal, access the View Invoices page.

    2. For the invoice you want to pay, click Pay Online.
      Image Added
      The invoice appears.

    3. Mark the payment. The 3D Secure 2.0 authentication process page appears.

    4. Click Proceed with Authentication.
      Image Added
      A page presenting the challenge from the credit card gateway provider appears.

      Different gateways

      Each gateway will display and require different things

      from the user

      depending on

      their

      its individual processes

      .Image Removed
    5. If the payer completes the challenge successfully, they will be redirected to the signed quote after the challenge is completed. 
    6. If the payer fails the challenge, they will be redirected back to the quote signature page to choose another payment method.

    Processing User initiated charges with SCA

    1. Within the Ubersmith admin interface, initiate a credit card payment for an invoice.Image Removed
    2. If the bank requests SCA for the charge, an error will be displayed to the user and an email will be sent to the customer.Image Removed
    3. The client receives the email and follows the instructions within to log in to Ubersmith's client portal and complete the charge.Image Removed

    Automatically Initiated Charges with SCA

    Automated credit card charges, initiated by the daily invoicing script, that trigger an SCA challenge will result in an email notice to the client directing them to log in and complete the payment.   Unlike other automatic transactions that fail, SCA challenged transactions will not be added to the retry queue because they require the payer’s intervention.  These failed charges will appear under the charge log with the message prefix "[3DSecure 2.0]". The rest of the message may vary depending on the provider.Image Removed
    1. .

    2. Click Submit.
      Image Added
      The invoice appears.

    3. Click Mark Payment.

    Signing Quotes with SCA

    1. Once you have emailed the approved quote to the client, the client can access the quote online and sign the contract and pay for the service.
    2. From the Payment Information section on the Quote Signature page, the client selects credit card, electronically signs the quote and clicks Sign Contract.


      Image Added
      The 3D Secure 2.0 authentication process page appears.
    3. Click Proceed with Authentication.
      Image Added
      A page presenting the challenge from the credit card gateway provider appears. Each gateway will display and require different things depending on its individual processes.
    4. Click Submit.
      Image Added
      The Quote Signature page appears.



    панель
    borderColor#8181AA
    bgColor#FDFDFD
    titleColor#8181AA
    titleBGColor#2F304F
    borderStylesolid
    titleOn this page

    Оглавление
    indent10px