Contrib.social

Can continue without CCV to the final payment stage

Open on Drupal.org →
Created on 10 May 2024, about 2 months ago
Updated 13 May 2024, about 1 month ago

Firstly, thanks for writing this module, nice clean code too!

Problem/Motivation

Integrating Opayo

Steps to reproduce

Complete a standard card payment without a CVV code

Proposed resolution

- Make the CCV field mandatory
- Valid the CCV after submitting the card details, before reaching the payment confirmation page. (Or maybe it is working and our Opayo test account is allowing no CVV code, but I thought it was supposed to be 123 for test cards)

Thanks

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

jez300

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @jez300
  • Assigned to mwjansen
  • Comment about 2 months ago →
    mwjansen

    Yes, fair point.

    I would need to test to be 100% sure but must assume that a missing CVV normally means the 'card tokenisation' step would fail in production. This would then get reported back to the module's javascript, this then posts Opayo's error message back to the back-end where it should get translated into a Drupal error message.

    So ... (unless I'm wrong about the above) the transaction wouldn't proceed in production.
    Obviously checking for a non-empty CVV is straightforward: reporting back to the Drupal form javascript is where I'd have to do a bunch of digging.

  • Comment about 1 month ago →
    jez300

    Thanks. I'll test against a live account when I have access and report back.
    I wonder if you are able to skip the CCV check on one of your live sites?

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024