Renew Card

<p>The identifier for this request. This endpoint does not provide idempotent retries. Do not automatically resend a request after a timeout or lost response, with either the same identifier or a new one. Reconcile the original outcome before making another renewal request. Use Card Renewal V2 when you need idempotent retries.</p>

<p>card action :</p><ul><li class="docBullet">1==&gt;Replacement (new pan + new token + new expiry generated)</li><li class="docBullet">2==&gt; Renew (old pan + old token + new expiry generated)</li></ul>

<p>How to deliver image back to client. Example :</p><ul><li class="docBullet">1==&gt; Image in plain base64, encrypted pan, cvv, token, expiry, and emboss_name).</li><li class="docBullet">2 ==&gt; Image in byte encrypted, encrypted pan, cvv, token, expiry, and emboss_name.</li><li class="docBullet">3 ==&gt; Data details JSON (encrypted pan, cvv, token, expiry, and emboss_name but no image.</li><li class="docBullet">4 ==&gt; Image in byte encrypted, masked pan back, cvv, token, expiry, and emboss_name.</li></ul>

<p>Show or hide pan, cvv, expiry, token, and emboss_name in response image. 1 means show and 0 means hide</p><ul><li class="docBullet"><code>1</code> — pan</li><li class="docBullet"><code>2</code> — cvv</li><li class="docBullet"><code>3</code> — expiry</li><li class="docBullet"><code>4</code> — emboss_name</li><li class="docBullet"><code>5</code> — token</li></ul><p>EG: 00111 (Hide pan and cvv but show expiry, token, and emboss_name).</p>

<p>Show or hide pan, cvv, expiry, token, and emboss_name in response json. 1 means show and 0 means hide</p><ul><li class="docBullet"><code>1</code> — pan</li><li class="docBullet"><code>2</code> — cvv</li><li class="docBullet"><code>3</code> — expiry</li><li class="docBullet"><code>4</code> — token</li><li class="docBullet"><code>5</code> — emboss_name</li></ul><p>EG: 00111 (Hide pan and cvv but show expiry, token, and emboss_name).</p>

<p>The optional reason for renewal or replacement, up to 255 characters. If omitted, no reason is supplied with the request.</p>

<p>The network status to assign as part of renewal or replacement. You do not need to call <code>pws_set_card_status</code> first to apply this value. For a physical-card renewal with <code>card_action=2</code> and an unchanged card product, Lume applies this status immediately to the current card and stores the same status for the pending renewal. You cannot specify separate statuses for them in this request.</p><p>Allowed values:</p><ul><li class="docBullet"><code>1000</code> — Fully operational.</li><li class="docBullet"><code>1001</code> — Refer to issuer.</li><li class="docBullet"><code>1004</code> — Capture card.</li><li class="docBullet"><code>1005</code> — Decline all transactions.</li><li class="docBullet"><code>1007</code> — Decline all transactions.</li><li class="docBullet"><code>1008</code> — Honor with ID.</li></ul><p>Values outside this list fail request validation. Default: <code>1000</code>. Omitting this field applies <code>1000</code>; it does not preserve the current status. To keep an otherwise usable card operational while renewal is pending, specify <code>1000</code> or omit this field. Specifying <code>1005</code> blocks the current card and stores <code>1005</code> for the renewal.</p><p>Lume checks the existing card separately. Existing statuses <code>1005</code>, <code>1006</code>, <code>1007</code>, <code>1041</code>, <code>1043</code>, <code>1054</code>, <code>1154</code>, and <code>1062</code> do not by themselves prevent renewal; other renewal checks still apply. You do not need to set one of these statuses before renewal. This list describes existing-card eligibility, not additional allowed values for this request.</p><p>An existing card with status <code>1009</code> or <code>1199</code> is void and cannot be renewed or replaced. Existing statuses <code>1010</code> (due payment block) and <code>1011</code> (KYC/AML hold) also prevent renewal or replacement. The requested <code>status_nwk</code> cannot override these restrictions.</p><p>DE39 is the payment network response-code field; the listed values explain the authorization response associated with each status.</p>

<p>The card control flags, encoded as exactly 32 characters containing only <code>0</code> and <code>1</code>. Positions are one-based, counted from left to right: position 1 is the leftmost character. <code>1</code> enables a flag; <code>0</code> disables it. Omit this field to retain the existing card's flags. A supplied value replaces all 32 flags; an all-zero value clears them.</p><p>For example, <code>00001000000000000000000000000000</code> sets only position 5 (decline transactions other than e-commerce). Other card status and authorization checks still apply. To retain other restrictions, preserve their positions in the supplied value.</p><ul><li class="docBullet"><code>3</code> — Send card bal in De54 in next auth</li><li class="docBullet"><code>4</code> — Send pin unblock to card</li><li class="docBullet"><code>5</code> — Set card to decline all tranasaction except ecommerce</li><li class="docBullet"><code>6</code> — Set card to decline all Contactless transaction</li><li class="docBullet"><code>9</code> — Set card to decline all Ecommerce</li><li class="docBullet"><code>10</code> — Set card to decline all ATM</li><li class="docBullet"><code>11</code> — Set card to decline Bal enquiry over auth</li><li class="docBullet"><code>12</code> — Set card to decline cash back txns</li><li class="docBullet"><code>14</code> — Set card to decline Auth credit pur/refund (DE3_1=20)</li><li class="docBullet"><code>19</code> — Set card to decline credit payment (DE3_1=28)</li><li class="docBullet"><code>20</code> — Set card to decline non base currency txn</li><li class="docBullet"><code>21</code> — Set card to decline all account enq (de61_7=8)</li><li class="docBullet"><code>22</code> — Set card to decline card not present txns</li><li class="docBullet"><code>23</code> — Set card to decline Cardholder not present txns</li><li class="docBullet"><code>24</code> — Set card to decline failover to mag at emv capable atm</li><li class="docBullet"><code>25</code> — Set card to decline mag at atm</li><li class="docBullet"><code>26</code> — Alow if fallback chp->mag at chp capable pos DE22_1=80</li><li class="docBullet"><code>27</code> — Allow if de22_1=02 & De48_88 =Y</li><li class="docBullet"><code>28</code> — Set card to approve if AVS match fails</li><li class="docBullet"><code>29</code> — Set card to decline Recurring transaction</li></ul><p>In the list, DE means a payment-message data element: DE54 carries balance information, DE3 identifies the transaction type, DE61 carries point-of-sale information, DE22 identifies the card-entry method, and DE48 carries additional transaction data. ATM means automated teller machine; POS means point of sale; AVS means address verification service. MDES and VTS are Mastercard and Visa digital token services. EMV refers to chip-card payment standards.</p>

<p>Card product id.</p><p>1. If no card product id sent, then default value set at card is taken.</p><p>2. If card product id is sent different from one set during card create, it will act as replacement i.e. new pan, new token since bin range value will be different.</p>

<p>Expiry date during renewal/replacement. Accepted format yyyy-mm-dd hh:mm:ss<br /><br />If client send expiry in request, same is assigned during replacement/renewal.</p><p>If expiry date is not send by client, automatic expiry date is computed from product level. This applies to both renewal and replacement.</p><p>Note : There could be a scenario where weak cvv is computed during renewal/replacement. Example 111, 222</p><p>1. Replacement(new pan, new token, new expiry)</p><ul><li>If weak cvv is computed as per pan selected, system will internally discard this pan and look for new pan such that new cvv is computed.</li></ul><p>2. Renewal (same pan, same token, new expiry). Since pan should not be changed during renewal, so we change expiry such that new cvv is computed.</p><ul><li>If client send expiry in request and weak cvv is computed, then below response will be sent to client.<br /><span style="color: #333399;"><strong>weakCvv (1028, Weak cvv computed. Change expiry and resend request again)</strong></span><br /><br /></li><li>If client do not send expiry in request, then automatic expiry is computed from product level. Now if a weak cvv is computed, then system will internally increase 1 month to automatic computed expiry and process request again</li></ul>

<p>Inherit existing card rules. Based on value provide, it will either inherit existing rules or skip.&nbsp;</p><ul><li>0 ==&gt; Inherit</li><li>1 ==&gt; Donot inheri</li></ul><p>Default value is 0 i.e. always inherit</p>