Send a client batch

in this tutorial, you'll learn how to ✅ register the relevant webhooks ✅ submit a client batch of payments ✅ cancel the batch the tutorial assumes you have a knowledge of apis and how they work for more information on sending api see structure for more details the tutorial uses these api endpoints api description originate ach client batches submits 2 or more payments from the same cross river account number as a batch cancel ach client batches cancels all the payments in the batch that have not yet been completely processed important do not poll the apis for status updates and reconciliation purposes incorporate webhooks into the payment reconciliation process the tutorial uses these webhooks see all ach related webhook events webhook description ach batch imported notifies you that the client batch has been imported ach batch canceled notifies you that all pending or on hold payments in the client batch are canceled before you begin make sure you have get api credentials partner id account number register relevant webhook events to receive the webhook events for this tutorial both partner accounts need to accounts, cards and payment events each specific webhook event type once you are registered, the event objects are sent to the registered urls the event object contains a list of resource identifiers used to download details on each event submit a client batch use a client batch when you have several transfers to or from the same account for example, for payroll in this tutorial the example account number is 2207975570 the following 5 different actions appear in the sample code name account number transaction type service type amount routing number account type standard entry class (sec) codes john wick 12345678 push sameday 113 021000021 checking ppd cleveland brown 2342123458 pull standard 243591 021000021 checking ppd matt cauthon 2342123458 pull standard 50 021000021 checking ppd perrin aybara 2342123458 push standard 2750 021000021 checking ppd elayne trakand 2342123458 pull sameday 15000 021000021 checking ppd call post ach/v1/client batches the details of each payment are defined by the call attributes values for these attributes must be provided for each payment in the batch important we strongly recommend that you include an idempotency key in your request header to provide duplicate protection should the payment fail read more about idempotency keys money amounts in api calls and responses are written without a decimal point between the dollars and the cents post ach/v1/client batches { { "payments" \[ { "accountnumber" "2207975570", "receiver" { "routingnumber" "021000021", "accountnumber" "12345678", "accounttype" "checking", "name" "john wick" }, "seccode" "ppd", "description" "string", "transactiontype" "push", "amount" 113, "servicetype" "sameday" }, { "accountnumber" "2207975570", "receiver" { "routingnumber" "021000021", "accountnumber" "2342123458", "accounttype" "checking", "name" "cleveland brown" }, "seccode" "ppd", "description" "string", "transactiontype" "pull", "amount" 243591, "servicetype" "standard" }, { "accountnumber" "2207975570", "receiver" { "routingnumber" "021000021", "accountnumber" "2342123458", "accounttype" "checking", "name" "matt cauthon" }, "seccode" "ppd", "description" "string", "transactiontype" "pull", "amount" 50, "servicetype" "standard" }, { "accountnumber" "2207975570", "receiver" { "routingnumber" "021000021", "accountnumber" "2342123458", "accounttype" "checking", "name" "perrin aybara" }, "seccode" "ppd", "description" "string", "transactiontype" "push", "amount" 2750, "servicetype" "standard" }, { "accountnumber" "2207975570", "receiver" { "routingnumber" "021000021", "accountnumber" "2342123458", "accounttype" "checking", "name" "elayne trakand" }, "seccode" "ppd", "description" "string", "transactiontype" "pull", "amount" 15000, "servicetype" "sameday" } ] } a successful api call returns a json response with the details of the client batch record that contains the client batch id (in our case, fcb7188f e051 4f5b addd afaa00eadb3a ) and individual paymentidentifiers the identifiers appear in the response in the order that the payments were listed in the request so in our case, the payment to john wick is assigned paymentidentifier 04793f3 13d9 4d52 b57e afaa00eb6c74 , the payment from cleveland brown corresponds to dbe36253 06d1 462a 9117 afaa00eb6c74 , and so on sample client batch response { "id" "fcb7188f e051 4f5b addd afaa00eadb3a", "referenceid" "cb0461724aawt", "status" "processing", "accountnumber" "2207975570", "paymentcount" 5, "debittotal" 258641, "credittotal" 2863, "importcount" 0, "productid" "cc62e17f 5912 483e 9e42 aed30112fbb6", "partnerid" "1e5d3f04 ae24 4af6 9e30 aecf012b99dd", "createdat" "2023 02 15t09 15 05 1486312 05 00", "lastmodifiedat" "2023 02 15t09 15 05 1486312 05 00", "paymentidentifiers" \[ "f04793f3 13d9 4d52 b57e afaa00eb6c74", "dbe36253 06d1 462a 9117 afaa00eb6c74", "1e1a08c7 1e60 452b b22b afaa00eb6c74", "a0bc6816 e85e 4ba6 bf9a afaa00eb6c74", "6ed9ea59 2522 4550 8e5d afaa00eb6c74" ] } the status attribute in the response indicates that your batch is processing it does not indicate that the batch was imported successfully the importcount attribute in the response indicates how many payments were imported (meaning originated) out of the total at the time of the response when the status of the client batch changes to imported the ach batch imported webhook event fires the status in the webhook refers to the webhook status, not the client batch status ach batch imported webhook { "id" "b060d47c 7ab5 4a34 8803 afaa00ec617e", "eventname" "ach batch imported", "status" "pending", "partnerid" "1e5d3f04 ae24 4af6 9e30 aecf012b99dd", "createdat" "2023 02 15t09 20 38 18 05 00", "resources" \[ "ach/v1/client batches/fcb7188f e051 4f5b addd afaa00eadb3a" ], "details" \[ { "clientbatchid" "fcb7188f e051 4f5b addd afaa00eadb3a", "accountnumber" "2207975570" } ] } for example, when the federal reserve accepts the payment the status changes to processing , which triggers the ach payment sent event every status change from this point on triggers the event until the payment posts to the receiving account (status complete ) cancel a payment in the batch sometimes it's most efficient to cancel a client batch before all the payments have imported rather than try to cancel a large number of payments individually call the cancel batch api to cancel any pending or on hold payments within a batch call post /v1/client batches/{id}/cancel to cancel the batch use the client batch id the id value (in our case, fcb7188f e051 4f5b addd afaa00eadb3a ) received in the response to the post ach/v1/client batches call curl x post \ header 'accept application/json' \ header 'authorization bearer '\<token>' https //sandbox crbcos com/ach/v1/client batches/fcb7188f e051 4f5b addd afaa00eadb3a/cancel' a successful api call returns a json response with the details of the client batch record that contains the individual payment identifiers of all payments that were canceled (payments with a completed status cannot be canceled ) the status in the response is canceling as with the client batch request above, each identifier returned corresponds to the order in which the payments were presented in the request { "id" "fc0d501d c36b 45b4 a0d5 afaa00eb6c74", "referenceid" "cb0460ujr6dna", "status" "canceling", "accountnumber" "2207975570", "paymentcount" 5, "debittotal" 258641, "credittotal" 2863, "importcount" 5, "productid" "cc62e17f 5912 483e 9e42 aed30112fbb6", "partnerid" "1e5d3f04 ae24 4af6 9e30 aecf012b99dd", "createdat" "2023 02 15t09 17 09 077 05 00", "importedat" "2023 02 15t09 17 19 123 05 00", "lastmodifiedat" "2023 02 15t09 17 26 8406542 05 00", "paymentidentifiers" \[ "6ed9ea59 2522 4550 8e5d afaa00eb6c74", "dbe36253 06d1 462a 9117 afaa00eb6c74", "1e1a08c7 1e60 452b b22b afaa00eb6c74", "f04793f3 13d9 4d52 b57e afaa00eb6c74", "a0bc6816 e85e 4ba6 bf9a afaa00eb6c74" ] } when the cancellation is complete, it triggers the ach batch canceled webhook event note the client batch id (in this case , fcb7188f e051 4f5b addd afaa00eadb3a ) corresponds to the client batch id used in the cancellation request { "id" "a6593026 ea2c 42b1 ae57 afaa00ec84b2", "eventname" "ach batch canceled", "status" "pending", "partnerid" "1e5d3f04 ae24 4af6 9e30 aecf012b99dd", "createdat" "2023 02 15t09 21 08 21 05 00", "resources" \[ "ach/v1/client batches/0d4cf4dd bcbd 4eb7 878d afaa00ec59c0" ], "details" \[ { "clientbatchid" "fcb7188f e051 4f5b addd afaa00eadb3a", "accountnumber" "2207975570" } ] }