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
- ffb0c1903db7bb231ba746c2edc6cc1045392137291f03a6690c5964b04fcc15
- request
- aa7c688cf3892008f3429ec71c0b6d051a053844f4d60def486591497cfd6c8f
- transaction
- 503bbab6a6f56d67ba864971cc7449d527479c8d4b98d39445f72aea45ed716ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37385
the chainentry 37385
- sealed to the entry before
- 0990cbe2beedc21bab24ec7d6f09cf5303ba58228820f2a6ce679f1f70b3302c
- this leaf
- d6d7a3e9f4d698cf2da07ae471f2b6f94e8be526b73f27ecb7acd468ce513e14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L9ltRFHZyvKOUiOa52H1Z5fXEhqPBEAygwcskkAUhZNC5z1QKSUy2ReiqPdHYaefcLcDXI0XaIpyxfgF/X/EDQ==