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
- b3def003f05d066e4e2ef1965550eeddd7cb05a1300e18f6e9f4de26e11bd513
- request
- 48457223786582ca115775f734271e842cbad4b33688d4545d272bc13cd1eeff
- transaction
- 31ebfee7b4594c08df75f1455baa79e84217da22c5d2e9501288f98fa88886d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52578
the chainentry 52578
- sealed to the entry before
- 15c649a7316e516f949253ae71083f759126b23ebd4155c505cb139e10c76be8
- this leaf
- 244b0492f208c69a3ec91e9b0d0fc54b795b619e1bfedd428111e2160da687ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- no5SRIZpecV4Wl+uc2RlaHD6F/pG6aWKJHiN9r1XjVL/oR/7J1Uqo4hw5zObZncWg6YU78qIRm7AxPr3DIeYBg==