202 Accepted immediately and do the actual work in the background. Poll Get a bulk transfer to see the outcome, or query reprocess logs for a full audit trail of every attempt.
Only items in
failed status can be reprocessed. completed items are left untouched by both endpoints below.Reprocess a batch
Retries everyfailed item in a batch. Items that are completed are skipped; the request has no effect on them.
Endpoint
Path parameters
The ID of the batch to reprocess.
Headers
Your public API key.
Your API secret. Use a
stl_test_... value in sandbox, stl_live_... in production.Your business ID.
Response
true on success."Bulk transfer reprocessing started" if any items were queued, or "No failed items to reprocess" if the batch has none.The batch that was reprocessed.
Number of failed items that were queued for retry.
0 if there was nothing to reprocess.Before starting, Interstellas checks that your business account has enough available balance to cover the sum of all failed items being retried. If it doesn’t, the request fails outright (see Errors below) rather than partially retrying — this differs from a normal batch, where an insufficient-funds failure is per-item, discovered during processing.
Code examples
Example response
Errors
| Status | Cause |
|---|---|
400 Bad Request | Batch status isn’t failed or partially_completed (e.g. it’s still pending/processing, or already fully completed) — message includes the current status |
400 Bad Request | "Insufficient Funds" — your account can’t cover the total of all failed items being retried |
401 Unauthorized | businessId header missing, or credentials invalid |
404 Not Found | No bulk transfer with this ID exists for your client and business |
Reprocess a single item
Retries exactly one failed item, without touching any other item in the batch.Endpoint
Path parameters
The ID of the batch the item belongs to.
The item’s
id, from the items array in Get a bulk transfer.Headers
Your public API key.
Your API secret. Use a
stl_test_... value in sandbox, stl_live_... in production.Your business ID.
Response
true on success."Transfer item reprocessing started".The batch the item belongs to.
The item that was reprocessed.
The new transaction reference generated for this retry. The item’s original reference is preserved separately as
originalTransactionReference — see Get a bulk transfer.Code examples
Example response
Errors
| Status | Cause |
|---|---|
400 Bad Request | Item not found in this batch |
400 Bad Request | Item’s current status isn’t failed — message includes the current status |
400 Bad Request | The item was reprocessed by a concurrent request a moment earlier ("Transfer item is not in a retryable state (concurrent update detected)") — safe to check the item’s current status and decide whether to retry |
400 Bad Request | No payment account found for this business |
401 Unauthorized | businessId header missing, or credentials invalid |