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
- 76f80a0a0d601048d04ed48f26c7085fc498f93ea84e4921457fb5247c5b6226
- request
- 81a669f2043617330683bbad80f283795cf51357965eec6b996a771c288943ca
- transaction
- 82be32e0da20caf30b35e00d23f069c29c82ce76be772f209c2a4cbf0dc08096computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34683
the chainentry 34683
- sealed to the entry before
- 0bdb7b3560fc50a10e54d7abf3b461d8a497a6f4373448c49e25f15e33343397
- this leaf
- 6ada6d317c51577dee069d7c7bbd44ca60bc436666b1ad44b3ce6a3c906b34b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Hv770KvQBeSP1+6+QhGoIl+sQd0vIVP/8YAti+IkBxzj2xNuecXbGnGl04ZteZM2L6ddgAYQrDik6BGpOYCDA==