13 Matching Annotations
  1. Last 7 days
    1. 500 free identity-verifications per month on Order Form B

      it's in form b, in the executed agreement! "The Platform Fee includes 500 new End User KYC completions per month. User Onboarding Fees for completions beyond 500 per month are billed per Schedule 3. User Application Fees apply to all KYC initiations per Schedule 3."

    2. Our current process for a limit-increase request: Google form → Lucas logs it → Janice reviews over email → Zsuzs approves → someone executes

      definitely should reform but this is not true actually, janice reviews, zsuzs is not pat of compliance anymore

    3. supporting signal

      we could also think about other signals we saw Bridge utilizing: monitoring IP addresses, if suddenly there's a change, block the pmt for manual review

    4. Phase 1 launch framed as "limited testing with tighter rules

      We should define this. Should be volume plus time base in my opinion.

      Should it be min. 60days? and volume and txn number?

    5. supporting signal

      Should we consider other supporting signals?

      E.g. how long FOMO user + FOMO volume/activity

      I think the biggest - worst risk is new users signing up to FOMO just to abuse this ACH debit feature. We could definitely stop this. I'm not sure how to solve technically but could we create tags where fomo gives us info on a user per a frameowrk we create?