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
- ba4bf497b76e994f9ead3080a6991014aed2f98eda8f72d95455cff8b7308b18
- request
- 2e4c25c5819e76bb963425f1334cdc791dbdd845f8d39f70cd235a2ca2697224
- transaction
- 00c4a244f9900d0baca106f7dc5725d011ed352f266ebeebeb4d70a6ddf67b5bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64456
the chainentry 64456
- sealed to the entry before
- 3871193bdf05f80014b66595cd3a907e4d8844ebc6155bb00011884698fbeb9d
- this leaf
- 99775975b7d6efe4dda24d04bfd59b18813019476d516b71a8ef184ada3bea50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /oqmhqQIV3MQH5HB+3VixdrZxyIltLcNMVKGcuYo7mOftsu1RP89KiJpNZ/IZqM762obvuhveN0DQGI/5SQYCA==