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
- 0285eef05c1ec5d6b2d91a9287fcd3bfb23f8aa80016a0aef173d01486e921cc
- request
- 592c0c4a15f3cb55c2eea133182cb3860da0e83aba677e0d9324c66304f40dd3
- transaction
- 0a457af8da822b78e29ba4ad1057c1050b2d2828564ff2653c8caa1156806694computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73830
the chainentry 73830
- sealed to the entry before
- b2a62bff0245f26dcc83d05cb9c5817397f4758067e78f3e25e89cd885cf1261
- this leaf
- b5bb5406d433a84d8229d0792b907522b343ddc90848f75c67b2ffb8d7b3d68a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lnJOHyMMozVkp0SFI+bVP2xEU0328YL+wCNflmo2R2qggPPrYVELhKmKqgrqwHAQoYXI3/fSI/T5tiXH3rRkCA==