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
- 95c4cf23b280da57e4a1c473ea04da18ed941454412af1f1434296c6815de55d
- request
- 7f831e7e83a46fef1088d503feebc2a120ea2ce9a3b990b99b34844bfe46c390
- transaction
- 760f5632d695f7cda20f4d8054ac615a9d27498297a499be2627d4f929fa8876computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57418
the chainentry 57418
- sealed to the entry before
- bc8faf95a7669ecf41e69ef5710f29d02ba9883051895195e0044c4632c5189b
- this leaf
- 0e742a41f8d271303e9c14f0c4e5b1a4cabee207575bb0ab9f405cf52246f606
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2X64uk7DtDoZqhaScINb33OOZoNTVduevOhA3VO3tu4+hMdFixtcXrHCmbiJNuVs37yA2ser9Snat94hJDJqCQ==