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
- 8ce01cd979048f8e7361c543e70346ea11f806df0c7bb4d9204cce9fa674a050
- request
- 63365d62722a3893f522d4daf14852ae55f26151a40caac2b49383fdc13a9335
- transaction
- 6b8cabada915d673f324e5959e2fdcb0f8b0821e3fc2821383498e0e348a6f7bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49070
the chainentry 49070
- sealed to the entry before
- 3f626af2cff9c0a17638c6c36b953d517aa070bab6b4cf040398dca27f544cbc
- this leaf
- 54a75887ca2530d814c99af1784f06586144cd44ba9ec25ee38cfd0ce7cb7d85
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ujiuhEcKvwN62pLPFKmy/ldpr6kW5LtGCFB8z68i344cnxdHAs3D535+bJkVcR881w2yI11glgRtlPq/RFo+BA==