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
- 690c74a50fd934bf7159a9fabc061e26d5a1702a96019b03c7e2d2bc16b3e7af
- request
- 06fdeeb023e6fec0de2b30d4cdd99e5133b40574327a83ccb1dcf1ad0bf017b9
- transaction
- 63afdaaf1093cedc422be9f2ec6aa2dcddadc709526f9f7d0b1e3f3782c16112computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29076
the chainentry 29076
- sealed to the entry before
- 9667594225bdd4a8a98ff61f9df3a63a26902dd98974bed666e10c2d72304f52
- this leaf
- c1aa0cb85d45f64c24bb0ae954a289aa7614f5e19945f66808b3b3227b2e8365
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cHlZ7L7HxeN0oeU6CTAAsJfvMsPQaggHwWw6ZvYJduDEsXJXxGNBeT1NFqStIy0HcQIcjTlIHLbG80wKjpyYAg==