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
- ee1ff347229d2f567784a5168570314149de10d6318a879e7cb13c3c9b60e940
- request
- 648c1a4f2bd6df770a00d6e7d5de0e2ebcd4c8560857b3239c8e7b73e9d0e91b
- transaction
- 6af7849ce39472d95e18fbfd900ab6744862b0b67655a3ebecf01113cf2c2504computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22144
the chainentry 22144
- sealed to the entry before
- bfebc38297bd00b4f2d4f48e438ce1d782c5903cca131b383fa1d733edf38d14
- this leaf
- 4970b7e108b17ec3963fd2c1041e3a727493499d74163b7242976d98eeba7e4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iL3gB6cZMwZdRbl/S9aMIdXTkhGhjGIwyQkg+LGtpsQjOT1nNw4HrgonLL9AB69TDE/lTP98EjxVN8dpt+N1CA==