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
- 30fcb9c1079d53eaaff4153f614904ad6d5d7ef7984727593f4531f954a05e1f
- request
- 80688693c9661eecb1bbe64f530d48df477d79cfc1ba54f19dd3594c5cee4eef
- transaction
- 99ed1acc88dfcecbb0fdb5199315841cc57b8fb664ffa68dcb64452be37ee336computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24855
the chainentry 24855
- sealed to the entry before
- 0e71a1370a8c1f2f4b6e76316996e604bf03fa1074291575b7bcbcd5706852f7
- this leaf
- 6d68ca6df360f9fc81e16cd05a768aa7c7824de435de7468373e684956c22b1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qVwTWMQx51qSmS4m9FPi6xIpXwjjY8D8dkvLIX9rREJJLZOQxIUi9rDuAHj2hn6UkXxmfX6jpxOpUK+zyjq+Bw==