Enhancement #14191
[VST2 - Backoffice_API] Add New Card Fields
| Status: | Closed | Start date: | 23 August 2022 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 29 August 2022 | |
| Assignee: | wong yen chen | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Background
Netmember would like to align the naming convention on card related fields and add an additional field of [cardFace] to bill payment.
Enhancement/Changes
Change of name
1. cardType --> cardScheme
2. cardName --> cardType
New field
1. cardFace
Expectation
1. API specification update
2. Changed all the related API
3. Changed all the related field(s) in Backoffice
History
#1 Updated by wong yen chen about 2 years ago
[Update]
Enhancement/Changes
Change of name
1. cardType --> cardScheme (e.g. VISA, MAST, UPAY, JCB)
New field
1. cardFace (not sure what will they pass)
2. productCode (e.g. VJ, MCP...)
#2 Updated by wong yen chen about 2 years ago
[Update] Code of Card Scheme
V: VISA
M: MASTERCARD
J: JCB
U: UNION PAY
#3 Updated by Shafiqah Rahni about 2 years ago
- Status changed from New to Resolved
- Assignee changed from Shafiqah Rahni to wong yen chen
- % Done changed from 0 to 100
BillPaymentApi
Revision: 218743
Change card type -> card scheme
Add cardFace, productCode
1. - update cardType to cardScheme
- add cardFace, productCode in getBillPayment response
2. - update cardType to cardScheme
- add cardFace, productCode in performBillPayment request
3. - update cardType to cardScheme
- add cardFace, productCode in getTrxRecordDetail response
4. - update cardType to cardScheme
- add cardFace, productCode in getBillPaymentDetail response
Revision: 218762
Update Code of Card Scheme -> V,M,J,U
BackOffice
Revision: 218741
Change card type -> card scheme
Add cardFace, productCode
1. Schedule/Recurrent payment detail
2. Bill History detail
Revision: 218742
Update Card type drop down
1. Daily report search criteria
#4 Updated by wong yen chen about 2 years ago
Tested all good.
#5 Updated by wong yen chen about 2 years ago
- Status changed from Resolved to Closed
Deployed to all environment @ 29/8/2022