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
- 8084133de884385fa5a1cd39666d135af97082a63650c81649a0b3a02cfc349a
- request
- 9b010e1e2db1728a862d37b93455e0ad42852f59875b149df257cf42d0e1dff6
- transaction
- 78baab61ccbec66db9b2179b0f834f6138f19604867e00d16f2042f3b5168d59computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56838
the chainentry 56838
- sealed to the entry before
- 7e4fc93661888f2cd002be2cb68e108aa30551316ea07ae0ecc0ae0a5d6524e3
- this leaf
- 33c0cbdedaad239221012990a3a781eb3ef1df3ccfacaf2701223a60ef5aaaa7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L/GeuTAofhZhuBDDSDJd6B0H6E6gGMvBp6jNK0p+oB+NrWprKjNqNHqAEc+Erq+UZuFpOiWxbnkGiuzaiiwXDA==