In-App Stored Card Update
Update Expiry Date, Cardholder Name, or Custom Name of a Stored Card
Purpose
This method is used by myPOS Checkout API to allow the cardholder to securely update the expiry date, cardholder name, and the custom name of an already stored card. The customer will remain within the pages of the external application. All needed data (including payment card details) will be collected and submitted to myPOS Checkout API by the external app. myPOS Checkout API will return an XML/JSON with the result.
Method Properties
| Property | Typical Value | Type | Required | Description |
|---|---|---|---|---|
| CardToken | 1041333312721BC752C1AB7743D0821AA1C9CA09 | String (50) | YES | Uniquely generated token of the PAN of the card (returned as a response property of IPCIAPurchase). |
| CardholderName | John Smith | String (30) | YES | New name on the card |
| CardType | 1 | N(1) | YES | Please refer to Card Types. |
| ExpDate | Byte[] | BASE64 | YES | New expiry date, encoded |
| CVC | Byte[] | BASE64 | YES | Card CVC, encoded |
| ECI | 6 | N(1) | YES | Electronic Commerce Indicator |
| AVV | Byte[] | BASE64 | Conditional | Required when the card is 3DS enabled |
| XID | Byte[] | BASE64 | Conditional | Required when the card is 3DS enabled |
| CardVerification | 2 | N(2) | YES | Specify whether the card data to be verified or not before storing. |
| Amount | 23.45 | Double | Conditional | Amount of the transaction. Used in the request if CardVerification = 2. |
| Currency | EUR | A(3) | Conditional | ISO 3-character currency code. Used in the request if CardVerification = 2. |
| OutputFormat | xml | String | NO | Output format of data. Can be “xml” or “json”. Default is “xml”. |
Partner Identification
If you are part of our Partners Program, you will need to submit these two additional parameters with each of your requests to the API. This will provide you with analytics about the usage in your myPOS Partners Portal account and help our support teams assist you better.
Note: This requires you to set the API version of your requests to 1.4.1. No other changes in the code/requests are necessary.
| Property | Typical Value | Type | Description |
|---|---|---|---|
| PartnerID | mps-p-XXXXXXXX | String | Identical number for the partner |
| ApplicationID | mps-app-XXXXXXXX | String | Identical number for the application |
Response Properties
| Property | Typical Value | Type | Description |
|---|---|---|---|
| CardToken | 1041333312721BC752C1AB7743D0821AA1C9CA09 | String (50) | Uniquely generated token of the PAN of the card (returned as a response property of IPCIAPurchase). |
| PAN | 4885 | N(4) | Last four digits of the account number (PAN). |
| ExpDate | 1703 | N(4) | Card expire date. Format YYMM. |
| CardType | 1 | N(1) | Please refer to Card Types. |
Important Notes
- You must be PCI SAQ-D certified to use this method due to handling sensitive card data.
- If you're using 3D Secure, make sure to send
AVVandXID. - This API is ideal for subscription-based platforms or wallet services that allow customers to manage their stored cards.
Example Request
<IPC_response>
<IPCmethod>IPCIAStoredCardUpdate</IPCmethod>
<PAN>4885</PAN>
<ExpDate>1703</ExpDate>
<CardType>1</CardType>
<Status>0</Status>
<StatusMsg>Success</StatusMsg>
</IPC_response>