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
- 1cc3e826302102af7a99d5cd42a1f646ea3e9da2b83c5d630ea96e6098c47b40
- request
- df26f8b745313fd71ace3cbf351fdb001e271db7a64c9a0c351445acdbeae8b0
- transaction
- f1d273855273220f5176319c0f64ad351c7031f8461c35d3649606156d93df33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75614
the chainentry 75614
- sealed to the entry before
- 26a9a536b96edbc3f3fbebcfaea7e3a2f439e561c77dee14174dd9b19fb76130
- this leaf
- 9055dd49fd41af636a159945c71467a81b6e6055cc9c7589ad138f18a0aae6ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SLDiJmL8okklh2pnNSlmCQ9uSoZ764fqTeSL7lILQZ3jvTvs4a3Qqg2H6IOkMbr2ypHjJYHLfxY7wH3ptEThAg==