PApaymentology
Card V2

Create Bulk Blank Cards

This web service allows to create blank cards in bulk. Blank card means a card with no account and no customer linked to it. Bank will use this api to create bulk cards in advance and print it through manufacturer.

Customer when requires an instant card, bank will create account, customer and link to blank card.

For linking blank card with new customer, use below api

/pws/v2/pws_link_card_acc

Version 2 create bulk cards api support idempotency:

  • If the previous api request was a success and the client sends the same api_unique_identifier, then the previous response will be returned.
  • If the previous request fails and the client send the sameapi_unique_identifier, then the new create bulk card request will be processed with the incoming API parameters.
post/pws/v2/pws_create_bulk_cards/

Request

  • Base URL
    https://api.uat.paymentology.com/ppws/api
  • URL
    https://api.uat.paymentology.com/ppws/api/pws/v2/pws_create_bulk_cards/
  • Auth
    none declared

Request body

api_call_unique_identifierstring required

Unique number that must be passed at each API request. Identifier to make each API request unique

client_idinteger required

Unique identifier for the client which Paymentology will provide at outset

crd_prdct_idinteger required

Card product id (Need to input correct product id for your card so it will inherit full required properties and be fully linked with business.)

status_nwkinteger required
<p>Status network :</p> <ul> <li class="docBullet">1000 : Fully operational DE39=00</li> <li class="docBullet">1001 : Refer to issuer DE39=01</li> <li class="docBullet">1004 : Capture card DE39=04</li> <li class="docBullet">1005 : Decline all txns DE39=05</li> <li class="docBullet">1008 : Honour with ID DE39=08</li> <li class="docBullet">1041 : Lost card - capture DE39= 41</li> <li class="docBullet">1043 : Stolen card - capture DE39=43</li> <li class="docBullet">1054 : Expired card - report DE39=54</li> <li class="docBullet">1154 : Expire card - don't inform</li> <li class="docBullet">1062 : Restricted card</li> <li class="docBullet">1199 : Void card - report DE39=05</li></ul>
total_cardsinteger required

Total number of cards to be created

user_idstring

User Id of the Customer who triggered the API request.

remarksstring

Remarks for API request

tok_flagsstring
<p>Flags for token to assign various tasks to the card. 0 ==>Flag inactive | 1==> Flag Active . Descriptions for each tok flag bits are given below : </p> <table> <thead> <tr></td><td><strong>TOK_DESCRIPTION</strong></td><td><strong>BIT_POSITION</strong></td> </tr> </thead> <tbody> <tr><td title ="After every transaction, send card balance to the scheme, to allow for balance to be displayed, i.e. for ATM transactions">Send card bal in De54 in next auth</td><td>3</td></tr> <tr><td title ="Should the maximum number of pin retries be exceded, then enable pin unblocking on chip card. Send to issuer to unblock">Send pin unblock to card</td><td>4</td></tr> <tr><td title ="Only allow ecommerce transactions (including MDES and VTS transactions)">Sets card to decline all tranasaction except ecommerce</td><td>5</td></tr> <tr><td title ="Set card to decline all Contactless transaction">Set card to decline all Contactless transaction</td><td>6</td></tr> <tr><td title ="Decline all ecommerce transactions (including MDES and VTS transactions)">Sets card to decline all Ecommerce</td><td>9</td></tr> <tr><td title ="Decline all ATM Cash withdrawal transactions">Sets card to decline all ATM</td><td>10</td></tr> <tr><td title ="Do not allow any balance enquiry transactions">Sets card to deline Bal enquiry over auth</td><td>11</td></tr> <tr><td title ="In the case of POS transactions, the cash disbursement of a portion of the transaction amount is not allowed. The merchant cannot give cash to cardholder as part of the transaction.">Sets card to decline cash back txns</td><td>12</td></tr> <tr><td title ="No transactions are allowed that will credit the card balance, including refunds to the card.">Sets card to decline Auth credit pur/refund (DE3_1=20)</td><td>14</td></tr> <tr><td title ="No payments allowed, only POS and ecommerce transactions and. i.e. MC MoneySend, credit card installments, etc">Sets card to decline credit payment (DE3_1=28)</td><td>19</td></tr> <tr><td title ="Only transactions in the base currency are allowed, decline any transaction in a non-base currency">Sets card to decline non base currency txn</td><td>20</td></tr> <tr><td title ="No account verification requests should be allowed">Sets card to decline all account enq (de61_7=8)</td><td>21</td></tr> <tr><td title ="Only approve transactions where the card is present. If card not present, decline transaction">sets card to decline card not present txns</td><td>22</td></tr> <tr><td title ="card Where the card information is provided but neither the cardholder or the card are physically present (i.e. mail-order) decline the transaction. ">sets card to decline Cardholder not present txns</td><td>23</td></tr> <tr><td title ="CATM Fallback - where a chip-card is used at chip-capable ATM, do not allow fallback to magnetic strip">sets card to decline failover to mag at emv capable atm</td><td>24</td></tr> <tr><td title ="ATM Fallback - where a chip-card is used at an ATM (chip-capable or not) do not allow fallback to magnetic stripe">sets card to decline mag at atm</td><td>25</td></tr> <tr><td title ="POS Fallback - where a chip-card is used at chip-capable POS, allow fallback to to magnetic strip">Alow if fallback chp->mag at chp capable pos DE22_1=80</td><td>26</td></tr> <tr><td title ="POS Fallback - when the magnetic strip is used for a transaction, only allow the transaction of the entire track can be read, i.e. only PAN sent then decline transaction">Allow if de22_1=02 & De48_88 =Y</td><td>27</td></tr> <tr><td title ="Sets card to approve if AVS match fails">Sets card to approve if AVS match fails</td><td>28</td></tr> <tr><td title ="Do not allow subscription transactions, decline recurring transactions">Set card to decline Recurring transaction</td><td>29</td></tr> </tbody> </table>
exp_datestring
<p>Expiry Date, accepted format yyyy-mm-dd hh:mm:ss.<br />If not provided, default expiry from product is inherited.</p>
client_card_ref'range[-infinity, 100]'

Unique client reference relating to order, card or customer where present should always be quoted in correspondence.

image_namestring

Image template name for the card to be generated. This field is case sensitive. Card image has to be populated as configured in paycontrol.

emboss_namestring

Name that appears in front of the card.

auth_typestring
<p>Authorization Type :</p> <ul> <li class="docBullet">0==&gt;Internal</li> <li class="docBullet">1==&gt;External</li> <li class="docBullet">2==&gt; Notification</li> </ul>

Example request

{
  "api_call_unique_identifier": "438574845790657485",
  "client_id": 760131,
  "crd_prdct_id": 67,
  "status_nwk": 1000,
  "total_cards": 50,
  "tok_flags": "00000000000000000000000000000000",
  "exp_date": "2025-01-01 00:00:00",
  "client_card_ref": "client choice",
  "image_name": "paymentology",
  "emboss_name": "Akshay Patel",
  "auth_type": "0",
  "manufacturer_detail": {
    "card_manuf_id": 12,
    "atm_lang": "01",
    "carrier_type": "1",
    "carrier_insrt1": 1,
    "carrier_insrt2": 1,
    "carrier_lang": "ENG",
    "envelope_ref": 1,
    "perso_fields": "11111"
  },
  "delivery_detail": {
    "del_title": "Mr",
    "del_fname": "Akshay",
    "del_sname": "Patel",
    "del_addr1": "London",
    "del_addr2": "Nadipur",
    "del_city": "Pokhara",
    "del_country": "Nepal",
    "del_email": "akshay@paymentology.com",
    "del_mobile": "+9779846545555",
    "del_method": 1,
    "del_region": "ENG"
  }
}

Response

Successful Response

Example response

{
  "header": {
    "error_desc": "success"
  },
  "body": [
    {
      "expiry": "03/21",
      "token": 788193393,
      "last_four_digit_number": "0082"
    }
  ]
}

Changes

No recorded changes to this operation across all 2 revisions of this API.