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
- cf4ca08e83b0013c50bea2ec6c8a60bec75707b40b4dbf463a74b6522acdc02b
- request
- c8c688114865ae7a9aadf62b64e8a077b0e3c32965a1420ef238e6df8b63f90e
- transaction
- f38cd53afedf5894c88b6ac28964342bf4b5d68640648d6abae9bf8b46e1d64dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38949
the chainentry 38949
- sealed to the entry before
- 0b2ebb74c4104042ccb062d6dfb48d5d1e8e921086473f9075bdb98590a7af94
- this leaf
- d25eb00bf74131868be1941cf4d37da1bd92f7ade12c9f1390368eb304d1fd0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CxqcveQZdt0isYC9avt7o8C8JmuYYvZk4ryICFsakmZ9BzM2nDX9LUC3s6HnD7DGAXNQlrqiTuzP1KPLeaHFBw==