Create Card with Thredd Generated Card Number
You have the option to use Thredd-generated card numbers on the same account range if required. You can use the same Create Customised Card endpoint for this. Make sure that you are not specifying the customised card number (customPan) and its reference number (referenceNumber) in the request.
See the following Create Customised Card request example, where no customised card number is included in the customPan field and no reference number in the referenceNumber field:
{
"productReference": "",
"customerAccount": "",
"expiryDate": "",
"accessCode": "",
"coBrand": "",
"fulfil1": "",
"fulfil2": "",
"cardName": "",
"singleUse": false,
"nonReloadable": false,
"CardHolder": {
"Title": "Mrs.",
"FirstName": "Francis",
"LastName": "Armstrong",
"Dob": "2002-09-26",
"Gender": "F",
"Mobile": "(246) 779-6344 x88395",
"Telephone": "714.342.9465 x799",
"Email": "[email protected]",
"Address": {
"AddressLine1": "21156",
"AddressLine2": "Northwest",
"AddressLine3": "6469 Ullrich Street",
"City": "North Erichhaven",
"PostCode": "74494-8786",
"Country": "826"
},
"DeliveryAddress": {
"AddressLine1": "21156",
"AddressLine2": "Northwest",
"AddressLine3": "6469 Ullrich Street",
"City": "North Erichhaven",
"County": "Cambridgeshire",
"PostCode": "74494-8786",
"Country": "826"
}
},
"Groups": {
"Limit": "",
"Mcc": "",
"Usage": "",
"AuthorisationFee": "",
"ScheduledFee": "",
"WebserviceFee": "",
"LimitedNetwork": "",
"CardLinkage": "",
"AuthorisationCalendar": "",
"ForeignExchange": "",
"Whitelist": "",
"Blacklist": ""
},
"customPan": "",
"referenceNumber": null,
"productId": 443,
"ManufacturerDetails": {
"DeliveryMethod": "",
"DeliveryCode": "suywmq",
"LanguageCode": "EN",
"CarrierType": "suywmq",
"VanityName": "suywmq",
"Url": "https://natalia.net",
"CardPhysicalLayout": {
"ImageId": "suywmq",
"EmbossLine4": "suywmq",
"ThermalLine1": "suywmq",
"ThermalLine2": "suywmq",
"LogoFrontId": "suywmq",
"LogoBackId": "suywmq"
}
}
}If accepted, a 202 response is returned.
{
"messageId": "c012a5c5-7665-41f5-b317-6a59dadabba7"
}If unsuccessful, a webhook event will be sent to notify you of the failure. The event code for a card generation failure is 121. For more information, see the Webhook Notifications for Card Creation Failure section.
Webhook Notification for Card Creation Failure
Card creation requests are processed asynchronously. When you submit a request to the endpoint, Thredd returns an immediate 202 Accepted response containing a unique messageId.
If background processing fails after the 202 Accepted response has been issued, Thredd will send an Event Delivery System (EDS) webhook notification with event code 121 (Card Creation Failure).
Event Summary
| Property | Value |
|---|---|
| Event Code | 121 |
| Event Name | Card Creation Failure |
| Delivery Method | HTTPS POST (via Event Delivery System) |
| Correlation | Correlates to the original request using messageId |
Webhook Payload Example
When an asynchronous card creation request fails, Thredd delivers an Event Code 121 to your configured webhook URL:
{
"context": {
"notificationId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
"eventCode": 121,
"eventVersion": "v1",
"notificationTime": "2026-10-20T12:00:00Z"
},
"payload": {
"messageId": "e1cb2235-d65c-495f-b792-d231f1f7b1e2",
"reason": "The provided reference number is already in use."
}
}Updated 2 days ago