Service
Batch debit
Many debits are grouped into one batch, processed in a session, and reconciled with a result file.
There are two API generations: cms_create_ad_batch and cms_status_ad_batch are version 1. ad-make-batch and ad-status-batch are version 2 and add BATCH_ID. Files can be sent as multipart or JSON base64.
Funds still move from the mandated customer account to the enterprise account at the bank. Fintwin tracks batch status.
Try sends the JSON file description from the form. The real upload API expects multipart. The sandbox may reject that description.
Create debit batch
/api/v1/cms_create_ad_batchBatch status/api/v1/cms_status_ad_batchRefund a debit/api/v1/cms_refund_ad_by_fwCreate batch v2/api/v1/batch-req/ad-make-batchBatch status v2/api/v1/batch-req/ad-status-batchUpload batch file/api/v1/batch-file/cms_upload_batch_requestCheck batch file result/api/v1/batch-file/cms_check_batch_resultDownload batch result/api/v1/batch-file/cms_download_batch_resultUpload batch as JSON/api/v1/batch-file-base64/upload-batch-fileCheck JSON batch file/api/v1/batch-file-base64/check-batch-fileDownload result as JSON/api/v1/batch-file-base64/download-result-batch-file