Further information about our Issuing API.
- Authorization transaction types
- Account types
- Card statuses
- Response codes
- Date range types
- Viva Payments Event Identifier
- Clearing Transaction Type Id
- Get Support
Authorization transaction types
Note: Refers to Mastercard-defined
Cardholder Transaction Type Code:
|Id||Transaction Type||Account Action||Authorization / Clearing Presentment||Clearing Transaction Type ID|
|00||Purchase||Debit||Both||00 or 18 ; for details see Clearing Transaction Type Id|
|09||Purchase with Cashback||Debit||Both||09|
|20||Purchase Return/Refund||Credit||Clearing only||20|
|30||Balance Inquiry||Inquiry||Authorization Only||-|
|91||PIN Unblock||PIN Management||Authorization Only||-|
|92||PIN Change||PIN Management||Authorization Only||-|
Details on account types:
|30||Credit Card Account||From/To|
Please see our card statuses page for details.
Describes the applicable (ISO) response codes returned by the partner on an authorization request:
|Approve||00||Approved or completed successfully||Approve|
|Insufficient Funds||51||Balance does not suffice for the requested amount||Decline|
|Transaction not permitted to cardholder||57||Decline due to partner’s fraud rules, compliance requirements etc.||Decline|
|Restricted card||62*||Decline due to partner’s fraud rules etc.||Decline|
|Do not honor||05||Generic Decline||Decline|
* For use when the card has been temporarily suspended on the partner side, while it appears active at the issuer end. As a result, authorization requests are forwarded to the partner.
In this case, the appropriate API calls (Retrieve card information and Set card status) should be used to update card status information.
Date range types
Details on date range types:
Viva Payments Event Identifier
An Event Identifier represents a systemic code, indicating the specific reason for which a request failed.
Even though the API error code (HTTP Status code) should, in most cases, be adequate to indicate the reason of the failure, the EventId goes a step further to pinpoint the concrete reason.
EventIds related to the Issuing API:
|11000||CardManagementValidationFailed||Indicates that a Card Product was not found|
|4700 - 4710||CardGenerationFailed||Indicates that a procedure related to card number or PIN generation failed|
|12000||EmbossingRequestValidationFailed||Indicates that an embossing requests does not contain the required data to complete (e.g. productId is missing)|
|12002||CardActivationValidationFailed||Returned when a card activation request does not contain the required data (e.g. cardholder’s mobile is missing) or the card’s status is not Inactive|
Clearing Transaction Type Id
Details on clearing transaction types:
|Clearing Transaction Type Id||Corresponding Authorization Transaction Type Id||Description|
|00||00||Purchase (Goods and Services)|
|01||01||ATM Cash Withdrawal|
|09||09||Purchase (Goods and Services) with Cash Back|
|18||00||Unique Transaction (requires unique MCC)*|
|20||20||Credit (Purchase Return) Note: only present in clearing files|
* List of unique Merchant Category Codes:
4829- Money Transfer
6050- Quasi Cash Financial Institution
6051- Quasi Cash–Merchant
7801- Internet Gambling
7802- Government Licensed Horse/Dog Racing
7995- Gambling Transactions
If you would like to integrate with Viva Wallet, or if you have any queries about our products and solutions, please see our Get Support page to see how we can help!