On This Page
Uploading a Request File
IMPORTANT
For each PAN you upload, you can receive multiple responses. For example,
if you upload one Visa card for an update, you can receive both a Mastercard and Visa
response, or two Visa responses.
To upload the request file, use HTTPS. Your client application must support HTTP/1.0 or
HTTP/1.1 and TLS 1.2 or later.
To access the Account Updater URL, you must authenticate using either HTTP signature
authentication or JWT authentication.
Before you submit files to the production server, test your request files. Follow the
instructions in Testing.
Use the following URLs for submitting test and live Account Updater request files:
- Test:https://api.smartpayfuse-test.barclaycard/accountupdater/v1/batches/upload-csv-card-numbers
- Production:https://api.smartpayfuse.barclaycard/accountupdater/v1/batches/upload-csv-card-numbers
The request is a POST form data request with a CSV file keyed as a data file.
A successful request results in an HTTP 200 response code. The following error codes are
possible:
Code | Description | Failure Scenarios |
|---|---|---|
400 | Bad Request | Malformed request. Payload too large. |
401 | Unauthorized | Invalid request credentials. Public key matching public key fingerprint not found. |
403 | Forbidden | Invalid merchant header in uploaded file. |
500 | Internal Server Error | Message fails to be put on queue for processing. |
503 | Server Unavailable | Internal database unavailable to retrieve public key. |
For more information on submitting a PAN upload request see Sample AU Application for Uploading a CSV of PANs.