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
- d02061644ab4f9880821372e2d2f481a48febf108e2e54333e5a8c74e2c91544
- request
- 5305ca173b321279665d5c71e7d7afd31d441621ef95b123f9bdd76be76e6f61
- transaction
- 7fc17dac2b05c71106d93730ddfb6948debea4b3b53a57f102f879c1295b8be7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60367
the chainentry 60367
- sealed to the entry before
- 771bd6e0288a34004656c2c684cde97b4041157820a32866ddef44f1b179f99e
- this leaf
- 71efa135cc3befdd150d8cfd8dc57606b09e38350b8558857b9b993da95c823d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A+kAv2ROzso8muhYeivvC9Q+tPAkTVBW38wpIJz8xeTUco+TV3MJERXH7T53EGqmUZg2mKOo9B7mdkm3bwbuAw==