Approving collections

Collections that are created by automation or by users must be approved. Collections are identified by their 'collectionidentification' which is simply the unique reference used with BankTech. Collections can be approved in a couple ways but since you are reading the developer guide we assume you are interested in how to approve collections through our API.

Preapproval

Collections that are generated by automation may be pre-approved at the mandate level at the time of mandate registration. Alternatively, if configured, all mandates may be made valid to generate collections regardless of the mandate level pre-approval setting that is the default solution. If collections are manually created, they may also be pre-approved when created.

Manual approval

Where collections are not pre-approved for submission, they will need to be manually approved by a suitably authorised user. These can be approved in single or in bulk and in advance. Where collections are approved and not yet submitted and should be amended, they will need to be manually unapproved and amended and finally re-approved for submission.

API methods

POST: /collections/bulk/approve

This will approve single or multiple collections.

• Rate limit: 1 per second

• Payload size: 1,000 collections

POST: /collections/bulk/unapprove

This will unapprove single or multiple collections.

• Rate limit: 1 per second

• Payload size: 1,000 collections

Only collections that have been approved and have not yet been submitted can be unapproved.