why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- fe078c77eb65e613519e74551bdcef6a6b963826015b90463459b3766c054bb9
- request
- e554757e8d6054c7e264e5c88ebcc99c38ccd13a5f0ad52d775350a16cdbd0f8
- transaction
- 26d7b476ad5aaf4aaa35886e75f4b5fc12aed0028c513bde73bc77ffc1317e18computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52123
the chainentry 52123
- sealed to the entry before
- 9843b5b25a902c094964104588fea646659dd729386dc10991214292522db8bc
- this leaf
- 86b50e524a787ec99d55e1d5f7e9e1495db0edb7d393b3bb8d7872e85b854607
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UvGruNpMsR64ftXuXhKl/EXX1PGrIkWTIF7vvvq/5YNx+iiKbNapMof41jMP/UlETYiyFtdzWuyK9GoL/PUeAw==