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
- 78ad7cb54af16297f7133f6f3555f393a2efcf07705ff1a1e0bcc830598adc28
- request
- 5c4beb8f33bb848fc5577f734f6b4a620fc97a8571a69a671f793899f47221f7
- transaction
- 35b4bc6a0a2a4af2559b791ab0fbedd69cda236028a43f11e75a865edfc328cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7057
the chainentry 7057
- sealed to the entry before
- 3cda6b72a122c158468897044f593adc07a4f5d9f243e28373f221821dc2c577
- this leaf
- 40c784bd831ca54024c55c0ccc4892e7f61f0d940e687195621369a251054ee4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HdQO9QdlT+t8a7Rg9X+b3LhFWvN09Z/m8ENVhPDpBAbCrPpbCNCw+uy+iOiz/rGaHb5sZq/s6oqa8634pc9kDA==