-
Given this IBAN Value "JO69WXCV8898216666923864119419", The Iban.isValid() returns false.
Confirmed the mentioned iban was valid using IBANValidator of apache commons validator and from from https:…
-
**Description.**
New functionality add an IbanValidator.
**Solution**
A new class called IbanValidator in the Validators project.
* This class should validate and format the given Iban value.
*…
-
using System;
using Xunit;
using QRCoder;
using Shouldly;
using System.Globalization;
using System.Threading;
using QRCoderTests.XUnitExtenstions;
using static QRCoder.PayloadGenerator.BezahlCo…
-
**Symfony version(s) affected**: all
**Description**
Current IBAN validator uses general IBAN checksum only, while some countries use internal check digit algorithms to validate domestic BBAN. W…
-
This IBAN should not be valid: FI21 1234 5600 0007 85fdgdfg
I use
$ibanValidator = new IBANValidator();
$is_valid = $ibanValidator->validate('FI21 1234 5600 0007 85fdgdfg');
-
follow up to #914
after the scopes are gone more then half of the tests are gone as well. but the rest needs a new implementation around validation or permission checks.
-
What do you think about deprecating the `Date` and `Time` constraints in favor of add a `format` option to the `DateTime` constraint.
We can do that using the `DateTime::createFromFormat()` and `DateT…
-
# This is a Bug Report
#### :tophat: Description
* What went wrong?
Exception when adding a user collaboration.
* What did you expect should have happened?
* What was the config you used?
* …
-
Hi,
I have a problem with the IbanValidator. Iban "FR76" is considered as valid.
The problem is that the Iban length according to the country is not tested ([step 1 of the validation algorithm](htt…
-
Some users don't enter the IBAN with uppercase which causes a validation failure. Why not just always convert the input to uppercase before validation?
@sprain @webmozart
ruudk updated
10 years ago