Card Issuing & Management
Card Details Update
This page explains how to update selected card details after card issuance is complete. The flow covers submitting a partial card update, confirming the update, and retrieving the latest card record so your system can display the confirmed information back to the cardholder.
Overview
Card details update allows your system to modify selected card information after the card has already been issued. This should be handled as a controlled partial update flow.
After submitting the update, your system should confirm the result and retrieve the latest card record when needed to keep the cardholder experience synchronized.
Recommended flow
Use the following flow when updating selected card details after issuance.
Identify the card
Use the stored card reference to identify the card that requires an update.
Submit partial update
Submit only the card details that need to be updated after card issuance.
Confirm update result
Process the response returned by Payblr and confirm whether the update was completed.
Retrieve latest card record
Retrieve the latest card record so your system can display confirmed information to the cardholder.
Card Details Update Sequence Diagram
Recommended card details update sequence
User
Cardholder
System
Client System
Platform
Payblr APIs
1. Request card details update
Cardholder submits updated card details in the client app.
2. Submit partial card update
Confirmed dataEndpoint
Update CardMethod
PATCH /program-manager/thr/cards/{publicToken}Client system sends the selected card details to be updated.
3. Return update result
Endpoint
Update CardPayblr returns the result of the partial card update request.
4. Retrieve Card
Endpoint
Retrieve CardMethod
GET /program-manager/thr/cards/{publicToken}Client system retrieves the latest card record after the update.
5. Return latest card record
Confirmed dataEndpoint
Retrieve CardPayblr returns the latest card record with the confirmed card details.
6. Display confirmed details
Client system displays the confirmed card details to the cardholder.
API sequence
The following sequence summarizes the API activities involved in updating selected card details.
| Order | API activity | Purpose | Output / next action |
|---|---|---|---|
| 1 | Update Card | Submit selected card details that need to be updated. | Process the update result returned by Payblr. |
| 2 | Retrieve Card | Retrieve the latest card record after the update. | Display or store the confirmed card details. |
Request patterns
PATCH /program-manager/thr/cards/{publicToken}
Authorization: Bearer [ACCESS_TOKEN]
Content-Type: application/json
GET /program-manager/thr/cards/{publicToken}
Authorization: Bearer [ACCESS_TOKEN]
Accept: application/jsonImplementation notes
Before implementing card details update, confirm which fields are supported for update and which fields require separate card lifecycle operations.
- Use the stored card reference to identify the correct card before submitting updates.
- Submit only the fields that need to be updated when using a partial update flow.
- Validate user-entered information before sending the update request.
- Retrieve the latest card record after the update when your user experience depends on confirmed card data.
- Log request identifiers, card references, updated fields, response status, and timestamps for troubleshooting.
Validate updated fields
Confirm field format, required conditions, and supported update rules before submitting a partial update.
Keep card details synchronized
Retrieve the latest card record when the cardholder experience needs to show confirmed updated information.
Next steps
After implementing card details update, continue with CVV and PIN status management, secure card data, and renewal or replacement documentation as needed for your cardholder lifecycle.