# CF-6193 - Bulk Pay UI Error Handling

## Current Behavior

When creating bulk payments, the frontend can result in a few possible states:

1. bulk_create POST fails
1. bulk create POST succeeds with no errors
1. bulk create POST succeeds but with errors for all payments: `Payword Incorrect`
1. bulk create POST succeeds but with errors for all payments: `The payment for this invoice could not be created`
1. bulk create POST succeeds but with errors for some payments: `Payword Incorrect`
1. bulk create POST succeeds but with errors for some payments: `The payment for this invoice could not be created`
1. bulk create POST succeeds but with mixed errors for all payments : `Payword Incorrect` & `The payment for this invoice could not be created`
1. bulk create POST succeeds but with mixed errors for some payments : `Payword Incorrect` & `The payment for this invoice could not be created`

I imagine #2, #3 and #4 would be the vast majority of cases.

## API Options

1. Leave current APIs
1. Modify procore - parses all individual responses from Pay and responds to frontend w/ 401 if some or all payments have incorrect password
1. Modify procore and pay
- New pay endpoint to check if payword is correct
- procore can call endpoint before making payment requests