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
- 0e8cb88dc6e9ce1e662aa032ff48c427a99f8f42a38826fc14751044c8d96011
- request
- fccc0e9209cb625433752f878abf616d5e064129c5112375bcfcfe27c6f8b711
- transaction
- dd9eede432e803b7e7ad8df666503b1fe7336b5f9df47102cd5b0bf8a7114e5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16103
the chainentry 16103
- sealed to the entry before
- c32e9d1a5a2e8820544505975afc389b2453d7a3315b3a2fe1b15e6a1349c9bf
- this leaf
- a6e5fbc08000ebd5e5a96561de23f85a5236f7a29f5c9413fbad84f0d38bfb46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6NJdwibUO4PASgMqEVz57KQf2MkONFskNI2+YCyVbcw4Kvw3gmFV2mXcfuu993GQIsC4/aYBHeN9nEZplIp1CA==