Data EXchange Spec V231
Data EXchange Spec V231
Data eXchange
Page 1
Document Enhancement Summary
The Data eXchange specification is published quarterly the last Friday of the month - March, June,
September and December. The version indicates the published date with the major number
representing the year and the minor number representing the completed quarter.
All current implementations of Data eXchange will continue to function properly. No changes
were made that will impact existing Data eXchange applications.
Page 2
Contents
1 Document Revision History ................................................................................................................................. 13
2 Overview ............................................................................................................................................................... 16
3 Security................................................................................................................................................................. 20
3.1 Server Authentication.................................................................................................................. 20
3.2 TLS (Transport Layer Security) ................................................................................................... 20
3.3 Client ID Verification ................................................................................................................... 21
3.4 Cardnumber Verification ............................................................................................................. 21
4 Server Response .................................................................................................................................................. 23
4.1 Completion Status....................................................................................................................... 23
4.2 Exceptions .................................................................................................................................. 24
5 Exception Handling .............................................................................................................................................. 27
5.1 TService Level Expectations ....................................................................................................... 27
5.1.1 Availability ............................................................................................................................................ 27
5.1.2 Performance ......................................................................................................................................... 27
5.1.3 Problem/Request Management ............................................................................................................. 28
5.1.4 Disaster/Recovery ................................................................................................................................. 28
6 SEARCHXML Request.......................................................................................................................................... 30
6.1 Search by Name ......................................................................................................................... 31
6.1.1 Request Parameters ............................................................................................................................. 31
6.1.2 Sample URL and Response .................................................................................................................. 31
6.1.3 Tag and Property Reference.................................................................................................................. 36
6.2 Search by Criteria Request ......................................................................................................... 39
6.2.1 Request Parameters ............................................................................................................................. 39
6.2.2 Sample URL Request and Response..................................................................................................... 40
6.2.3 Tag and Property Reference.................................................................................................................. 43
7 GETDATAXML Request ....................................................................................................................................... 46
7.1 Account Memo Information ......................................................................................................... 49
7.1.1 Request Parameters ............................................................................................................................. 49
7.1.2 Sample URL Request and Response..................................................................................................... 49
7.1.3 Tag and Property Information ................................................................................................................ 53
7.2 Card Summary Information ......................................................................................................... 57
7.2.1 Request Parameters ............................................................................................................................. 57
7.2.2 Sample URL and Response .................................................................................................................. 59
7.2.3 Tag and Property Reference.................................................................................................................. 62
7.3 Card Summary Information and eStatement Enrollment Status ................................................... 75
7.3.1 Request Parameters ............................................................................................................................. 75
7.3.2 Sample URL and Response .................................................................................................................. 76
7.3.3 Tag and Property Reference.................................................................................................................. 79
7.4 Cardholder Information ............................................................................................................... 88
Page 3
7.4.1 Request Parameters ............................................................................................................................. 88
7.4.2 Sample URL and response.................................................................................................................... 89
7.4.3 Tag and Property Reference.................................................................................................................. 91
7.5 Extended Cardholder Information ................................................................................................ 95
7.5.1 Request Parameters ............................................................................................................................. 95
7.5.2 Sample URL and Response .................................................................................................................. 96
7.5.3 Tag and Property Information ................................................................................................................ 99
7.6 Payment History Information ..................................................................................................... 106
7.6.1 Request Parameters ........................................................................................................................... 106
7.6.2 Sample URL and response.................................................................................................................. 107
7.6.3 Tag and Property Reference................................................................................................................ 110
7.7 Payment On Demand - Get Info ................................................................................................ 123
7.7.1 Request Parameters ........................................................................................................................... 123
7.7.2 Sample URL and response.................................................................................................................. 123
7.7.3 Tag and Property Reference................................................................................................................ 125
7.8 Recent Activity Information........................................................................................................ 130
7.8.1 Request Parameters ........................................................................................................................... 130
7.8.2 Sample URL and response.................................................................................................................. 133
7.8.3 Tag and Property Reference................................................................................................................ 137
7.9 Rewards/Rebates Information ................................................................................................... 156
7.9.1 Traditional Rewards ............................................................................................................................ 156
7.9.2 Premium Loyalty Platform.................................................................................................................... 156
7.9.3 Request Parameters ........................................................................................................................... 156
7.9.4 Sample URL ....................................................................................................................................... 157
7.9.5 Sample Response for Traditional Rewards........................................................................................... 157
7.9.6 Tag and Property Reference for Traditional Rewards ........................................................................... 158
7.9.7 Sample Response for PLP .................................................................................................................. 160
7.9.8 Tag and Property Reference for PLP ................................................................................................... 162
7.10 Special Consolidated Account Information ................................................................................ 169
7.10.1 Request Parameters ....................................................................................................................... 169
7.10.2 Sample URL and response ............................................................................................................. 170
7.10.3 Tag and Property Reference ........................................................................................................... 172
7.11 Statement Balances and Summary Data ................................................................................... 189
7.11.1 Request Parameters ....................................................................................................................... 189
7.11.2 Sample URL and response ............................................................................................................. 190
7.11.3 Tag and Property Reference ........................................................................................................... 194
7.12 Statement Data, Last Cycle....................................................................................................... 206
7.12.1 Request Parameters ....................................................................................................................... 207
7.12.2 Sample URL and response ............................................................................................................. 209
7.12.3 Tag and Property Reference ........................................................................................................... 212
7.13 Statement Data, One (1) Prior Cycle ......................................................................................... 221
7.13.1 Request Parameters ....................................................................................................................... 222
7.13.2 Sample URL and response ............................................................................................................. 224
7.13.3 Tag and Property Reference ........................................................................................................... 227
7.14 Statement Data, Two (2) Prior Cycles ....................................................................................... 237
7.14.1 Request Parameters ....................................................................................................................... 238
7.14.2 Sample URL and response ............................................................................................................. 240
7.14.3 Tag and Property Reference ........................................................................................................... 243
7.15 Statement Data, Single Specified Cycle .................................................................................... 252
7.15.1 Request Parameters ....................................................................................................................... 253
7.15.2 Sample URL and response ............................................................................................................. 254
7.15.3 Tag and Property Reference ........................................................................................................... 258
Page 4
7.16 Statement Data, Last Three (3) Cycles...................................................................................... 263
7.16.1 Request Parameters ....................................................................................................................... 264
7.16.2 Sample URL and response ............................................................................................................. 265
7.16.3 Tag and Property Reference ........................................................................................................... 272
7.17 Statement Data, Last Three (3) Cycles and Recent Activity ....................................................... 286
7.17.1 Request Parameters ....................................................................................................................... 287
7.17.2 Sample URL and response ............................................................................................................. 290
7.17.3 Tag and Property Reference ........................................................................................................... 298
7.18 Statement Summaries, All Available .......................................................................................... 321
7.18.1 Request Parameters ....................................................................................................................... 321
7.18.2 Sample URL and response ............................................................................................................. 322
7.18.3 Tag and Property Reference ........................................................................................................... 326
7.19 CVV2 Validation........................................................................................................................ 334
7.19.1 Request Parameters ....................................................................................................................... 334
7.19.2 Sample URL and Response ............................................................................................................ 334
7.19.3 Tag and Property Reference ........................................................................................................... 335
7.20 Promotional / Protected Balances ............................................................................................. 336
7.20.1 Request Parameters ....................................................................................................................... 336
7.20.2 Sample URL and Response ............................................................................................................ 336
7.20.3 Tag and Property Reference ........................................................................................................... 338
7.21 FICO Score............................................................................................................................... 340
7.21.1 Request Parameters ....................................................................................................................... 341
7.21.2 Sample URL and Response ............................................................................................................ 341
7.21.3 Tag and Property Reference ........................................................................................................... 342
7.22 PFM.......................................................................................................................................... 343
7.22.1 Request Parameters ....................................................................................................................... 343
7.22.2 Sample URL Request and Response .............................................................................................. 343
7.22.3 Tag and Property Reference ........................................................................................................... 345
7.23 Multiple Function Call ................................................................................................................ 349
7.23.1 Request Parameters ....................................................................................................................... 349
7.23.2 Sample URL and Response ............................................................................................................ 350
7.23.3 Tag and Property Reference ........................................................................................................... 360
7.24 Redemption History .................................................................................................................. 369
7.24.1 Request Parameters ....................................................................................................................... 369
7.24.2 Sample URL and Response ............................................................................................................ 370
7.24.3 Tag and Property Reference ........................................................................................................... 371
7.25 Cardholder Plastics ................................................................................................................... 372
7.25.1 Request Parameters ....................................................................................................................... 372
7.25.2 Sample URL and Response ............................................................................................................ 372
7.25.3 Tag and Property Reference ........................................................................................................... 375
7.26 Dispute History ......................................................................................................................... 378
7.26.1 Request Parameters ....................................................................................................................... 378
7.26.2 Sample URL and Response ............................................................................................................ 378
7.26.3 Tag and Property Reference ........................................................................................................... 380
7.27 Retrieve Emboss requests ........................................................................................................ 382
7.27.1 Request Parameters ....................................................................................................................... 382
7.27.2 Sample URL and Response............................................................................................................ 382
7.27.3 Tag and Property Reference ........................................................................................................... 383
7.28 Statement History ..................................................................................................................... 385
7.28.1 Request parameters ....................................................................................................................... 385
7.28.2 Sample URL and response ............................................................................................................. 385
7.28.3 Tag and Property Reference ........................................................................................................... 388
Page 5
7.29 Credit Bureau Reporting History ................................................................................................ 390
7.29.1 Request parameters ....................................................................................................................... 390
7.29.2 Sample URL and response ............................................................................................................. 390
7.29.3 Tag and Property Reference ........................................................................................................... 391
7.30 Payment Allocation ................................................................................................................... 395
7.30.1 Request parameters ....................................................................................................................... 395
7.30.2 Sample URL and Response............................................................................................................ 395
7.30.3 Tag and Property Reference ........................................................................................................... 398
8 ACCTXML ........................................................................................................................................................... 400
8.1 New Cardholder Account .......................................................................................................... 402
8.1.1 Request Parameters ........................................................................................................................... 402
8.1.2 Sample URL and response.................................................................................................................. 412
8.1.3 Tag and Property Reference................................................................................................................ 415
8.2 New Generated Cardholder Account ......................................................................................... 416
8.2.1 Request Parameters ........................................................................................................................... 416
8.2.2 Sample URL and response.................................................................................................................. 428
8.2.3 Tag and Property Reference................................................................................................................ 431
8.3 Declined ICS Application........................................................................................................... 432
8.3.1 Request Parameters ........................................................................................................................... 432
8.3.2 Sample URL and response.................................................................................................................. 433
8.4 Account Transfer ...................................................................................................................... 435
8.4.1 Request Parameters ........................................................................................................................... 435
8.4.2 Sample URL and Response ................................................................................................................ 439
8.4.3 Tag and Property Reference................................................................................................................ 440
8.5 Activate/Deactivate Card........................................................................................................... 441
8.5.1 Request Parameters ........................................................................................................................... 441
8.5.2 Sample URL and Response ................................................................................................................ 442
8.5.3 Tag and Property Reference................................................................................................................ 443
8.6 Order Replacement Card .......................................................................................................... 444
8.6.1 Request Parameters ........................................................................................................................... 444
8.6.2 Sample URL and Response ................................................................................................................ 446
8.6.3 Tag and Property Reference................................................................................................................ 448
8.7 Order PIN Letter ....................................................................................................................... 450
8.7.1 Request parameters............................................................................................................................ 450
8.7.2 Sample URL and response.................................................................................................................. 450
8.7.3 Tag and Property Reference................................................................................................................ 452
8.8 External Status ......................................................................................................................... 454
8.8.1 Request Parameters ........................................................................................................................... 454
8.8.2 Sample URL and Response ................................................................................................................ 455
8.8.3 Tag and Property Reference................................................................................................................ 457
8.9 Authorization and Transaction Posting ...................................................................................... 458
8.9.1 Request parameters............................................................................................................................ 459
8.9.2 Sample URL and response.................................................................................................................. 460
8.9.3 Tag and Property Reference................................................................................................................ 461
8.9.4 Authorization Error Codes ................................................................................................................... 462
8.10 Submit Disputes........................................................................................................................ 470
8.10.1 Request Disputes Reason Codes.................................................................................................... 470
8.10.2 Submit Dispute ............................................................................................................................... 472
8.11 Lost .......................................................................................................................................... 475
8.11.1 Request Parameters ....................................................................................................................... 475
8.11.2 Sample URL and response ............................................................................................................. 481
Page 6
8.11.3 Tag and Property Reference ........................................................................................................... 483
8.12 Instant Issue EMV/Contactless Omaha ..................................................................................... 484
8.12.1 Create new account and set PIN information ................................................................................... 484
8.12.2 Set PIN Offset ................................................................................................................................ 494
8.12.3 PIN Verification Number ................................................................................................................. 497
8.12.4 EMV Data Request ......................................................................................................................... 500
8.12.5 Instant Issue Details ....................................................................................................................... 502
8.12.6 Retreive Chip Data Detail................................................................................................................ 510
8.12.7 Post Chip Data Detail ..................................................................................................................... 513
8.13 Redeem Rebates ...................................................................................................................... 516
8.13.1 Request Parameters ....................................................................................................................... 517
8.13.2 Sample URL and Response ............................................................................................................ 517
8.13.3 Tag and Property Reference ........................................................................................................... 518
8.13.4 Error Messages .............................................................................................................................. 518
8.14 Account Updater ....................................................................................................................... 520
8.14.1 Request Parameters ....................................................................................................................... 520
8.14.2 Sample URL and Response ............................................................................................................ 522
8.14.3 Tag and Property Reference ........................................................................................................... 523
8.15 Authorization............................................................................................................................. 524
8.15.1 Request parameters ....................................................................................................................... 524
8.15.2 Sample URL and response ............................................................................................................. 525
8.15.3 Tag and Property Reference ........................................................................................................... 526
8.16 Post Transaction ....................................................................................................................... 528
8.16.1 Request parameters ....................................................................................................................... 528
8.16.2 Sample URL and response ............................................................................................................. 529
8.16.3 Tag and Property Reference ........................................................................................................... 530
8.17 Cancel Emboss requests .......................................................................................................... 531
8.17.1 Request Parameters ....................................................................................................................... 531
8.17.2 Sample URL and Response............................................................................................................ 531
8.17.3 Tag and Property Reference ........................................................................................................... 532
8.18 EMV PIN Change ..................................................................................................................... 533
8.18.1 Request Parameters ....................................................................................................................... 533
8.18.2 Sample URL and Response ............................................................................................................ 533
8.18.3 Tag and Property Reference ........................................................................................................... 534
8.19 Refund Rebates ........................................................................................................................ 535
8.19.1 Request Parameters ....................................................................................................................... 535
8.19.2 Sample URL and Response ............................................................................................................ 535
8.19.3 Tag and Property Reference ........................................................................................................... 536
8.20 Omaha PIN Resets ................................................................................................................... 537
8.20.1 Request parameters ....................................................................................................................... 537
8.20.2 Sample URL and response ............................................................................................................. 538
8.20.3 Tag and Property Reference ........................................................................................................... 539
9 CompDataXML.................................................................................................................................................... 541
9.1 Create Company....................................................................................................................... 542
9.1.1 Request Parameters ........................................................................................................................... 542
9.1.2 Sample URL and Response: ............................................................................................................... 547
9.1.3 Tag and Property Reference................................................................................................................ 549
9.2 Delete Company ....................................................................................................................... 550
9.2.1 Request Parameters ........................................................................................................................... 550
9.2.2 Sample URL and Response ................................................................................................................ 550
9.2.3 Tag and Properrty Reference .............................................................................................................. 551
Page 7
9.3 Update Company ...................................................................................................................... 552
9.3.1 Request Parameters ........................................................................................................................... 552
9.3.2 Sample URL and Response ................................................................................................................ 554
9.3.3 Tag and Property Reference................................................................................................................ 556
9.4 Company Accounts ................................................................................................................... 557
9.4.1 Request Parameters ........................................................................................................................... 557
9.4.2 Sample URL and Response ................................................................................................................ 557
9.4.3 Tag and Property Reference................................................................................................................ 559
9.5 Company Information................................................................................................................ 560
9.5.1 Request Parameters ........................................................................................................................... 560
9.5.2 Sample URL and Response ................................................................................................................ 560
9.5.3 Tag and Property Reference................................................................................................................ 563
9.6 Company Memos...................................................................................................................... 565
9.6.1 Request Parameters ........................................................................................................................... 565
9.6.2 Sample URL and Response ................................................................................................................ 565
9.6.3 Tag and Property Reference................................................................................................................ 567
9.7 Company Recent Activity .......................................................................................................... 568
9.7.1 Request Parameters ........................................................................................................................... 568
9.7.2 Sample URL and Response ................................................................................................................ 568
9.7.3 Tag and Property Reference................................................................................................................ 571
9.8 Add Company Memo ................................................................................................................ 577
9.8.1 Request Parameters ........................................................................................................................... 577
9.8.2 Sample URL and Response ................................................................................................................ 577
9.8.3 Tag and Property Reference................................................................................................................ 578
9.9 Company Payment Information ................................................................................................. 579
9.10 Company Credit Line Disbursments .......................................................................................... 579
9.11 Company Change Account Type............................................................................................... 579
10 NEWMEMOXML Request ................................................................................................................................... 580
10.1 Create Memo ............................................................................................................................ 581
10.1.1 Request Parameters ....................................................................................................................... 581
10.1.2 Sample URL and Response............................................................................................................ 582
10.1.3 Tag and Property Reference ........................................................................................................... 583
11 CHUPDATEXML Request ................................................................................................................................... 585
11.1 Update Cardholder Information ................................................................................................. 586
11.1.1 Request Parameters ....................................................................................................................... 586
11.1.2 Sample URL and Response............................................................................................................ 588
11.1.3 Tag and Property Reference ........................................................................................................... 589
11.1.4 Update Cardholder Information - Working with Authorized Users...................................................... 590
11.2 Add, Update, View Cardholder Information................................................................................ 594
11.2.1 View Cardholder Information ........................................................................................................... 594
11.2.2 Add Cardholder .............................................................................................................................. 604
11.2.3 Update Cardholder ......................................................................................................................... 608
11.2.4 Delete Cardholder .......................................................................................................................... 611
Request Parameters ......................................................................................................................................... 611
Sample URL and Response .............................................................................................................................. 611
Tag and Property Information ............................................................................................................................ 612
12 CLADJUSTXML Request .................................................................................................................................... 613
12.1 Credit Limit Adjustment ............................................................................................................. 614
Page 8
12.1.1 Request parameters ....................................................................................................................... 614
12.1.2 Sample URL and response ............................................................................................................. 615
12.1.3 Tag and Property Reference ........................................................................................................... 618
13 PAYXML Request ............................................................................................................................................... 620
13.1 Payment on Demand ................................................................................................................ 622
13.1.1 Request parameters ....................................................................................................................... 624
13.1.2 Sample URL and response ............................................................................................................. 625
13.1.3 Tag and Property Reference ........................................................................................................... 627
13.1.4 Payment on Demand from Savings Account .................................................................................... 627
13.1.5 Payment on Demand Alternative Processing ................................................................................... 627
13.2 Right Time Payment ................................................................................................................. 629
13.2.1 Request parameters ....................................................................................................................... 629
13.2.2 Sample URL and response ............................................................................................................. 631
13.2.3 Tag and Property Reference ........................................................................................................... 632
13.3 Reverse Right Time Payment.................................................................................................... 634
13.3.1 Request parameters ....................................................................................................................... 634
13.3.2 Sample URL and response ............................................................................................................. 635
13.3.3 Tag and Property Reference ........................................................................................................... 636
13.4 Balance Consolidation .............................................................................................................. 639
13.4.1 Request parameters ....................................................................................................................... 639
13.4.2 Sample URL and response ............................................................................................................. 642
13.4.3 Tag and Property Reference ........................................................................................................... 644
13.5 Automatic Payments ................................................................................................................. 646
13.5.1 Request Parameters ....................................................................................................................... 646
13.5.2 Sample URL and Response ............................................................................................................ 647
13.5.3 Tag and Property Reference ........................................................................................................... 648
13.6 eBalcon .................................................................................................................................... 649
13.6.1 Use Case ....................................................................................................................................... 649
13.6.2 Lender Lookup ............................................................................................................................... 650
13.6.3 State Zip Validation ........................................................................................................................ 653
13.6.4 Submit eBalCon Request ................................................................................................................ 655
13.6.5 Error Messages .............................................................................................................................. 660
13.7 Onetime Future Payments ........................................................................................................ 662
13.7.1 Submit a One Time Future Payment ............................................................................................... 662
13.7.2 List of a One Time Future Payment ................................................................................................. 663
13.7.3 Delete a One Time Future Payment ................................................................................................ 665
14 SENDDATAXML Request ................................................................................................................................... 668
14.1 Non-Monetary Transaction ........................................................................................................ 669
14.1.1 Request parameters ....................................................................................................................... 669
14.1.2 Sample URL and response ............................................................................................................. 671
14.1.3 Setting Alternate Addresses ............................................................................................................ 673
14.1.4 Travel Notifications ......................................................................................................................... 676
15 ESTMTXML ......................................................................................................................................................... 677
15.1 eStatement Enrollment.............................................................................................................. 679
15.1.1 Request parameters ....................................................................................................................... 679
15.1.2 Sample URL and response ............................................................................................................. 680
15.1.3 Tag and Property Reference ........................................................................................................... 681
15.2 Cancel eStatement Enrollment .................................................................................................. 682
15.2.1 Request parameters ....................................................................................................................... 682
Page 9
15.2.2 Sample URL and response ............................................................................................................. 682
15.2.3 Tag and Property Reference ........................................................................................................... 683
15.3 Modify eStatement Settings ...................................................................................................... 684
15.3.1 Request parameters ....................................................................................................................... 684
15.3.2 Sample URL and response ............................................................................................................. 684
15.3.3 Tag and Property Reference ........................................................................................................... 685
15.4 Available eStatements .............................................................................................................. 687
15.4.1 Request parameters ....................................................................................................................... 687
15.4.2 Sample URL and response ............................................................................................................. 687
15.4.3 Tag and Property Reference ........................................................................................................... 690
15.5 eStatement Presentment (Statement Retrieval) ......................................................................... 690
15.5.1 Request parameters ....................................................................................................................... 691
15.5.2 Sample SCS eStatement request URL and response ...................................................................... 692
15.5.3 Tag and Property Reference ........................................................................................................... 693
15.5.4 Decode SCS STMTDATA ............................................................................................................... 693
15.5.5 Decoded XML Response Sample for an SCS eStatements .............................................................. 697
15.5.6 Sample URL and response ............................................................................................................. 699
15.5.7 Tag and Property Reference ........................................................................................................... 700
15.6 eStatement Enrollment Status Request ..................................................................................... 702
15.6.1 Request parameters ....................................................................................................................... 702
15.6.2 Sample URL and response ............................................................................................................. 702
15.6.3 Tag and Property Reference ........................................................................................................... 703
16 DYOCXML ........................................................................................................................................................... 705
16.1 Design Your Own Card (DYOC) Function.................................................................................. 706
16.1.1 Request Parameters ....................................................................................................................... 706
16.1.2 Sample URL and Response............................................................................................................ 707
16.1.3 Tag and Property Reference ........................................................................................................... 708
17 Alerts .................................................................................................................................................................. 710
17.1 Member Alerts and Controls...................................................................................................... 711
17.1.1 Use Case ....................................................................................................................................... 711
17.1.2 Get Client Participation ................................................................................................................... 712
17.1.3 Get Cardholder Registration Status ................................................................................................. 715
17.1.4 Create / Update Registration ........................................................................................................... 721
17.1.5 Set Alert Preference and Threshold Values ..................................................................................... 723
17.1.6 Alert History ................................................................................................................................... 727
17.1.7 Control History ............................................................................................................................... 730
17.1.8 Omaha (credit/debit) Alerts / Preference Definitions ......................................................................... 732
17.1.9 Omaha (credit / debit) Controls / Preference Definitions ................................................................... 734
17.1.10 Wilmington (debit/credit) Alerts / Preference Definitions ................................................................... 735
17.1.11 Wilmington (debit/credit) Controls / Preference Definitions ............................................................... 736
17.2 Ondot Alerts and Controls ......................................................................................................... 737
17.2.1 Terms and Conditions..................................................................................................................... 738
17.2.2 Register Valid User......................................................................................................................... 738
17.2.3 Update Registrar ............................................................................................................................ 742
17.2.4 Process Flow.................................................................................................................................. 745
17.2.5 Create Session ............................................................................................................................... 745
17.2.6 Get Registration Details .................................................................................................................. 747
17.2.7 Get Assets ..................................................................................................................................... 750
17.2.8 Get Policy ...................................................................................................................................... 754
17.2.9 Set Card Policy............................................................................................................................... 759
Page 10
17.2.10 Get Messages ................................................................................................................................ 768
17.2.11 Alert Delivery .................................................................................................................................. 771
18 Integrated Debit Processing (Sig & PIN) ........................................................................................................... 772
18.1 Add a new draft account to a Debit PIN card ............................................................................. 773
18.1.1 Request Parameters ....................................................................................................................... 773
18.1.2 Sample URL and Response............................................................................................................ 774
18.2 Delete a draft account from a Debit PIN card............................................................................. 776
18.2.1 Request Parameters ....................................................................................................................... 776
18.2.2 Sample URL and Response ............................................................................................................ 776
18.3 Update draft account to a Debit PIN card .................................................................................. 778
18.3.1 Request Parameters ....................................................................................................................... 778
18.3.2 Sample URL and Response ............................................................................................................ 779
18.4 DDA View ................................................................................................................................. 780
18.4.1 Request Parameters ....................................................................................................................... 780
18.4.2 Sample URL and Response............................................................................................................ 780
18.4.3 Tag and Property Reference ........................................................................................................... 781
18.5 Debit Balance Update DDA account level.................................................................................. 783
18.5.1 Data eXchange Request Parameters .............................................................................................. 783
18.5.2 Sample URL and Response ............................................................................................................ 784
19 Health Check ...................................................................................................................................................... 785
19.1.1 Request Parameters ....................................................................................................................... 785
19.1.2 Functions to be invoked internally ................................................................................................... 786
19.1.3 Steps to be performed to determine the health:................................................................................ 787
19.1.4 Sample URL and Response ............................................................................................................ 787
19.1.5 Tag and Property Reference ........................................................................................................... 788
20 Appendix A – Request and Function ID Quick Reference ................................................................................ 789
21 Appendix B – Valid entries for the CONTROL Node ......................................................................................... 802
22 Appendix C – Interpreting the USERFLAGS1THRU4 Node .............................................................................. 804
23 Appendix D – Foreign Address Handling.......................................................................................................... 806
24 Appendix E – Valid entries for the AUTHDECLINEREASONCODE Node ........................................................ 808
25 Appendix G – Interpreting the HISTORY Node ................................................................................................. 816
26 Appendix H – AutoPay Flags ............................................................................................................................. 818
27 Appendix I – Foreign Transaction Handling ..................................................................................................... 820
27.1 General Guidelines for Cycle-to-Date Foreign Transactions ...................................................... 820
27.2 General Guidelines for Statemented Foreign Transactions ........................................................ 821
27.3 First Data Country and Foreign Currency Codes ....................................................................... 824
28 Appendix J – Statement Data ............................................................................................................................ 832
28.1 Merchandise Purchase Transaction .......................................................................................... 832
28.1.1 Rules ............................................................................................................................................. 833
28.2 Purchase Adjustments .............................................................................................................. 833
28.2.1 Rules ............................................................................................................................................. 833
28.3 Balance Transfer ...................................................................................................................... 834
28.3.1 Rules ............................................................................................................................................. 834
Page 11
28.4 Finance..................................................................................................................................... 834
28.4.1 Rules ............................................................................................................................................. 835
28.5 Payments ................................................................................................................................. 835
28.5.1 Rules ............................................................................................................................................. 836
28.5.2 Payment Adjustment....................................................................................................................... 836
28.5.3 Rules ............................................................................................................................................. 836
28.6 CREDITS.................................................................................................................................. 837
28.6.1 Rules ............................................................................................................................................. 837
28.7 Credit Insurance ....................................................................................................................... 838
28.7.1 Rules ............................................................................................................................................. 838
28.8 FEES and CHARGES ............................................................................................................... 838
28.8.1 Rules ............................................................................................................................................. 840
29 Appendix K – Certified SENDATAXML Numbered NonMons ........................................................................... 841
Non-Monetary transactions.................................................................................................................... 841
PI Non-Monetary transactions ............................................................................................................... 897
30 Appendix L – Special Characters ...................................................................................................................... 910
31 Appendix M – Fraud Area Codes ....................................................................................................................... 911
31.1 MasterCard ............................................................................................................................... 911
31.2 Visa .......................................................................................................................................... 913
Appendix N – Authorization Type Codes and Transaction Type Codes .................................................................. 915
Authorization type codes ....................................................................................................................... 915
Transaction type codes ......................................................................................................................... 916
Appendix O – Ondot Merchant Types........................................................................................................................ 918
Page 12
1 Document Revision History
Page 13
7.25 Add PIID fraud suspension strategy, start date,
and end date
20.4 8.2 Credit Card account number can be masked in 12/30/2020
the New Account request (1440)
17.2.8 Ondot support for multiple My Regions alert and
control
17.2.9 Ondot support for exception countries related to
the international control
21.1 8.18 New function for EMV PIN Changes 03/31/2021
Appendix O Full list of merchant categories and associated
merchange group in for Ondot merchant alert
(A04) and control (C04)
6.2 Search by criteria now supports debit cards
11.2.1 Customer view add role start and end dates
21.2 7.9 PLP Rewards – expiration totals added 06/30/2021
7.25 Customer View 1480 – Role start and End date
added
8.9, 8.15, 8.16 Post transaction 1448, 1486 – Additional Batch
Headers supported
15.1 eStatement enrollment suppress SRN 1608
21.3 8.12.6.1 Remove the MBRSEQ parameter from the 1727 09/30/2021
response when MBRSEQ=N is included in the
request
7.8, 7.17 Add expiration date and plastic type of the card
usedfor the authorization
7.2, 7.3, 7.8, Add four character Userflags string to account
7.10, 7.16, 7.12, summary response
7.13, 7.14, 7.17
21.4 7.28 New Statement History function 12/30/2021
8.19 New Refund Rebates function
22.1 11.2 Universal Addressing - View, Update, Add 03/31/2022
Cardholder
7.4 Universal Addressing - Cardholder Information
7.5 Universal Addressing - Extended Cardholder
Information
11.2 Special Character support – Update, Add
Cardholder
Page 14
22.2 7.2, 7.3, 7.8, Address Verification Flag, Upgrade date 06/30/2022
7.12, 7.13, 7.14,
7.16, 7.17
7.8, 7.17 Original authorization amount
7.29 Credit Bureau Reporting History
22.3 7.2, 7.3, 7.8, Add Pricing Strategy, and support greater than 09/30/2022
7.11, 7.12, 7.13, 500 transactions in the transaction history
7.14, 7.15, 7.16, response.
7.17
8.20 New Function – PIN Reset Optis platform
17.1 Member Alerts will be sunsetting Mar 2023
7.29 New Function – Credit Bureau Reporting
8.11 Support rush plastic request in Lost function
1452
22.4 13.7.2 One Time Future Dated payment history 12/31/2022
(function 1460)
7.9 CU Rewards function 1407 support for Member
Loyalty Reward accounts
7.25 MLMU and status change date added to function
1480
8.16 Post payment transaction 271 support added to
specify the balance ID for a promotional
payment
23.1 13.5, 7.7 Autopayment Enrollment Type 03/31/2023
6.1, 6.2 Include draft accounts in response
7.30 New Function: Payment Allocation
7.25 PIN Offset included fro primary and secondary
cardholders
7.28 Min Pay Due versus 36 month payoff added to
function 1430 Statement History function
Page 15
2 Overview
Data eXchange provides the ability to programmatically request and make some modifications to
consumer account data on the First Data Omaha platform. This document defines the
specifications for the process to retrieve and modify data on the First Data system. This document
is designed to illustrate the various request types, the format of the requests and the format of the
XML response.
All requests that are issued to the Data eXchange web server are authenticated and logged.
Cardholder , Account and Transaction information: the ability to obtain cardholder and
account related data including transaction and authorization information.
New Account: the ability to open new credit card accounts and entry of declined
applications into Issuer’s Clearinghouse is available.
Account Transfer: the ability to transfer from one existing account to another existing
account.
Balance Consolidation: the ability to process a balance consolidation on behalf of their
member via traditional check processing and electronic funds transfer.
NonMonetary transaction: the ability to post information to the NonMonetary attributes
on the credit card account
Payment on Demand: the ability to support ACH payments
Right Time Payment: the ability to allow cardholders to make payments through their
credit union and have the payment immediately impact their available credit by posting an
authorization on the account.
eStatement: the ability to enroll, manage user settings for eStatement delivery and
notification, delivery of eStatements and ability to cancel enrollment in eStatements.
Instant Issue: traditional mag-stripe and support for EMV instant issue.
Commercial Cards: the ability to interact with commercial accounts.
External statusing: the ability to set the external status and status an account Lost / Stolen.
The pilot Data eXchange environment is pointed to the test region (M-Cycle) of First Data. The URL
for the pilot environment is https://pilotdata.epscu.com. The VPN routers in the will need to have
routing setup for our 199.186.97.0. The URL will resolve to 199.186.97.51.
Page 16
The production Data eXchange environment is pointed to the live region (C-Cycle) of First Data.
The URL for the production environment is https://data.epscu.com. The VPN routers in the will
need to have routing setup for our 199.186.97.0 and 199.186.98.0 networks. The production URL
can resolve to several IPs that are supporting the Data eXchange production environment.
All functions can be made available to all audiences depending upon how the function is integrated
into member-facing and employee-facing applications, however special care should be made when
accessing certain update functions. Please refer to Appendix A - Request and Function ID Quick
Reference for further information on functions that PSCUFS recommends be restricted to internal,
or employee, facing applications and those functions that could be opened to member-facing self-
service applications.
Each Data eXchange request consists of a set of fixed parameters, the function id that identifies the
type of request being made, followed by a set of variable parameters. This document provides an in
depth description of each function currently available in Data exchange including a description of
fixed and variable parameters required for each function, an example request for each function,
and a sample response with each node of the response described.
Beginning:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.xml.xmlProc
ess&
Middle:
A set of fixed required parameters: RQID, APPID, APPLICATIONID, REQUESTID, and FUNCTIONID
End:
A set of variable parameters depending on the Data eXchange request: CLIENTID, CARDNUMBER,
etc.
The fixed parameter RQID describes the type of request that is being made. The following are the
RQID values used by Data eXchange
RQID Description
Page 17
RQID Description
SEARCHXML Data eXchange functions that search for accounts on the First Data Omaha
platform.
Page 18
An XML response is returned for each Data eXchange request made. A complete description of the
nodes of for each response can be found with each functions description. Please note that the
order of the nodes returned in each XML response will vary from request to request. As such,
presentation of data returned in the nodes should always be referenced by node name rather than
by node order. The XML responses provided in this document may include nodes that wrap from
one line to the next, this is caused by document formatting and not a result to expect in the XML
response.
It is the Financial Institution's responsibility to ensure all activity in Data eXchange is compliant with
current and all regulatory requirements.
Page 19
3 Security
3.1 Server Authentication
Authentication between the requesting server and the Data eXchange web server occurs using a
private connection and IP authentication. Private connection requires that the requesting server
communicate with the Data eXchange web server using a private frame relay or VPN connection.
This method ensures that only requests from known and trusted sources are responded to by the
Data eXchange web server. Public DNS is utilized for site address resolution, however the name of
the Data eXchange web server (data.epscu.com) will resolve to a private IP address. Requests from
servers outside of the private network will fail, as they will not have access to the private address.
The VPN routers in the will need to have routing setup for our 199.186.97.0/24 and
199.186.98.0/24 networks for production and 199.186.97.51 for the pilot environment.
IP Authentication further validates that the specific request is being sent by a known and trusted IP
address for each organization. This method determines the inbound request IP address and checks
this IP address against the organization’s registered information in the Data eXchange database. If
the IP address matches, the connection is allowed. If the IP address does not match, an XML
response is provided by the Data eXchange application indicating an IP address mismatch. A sample
of this response is shown below:
- <INVISION>
- <XMLMESSAGE>
- <ERRORMESSAGE>
- <ROW id=1>
<MESSAGE>Unable to validate IP address</MESSAGE>
<MESSAGE_ID>303</MESSAGE_ID>
</ROW>
</ERRORMESSAGE>
</XMLMESSAGE>
</INVISION>
The process requires a TLS connection (only TLS 1.2 is supported) to ensure the proper encryption
is in place to protect the confidential data. TLS encrypts the payload of the packet. So as
Page 20
information is passed between client and server (CU/Vendor and PSCU) – the network piece is in
the clear, like Source and Destination IP address – but the payload of the packet that contains the
Data eXchange info is encrypted using TLS certificates.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.xml.xmlProcess&RQI
D=GETDATAXML&CLIENTID=XXXX&CARDNUMBER=9999999999999999&APPID=106&APPLICATIONID
=102&REQUESTID=102&FUNCTIONID=1402
The Data eXchange application checks each request to ensure that the Client ID provided in the
request is a participant in the Data eXchange solution. If the verification fails, a Page Not Found
response is returned.
The Data eXchange application checks each request to ensure that the card number provided in the
request is associated with the client ID contained in the request. If the card number does not
belong to the institution, an error response is provided to the requesting server. An example of
this response appears below:
Page 21
- <INVISION>
-<GETDATAXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
-<PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1402</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME=EXCEPTION OCCURRED>java.lang.Exception: Card number
not valid for this institution</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>1</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 22
4 Server Response
4.1 Completion Status
A status code is returned within each response from the Data eXchange application. A successful
request will display a value of zero (0) in the <ods: STATUS><ods:CODE> node contained in the ods
namespace.
A Data eXchange request that fails preliminary participation validation will appear as follows:
<?xml version="1.0"?>
-<INVISION>
-<XMLMESSAGE>
-<ERRORMESSAGE>
-<ROW id="1">
<MESSAGE>Institution does not participate in Data eXchange</MESSAGE>
<MESSAGE_ID>303</MESSAGE_ID>
</ROW>
</ERRORMESSAGE>
</XMLMESSAGE>
</INVISION>
A failed Data eXchange request that passes validation will return a value of one (1) in this node.
Additionally, a failed request will include a tag with the attribute NAME=EXCEPTION OCCURRED in
the odsPscu namespace. This node will include a specific error message describing the error that
has occurred. An example of the ods namespace of a failed request is shown below:
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1402</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
-<odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME=EXCEPTION OCCURRED>java.lang.Exception: Card number
not valid for this institution</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
Page 23
-<ods:STATUS>
<ods:CODE>1</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
If the ods:STATUS/ods:CODE value is returned as a zero (0), then the request was successfully
processed. This will appear towards the end of the response XML document as shown below:
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
4.2 Exceptions
There are various exceptions that may occur when sending requests to the Data eXchange
application. During nightly First Data batch processing, it is possible that access to the FDR data
may be temporarily unavailable. Exceptions may also occur if parameters are not received properly
in the request. In each case, the <ods: CODE> node will contain a value of 1. The most common
exceptions and their reasons are listed in the table below.
Page 24
Reason Exception Text
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is: javax.transaction.TransactionRolledbackException: JZ006: Caught
IOException: JZ0EM: End of data
The card number java.lang.Exception: Cardholder information not on file for card number
submitted is not XXXXXXXXXXXXXXXX
in the First Data
system
Card number java.lang.Exception: Card number not valid for this institution.
does not belong
to the institution
making the
request
Card number not java.lang.Exception: Invalid Card number
valid – does not
pass a Mod10
check
Code error java.rmi.ServerException: RemoteException occurred in server thread; nested
processing exception is: java.rmi.ServerException: RuntimeException; nested exception is:
request, java.lang.NullPointerException
parameters not
received properly
Code error java.lang.ArrayIndexOutOfBoundsException: 0 >= 0
processing
request, invalid
First Data
response
PSCU Corporate java.rmi.UnmarshalException: Error unmarshaling return; nested exception is:
Database java.lang.ClassNotFoundException: org.jboss.resource.ResourceException (no
temporarily security manager: RMI class loader disabled)
unavailable java.sql.SQLException: No more data to read from socket
PSCU Server being javax.naming.NameNotFoundException: OneLinkDirector not bound
reset javax.naming.CommunicationException [Root exception is
java.rmi.ConnectException: Connection refused to host]
Page 25
Reason Exception Text
java.rmi.UnmarshalException: Error unmarshaling return header; nested
exception is: java.net.SocketException: Connection reset by peer: Connection
reset by peer
javax.naming.CommunicationException: Receive timed out [Root exception is
java.io.InterruptedIOException: Receive timed out]
Client ID in Unknown error: %s
request is null
Page 26
5 Exception Handling
When incorporating data from Data eXchange in your application, it is important to consider how
to handle exceptions gracefully when they occur. Although exceptions in general are rare, various
exceptions will happen during maintenance periods at PSCU Financial Services and during First Data
implementations. Whenever possible, exception messages (such as those listed in the table above)
will be contained in the response XML. However, there may be cases where an HTTP exception
response such as a 404 (not found) or a 500 (server error) is returned. Additionally, when First
Data cycles each night, various pieces of information in the cardholder information files at First
Data will be unavailable. This typically lasts only a few minutes, but may last for as long as an hour
during some cycles in the month.
Data eXchange is available 24x7x365 with a scheduled maintenance window of Sunday mornings
between 1:00am and 5:00am ETZ. During the First Data nightly processing window, various
features and functions it is possible that various data elements will be temporarily unavailable
while First Data updates occur. First Data typically performs these updates between 2:00am and
5:00am ETZ, Sunday through Friday. Our target is to achieve a 99.5% success rate for responses
inclusive of the published maintenance windows.
The Data eXchange environment is configured as ACTIVE – ACTIVE in our St Petersburg and Phoenix
data centers. Data eXchange requests are received by the global load balancer and routed to the
environment with the least load. It also monitors the availability of each environment and if an
environment is offline, the global load balancer will route all requests to the environment that is
online.
5.1.2 Performance
The response time for Data eXchange will differ depending on the function requested. For example,
a simple fixed response transaction will process more quickly than a complex variable response. A
Cardholder Information or Card Summary request is considered to be a simple transaction while a
Statement Activity request is an example of a more complex transaction with a large variable
number of transaction line details returned. Responses are classified into 4 ranges:
Page 27
Simple Complex
Good <2 <4
Acceptable >2 <4 >5 < 8
Poor >4<7 > 8 < 12
Unacceptable >7 > 12
Response times are monitored and analyzed regularly to ensure adherence to the published service
level objectives. The measurements are taken when the Data exchange server receives the request
and again when the request has completed processing. The difference between these two figures
is recorded for every transaction. The measurements do not include network latency or
transmission time. In most cases, depending upon the speed of your connection, network latency
will add an additional 1-2 seconds to the time of each transaction.
PSCU provides financial institutions with access to the PSCU Response Center / Network Operacting
Center (NOC) with support personnel to assist with processing problems/requests twenty-four (24)
hours a day, via one (1) telephone number. This telephone number is 888-638-7728.
To accomplish this objective, the following are steps in the Problem/Request Management process:
1. Notification – Financial Institution calls the Response Center to report problem or request.
2. Response Center - The Response center will work with the financial institution to resolve
the item, update the problem/request database and gives the financial institution a unique
tracking number that can be referred to at any time. If the item cannot be solved, the
Response Center will notify the appropriate support group and assign the problem/request.
3. Support Group - The support group person will work with the financial institution to resolve
the item. After the problem/request is resolved, the support person will notify the
Response Center as to the completion.
5.1.4 Disaster/Recovery
PSCU Financial Services, Inc. is committed to the effective support of its stakeholders and requires
that robust processes and procedures be adopted. These apply to all aspects of the operation of
the organization. All processes are administered according to documented procedures, which
ensure consistent operation under normal conditions and rapid recovery from abnormal
circumstances.
Page 28
PSCU Financial Services provides the following:
Page 29
6 SEARCHXML Request
The SEARCHXML Requests provide the ability to search the First Data system using different criteria
to locate card holders. Section 6 of this document provides a detailed description of each of the
SEARCHXML function along with the fixed, required and variable parameters, a sample search
request and response, and a description of each node within the response.
Function ID Description
1400 Search by Name - Search the First Data system for card holders by Name and
optionally by State.
1401 Search by Criteria - Search the First Data system for card holders by specific
criteria – Social Security Number, DDA Account Number, Home Phone Number or
Business Phone Number.
Page 30
6.1 Search by Name
The Search by Name request enables a search of the First Data system using a cardholder’s name.
The search is equivalent to performing an Alpha Lookup (AL) and will search both the Primary and
Secondary cardholder’s names for all system/principal pairs within the Client.
*Types include Alpha, Numeric and Alphanumeric. Any other value listed in this column is to be
considered the fixed value for the parameter.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.xml.xmlPro
cess&RQID=SEARCHXML&APPID=106&APPLICATIONID=102&REQUESTID=102&FUNCTIONID=1400
&CLIENTID=9999&NAME=XXXXX
Page 31
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <SEARCHXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
-<V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1400</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
Page 32
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="WARNING">FALSE</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SEARCHXML>
</INVISION>
The XML response shown contains all of the XML nodes that can be expected, although the
response document received by the requesting server may have the nodes in a different order than
they appear in this document. The response document will contain a collection with the tag name
of WARNING. This tag indicates if the number of matches exceeds the system limitation of 250. If
the value of the node is FALSE, then the limitation was not exceeded. If the value is TRUE, then the
Page 33
limitation was exceeded. To further refine the return result set, the Data eXchange application
supports the use of State parameter.
A full request with all optional parameters will appear similar to the following:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.xml.xmlPro
cess&RQID=SEARCHXML&APPID=106&APPLICATIONID=102&REQUESTID=102&FUNCTIONID=1400
&CLIENTID=9999&NAME=JONES&STATE=XX&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <SEARCHXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
-<V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1400</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME MI</odsPscuTAG>
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
Page 34
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME MI</odsPscuTAG>
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME MI</odsPscuTAG>
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="WARNING">FALSE</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SEARCHXML>
Page 35
</INVISION>
Valid Codes:
A - Authorization prohibited
B - Bankrupt
Z - Charge off
C - Closed
F - Frozen
I - Interest accrual prohibited
L - Lost
Blank - Normal
E - Revoked
U - Stolen
EXTERNALSTATUS External Status Code in Words, based on the Alpha 30 BS
code designation found within the First Data
system. This is an Issuer-assigned status code
determining specific account processing.
Valid codes:
Authorization prohibited
Bankrupt
Charge off
Closed
Frozen
Page 36
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Interest accrual prohibited
Lost
Normal
Revoked
Stolen
INTCODE Internal Status Code as found within the First Alpha 1 BS
Data system, one character, system defined
code determining the specific account
processing.
Valid code:
N - Credit balance
D - Delinquent
X - Delinquent and overlimit
Blank - Normal
O - Overlimit
INTERNALSTATUS Internal Status Code in Words, based on the Alpha 30
code designation found within the First Data
system. This is a System-assigned status code
determining specific account processing.
Valid codes:
Credit balance
Delinquent
Delinquent and overlimit
Normal
Overlimit
PRIMARYNAME Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
SAVINGS Savings account number Numeric 15 NM AFR
SECONDARYNAME Secondary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
STATE Cardholder’s address – 2 Character State Alpha 2 NM CSR
Abbreviation
Page 37
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
WARNING Indicates if the number of search matches Alpha 4-5
exceeds the system limitation of 250.
Page 38
6.2 Search by Criteria Request
The Search by Criteria Request enables a search of the First Data system using one of the following:
Social Security Number, DDA Account Number, Home Telephone Number or Business Telephone
Number. The search is equivalent to performing an RG search in First Data. This function with the
D=YES will return debit card records regardless of the platform – Wilmington / Omaha – the debit
program processes on. The information in the response for a debit card is no different than the
information n the response for a credit card.
Page 39
NOTE: At least one of the four optional parameters *must* be included in the request.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.xml.xmlProc
ess&RQID=SEARCHXML&APPID=106&APPLICATIONID=102&REQUESTID=102&FUNCTIONID=1401&C
LIENTID=9999&SSN=999999999&
The XML response shown contains all of the XML nodes that can be expected, although the
response document received by the requesting server may have the nodes in a different order than
they appear in this document. The response document will contain a collection with the tag name
of WARNING. This tag indicates if the number of matches exceeds the system limitation of 250. If
the value of the node is FALSE, then the limitation was not exceeded. If the value is TRUE, then the
limitation was exceeded.
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <SEARCHXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
-<V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1401</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME MI</odsPscuTAG>
Page 40
<odsPscuTAG NAME="SECONDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME MI</odsPscuTAG>
<odsPscuTAG NAME="SECNDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STATE">ST</odsPscuTAG>
<odsPscuTAG NAME="EXTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="PRIMARYNAME">LASTNAME,FIRSTNAME MI</odsPscuTAG>
<odsPscuTAG NAME="SECNDARYNAME">LASTNAME,FIRSTNAME
MI</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CITY">CITY NAME</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="WARNING">FALSE</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
Page 41
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SEARCHXML>
</INVISION>
Page 42
6.2.3 Tag and Property Reference
Valid Codes:
A - Authorization prohibited
B - Bankrupt
Z - Charge off
C - Closed
F - Frozen
I - Interest accrual prohibited
L - Lost
Blank - Normal
E - Revoked
U - Stolen
EXTERNALSTATUS External Status Code in Words, based on the Alpha 30
code designation found within the First Data
system. This is an Issuer-assigned status
code determining specific account
processing.
Valid codes:
Authorization prohibited
Bankrupt
Charge off
Closed
Frozen
Interest accrual prohibited
Page 43
OdsPscu TAG NAME Description Type Length First
Data
Screen
Lost
Normal
Revoked
Stolen
INTCODE Internal Status Code as found within the Alpha 1 BS
First Data system, one character, system
defined code determining the specific
account processing.
Valid code:
N - Credit balance
D - Delinquent
X - Delinquent and overlimit
Blank - Normal
O - Overlimit
INTERNALSTATUS Internal Status Code in Words, based on the Alpha 30
code designation found within the First Data
system. This is a System-assigned status
code determining specific account
processing.
Valid codes:
Credit balance
Delinquent
Delinquent and overlimit
Normal
Overlimit
PRIMARYNAME Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
SAVINGS Savings account number Numeric 15 NM AF
SECNDARYNAME Secondary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
STATE Cardholder’s address – 2 Character State Alpha 2 NM CSR
Abbreviation
Page 44
OdsPscu TAG NAME Description Type Length First
Data
Screen
WARNING Indicates if the number of search matches Alpha 4-5
exceeds the system limitation of 250.
Page 45
7 GETDATAXML Request
The GETDATAXML Request provides information about the credit card and about the
cardholder. Section 7 of this document provides a detailed description of each of the
SEARCHXML functions along with the fixed, required and variable parameters, a sample
search request and response, and a description of each node within the response and
the corresponding screen in First Data where the data may typically be found.
Function ID Description
1402 Card Summary – returns summary data on the cardnumber submitted -
such as balances, payment due dates and amounts, interest rates and
status codes
1462 Card Summary and eStatement Enrollment Information – Returns the
Card Summary information found in the Data eXchange 1402 function and
the current eStatement Enrollment Status.
1403 Cardholder Information – returns data about the cardholder of the
cardnumber submitted - such as names, addresses, social security
numbers, dates of birth and phone numbers
1407 Rewards Activity and History – returns CU Rewards/rebates data or PLP
rewards/rebate data for the cardnumber submitted – includes total points
earned, pending, redeemed, points that are still available for redemption
and point expiration date
1411 Statement Data, Last Cycle – returns data from the cardholder’s last
statement – includes transactions, payments and fees as well as
statement balance and statement date
1412 Statement Data, One Cycle Prior – returns data from the cardholder’s
prior statement – includes transactions, payments and fees as well as
statement balance and statement date
1413 Statement Data, Two Cycles Prior – returns data from the cardholder’s
next prior statement – includes transactions, payments and fees as well as
statement balance and statement date
1414 Payment History – returns payment history data for the cardnumber
submitted – includes the 12 month payment history and recent detail on
payments due and payments made
1415 Recent Activity – returns transaction data that has occurred on the
Page 46
Function ID Description
account since the cardholder’s most recent statement – includes
transactions, payments and outstanding authorizations
1417 Account Memos – returns the details of the memos on the CIS screen
currently written on the account for the cardnumber submitted in the
request
1423 Extended Cardholder Information - returns data about the cardholder of
the cardnumber submitted - such as names, addresses, social security
numbers, dates of birth and phone numbers – also returns additional
information on authorized users and alternate addresses in place
1426 Demand Payment Request – obtain current demand payment related
settings such as DDA, Routing & Transit and AutoPayFlag values
1429 Special Consolidated Account Information – returns summary data on the
cardnumber submitted - such as balances, payment amounts, autopay
information, account cross references, status codes, previous high balance
and collector code
1430 Statement History – Up to 12 cycles of statement history
1431 Statement Data, Last 3 Cycles – returns data from the cardholder’s last
three statements – includes transactions, payments and fees as well as
statement balances and statement dates
1432 Statement Data, Last 3 Cycles and Recent Activity – returns data from the
cardholder’s last three statements, transactions since the last statement
and summary information on the account – includes outstanding
authorizations, transactions, payments and fees as well as statement
balances and statement dates
1433 Statement Balances and Summary Data – returns summary information
from the last three cycles and current summary account data – includes
totals for transactions, payments and fees as well as statement balances
and statement dates returned as discrete nodes
1436 Statement Summaries, All Available – returns summary level information
for up to 12 months of stored Cardholder Statements – includes totals for
transactions, payments and fees as well as statement balances and
statement dates organized into collections
1437 Statement Data, Single Specified Cycle – returns data from the
cardholder’s statement based on the statement date provided in the
request – includes transactions, payments and fees as well as statement
balance and statement date
Page 47
Function ID Description
1446 CVV2 – Validates the provided CVV2 code.
1449 Promotion/Protected Balance – returns information about existing
promotion/protected balances on an account.
1463 FICO Score – Returns the current FICO score on the credit card record
1474 Reward / Redemption History – Returns the history of an accounts
reward / rebate redemption
1479 Dispute History – History of the disputes on the account as reflected by
the CDH screen
1480 Cardholder Plastics – Returns attributes related to the plastics on the
account for all cardholders on the account.
1489 Retreive Emboss Requests – Returns the emboss requests currently
available for the plastic
1800 PFM – Obtain credit card transactions for a Personal Finance Management
tool.
Page 48
7.1 Account Memo Information
The Account Memo Information request returns the memos for the specified cardholder
account. The information reflects the information on the CIS screen in the First Data
system. Eash collection returned in the URL contains one line from the CIS screen. The
order of the returned collections may not reflect the order the memos appear on the
CIS screen.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1417&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
-<GETDATAXML>
-<VALIDATION>
Page 49
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
-<V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1417</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
MI</odsPscuTAG>
<odsPscuTAG
NAME="YTDINTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST MI</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="LASTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
Page 50
<odsPscuTAG NAME="MEMOCLKI"D>XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">FIRST MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">SECOND MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">THIRD MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">FOURTH MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">FIFTH MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
Page 51
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">SIXTH MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">SEVENTH MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">EIGHTH MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">NINTH MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
Page 52
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 53
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
without decimal places
CREDITLIMIT The maximum credit extended to Numeric 16 BS
the account (this amount, less the
current balance and any
outstanding authorizations, gives
the available credit on the account),
shown as a whole number without
decimal places
CURRENTBALANCE Current balance on account, shown Numeric 16 BS
as a signed number with 2 decimal
places and the decimal point in the
response
INTCODE Internal Status Code as found Alpha 1 BS
within the First Data system, one
character - System-assigned code
determining specific account
processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTSTATUSCODE Current Internal Status Code, in Alpha 30
Words (for valid descriptions, see
INTCODE)
LASTBALANCE Outstanding balance on the last Numeric 19 BS
statement, shown as a signed
number with 2 decimal places and
decimal point shown in response
LASTPAYAMT Amount of the last payment, in Numeric 19 BS7
dollars and cents with decimal point
shown in response
Page 54
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note: Some
situations may return 000000 as the
value)
LASTSTMTDATE Date of the last statement, in Numeric 6 BS2
YYMMDD format (Note: Some
situations may return 000000 as the
value)
MEMOCLKID Initials attached to the memo Alpha 3 CIS
item’s creation – for system
generated (automatic) CIS memos,
this field will not contain a value
MEMODATA Memo item’s text Alphanumeric 62 CIS
MEMODATE The date the memo item was input Numeric 6 CIS
into the host system, shown in
YYMMDD format (Note: Some
situations may return 000000 as the
value)
MEMOSEQUENCE Memo item’s sequence number Numeric 3 CIS
MEMOTYPE Memo type code assigned by First Alpha 1 CIS
Data
Valid codes:
A - Account Level Processing
memos
B - Chargeback memos
C - CIS memos
J - Adjustment memos
N - Non-monetary transaction
memos
P - Payment memos
R - Retrieval memos
W - CIMS memos
X - Collections memos
Page 55
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
PRIN Client-defined identifier of the level Numeric 4 BS6
within a System Bank Identifier that
is used
to group Agent Bank Identifiers
together for processing and
reporting
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and
reporting
YTDINTBILLED Amount of interest billed on the Numeric 15 BS
account Year-To-Date
YTDINTPAID Amount of interest paid Year-to- Numeric 15 BS
Date, in dollars and cents with
decimal point shown in response
Page 56
7.2 Card Summary Information
The Card Summary Information request returns the summary for the specified
cardholder account. The information is similar to the information found on the BS
screens in the First Data system.
Page 57
Parameter Description Type Required Length
/
Optional
CASHADV Y – Include cash advance limit Fixed Optional 1
and cash advance outstanding
balance
COMPINFO Y – Company ID, company Fixed Optional 1
account type and company
name will be returned
EXTSTAT Y – include external status Fixed Optional 1
change date and reason code
FULLMINPAYDUE Y - Include the full minimum Fixed Optional 1
payment due in dollars and
cents
OPA Y – include the OPA in the Fixed Optional 1
response
PET Y-Returnes the Personal Fixed Optional 1
Emboss Text
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) for primary and
secondary. This feature is only
valid for Separate Entity
clients.
PISTATUS Y – Returns the status of the Alpha Optional 1
PIID for Separate Entity
PS Y – Include pricing strategy Fixed Optional 1
PYI Y – Returns previous years Fixed Optional 1
interest billed and previous
years interest paid
UPC Y-Incluced UPC values in Fixed Optional 1
response
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
W YES – The request is being Fixed Optional 3
submitted for a Wilmington
Page 58
Parameter Description Type Required Length
/
Optional
account
XREF Y – Include the cross reference Fixed Optional 1
accounts
YTDINTBILLED YES – Return YTD Intererst Fixed Optional 3
Billed
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=1
02&FUNCTIONID=1402&REQUESTID=102&CARDNUMBER=9999999999999999
&CLIENTID=9999&PIID=Y&ADDLNONMON=Y
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1402</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELINQ">999</odsPscuTAG>
<odsPscuTAG NAME="NEXTPAYDATE">MM-DD-YY</odsPscuTAG>
Page 59
<odsPscuTAG
NAME="CURRENTBALANCE">0000000009999.99</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG
NAME="EXTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG
NAME="AMTPAST_DUE">0000000000009999</odsPscuTAG>
<odsPscuTAG
NAME="LASTCREDITLINEDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="LASTBALANCE">0000000000009999.99</odsPscuTAG>
<odsPscuTAG NAME="OPENDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">0000000000009999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">0000000000099999</odsPscuTAG>
<odsPscuTAG NAME="STATUS">X</odsPscuTAG>
<odsPscuTAG NAME="CONTROL">X</odsPscuTAG>
<odsPscuTAG NAME="USERFLAGS1THRU4">DESCRIPTION
(X)</odsPscuTAG>
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG
NAME="YTDINTPAID">000000000999.99</odsPscuTAG>
<odsPscuTAG NAME="CASHADVANCEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="PURCHASEAPR">99.999</odsPscuTAG>
<odsPscuTAG
NAME="DATELASTPLASTICORDER">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">0000000000000999</odsPscuTAG>
<odsPscuTAG NAME="NUMPLASTICS">009</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">0000000000009999</odsPscuTAG>
<odsPscuTAG NAME="EXPIREDATE">MMYY</odsPscuTAG>
Page 60
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="CREDITLIFEINDICATOR">9</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="AFFINITYNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="BILLINGCYCLE">99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLINEAM">99999999999</odsPscuTAG>
<odsPscuTAG NAME="CREDITLINECD">99</odsPscuTAG>
<odsPscuTAG NAME="CREDITLINEDT">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="FRAUDSCORE">999</odsPscuTAG>
<odsPscuTAG NAME="FRAUDSCOREDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="FRAUDSTRAT">99</odsPscuTAG>
<odsPscuTAG NAME="FRAUDSTRATDT">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="FRAUDSUSPENDSTARTDT">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="FRAUDSUSPENDSTRATEGY">99</odsPscuTAG>
<odsPscuTAG
NAME="FRAUDSUSPENDENDDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="MISC1">XXXX</odsPscuTAG>
<odsPscuTAG NAME="MISC9">X</odsPscuTAG>
<odsPscuTAG NAME="MISC8">XX</odsPscuTAG>
<odsPscuTAG NAME="MISC7">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="MISC6">X</odsPscuTAG>
<odsPscuTAG NAME="MISC5">X</odsPscuTAG>
<odsPscuTAG NAME="MISC4">XX</odsPscuTAG>
<odsPscuTAG NAME="MISC3">XX</odsPscuTAG>
<odsPscuTAG NAME="MISC2">XX</odsPscuTAG>
<odsPscuTAG NAME="MISC13">X</odsPscuTAG>
<odsPscuTAG NAME="MISC10">X</odsPscuTAG>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
Page 61
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 62
OdsPscu TAG NAME Description Type Length First
Data
Screen
percentage with 3 decimal places
CASHADVLIMIT Cash advance limit included when Numeric 16 BS5
CASHADV=Y
CASHADVOUTBAL Cash advance outstanding balance Numeric 16 BS5
included when CASHADV=Y
CARDTYPE Description of the Card program – Alpha 25
Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 63
OdsPscu TAG NAME Description Type Length First
Data
Screen
CONTROL Reissue control flag. This code Alpha 1 BS
controls reissue processing. Refer
to Appendix B for valid CONTROL
codes. This value is updated in
real-time when a card is activated.
CRDTBURSCOR Credit bureau score Numeric 3 NM CR
CREDITAVAIL Dollar amount of the account's Numeric 16 BS
unused credit as of the indicated
date, shown as a whole number
without decimal places
CREDITLIFEINDICATOR Account’s credit insurance flag Numeric 1 BS
Page 64
OdsPscu TAG NAME Description Type Length First
Data
Screen
ADDLNONMON parameter is
included in the request
Valid codes:
A - Automatic
C - Permanently deferred
D - Adaptive Control decrease
I - Adaptive Control increase
M - Manual
O - Never increased
R - Adaptive Control increase or
decrease using the LSX transaction
S - Automatic increase due to
check transaction maximum line
without an
available credit buffer
T - Increase due to additional
deposit for secured account
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to
check transaction maximum line
with an
available credit buffer
3 - Decrease due to mid-cycle
credit line processing via Adaptive
Control
4 - Increase due to mid-cycle credit
line processing via Adaptive
Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
Page 65
OdsPscu TAG NAME Description Type Length First
Data
Screen
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was Numeric 2 BS
established. This value will be
returned when the ADDLNONMON
parameter is included in the
request
Format: MMYY
CURRENTBALANCE Current balance on account, Numeric 16 BS
shown as a signed number with 2
decimal places and the decimal
point in the response
DATELASTPLASTICORDER Date of the last order of plastics on Numeric 6 PIR
the account, in YYMMDD format
(Note: Some situations may return
000000 as the value)
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
EMAILADDR Email address Alpha Variabl NM EP
Numeric e
EXPIREDATE Date the credit account expires, in Numeric 4 BS
MMYY format
EXTCODE External Status Code as found Alpha 1 BS
within the First Data system, one
character - Issuer-assigned status
code determining specific account
processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited (I)
Page 66
OdsPscu TAG NAME Description Type Length First
Data
Screen
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
EXTSTATUSCODE External Status Code, described in Alpha 30
Words (for valid descriptions, see
EXTCODE)
EXTSTATDT Date the external status changed Numeric 6 NM SA1
EXTSTATRESCD Reason for the external status Numeric 2 NM SA1
change
FRAUDSCORE Fraud Score Numeric 3 NM CR
This value will be returned when
the ADDLNONMON parameter is
included in the request
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM CR
Format: YYMMDD
This value will be returned when
the ADDLNONMON parameter is
included in the request
FRAUDSTRAT Current fraud strategy assigned to Numeric 2 NM CR
the account
This value will be returned when
the ADDLNONMON parameter is
included in the request
FRAUDSTRATDT Date current fraud strategy Numeric 6 NM CR
assigned to the account
Format: YYMMDD
This value will be returned when
the ADDLNONMON parameter is
included in the request
FRAUDSUSPENDENDDT End date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may
be null.
Format:
Page 67
OdsPscu TAG NAME Description Type Length First
Data
Screen
YYMMDD
This value will be returned when
the ADDLNONMON parameter is
included in the request
FRAUDSUSPENDSTARTDT Start date for the suspension of Numeric 6 NM CR
the fraud strategy. This parameter
may be null.
Format:
YYMMDD
This value will be returned when
the ADDLNONMON parameter is
included in the request
FRAUDSUSPENDSTRATEGY Strategy that will be enforced Numeric 2 NM CR
during time period defined by start
and end date This value will be
returned when the ADDLNONMON
parameter is included in the
request
FULLMINPAYDUE Full minimum payment due as Numeric 19 CSS
calculcated at statement cycle.
Format:
9999999999999999.99
INTCODE Internal Status Code as found Alpha 1 BS
within the First Data system, one
character - System-assigned code
determining specific account
processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
Page 68
OdsPscu TAG NAME Description Type Length First
Data
Screen
INTSTATUSCODE Current Internal Status Code, in Alpha 30
Words (for valid descriptions, see
INTCODE)
LASTBALANCE Outstanding balance on the last Numeric 19 BS
statement, shown as a signed
number with 2 decimal places and
decimal point shown in response
LASTCREDITLINEDATE Date of the last credit limit Numeric 4 BS
adjustment, in MMYY format
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
LASTPAYAMT Amount of the last payment, in Numeric 19 BS7
dollars and cents with decimal
point shown in response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note: Some
situations may return 000000 as
the value)
LASTSTMTDATE Date of the last statement, in Numeric 6 BS2
YYMMDD format (Note: Some
situations may return 000000 as
the value)
MINPAYAMT The minimum payment required to Numeric 16 BS
retain a current status on the
account (this amount may or may
not include overlimit and or past
due amounts) and is shown as a
whole number without decimal
places. This value does reflect any
payment made during the current
cycle.
MISC1 Miscellaneous field 1. This value AlphaNu 4 NM CS
will be returned when the meric
ADDLNONMON parameter is
Page 69
OdsPscu TAG NAME Description Type Length First
Data
Screen
included in the request
MISC2 Miscellaneous field 2. This value AlphaNu 5 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC3 Miscellaneous field 3. This value AlphaNu 7 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC4 Miscellaneous field 4. This value AlphaNu 10 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC5 Miscellaneous field 5. This value AlphaNu 8 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC6 Miscellaneous field 6. This value AlphaNu 12 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC7 Miscellaneous field 7. This value AlphaNu 10 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC8 Miscellaneous field 8. This value AlphaNu 10 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC9 Miscellaneous field 9. This value AlphaNu 10 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC10 Miscellaneous field 10. This value AlphaNu 10 NM CS
Page 70
OdsPscu TAG NAME Description Type Length First
Data
Screen
will be returned when the meric
ADDLNONMON parameter is
included in the request
MISC13 Miscellaneous field 13. This value AlphaNu 50 NM CS
will be returned when the meric
ADDLNONMON parameter is
included in the request
MOBILEPHONE Mobile phone Numeric 10 NM EP
NEXTPAYDATE Date the next payment is due on Numeric 8 BS4
the account, in MM-DD-YY format
Page 71
OdsPscu TAG NAME Description Type Length First
Data
Screen
A – Auth blocked
PRIN Client-defined identifier of the Numeric 4 BS6
level within a System Bank
Identifier that is used
to group Agent Bank Identifiers
together for processing and
reporting
PURCHASEAPR Annual Percentage Rate applying Numeric 6 NM SA2
to purchases and merchandise,
shown as a percentage with 3
decimal places.
PYIPDAMT Previous years interest paid Numeric 13 NM PH
Included when PYI=Y is included in
the request
PYIBLLDAMT Previous years interest billed Numeric 13 NM PH
Included when PYI=Y is included in
the request
SECONDARYPIID Plastic Identifier (card number) for Numeric 16 PIR
the secondary cardholder. This
feature is only valid for Separate
Entity clients when PIID=Y is
included in the request.
SECONDARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
SPCLFLAGS Value in the special flags 5 – 8 field Alpha 4 BS
STATUS External Status Code as found Alpha 1 BS
within the First Data system, one
character – see valid codes listed
above in EXTCODE node
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
Page 72
OdsPscu TAG NAME Description Type Length First
Data
Screen
together for processing and
reporting
UPC1 Value of the UPC 1 field Alpha 1 NM CC
Numeric
UPC2 Value of the UPC 2 field Alpha 1 NM CC
Numeric
UPC3 Value of the UPC 3 field Alpha 1 NM CC
Numeric
UPC4 Value of the UPC 4 field Alpha 1 NM CC
Numeric
UPC5 Value of the UPC 5 field Alpha 1 NM CC
Numeric
UPC6 Value of the UPC 6 field Alpha Up to 2 NM CC
Numeric
UPC7 Value of the UPC 7 field Alpha Up to 2 NM CC
Numeric
UPC8 Value of the UPC 8 field Alpha Up to 3 NM CC
Numeric
UPC9 Value of the UPC 9 field Alpha Up to 3 NM CC
Numeric
UPC10 Value of the UPC 10 field Alpha Up to 4 NM CC
Numeric
UPC11 Value of the UPC 11 field Alpha Up to 5 NM CC
Numeric
UPC12 Value of the UPC 12 field Alpha Up to 6 NM CC
Numeric
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of the Alphanu 25 BS
plastic, described in words with meric
the First Data code for the
activation status following the
description in parenthesis – please
see Appendix C of this document
Page 73
OdsPscu TAG NAME Description Type Length First
Data
Screen
for further information.
USF14 Four character value of the Alpha 4 BS
Userflags field
YTDINTBILLED Amount of interest billed on the Numeric 15 BS
account Year-To-Date
YTDINTPAID Amount of interest paid Year-to- Numeric 15 BS
Date, in dollars and cents with
decimal point shown in response
Page 74
7.3 Card Summary Information and eStatement Enrollment Status
The Card Summary Information request returns the summary for the specified
cardholder account and the cardholder’s eStatement Enrollment Status. The
information is similar to the information found on the BS and NM EBP screens in the
First Data system. This function will return the eStatement enrollment status from the
mainframe. The mainframe is not the system of record for eStatement participation.
The best practives recommendation is to use the 1402 function for the account
summary information and the 1620 function for the eStatement participation. The 1620
function will query the actual system of record for eStatement participation.
Page 75
Parameter Description Type Required Length
/
Optional
address verification flag
ALTSTMT Y – Include alternate Fixed Optional 1
statement code in the
response
BSCR Y- Include behavior score in Fixed Optional 3
the results
FULLMINPAYDUE Y - Include the full minimum Fixed Optional 1
payment due in dollars and
cents
OPA Y – Include OPA in response Fixed Optional 1
PET Y – Include the Personal Fixed Optional 1
Emboss Text in the response
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) for primary and
secondary. This feature is only
valid for Separate Entity
clients.
PISTATUS Y – Returns the status of the Alpha Optional 1
PIID for Separate Entity
PS Y – Include Pricing Strategy Fixed Optional 1
PYI Y-Include previous years Fixed Optional 1
interest billed and paid in the
response
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1462&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&PIID=Y&
Page 76
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1462</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELINQ">999</odsPscuTAG>
<odsPscuTAG NAME="NEXTPAYDATE">MM-DD-YY</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">0000000009999.99</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG
NAME="EXTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG
NAME="AMTPAST_DUE">0000000000009999</odsPscuTAG>
<odsPscuTAG
NAME="LASTCREDITLINEDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="LASTBALANCE">0000000000009999.99</odsPscuTAG>
<odsPscuTAG NAME="OPENDATE">MMYY</odsPscuTAG>
Page 77
<odsPscuTAG
NAME="LASTPAYAMT">0000000000009999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">0000000000099999</odsPscuTAG>
<odsPscuTAG NAME="STATUS">X</odsPscuTAG>
<odsPscuTAG NAME="CONTROL">X</odsPscuTAG>
<odsPscuTAG NAME="USERFLAGS1THRU4">DESCRIPTION
(X)</odsPscuTAG>
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG
NAME="YTDINTPAID">000000000999.99</odsPscuTAG>
<odsPscuTAG NAME="CASHADVANCEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="PURCHASEAPR">99.999</odsPscuTAG>
<odsPscuTAG
NAME="DATELASTPLASTICORDER">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">0000000000000999</odsPscuTAG>
<odsPscuTAG NAME="NUMPLASTICS">009</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">0000000000009999</odsPscuTAG>
<odsPscuTAG NAME="EXPIREDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="ESTATEMENTENROLLMENTSTATUS">E</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="CREDITLIFEINDICATOR">9</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 78
</GETDATAXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 79
OdsPscu TAG NAME Description Type Length First
Data
Screen
These values are primarily
used for reporting to Visa and
MasterCard and cannot be
changed.
CHNAME Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI
format
CHSECONDARY Secondary Cardholder’s name Alpha 26 NM CSR
in LastName,FirstName MI
format
CLIENTID PSCU assigned client identifier Numeric 6
CONTROL Reissue control flag. This code Alpha 1 BS
controls reissue processing.
See Appendix B for further
information. This value is
updated in real-time when a
card is activated.
CRDTBURSCOR Credit bureau score Numeric 3 NM CR
CREDITAVAIL Dollar amount of the Numeric 16 BS
account's unused credit as of
the indicated date, shown as a
whole number without
decimal places
CREDITLIFEINDICATOR Account’s credit insurance flag Numeric 1 BS
Page 80
OdsPscu TAG NAME Description Type Length First
Data
Screen
CREDITLIMIT The maximum credit extended Numeric 16 BS
to the account (this amount,
less the current balance and
any outstanding
authorizations, gives the
available credit on the
account), shown as a whole
number without decimal
places
CURRENTBALANCE Current balance on account, Numeric 16 BS
shown as a signed number
with 2 decimal places and the
decimal point in the response
DATELASTPLASTICORDER Date of the last order of Numeric 6 PIR
plastics on the account, in
YYMMDD format (Note: Some
situations may return 000000
as the value)
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
EMAILADDR Email address Alpha Variabl NM EP
Numeric e
MOBILEPHONE Mobile phone Numeric 10 NM EP
OPENDATEDAY Day of the month the account Numeric 2 BS9
was opened
ESTATEMENTENROLLMENTSTATUS Only Valid for SCS eStatement Alpha 1 NM EBP
participating Credit Unions
Cardholder’s current
eStatement Enrollment Status
Valid Codes:
B – Cardholder receives both
Paper and Electronic
Page 81
OdsPscu TAG NAME Description Type Length First
Data
Screen
Statements
D – Cardholder receives both
Paper and Electronic
Statements and currently is
subject to delinquency
processing
E – Cardholder receives
Electronic Statements
L - The cardholder receives
both electronic and paper
statements and is billed
additionally for paper
statements.
Blank – The cardholder is not
enrolled in eStatements
EXPIREDATE Date the credit account Numeric 4 BS
expires, in MMYY format
EXTCODE External Status Code as found Alpha 1 BS
within the First Data system,
one character - Issuer-
assigned status code
determining specific account
processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited (I)
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
Page 82
OdsPscu TAG NAME Description Type Length First
Data
Screen
EXTSTATUSCODE External Status Code Alpha 30
Valid codes:
A = Authorization prohibited
B = Bankrupt
Z = Charge off
C = Closed
F = Frozen
I = Interest accrual prohibited
L = Lost
Blank or N = Normal
E = Revoked
U = Stolen
FULLMINPAYDUE Full minimum payment due as Numeric 19 CSS
calculated at statement cycle.
Format:
9999999999999999.99
INTCODE Internal Status Code as found Alpha 1 BS
within the First Data system,
one character - System-
assigned code determining
specific account processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTSTATUSCODE Current Internal Status Code, Alpha 30
in Words (for valid
descriptions, see INTCODE)
LASTBALANCE Outstanding balance on the Numeric 19 BS
last statement, shown as a
signed number with 2 decimal
places and decimal point
Page 83
OdsPscu TAG NAME Description Type Length First
Data
Screen
shown in response
LASTCREDITLINEDATE Date of the last credit limit Numeric 4 BS
adjustment, in MMYY format
LASTPAYAMT Amount of the last payment, Numeric 19 BS7
in dollars and cents with
decimal point shown in
response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note: Some
situations may return 000000
as the value)
LASTSTMTDATE Date of the last statement, in Numeric 6 BS2
YYMMDD format (Note: Some
situations may return 000000
as the value)
MINPAYAMT The minimum payment Numeric 16 BS
required to retain a current
status on the account (this
amount may or may not
include overlimit and or past
due amounts) and is shown as
a whole number without
decimal places. This value
does reflect any payment
made during the current cycle.
MOBILEPHONE Mobile phone Numeric 10 NM EP
NEXTPAYDATE Date the next payment is due Alpha 8 BS4
on the account, in MM-DD-YY
format
Page 84
OdsPscu TAG NAME Description Type Length First
Data
Screen
issued on the account
OPA Account number, mostly Numeric 16 BS
relevant to separate entity
OPENDATE Date the credit account was Numeric 4 BS
opened, in MMYY format
OPENDATEDAY Day of the month the account Numeric 2 BS9
was opened
PERSONZN Personal Emboss Text Alpha Up to PID
Included when PET=Y is Numeric 26
included in the request
PRICINGSTRATEGY Pricing strategy on the Alpha 4 NM ST
account Numeric
PRIMARYPIID Plastic Identifier (card Numeric 16 PIR
number) for the primary
cardholder. This feature is
only valid for Separate Entity
clients when PIID=Y is
included in the request.
PRIMARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
PRIN Client-defined identifier of the Alpha 4 BS6
level within a System Bank
Identifier that is used
to group Agent Bank
Identifiers together for
processing and reporting
PURCHASEAPR Annual Percentage Rate Numeric 6 NM SA2
applying to purchases and
merchandise, shown as a
percentage with 3 decimal
places.
PYIBLLDAMT Previous years interest billed Numeric 13 NM PH
Page 85
OdsPscu TAG NAME Description Type Length First
Data
Screen
Included when PYI=Y is in the
request
PYIPDAMT Previous years interest paid Numeric 13 NM PH
Included when PYI=Y is in the
request
SECONDARYPIID Plastic Identifier (card Numeric 16 PIR
number) for the secondary
cardholder. This feature is
only valid for Separate Entity
clients when PIID=Y is
included in the request.
SECONDARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
SPCLFLAGS Value in the special flags 5 – 8 Alpha 4 BS
field
STATUS External Status Code as found Alpha 1 BS
within the First Data system,
one character – see valid
codes listed above in
EXTCODE node
SYSTEM First Data-assigned identifier Alpha 4 BS6
of the level used to group
Principal Bank Identifiers
together for processing and
reporting
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of Alpha 25 BS
the plastic, described in words
with the First Data code for
the activation status following
the description in parenthesis
Page 86
OdsPscu TAG NAME Description Type Length First
Data
Screen
– please see Appendix C of
this document for further
information.
USF14 Four character Userflags string Alpha 4 BS
YTDINTPAID Amount of interest paid Year- Numeric 15 BS
to-Date, in dollars and cents
with decimal point shown in
response
Page 87
7.4 Cardholder Information
Page 88
7.4.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1403&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1403</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CHZIPCODE">99999</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG
NAME="MOTHERMAIDENNAME">LASTNAME</odsPscuTAG>
<odsPscuTAG NAME="CHADDR2">ADDRESS LINE 2
TEXT</odsPscuTAG>
<odsPscuTAG NAME="CHADDR1">ADDRESS LINE 1
TEXT</odsPscuTAG>
<odsPscuTAG NAME="SOCSECNBR">999999999</odsPscuTAG>
<odsPscuTAG NAME="CHSTATE">ST</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG
<odsPscuTAG
NAME="SHAREACCOUNT">99999999999999999</odsPscuTAG>
Page 89
<odsPscuTAG
NAME="SHAREDRAFT">99999999999999999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG
NAME="CHSECONDARYSSN">999999999</odsPscuTAG>
<odsPscuTAG NAME="DATEOFBIRTH">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="DATEOFBIRTHSEC">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHCITY">CITYNAME</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="EMAILHOME">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="EMAILHOMESOLICIT">Y</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EMAILWORK">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="EMAILWORKSOLICIT">Y</odsPscuTAG>
</COLLECTION>
- - <COLLECTION>
<odsPscuTAG NAME="SSNID">999999999</odsPscuTAG>
<odsPscuTAG NAME="AUTHNAME">LAST,FIRST M</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="SSNID">999999999</odsPscuTAG>
<odsPscuTAG NAME="AUTHNAME">LAST,FIRST M</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
Page 90
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 91
OdsPscu TAG NAME Description Type Length First Data
Screen
reporting to Visa and MasterCard
and cannot be changed.
CHADDR1 Cardholder’s address – Address Line Alphanu 26 for NM CSR
1 meric Visa
24 for
MC
CHADDR2 Cardholder’s address – Address Line Alphanu 26 for NM CSR
2, see Appendix D for Foreign meric Visa
Address guidelines 24 for
MC
CHCITY Cardholder’s address – Full City Alpha 18 NM CSR
Name, see Appendix D for Foreign
Address guidelines
CHNAME Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CHSECONDARY Secondary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CHSECONDARYSSN Social Security Number of the Numeric 9 ANS
secondary cardholder, without
formatting
CHSTATE Cardholder’s address – 2 Character Alpha 2 NM CSR
State Abbreviation, see Appendix D
for Foreign Address guidelines
CHZIPCODE Cardholder’s address – 10 digit Zip Numeric 10 NM CSR
Code, see Appendix D for Foreign
Address guidelines
CLIENTID PSCU assigned client identifier Numeric 6
CNTRYCD Country code – Only returned when Alpha 3 NM EA
UA=Y is included in request
DATEOFBIRTH Primary Cardholder’s date of birth Numeric 8 NM CSR
in CCYYMMDD format
DATEOFBIRTHSEC Secondary Cardholder’s date of Numeric 8 ANS
birth in CCYYMMDD format
EMAILHOME E-mail address on file, home Alphanu 50 NM EP
location meric
Page 92
OdsPscu TAG NAME Description Type Length First Data
Screen
EMAILHOMESOLICIT Code indicating whether the home Alpha 1 NM EP
e-mail address can be used for
solicitation
Valid codes:
N - No, you cannot solicit the
cardholder using this e-mail address
Y - Yes, you can solicit the
cardholder using this e-mail address
Valid codes:
N - No, you cannot solicit the
cardholder using this e-mail address
Y - Yes, you can solicit the
cardholder using this e-mail address
Page 93
OdsPscu TAG NAME Description Type Length First Data
Screen
Blank – Normal
A – Auth blocked
PRIN Client-defined identifier of the level Numeric 4 BS6
within a System Bank Identifier that
is used
to group Agent Bank Identifiers
together for processing and
reporting
SECONDARYPIID Plastic Identifier (card number) for Numeric 16 PIR
the secondary cardholder. This
feature is only valid for Separate
Entity clients when PIID=Y is
included in the request.
SECONDARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
SHAREACCOUNT Savings account number on file with Numeric 17 NM AF
the credit account, if any
SHAREDRAFT Checking account number on file Numeric 17 NM AF
with the credit account, if any
SOCSECNBR Social Security Number of the Numeric 9 NM CSR
primary cardholder, without
formatting
SSNID Social Security Number of the Numeric 9 ANS
authorized user, without formatting
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and
reporting
WORKPHONE Cardholder’s work telephone Numeric 10 NM CSR
number, without formatting
Page 94
7.5 Extended Cardholder Information
The Extended Cardholder Information request returns information found in the 1403
request – Cardholder Information – and any Alternate Address information. The XML
collections in the response for e-mail addresses, authorized users and alternate
addresses will only be returned when there is data present on the First Data System. If
there are no e-mail addresses on file, no authorized users on the account, or no
alternate addresses on the account the associated nodes are not returned. The
information returned in the XML response is found on various BS screens, and the ANS
and NM ES screens in the First Data System.
Page 95
7.5.2 Sample URL and Response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1423&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1423</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CHZIPCODE">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG
NAME="MOTHERMAIDENNAME">LASTNAME</odsPscuTAG>
<odsPscuTAG NAME="CHADDR2">ADDRESS LINE 2
TEXT</odsPscuTAG>
<odsPscuTAG NAME="CHADDR1">ADDRESS LINE 1
TEXT</odsPscuTAG>
<odsPscuTAG NAME="SOCSECNBR">999999999</odsPscuTAG>
<odsPscuTAG NAME="CHSTATE">ST</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG
NAME="SHAREACCOUNT">99999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="SHAREDRAFT">99999999999999999</odsPscuTAG>
Page 96
<odsPscuTAG NAME="HOMEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG
NAME="CHSECONDARYSSN">999999999</odsPscuTAG>
<odsPscuTAG NAME="DATEOFBIRTH">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DATEOFBIRTHSEC"
>CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE
">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHCITY">CITYNAME</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="EMAILHOME">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="EMAILHOMESOLICIT">Y</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EMAILWORK">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="EMAILWORKSOLICIT">Y</odsPscuTAG>
</COLLECTION>
- - <COLLECTION>
<odsPscuTAG NAME="SSNID">999999999</odsPscuTAG>
<odsPscuTAG NAME="AUTHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="AUTHMBRSEQ">99999</odsPscuTAG>
<odsPscuTAG
NAME="AUTHEXTID">XXXXXXXXXXXXXXXXXXXXXXXX</odsPs
cuTAG>
<odsPscuTAG
NAME="AUTHDATEOFBIRTH">CCYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="SSNID">999999999</odsPscuTAG>
<odsPscuTAG NAME="AUTHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="AUTHMBRSEQ">99999</odsPscuTAG>
Page 97
<odsPscuTAG NAME="AUTHEXTID">
XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ALTCUSTTYPE">XX</odsPscuTAG>
<odsPscuTAG NAME="ALTMBRSEQ">99999</odsPscuTAG>
<odsPscuTAG NAME="ALTADDCAT">X</odsPscuTAG>
<odsPscuTAG NAME="ALTADDTYPE">XXXX</odsPscuTAG>
<odsPscuTAG NAME="ALTADDFMT">X</odsPscuTAG>
<odsPscuTAG NAME="ALTADDLINE1">ALTERNATE ADDRESS LINE
1 TEXT</odsPscuTAG>
<odsPscuTAG NAME="ALTADDLINE2">ALTERNATE ADDRESS LINE
2 TEXT</odsPscuTAG>
<odsPscuTAG NAME="ALTCITY">CITYNAME</odsPscuTAG>
<odsPscuTAG
NAME="ALTCOUNTRY">COUNTRYCODE</odsPscuTAG>
<odsPscuTAG
NAME="ALTSTPROV">STATE/PROVINCE</odsPscuTAG>
<odsPscuTAG
NAME="ALTPOSTCODE">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="ALTEFFDTSTART">YYYY-MM-
DD</odsPscuTAG>
<odsPscuTAG NAME="ALTEFFDTEND">YYYY-MM-
DD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ALTCUSTTYPE">XX</odsPscuTAG>
<odsPscuTAG NAME="ALTMBRSEQ">99999</odsPscuTAG>
<odsPscuTAG NAME="ALTADDCAT">X</odsPscuTAG>
<odsPscuTAG NAME="ALTADDTYPE">XXXX</odsPscuTAG>
<odsPscuTAG NAME="ALTADDFMT">X</odsPscuTAG>
<odsPscuTAG NAME="ALTADDLINE1">ALTERNATE ADDRESS LINE
1 TEXT</odsPscuTAG>
<odsPscuTAG NAME="ALTADDLINE2">ALTERNATE ADDRESS LINE
2 TEXT</odsPscuTAG>
<odsPscuTAG NAME="ALTCITY">CITYNAME</odsPscuTAG>
<odsPscuTAG
NAME="ALTCOUNTRY">COUNTRYCODE</odsPscuTAG>
Page 98
<odsPscuTAG
NAME="ALTSTPROV">STATE/PROVINCE</odsPscuTAG>
<odsPscuTAG
NAME="ALTPOSTCODE">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="ALTEFFDTSTART">YYYY-MM-
DD</odsPscuTAG>
<odsPscuTAG NAME="ALTEFFDTEND">YYYY-MM-
DD</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 99
OdsPscu TAG NAME Description Type Length First Data
Screen
ALTADDLINE2 Alternate address – Text Alphanumeric 26 NM ES
describing the second line of
the cardholder’s address
ALTADDFMT Alternate address format code Alpha 1 NM ES
– code determining how
address information appears –
valid entries include:
F – Formatted
U – Unformatted
ALTADDTYPE Alternate address type code – Alpha 4 NM ES
code representing the address
classification.
Valid codes:
BLL1 - Billing
LTTR - Letter
PLST - Plastics
MALR - Mailers
STMT - Statement
RFRN - Reference
Only the Primary Cardholder on
the account can have alternate
addresses for types MALR and
PLST.
Page 100
OdsPscu TAG NAME Description Type Length First Data
Screen
type code represents if the
information returned is for the
principal or secondary
cardholder:
01 - Principal cardholder
02 - Secondary cardholder
ALTEFFDTEND Alternate address – effective Numeric 10 NM ES
end date of the address, date
address is no longer in effect,
in CCYY-MM-DD format with
the dashes included
ALTEFFDTSTART Alternate address – effective Numeric 10 NM ES
start date of the address, date
address becomes effective, in
CCYY-MM-DD format with the
dashes included
ALTMBRSEQ Alternate address – member Numeric 3 NM ES
sequence number, represents
the member for which this
address is associated
ALTPOSTCODE Alternate address – zip code or Numeric 10 NM ES
postal code of the cardholder’s
address
ALTSTPROV Alternate address – state Alpha 25 NM ES
abbreviation or name of the
province in which the address
is located
AUTHDATEOFBIRTH Birth date of the authorized user Numeric 8 ANS
CCYYMMDD
AUTHEXTRID Authorized user’s external Alphanumeric 24 CU3
cardholder identification value
AUTHMBRSEQ Authorized user’s member Numeric 5 ANS
sequence number
AUTHNAME Authorized User’s name in Alpha 25 ANS
LastName,FirstName MI format
AUTHPIID Presentation Identifier (card Number 16 PIR
Page 101
OdsPscu TAG NAME Description Type Length First Data
Screen
number) for the authorized
user. This feature is only valid
for Separate Entity clients
when PIID=Y is included in the
request.
AUTHPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
CARDTYPE Description of the Card Alpha 25
program – Some valid entries
include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 102
OdsPscu TAG NAME Description Type Length First Data
Screen
Name, see Appendix D for
Foreign Address guidelines
CHNAME Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CHSECONDARY Secondary Cardholder’s name Alpha 26 NM CSR
in LastName,FirstName MI
format
CHSECONDARYSSN Social Security Number of the Numeric 9 ANS
secondary cardholder, without
formatting
CHSTATE Cardholder’s address – 2 Alpha 2 NM CSR
Character State Abbreviation,
see Appendix D for Foreign
Address guidelines
CHZIPCODE Cardholder’s address – 10 digit Numeric 10 NM CSR
Zip Code, see Appendix D for
Foreign Address guidelines
CLIENTID PSCU assigned client identifier Numeric 6 N/A
CNTRYCD Country code – Only returned Alpha 3 NM EA
when UA=Y is included in
request
DATEOFBIRTH Primary Cardholder’s date of Numeric 8 NM CSR
birth in CCYYMMDD format
DATEOFBIRTHSEC Secondary Cardholder’s date of Numeric 8 ANS
birth in CCYYMMDD format
EMAILHOME E-mail address on file, home Alphanumeric 50 NM EP
location
EMAILHOMESOLICIT Code indicating whether the Alpha 1 NM EP
home e-mail address can be
used for solicitation
Valid codes:
N - No, you cannot solicit the
cardholder using this e-mail
address
Page 103
OdsPscu TAG NAME Description Type Length First Data
Screen
Y - Yes, you can solicit the
cardholder using this e-mail
address
Valid codes:
N - No, you cannot solicit the
cardholder using this e-mail
address
Y - Yes, you can solicit the
cardholder using this e-mail
address
Page 104
OdsPscu TAG NAME Description Type Length First Data
Screen
level within a System Bank
Identifier that is used
to group Agent Bank Identifiers
together for processing and
reporting
SECONDARYPIID Plastic Identifier (card number) Numeric 16 PIR
for the secondary cardholder.
This feature is only valid for
Separate Entity clients when
PIID=Y is included in the
request.
SECONDARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
SHAREACCOUNT Savings account number on file Numeric 17 NM AF
with the credit account, if any
SHAREDRAFT Checking account number on Numeric 17 NM AF
file with the credit account, if
any
SOCSECNBR Social Security Number of the Numeric 9 NM CSR
primary cardholder, without
formatting
SSNID Social Security Number of the Numeric 9 ANS
authorized user, without
formatting
SYSTEM First Data-assigned identifier of Numeric 4 BS6
the level used to group
Principal Bank Identifiers
together for processing and
reporting
WORKPHONE Cardholder’s work telephone Numeric 10 NM CSR
number, without formatting
Page 105
7.6 Payment History Information
The Payment History Information request returns the account’s payment history
information. This information is similar to the information found on the CPH screens in
the First Data System. Refer to Appendix G for explanation of the HISTORY node.
NOTE: PSCU reserves the right to add but not remove new fields utilizing the VERSION=2
parameter in the future. The user is responsible for ensuring all consuming applications
are capable of handling additional future fields when utilizing the VERSION=2
parameter.
Page 106
7.6.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1414&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
<INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1414</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="NEXTPAYDATE">MM-DD-YY</odsPscuTAG>
Page 107
<odsPscuTAG
NAME="MINPAYAMT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="AMTPAST_DUE">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CASHADVANCEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="PURCHASEAPR">99.999</odsPscuTAG>
<odsPscuTAG
NAME="EXTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="CREDITLIFEINDICATOR">9</odsPscuTAG>
<odsPscuTAG NAME="OVERLIMITHISTORY">99</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELINQ">999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE1">999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE2">999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE3">999</odsPscuTAG>
<odsPscuTAG NAME="HISTORY">XXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="LASTMONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="2MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="3MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="4MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="5MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="6MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="7MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="8MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
Page 108
<odsPscuTAG NAME="9MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="10MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="11MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
<odsPscuTAG NAME="12MONTH">HISTORY CODE
DESCRTIPTION</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="AMTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PMTDUEDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELQ">999</odsPscuTAG>
<odsPscuTAG
NAME="DELQAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="POSTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPMTDUE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CYCLEDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="EFFECTIVEDATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="AMTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PMTDUEDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELQ">999</odsPscuTAG>
<odsPscuTAG
NAME="DELQAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="POSTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPMTDUE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CYCLEDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="EFFECTIVEDATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="AMTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PMTDUEDATE">YYMMDD</odsPscuTAG>
Page 109
<odsPscuTAG NAME="DAYSDELQ">999</odsPscuTAG>
<odsPscuTAG
NAME="DELQAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="POSTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPMTDUE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CYCLEDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="EFFECTIVEDATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="AMTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PMTDUEDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELQ">999</odsPscuTAG>
<odsPscuTAG
NAME="DELQAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="POSTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPMTDUE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CYCLEDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="EFFECTIVEDATE">YYMMDD</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 110
OdsPscu TAG NAME Description Type Length First
Data
Screen
2MONTH Full description in words of Alpha 35
the second character
position of the HISTORY field
on the BS Screen
3MONTH Full description in words of Alpha 35
the third character position
of the HISTORY field on the
BS Screen
4MONTH Full description in words of Alpha 35
the fourth character position
of the HISTORY field on the
BS Screen
5MONTH Full description in words of Alpha 35
the fifth character position
of the HISTORY field on the
BS Screen
6MONTH Full description in words of Alpha 35
the sixth character position
of the HISTORY field on the
BS Screen
7MONTH Full description in words of Alpha 35
the seventh character
position of the HISTORY field
on the BS Screen
8MONTH Full description in words of Alpha 35
the eighth character
position of the HISTORY field
on the BS Screen
9MONTH Full description in words of Alpha 35
the ninth character position
of the HISTORY field on the
BS Screen
10MONTH Full description in words of Alpha 35
the tenth character position
Page 111
OdsPscu TAG NAME Description Type Length First
Data
Screen
of the HISTORY field on the
BS Screen
11MONTH Full description in words of Alpha 35
the eleventh character
position of the HISTORY field
on the BS Screen
12MONTH Full description in words of Alpha 35
the twelfth character
position of the HISTORY field
– this represents the oldest
history period on the BS
Screen
AGENT Client-defined identifier of Numeric 4 BS6
the level within a Principal
Bank Identifier that is used
to group accounts together
for processing and reporting
AMTPAID Amount of the payment Numeric 16 CPH
received, shown as a signed
number in dollars and cents
with decimal point shown in
response
AMTPAST_DUE Amount past due, if any, in Numeric 16 BS
whole dollars without
decimal places
CARDTYPE Description of the Card Alpha 25
program – Some valid
entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
Page 112
OdsPscu TAG NAME Description Type Length First
Data
Screen
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 113
OdsPscu TAG NAME Description Type Length First
Data
Screen
insurance premium is
charged, based on the plan
parameters in the Credit Life
section (CP IO CL) of the
Product Control File
CREDITLIMIT The maximum credit Numeric 16 BS
extended to the account
(this amount, less the
current balance and any
outstanding authorizations,
gives the available credit on
the account), shown as a
whole number without
decimal places
CURRENTBALANCE Current balance on account, Numeric 16 BS
shown as a signed number
with 2 decimal places and
the decimal point in the
response
CYCLE1 Count of times the account Numeric 3 BS
has been one-cycle
delinquent in the last two
years plus year to date.
Each time the account
becomes one-cycle
delinquent; the First Data
System adds one to this
field. If the cardholder clears
the delinquency within this
cycle, the number in this
field remains. If the account
moves to the next higher
delinquency level, the FD
System subtracts one from
the counter in this field and
Page 114
OdsPscu TAG NAME Description Type Length First
Data
Screen
adds one to the counter at
the next higher delinquency
level.
CYCLE2 Count of times the account Numeric 3 BS
has been two cycles
delinquent in the last two
years plus year to date.
Each time the account
becomes two cycles
delinquent, the First Data
System adds one to this
field. If the cardholder clears
the delinquency within this
cycle, the number in this
field remains. If the account
moves to the next higher
delinquency level, the FD
System subtracts one from
the counter in this field and
adds one to the counter at
the next higher delinquency
level.
CYCLE3 Count of times the account Numeric 3 BS
has been three-or-more-
cycles delinquent in the last
two years plus year to date.
Each time the account
becomes three-or-more-
cycles delinquent, the FD
System adds one to this
field. If the cardholder clears
the delinquency within this
cycle, the number in this
field remains. If the account
moves to the next higher
Page 115
OdsPscu TAG NAME Description Type Length First
Data
Screen
delinquency level, the FD
System adds one to this
field. For example, if the
account moves from three-
cycles to four-cycles
delinquent, the FD System
adds one to this field.
CYCLEDATE The statement cycle date of Numeric 8 CPH
this payment, in
CCYYMMDD format
DAYSDELINQ Number of Days the account Numeric 3 BS
is delinquent
DAYSDELQ Number of days this Numeric 2 CPH
payment is delinquent
DELQAMT Amount of this payment Numeric 19 CPH
that is attributable to past
payments that are now
delinquent, typically this is
the minimum payment that
was due on the prior
payment - shown with two
decimal places and the
decimal point shown in
response
EFFECTIVEDATE The effective date of this Numeric 6 CPH
payment, in YYMMDD
format (Note: Some
situations may return
000000 as the value)
EXTCODE External Status Code as Alpha 1 BS
found within the First Data
system, one character -
Issuer-assigned status code
determining specific account
Page 116
OdsPscu TAG NAME Description Type Length First
Data
Screen
processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited
(I)
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
EXTSTATUSCODE External Status Code, Alpha 30
described in words (for valid
descriptions, see EXTCODE)
FULLMINPAYDUE Full minimum payment due Numeric 19 CSS
as calculated at statement
cycle.
Format:
9999999999999999.99
HISTORY Identifier of the 12-month Alpha 12 BS
account activity history. The
12 status flags rotate when
the account cycles so that
the leftmost flag indicates
the account’s status during
the last cycle and the
rightmost flag indicates the
account’s status during the
current cycle one year ago.
Page 117
OdsPscu TAG NAME Description Type Length First
Data
Screen
the account’s status changes
due to an account transfer
or due to the posting of an
across-cycle reversal,
adjustment, or interest
charge-off. Only the first flag
on the left (last cycle)
changes by these postings.
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTSTATUSCODE Current Internal Status Alpha 30
Page 118
OdsPscu TAG NAME Description Type Length First
Data
Screen
Code, in words (for valid
descriptions, see INTCODE)
LASTMONTH Full description in words of Alpha 35
the first character position
of the HISTORY field on the
BS screen – this represents
the most recent period
LASTPAYAMT Amount of the last payment, Numeric 19 BS7
in dollars and cents with
decimal point shown in
response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note:
Some situations may return
000000 as the value)
MINPAYAMT The minimum payment Numeric 16 BS
required to retain a current
status on the account (this
amount may or may not
include overlimit and or past
due amounts) and is shown
as a whole number without
decimal places. This value
does reflect any payment
made during the current
cycle.
MINPMTDUE Minimum amount due for Numeric 19 CPH
this payment , shown with
two decimal places and the
decimal point shown in
response
NEXTPAYDATE Date the next payment is Numeric 8 BS4
due on the account, in MM-
DD-YY format
Page 119
OdsPscu TAG NAME Description Type Length First
Data
Screen
Page 120
OdsPscu TAG NAME Description Type Length First
Data
Screen
Format
99999999999999.9999
PAYOFFDAY10 Pay off ten days out Numeric 19 TBD
Format
99999999999999.9999
PMTDUEDATE Date the payment was due, Numeric 6 CPH
shown in YYMMDD format
(Note: Some situations may
return 000000 as the value)
POSTDATE The posting date of the Numeric 8 CPH
payment, in CCYYMMDD
format
PRIN Client-defined identifier of Numeric 4 BS6
the level within a System
Bank Identifier that is used
to group Agent Bank
Identifiers together for
processing and reporting
PURCHASEAPR Annual Percentage Rate Numeric 6 NM SA2
applying to purchases and
merchandise, shown as a
percentage with 3 decimal
places
SYSTEM First Data-assigned identifier Numeric 4 BS6
of the level used to group
Principal Bank Identifiers
together for processing and
reporting
Note: The following fields will only be returned when parameter VERSION=2 is passed.
CASHADVANCEOUTSTANDINGBAL Outstanding cash balance Numeric 16
AMT
TENDAYPAYOFF Estimated payoff amount for Numeric 16
the account in 10 days in
dollars and cents.
Page 121
OdsPscu TAG NAME Description Type Length First
Data
Screen
PERDAYINTEREST Current daily interest in Numeric 16
dollars and cents.
LASTSTMTDATE Date of last statemen in Numeric 6
YYMMDD format.
Note: The TENDAYPAYOFF calculation is specific to PCF setting 0: Current Balance + (per
day interest*10) + (per day interest * days since last statement).
Page 122
7.7 Payment On Demand - Get Info
The Payment On Demand – Get Info request returns the current settings for the DDA
number, Routing & Transit number, outstanding balance and the AutoPay Flag values.
These values are required for the execution of the Payment On Demand function 1410.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1426&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&FIXEDAUTOPAYAMT=Y&AUTOPAY=Y&
Page 123
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>B2211E44-F6EA-3FD7-007D-C6CA19C3DB72</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1426</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="AUTOPAYFLAG">0</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LAST,TWO
M</odsPscuTAG>
<odsPscuTAG
NAME="AUTOPAYRT">999999999</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">999999999999.99</odsPscuT
AG>
<odsPscuTAG NAME="
FIXEDAUTOPAYAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG
NAME="SHAREACCOUNT">99999999999999999</odsPscuTAG>
<odsPscuTAG NAME="DEMANDPAYCD">X</odsPscuTAG>
<odsPscuTAG
NAME="DEMANDPAYAMT">9999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="AUTOPAYDDA">999999999</odsPscuTAG>
Page 124
- <COLLECTION>
<odsPscuTAG
NAME="ISALLOWEDACCESS">FALSE</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYSTARTDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYENDDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYENRDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="AUTOSKIPPAY">X</odsPscuTAG>
<odsPscuTAG NAME="AUTOFLAGXFER">ACCOUNT
TYPE</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 125
OdsPscu TAG NAME Description Type Length First
Data
Screen
AUTOPAYENRTYPE Enrollment Type Alpha 1 NM AF
Valid codes:
P - Paper
T - Telephone
W - Web
blank - Either not enrolled or the
enrollment source is not known
AUTOPAYFLAG Code representing whether the Alpha 1 NM AF
cardholder account is set up for numeric
recurring automatic payments.
Values:
C - Suspend the cardholder's
automatic payment for the current
cycle.
N - Do not suspend the cardholder's
automatic payment for the current
cycle.
AUTOPAYSTARTDT Auto Pay Start Date. This value will be Numeric 6 NM AF
included when the AUTOPAY=Y is
included in the request.
Page 126
OdsPscu TAG NAME Description Type Length First
Data
Screen
Format: CCYYMMDD
CARDTYPE Description of the Card program – Alpha 25
Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 127
OdsPscu TAG NAME Description Type Length First
Data
Screen
C - Internet-initiated transaction to be
drawn from a checking account
The System enters WEB in the
standard entry code field on the
transmitted ACH file
S - Internet-initiated transaction to be
drawn from a savings account
The System enters WEB in the
standard entry code field on the
transmitted ACH file.
FIXEDAUTOPAYAMT Payment amount as defined by the Numeric 16 NM AF
card holder
ISALLOWEDACCESS Indicator confirming status of Alpha
payment request; this PSCU specific
XML tag is used for the PAYXML
Function 1410; possible values are
TRUE or FALSE
Page 128
OdsPscu TAG NAME Description Type Length First
Data
Screen
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and
reporting
Page 129
7.8 Recent Activity Information
The Recent Activity Information request will return any account activity that has
occurred since the last statement, including authorizations and posted transactions.
The Recent Activity information is similar to the information found on the CDA screen in
the First Data System.
Page 130
Parameter Description Type Required Length
/
Optional
authorization expiration
date and PI Type
A – includes information
from X, Y and Z plus original
authorization amount and
PIID for authorization
ADDLNONMON Y – Include additional Fixed Optional 1
NonMon information in the
response
X – include last non mon,
last non mon date, address
change date
Z – Also include open day,
email address, mobile
phone and credit score
A – Include above and the
address verification flag
ADDLTRAN Y – include the expanded Fixed Optional 1
reference number and
sequence number in the
posted transaction
collections
X – also include transaction
id, merchant city and state,
and point of sale entry
mode for posted
transactions
A – also include greater
than 500 transactions
ALTSTMT Y – Include alternate Fixed Optional 1
statement code in the
response
BSCR Y-Include the behavior Fixed Optional 1
score in the response
Page 131
Parameter Description Type Required Length
/
Optional
CASHADV Y – Include cash advance Fixed Optional 1
information
COMPINFO Y – Include company Fixed Optional 1
account type and company
name in the request
DYNAMICFEES ON Fixed Optional 2
EXTSTAT Y – Include date and reason Fixed Optional 1
code for external status
OPA Y – Include OPA in response Fixed Optional 1
PET Y-Include the Personal Fixed Optional 1
Emboss Text in the
response
PIID Y – Returns Plastic Fixed Optional 1
Identifier (card number)
associated with the
transaction. This feature is
only valid for Separate
Entity clients.
PS Y – Include pricing strategy Fixed Optional 1
PYI Y-Include the previous Fixed Optional 1
interest billed and paid
SHOWAUTHNUM ON – Use to indicate Fixed Optional 2
Authorization Number is to
be returned in the
transaction collection. This
can be used to associate an
Authorization to a posted
transaction
SHOWMERCHCODE ON – Use to indicate Fixed Optional 2
Merchant Code is to be
returned in the transaction
collection
TRANACCT Y – Include the PIID of the Fixed Optional 1
actual plastic used for the
Page 132
Parameter Description Type Required Length
/
Optional
transaction when the
CARDNUMBER is a control
account
TRANTYPE Y – Include transation type Alpha Optional 1
code for posted
transactions
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
UPC UPC=ON FIXED Optional 2
UPC codes 1 – 12 will be
included in the response
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
XREF Y – Include cross reference Fixed Optional 1
numbers
YTDINTBILLED YES-Return YTD Interest Fixed Optional 3
Billed
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1415&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
Page 133
1415&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&SHOWM
ERCHCODE=ON&SHOWAUTHNUM=ON
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1415</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="YTDINTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="LASTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
Page 134
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="NEXTPAYDATE">MM-DD-YY</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="EXTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="AUTHMERCHSTATE">ST</odsPscuTAG>
<odsPscuTAG
NAME="AUTHPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG
NAME="AUTHTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="AUTHAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="AUTHACTCODE"/>
<odsPscuTAG NAME="AUTHMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHCITY">CITY
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHNAME">MERCHANT
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHTRANS">XX</odsPscuTAG>
<odsPscuTAG
NAME="AUTHDECLINEREASONCODE">XX</odsPscuTAG>
<odsPscuTAG NAME="AUTHREF">999999</odsPscuTAG>
<odsPscuTAG
NAME="AUTHMERCHNMBR">9999999999999</odsPscuT
AG>
<odsPscuTAG NAME="AUTHZIP">999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
Page 135
<odsPscuTAG NAME="AUTHMERCHSTATE">ST</odsPscuTAG>
<odsPscuTAG
NAME="AUTHPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG
NAME="AUTHTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="AUTHAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="AUTHACTCODE"/>
<odsPscuTAG NAME="AUTHMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHCITY">CITY
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHNAME">MERCHANT
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHTRANS">XX</odsPscuTAG>
<odsPscuTAG
NAME="AUTHDECLINEREASONCODE">XX</odsPscuTAG>
<odsPscuTAG NAME="AUTHREF">999999</odsPscuTAG>
<odsPscuTAG
NAME="AUTHMERCHNMBR">9999999999999</odsPscuT
AG>
<odsPscuTAG NAME="AUTHZIP">999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
Page 136
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="EMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
Page 137
OdsPscu TAG NAME Description Type Length First
Data
Screen
ACCTCROSSREF1 Cross reference 1 Numeric 16 BS
ACCTCROSSREF2 Cross reference 2 Numeric 16 BS
ACCTCROSSREF3 Cross reference 3 Numeric 16 BS
ADDRCHDT Address change date Numeric 6 NM EP
ADDRFLG Address Verification Flag Alpha 1 NM AFR
AFFINITYNUMBER Affinity number on the account. This Numeric 16 NM CS
value will be returned when the
ADDLNONMON parameter is included
in the request.
AGENT Client-defined identifier of the Numeric 4 BS6
level within a Principal Bank
Identifier that is used
to group accounts together for
processing and reporting
ALTSTMT Alternate Statement Code Numeric 1 NM CS
AMTPAST_DUE Amount past due, if any, in whole Numeric 16 BS
dollars
Available when ACCTSUM=ON
ANNUALACT Annual Activity CD Numeric 1 NM AF
AUTHAGED A - Authorization has a matching Alpha 1 CDE
posted transaction.
D – Authorization was declined
Blank – transaction has not yet
posted.
E – Estimated
P – Pending Merchandise return
I - Incremental
AUTHACTCODE Valid values are: Alpha 1 BS &
A - Get new address. CDE
Do not print letters and
delinquency notification
statements.
You can override the effects of this
code on correspondence generated
via the Cardholder Letters System
Page 138
OdsPscu TAG NAME Description Type Length First
Data
Screen
when the Correspondence Flag on
the account record is set to 1 and
the Statement Hold Code on the
record is set to R.
To override the code's effects, take
the following actions.
Set the CORR FLAG
OVERRIDE field on the LT01
03, Letter Definition screen,
to P - Print, for each item
you want printed despite an
Authorization Control Code
of A.
Set the Letter Override
Suppression Flag parameter
in the Operational Controls
section (PF CM OC) of the
Product Control File to Y,
which overrides a Hold
Correspondence Flag of 1.
The System automatically
removes this code when an
address change posts to the
account record. However, if
you use the Automatic Auth
Flag in the Authorization
Settings section (AU BC AS)
of the PCF as part of an
Adaptive Control
Authorization strategy, you
must update the address
flag and/or the home phone
flag as well as entering the
new address or home phone
number.
Page 139
OdsPscu TAG NAME Description Type Length First
Data
Screen
M - This account has an unresolved
dispute.
This code prohibits the printing of
past due letters. This code also
places a hold code on the
statement.
Q - Always authorize unless an
external status prohibits
authorization. This code prohibits
the printing of the following.
Delinquency notification
statements
Statement message
generated from delinquency
message parameters in the
PCF
Delinquency letters
Overlimit courtesy
statements
Statement message
generated from overlimit
message parameters in the
PCF
Overlimit letters
S - Identify all convenience checks
as stop-payments.
V - Prohibit printing of the same
items listed for valid code Q. With a
statement hold code other than Y,
the System sends manually
requested letters.
Y - Always decline authorization.
The System automatically removes
this code when the account is no
Page 140
OdsPscu TAG NAME Description Type Length First
Data
Screen
longer delinquent. This code does
not apply to airlines.
blank - Normal authorization
processing occurs.
Page 141
OdsPscu TAG NAME Description Type Length First
Data
Screen
I - Verification performed by
Interchange
O - Verification performed using
method other than PIN
R - Verification performed by CPU
acquirer
U - First Data unable to perform
verification
V - Verification performed by First Data
X - Declined PIN on ATM balance
inquiry
blank - Not a PIN Management System
processor
AUTHPITYPE PI Type of card used for Numeric 2 CDE
authorization
AUTHPOSENTRYMODE Code representing how the Numeric 2 CDE
merchant entered the transaction.
Page 142
OdsPscu TAG NAME Description Type Length First
Data
Screen
transmission has been unaltered)
95 Chip/smart card data is
unreliable (Visa only)
AUTHREF System-assigned identifier of the Numeric 6 CDA
authorization approval code for the
approved transaction - this field is
blank if the authorization was
declined.
AUTHTIME Time of the authorization Numeric 6 CDE
Format: hhmmss
AUTHTRANACCT PIID of the actual plastic used when Numeric 16
the CARDNUMBER is a control
account
AUTHTRANCD Type of transaction authorization Alpha 2 CDA
Valid values:
AA - Authorization adjustment
AP - Preauthorization request
approved
CA - Cash advance authorization
approved
CD - Cash advance authorization
declined
CE - Cash advance authorization
approved by expansion
CO - Override declined cash advance
CP - Cash advance authorization
approved by positive identification
CS - Cash referral
CT - Cash advance authorization
approved by name
CV - Cash approval by VIP
CX - Cash advance authorization
manually declined
DA - Duplicate authorization
DC - Cash authorization approved
without issuer contact
DM - Merchandise authorization
approved without issuer contact
DP - Preauthorization request denied
IA - Issuer’s adjustment
MA - Merchandise authorization
Page 143
OdsPscu TAG NAME Description Type Length First
Data
Screen
approved
MC - In-store return
MD - Merchandise authorization
declined
ME - Merchandise authorization
approved by expansion
MI - Right-time payment
MO - Override declined merchandise
authorization
MP - Merchandise authorization
approved by positive identification
MR - Right-time pay/reversal
MS - Merchandise referral
MT - Merchandise authorization
approved by name
MV - Merchandise approval by VIP
MX - Merchandise authorization
manually declined
PA - Permanent authorization request
PP - Visa® and Mastercard® person-
to-person payment transaction
approval
PR - Visa and Mastercard person-to-
person payment transaction reversal
PX - Visa and Mastercard person-to-
person payment transaction decline
PZ - Permanent authorization
adjustment
QA - Merchandise Return Adjustment
QD - Reserved for restricted use
QQ - Reserved for restricted use
QR - Reserved for restricted use
QZ - Merchandise Return Adjustment
Declined
VA - Private label ETC return posted at
the time of return
XC - Manual override cash advance
authorization
XM - Manual override merchandise
authorization
AUTHTRANDATE Transaction date for the Numeric 6 CDA
authorization, in YYMMDD format
(Note: Some situations may return
Page 144
OdsPscu TAG NAME Description Type Length First
Data
Screen
000000 as the value)
AUTHTRANS Transaction code that represents Alpha 2 CDA
the type of authorization action,
valid codes are listed in Appendix F
of this document.
AUTHZIP Zip or postal code of the merchant Numeric 9 CDE
where the authorization took place
BILLINGCYCLE Billing Cycle code. This value will be Numeric 2 NM CS
returned when the ADDLNONMON
parameter is included in the request
BSCR Behavior Score Numeric 3 BS
Included when the BSCR=Y is in the
request
CARDTYPE Description of the Card program – Alpha 25
Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 145
OdsPscu TAG NAME Description Type Length First
Data
Screen
LastName,FirstName MI format
CHSECONDARY Secondary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CLIENTID PSCU assigned client identifier Numeric 6
CMPYACCTTYPE Company account type when Alpha 1 NM AC
COMPINFO=Y is included in the
request
S – Sub Account
C – Countrol Account
CMPYNAME Company Name when Alpha 12 NM AC
COMPINFO=Y Numeric
CRDTBURSCOR Credit bureau score Numeric 3 NM CR
CREDITAVAIL Dollar amount of the account's Numeric 16 BS
unused credit as of the indicated
date, shown as a whole number
without decimal places
CREDITLIMIT The maximum credit extended to Numeric 16 BS
the account (this amount, less the
current balance and any
outstanding authorizations, gives
the available credit on the account),
shown as a whole number without
decimal places
CREDITLINEAM Amount of the previous credit line This Numeric 15 TBD
value will be returned when the
ADDLNONMON parameter is included
in the request
CREDITLINECD Code representing the type of the last Alpha- 1 TBD
credit line change. This value will be Numeric
returned when the ADDLNONMON
parameter is included in the request
Valid codes:
A - Automatic
C - Permanently deferred
D - Adaptive Control decrease
I - Adaptive Control increase
M - Manual
O - Never increased
Page 146
OdsPscu TAG NAME Description Type Length First
Data
Screen
R - Adaptive Control increase or
decrease using the LSX transaction
S - Automatic increase due to check
transaction maximum line without an
available credit buffer
T - Increase due to additional deposit
for secured account
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to check
transaction maximum line with an
available credit buffer
3 - Decrease due to mid-cycle credit
line processing via Adaptive Control
4 - Increase due to mid-cycle credit line
processing via Adaptive Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was established. Numeric 2 TBD
This value will be returned when the
ADDLNONMON parameter is included
in the request
Format: MMYY
CURRENTBALANCE Current balance on account, shown Numeric 16 BS
as a signed number with 2 decimal
places and the decimal point in the
response
DATELASTPLASTICORDER Date of the last order of plastics on Numeric 6 PIR
the account, in YYMMDD format
(Note: Some situations may return
000000 as the value)
Available when ACCTSUM=ON
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
Available when ACCTSUM=ON
DTLAUTHNUM Authorization Number for the Numeric 5 CDE
Page 147
OdsPscu TAG NAME Description Type Length First
Data
Screen
transaction; included in response
when SHOWAUTHNUM=ON
included in the request
DTLDESC Description of the item, in words Alpha 40 CDA
DTLEXPREF Expanded reference number Numeric 17 CDE
DTLMERCHCATCODE Merchant Code for the transaction; Numeric 5 CDE
included in response when
SHOWMERCHCODE=ON included in
the request
DTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
DTLMERCHSTATE Merchant State Alpha 2 CDE
DTLPOSTDATE Posting Date of the item, in Numeric 6 CDA
YYMMDD format (Note: Some
situations may return 000000 as the
value)
DTLSEQNUM Sequence number Numeric 5 CDA
CSS
DTLINDTRANID Detail transaction indicator Numeric
DTLTRANACCT PIID of the actual plastic used when Numeric 16 CDE
the CARDNUMBER is a control
account
DTLTRANTYPE Transaction Type Code – refer to Numeric 3 CDE
Appendix N for list of transaction
type codes
EMAILADDR Email address Alpha Variabl NM EP
Numeric e
EMBEDDEDFEEAMT The Dynamic Fees value that will Numeric 15 CDA
display if the DYNAMICFEES=ON is
included in the URL request.
ESTATEMENTENROLLMENTST Only Valid for SCS eStatement Alpha 1 NM EBP
ATUS participating Credit Unions
Page 148
OdsPscu TAG NAME Description Type Length First
Data
Screen
Valid Codes:
B – Cardholder receives both Paper
and Electronic Statements
D – Cardholder receives both Paper
and Electronic Statements and
currently is subject to delinquency
processing
E – Cardholder receives Electronic
Statements
L - The cardholder receives both
electronic and paper statements
and is billed additionally for paper
statements.
Blank – The cardholder is not
enrolled in eStatements
Available when ACCTSUM=ON
EXPIREDATE Date the credit account expires, in Numeric 4 BS
MMYY format
Available when ACCTSUM=ON
EXPNRFRNNR Reference number for the Alpha 17 CDA
transaction item numeric
EXTCODE External Status Code as found Alpha 1 BS
within the First Data system, one
character - Issuer-assigned status
code determining specific account
processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited (I)
Page 149
OdsPscu TAG NAME Description Type Length First
Data
Screen
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
EXTSTATUSCODE External Status Code, described in Alpha 30
Words (for valid descriptions, see
EXTCODE)
EXTSTATDT Date the external status changed Numeric 6 NM SA1
EXTSTATRESCD Reason for the external status Numeric 2 NM SA1
change
FRAUDSCORE Fraud Score Numeric 3 NM CR
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM CR
Format: YYMMDD
FRAUDSTRAT Current fraud strategy assigned to the Numeric 2 NM CR
account
FRAUDSTRATDT Date current fraud strategy assigned to Numeric 6 NM CR
the account
Format: YYMMDD
FRAUDSUSPENDSTARTDT Start date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may be
null.
Format:
YYMMDD
FRAUDSUSPENDSTRATEGY Strategy that will be enforced during Numeric 2 NM CR
time period defined by start and end
date
FRAUDSUSPENDENDDT End date for the suspension of the fraud Numeric 6 NM CR
strategy. This parameter may be null.
Format:
YYMMDD
INTCODE Internal Status Code as found Alpha 1 BS
within the First Data system, one
character - System-assigned code
determining specific account
processing
Valid codes:
Credit balance (N)
Page 150
OdsPscu TAG NAME Description Type Length First
Data
Screen
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTSTATUSCODE Current Internal Status Code, in Alpha 30
Words (for valid descriptions, see
INTCODE)
LASTBALANCE Outstanding balance on the last Numeric 19 BS
statement, shown as a signed
number with 2 decimal places and
decimal point shown in response
LASTCREDITLINEDATE Date of the last credit limit Numeric 4 BS
adjustment, in MMYY format
Available when ACCTSUM=ON
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
LASTPAYAMT Amount of the last payment, in Numeric 19 BS7
dollars and cents with decimal point
shown in response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note: Some
situations may return 000000 as the
value)
LASTSTMTDATE Date of the last statement, in Numeric 6 BS2
YYMMDD format (Note: Some
situations may return 000000 as the
value)
MINPAYAMT The minimum payment required to Numeric 16 BS
retain a current status on the
account (this amount may or may
not include overlimit and or past
due amounts) and is shown as a
whole number without decimal
places. This value does reflect any
payment made during the current cycle.
Page 151
OdsPscu TAG NAME Description Type Length First
Data
Screen
MISC1 Miscellaneous field 1. This value will be AlphaNum 4 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC2 Miscellaneous field 2. This value will be AlphaNum 5 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC3 Miscellaneous field 3. This value will be AlphaNum 7 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC4 Miscellaneous field 4. This value will be AlphaNum 10 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC5 Miscellaneous field 5. This value will be AlphaNum 8 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC6 Miscellaneous field 6. This value will be AlphaNum 12 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC7 Miscellaneous field 7. This value will be AlphaNum 10 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC8 Miscellaneous field 8. This value will be AlphaNum 10 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC9 Miscellaneous field 9. This value will be AlphaNum 10 NM CS
returned when the ADDLNONMON eric
parameter is included in the request
MISC10 Miscellaneous field 10. This value will AlphaNum 10 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC13 Miscellaneous field 13. This value will AlphaNum 50 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MOBILEPHONE Mobile phone Numeric 10 NM EP
NEXTPAYDATE Date the next payment is due on Numeric 8 BS4
the account, in MM-DD-YY format
Page 152
OdsPscu TAG NAME Description Type Length First
Data
Screen
OPA Account number, mostly relevant Numeric 16 BS
to separate entity
OPENDATE Date the credit account was Numeric 4 BS
opened, in MMYY format
Available when ACCTSUM=ON
OPENDATEDAY Day of the month the account was Numeric 2 BS9
opened
PERSONZN Personal Emboss Text Alpha Up to 26 PID
Included when PET=Y is in the Numeric
request
PIID Plastic Identifier (card number) Numeric 16 CDE
associated with the transaction.
This feature is only valid for Separate
Entity clients when PIID=Y is included
in the request.
PRICINGSTRATEGY Pricing strategy on the account Alpha 4 NM ST
Numeric
PRIN Client-defined identifier of the level Numeric 4 BS6
within a System Bank Identifier that
is used
to group Agent Bank Identifiers
together for processing and
reporting
PURCHASEAPR Annual Percentage Rate applying to Numeric 6 NM SA2
purchases and merchandise, shown
as a percentage with 3 decimal
places.
Available when ACCTSUM=ON
PYIBLLDAMT Previous years interest billed Numeric 13 NM PH
Included when PYI=Y is in the
request
PYIPDAMT Previous years interest paid Numeric 13 NM PH
Included when PYI=Y is in the
request
SPCLFLAGS Special Flags 5 – 8. This value will be Alpha 4 BS
Page 153
OdsPscu TAG NAME Description Type Length First
Data
Screen
returned when the ADDLNONMON
parameter is included in the request
STATUS External Status Code as found Alpha 1 BS
within the First Data system, one
character – see valid codes listed
above in EXTCODE node
Available when ACCTSUM=ON
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and
reporting
TRANAMT Amount of the item, shown as a Numeric 15 CDA
signed number in dollars and cents
with 2 decimal places and a decimal
point shown in the response
TRANDATE Transaction date for the item, in Numeric 6 CDA
YYMMDD format (Note: Some
situations may return 000000 as the
value)
TRANTYPE Transaction type Numeric 3 CDE
See Appendix N for list of
transaction types
UPC1 UPC 1 Alpha 1 NM CC
Numeric
UPC2 UPC 2 Alpha 1 NM CC
Numeric
UPC3 UPC 3 Alpha 1 NM CC
Numeric
UPC4 UPC 4 Alpha 1 NM CC
Numeric
UPC5 UPC 5 Alpha 1 NM CC
Numeric
UPC6 UPC 6 Alpha 2 NM CC
Numeric
Page 154
OdsPscu TAG NAME Description Type Length First
Data
Screen
UPC7 UPC 7 Alpha 2 NM CC
Numeric
UPC8 UPC 8 Alpha 3 NM CC
Numeric
UPC9 UPC 9 Alpha 3 NM CC
Numeric
UPC10 UPC 10 Alpha 4 NM CC
Numeric
UPC11 UPC 11 Alpha 5 NM CC
Numeric
UPC12 UPC 12 Alpha 6 NM CC
Numeric
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of the Alpha 25 BS
plastic, described in words with the
First Data code for the activation
status following the description in
parenthesis – please see Appendix
C of this document for further
information.
Available when ACCTSUM=ON
USF14 Four character Userflags string Alpha 4 BS
YTDINTBILLED Amount of interest billed on the Numeric 15 BS
account Year-To-Date
YTDINTPAID Amount of interest paid Year-to- Numeric 15 BS
Date, in dollars and cents with
decimal point shown in response
Page 155
7.9 Rewards/Rebates Information
The Rewards function 1407 supports both the traditional Rewards program and the new
Premium Loyalty Program (PLP). The credit union must participate in a rewards program
– traditional or PLP – for the function to return data. The credit unions Account
Executive or Service Executive manages the enrollment and participation in rewards.
This function will return the information for Rewards for both Omaha and Wilmington
accounts when PSCU is providing Rewards processing.
The Rewards Information request will return the Rewards Information for all reward
programs beginning with ZZ. This information is similar to the information found on the
BON screens in the First Data System.
VERSION=2: If the optional parameter VERSION=2 is included in the request the
CURewards participation check is skipped. All rewards programs will be returned, not
just those having a”ZZ” prefix. The name of each program will be returned within each
collection as the alphanumericfield PROGRAMNAME.
The Rewards information provided in the 1407 response will come from the PLP
platform.
Page 156
Parameter Description Type Required Length
/
Optional
EXPIRED Y – include expiring points Fixed Optional 1
collection
Only valid for PLP
PROGRAM Y- Return the program names Fixed Optional 1
in the response.
TERMDATE Y – Will return the termination Fixed Optional 1
date of each program
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
W YES – The request is being Fixed Optional 3
submitted for a Wilmington
account
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=1
02&FUNCTIONID=1407&REQUESTID=102&CARDNUMBER=9999999999999999
&CLIENTID=9999
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1407</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CHNAMEFDR">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Platinum Traditional</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
Page 157
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="SPAID">9999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="ISALLOWEDACCESS">TRUE</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 158
OdsPscu TAG NAME Description Type Length First
Data
Screen
These values are primarily used for
reporting to Visa and MasterCard
and cannot be changed.
CHNAME Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CHNAMEFDR Primary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CHSECONDARY Secondary Cardholder’s name in Alpha 26 NM CSR
LastName,FirstName MI format
CLIENTID PSCU assigned client identifier Numeric 6
DUETOEXPIRE The number of points that will Numeric 10 BO2
expire if not redeemed prior to the
expiration date, formatted to one
decimal place with the decimal
point displayed in the response
EXPIRATIONDATE The date in which the points due to Numeric 6 BO2
expire will expire, in CCYYMM
format (please note there is no day
– points typically expire on the last
day of the month)
Page 159
OdsPscu TAG NAME Description Type Length First
Data
Screen
decimal place with the decimal
point displayed in the response
PRIN Client-defined identifier of the level Numeric 4 BS6
within a System Bank Identifier that
is used
to group Agent Bank Identifiers
together for processing and
reporting
PROGRAMNAME Rewards program name when Alpha 8 B01
PROGRAM=Y parameter is included Numeric
in the request
REDEEMABLEPOINTS The number of rewards points that Numeric 10 BO1
are able to be redeemed in the
rewards program, formatted to one
decimal place with the decimal
point displayed in the response
SPAID PSCU Internal Designation for the Numeric 5
System, Prin and Agent values
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and
reporting
TERMDATE Temination date of the program Date 6 BO1
TOTALPOINTSREDEEMED The number of rewards points that Numeric 10 BO2
have been redeemed in the
rewards program, formatted to one
decimal place with the decimal
point displayed in the response
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
Page 160
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1407</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="BALANCE">999999999.99</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="EXPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="EXPAMT">999999999.99</odsPscuTAG>
- </COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="EXPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="EXPAMT">999999999.99</odsPscuTAG>
- </COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="EXPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="EXPAMT">999999999.99</odsPscuTAG>
- </COLLECTION>
<odsPscuTAG NAME="REWARDTYPE">CCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ADJDLY">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ADJCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ADJLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ADJMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ADJQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ADJYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ADJLTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDDLY">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EARNEDLTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDDLY">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPRDLTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="FFDDLY">999999999.99</odsPscuTAG>
Page 161
<odsPscuTAG NAME="FFDCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="FFDLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="FFDMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="FFDQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="FFDYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="FFDLTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMDLY">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RDMLTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINDLY">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TINLTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTDLY">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTCTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTLSTCYCL">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTMTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTQTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTYTD">999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TOUTLTD">999999999.99</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 162
OdsPscu TAG NAME Description Type Length
Page 163
OdsPscu TAG NAME Description Type Length
program
Page 164
OdsPscu TAG NAME Description Type Length
Page 165
OdsPscu TAG NAME Description Type Length
Page 166
OdsPscu TAG NAME Description Type Length
Page 167
OdsPscu TAG NAME Description Type Length
traded out cycle to date for
the program
Page 168
7.10 Special Consolidated Account Information
The Special Consolidated Account Information request returns Summary data, plus
Account Cross Reference 1, 2 & 3, Previous High Balance and Collector Code. This
information is similar to the information found on the BS and NM CL2 screens in the
First Data System.
Page 169
7.10.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=1
02&FUNCTIONID=1429&REQUESTID=102&CARDNUMBER=9999999999999999
&CLIENTID=9999&PIID=Y&ACCTTFER=Y&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>D5262B05-513B-769B-DFB7-EBDE8F183703</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1429</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG
NAME="LASTBALANCE">9999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="ACCTCROSSREF3">99999999999999</odsPscuTAG>
<odsPscuTAG NAME="MINPAYPCT">00.00000</odsPscuTAG>
<odsPscuTAG
NAME="ACCTCROSSREF2">99999999999999</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEOVRCD">0</odsPscuTAG>
<odsPscuTAG
NAME="ACCTCROSSREF1”>99999999999999</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELINQ">999</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
Page 170
<odsPscuTAG NAME="MINPAYDUESTART">999999</odsPscuTAG>
<odsPscuTAG NAME="EXTSTATUSCODE">X</odsPscuTAG >
<odsPscuTAG NAME="CREDITAVAIL">999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="HIGHBALANCE">999999999999999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">999999</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYFLAG">0</odsPscuTAG>
<odsPscuTAG
NAME="AMTPAST_DUE">999999999999999</odsPscuTAG>
<odsPscuTAG NAME="OPENDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">9999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="ALTFINKEY4">00000</odsPscuTAG>
<odsPscuTAG NAME="INTSTATUSCODE" />
<odsPscuTAG NAME="ALTFINKEY3">00000</odsPscuTAG>
<odsPscuTAG NAME="ALTFINKEY2">000</odsPscuTAG>
<odsPscuTAG NAME="CYCLE3">000</odsPscuTAG>
<odsPscuTAG
NAME="DATELASTPLASTICORDER">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CHSECONDARY">LASTNAME,FIRSTNAME</odsPscuTAG>
<odsPscuTAG NAME="ALTFINKEY1">000</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE2">000</odsPscuTAG>
<odsPscuTAG NAME="CYCLE1">000</odsPscuTAG>
<odsPscuTAG
NAME="DEMANDPAYAMT">9999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="EXPIREDATE">MMYY</odsPscuTAG>
<odsPscuTAG NAME="USERFLAGS1THRU4">X</odsPscuTAG>
<odsPscuTAG
NAME="ACCOUNTTRANSFERDATE">MMDDYYYY</odsPscuTAG>
<odsPscuTAG NAME="ACCOUNTTRANSFERCODE">9</odsPscuTAG>
<odsPscuTAG
NAME="CHNAME">LASTNAME,FIRSTNAME</odsPscuTAG>
<odsPscuTAG NAME="COLLECTORCODE">000</odsPscuTAG>
Page 171
<odsPscuTAG NAME="DEMANDPAYCD">1</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEEND">999999</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYDDA">1</odsPscuTAG>
<odsPscuTAG
NAME="FIXEDAUTOPAYAMT">9999999999999.99</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 172
OdsPscu TAG NAME Description Type Length First Data
Screen
("from" account)
2 - New transfer account
("to" account)
3 - Original account ("from"
combined account)
4 - New combined account
("to" combined account)
ACCOUNTTRANSFERDATE Date of the last account Numeric 5 NM CR
transfer. This field will be
included when the
ACCTTFER parameter is
included in the request.
Format: YYJJJ
The JJJ is the Julian day
number and will need to be
converted to MMDD
ALTFINKEY1 Alternate Financial Numeric 3 NM SA1
Reporting Key 1
ALTFINKEY2 Alternate Financial Numeric 3 NM SA1
Reporting Key 2
ALTFINKEY3 Alternate Financial Numeric 5 NM SA1
Reporting Key 3
ALTFINKEY4 Alternate Financial Numeric 5 NM SA1
Reporting Key 4
AMTPAST_DUE Amount past due, if any, in Numeric 16 BS
whole dollars
AUTOPAYDDA Number identifying the Numeric 17 NM AF
cardholder checking
account
AUTOPAYFLAG Code representing the Alpha 1 NM AF
member’s current AutoPay numeric
setting.
Page 173
OdsPscu TAG NAME Description Type Length First Data
Screen
Flags, their definition and
payment source.
CARDTYPE Description of the Card Alpha 25
program – Some valid
entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 174
OdsPscu TAG NAME Description Type Length First Data
Screen
without decimal places
CREDITLIMIT The maximum credit Numeric 16 BS
extended to the account
(this amount, less the
current balance and any
outstanding authorizations,
gives the available credit
on the account), shown as
a whole number without
decimal places
CURRENTBALANCE Current balance on Numeric 16 BS
account, shown as a signed
number with 2 decimal
places and the decimal
point in the response
CYCLE1 Count of times the account Numeric 3 BS
has been one-cycle
delinquent in the last two
years plus year to date.
Each time the account
becomes one-cycle
delinquent; the First Data
System adds one to this
field. If the cardholder
clears the delinquency
within this cycle, the
number in this field
remains. If the account
moves to the next higher
delinquency level, the FD
System subtracts one from
the counter in this field and
adds one to the counter at
the next higher
delinquency level.
CYCLE2 Count of times the account Numeric 3 BS
Page 175
OdsPscu TAG NAME Description Type Length First Data
Screen
has been two cycles
delinquent in the last two
years plus year to date.
Each time the account
becomes two cycles
delinquent, the First Data
System adds one to this
field. If the cardholder
clears the delinquency
within this cycle, the
number in this field
remains. If the account
moves to the next higher
delinquency level, the FD
System subtracts one from
the counter in this field and
adds one to the counter at
the next higher
delinquency level.
CYCLE3 Count of times the account Numeric 3 BS
has been three-or-more-
cycles delinquent in the last
two years plus year to date.
Each time the account
becomes three-or-more-
cycles delinquent, the FD
System adds one to this
field. If the cardholder
clears the delinquency
within this cycle, the
number in this field
remains. If the account
moves to the next higher
delinquency level, the FD
System adds one to this
field. For example, if the
Page 176
OdsPscu TAG NAME Description Type Length First Data
Screen
account moves from three-
cycles to four-cycles
delinquent, the FD System
adds one to this field.
DATELASTPINORDER Date of last PIN order Date 6
Provided if VERSION=2 YYMMDD
included in request
DATELASTPINSHIPPED Date of last PIN shipped. Date 6
Provided if VERSION=2 YYMMDD
included in request
DATELASTPLASTICORDER Date of the last order of Numeric 6 PIR
plastics on the account, in
YYMMDD format (Note:
Some situations may return
000000 as the value)
DATELASTPLASTICSHIPPED Date of last plastic shipped Date 6
Provided if VERSION=2 YYMMDD
included in request
DAYSDELINQ Number of Days the Numeric 3 BS
account is delinquent
DEMANDPAYAMT Amount a cardholder Numeric 19 NM AF
authorized as a payment to
send in through
the Automated
Clearinghouse (ACH) using
the demand payment
feature, in dollars and
cents with decimal point
shown in response
DEMANDPAYCD Code representing the type Numeric 1 NM AF
of account for the
withdrawal of a demand
Automated Clearinghouse
(ACH) payment, and to
indicate whether the
Page 177
OdsPscu TAG NAME Description Type Length First Data
Screen
cardholder initiated the
transaction via telephone
or via the Internet. Valid
codes include:
1 - Telephone-initiated
transaction to be drawn
from checking account
2 - Telephone-initiated
transaction to be drawn
from checking account
EXPIREDATE Date the credit account Numeric 4 BS
expires, in MMYY format
EXTSTATUSCODE External Status Code as Alpha 1 BS
found within the First Data
system, one character -
Issuer-assigned status code
determining specific
account processing
Valid codes:
Authorization prohibited
(A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited
(I)
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
FIXEDAUTOPAYAMT Fixed AutoPay payment Numeric 19 NM AF
amount currently in effect
on the account, in dollars
Page 178
OdsPscu TAG NAME Description Type Length First Data
Screen
and cents with decimal
point shown in response
FULLMINPAYDUE Full minimum payment Numeric 19 CSS
due as calculated at
statement cycle.
Format:
9999999999999999.99
HIGHBALANCE Highest dollar balance Numeric 16 BS
billed in the last two years
plus year to date
INTSTATUSCODE Internal Status Code as Alpha 1 BS
found within the First Data
system, one character -
System-assigned code
determining specific
account processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit
(X)
Normal ()
Overlimit (O)
LASTBALANCE Outstanding balance on the Numeric 19 BS
last statement, shown as a
signed number with 2
decimal places and decimal
point shown in response
LASTPAYAMT Amount of the last Numeric 19 BS7
payment, in dollars and
cents with decimal point
shown in response
LASTPAYDATE Date of the last payment, Numeric 6 BS7
in YYMMDD format (Note:
Page 179
OdsPscu TAG NAME Description Type Length First Data
Screen
Some situations may return
000000 as the value)
LASTPINADDRESS1 Address Line 1 of last PIN Alpha 52
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS2 Address Line 2 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS3 Address Line 3 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS4 Address Line 4 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS5 Address Line 5 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS6 Address Line 6 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS7 Address Line 7 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS8 Address Line 8 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS9 Address Line 9 of last PIN Alpha 40
Page 180
OdsPscu TAG NAME Description Type Length First Data
Screen
mailer
Provided if VERSION=2
included in request
LASTPINADDRESS10 Address Line 10 of last PIN Alpha 40
mailer
Provided if VERSION=2
included in request
LASTPINMAILER Date of last PIN mailer. Date 6
This is generally the same CCMMD
as DATELASTPINORDER but D
is coming from another
source at FDR and acts as a
fallback in case the mailer
view where we are drawing
the other dates from is not
populated. It is suggested
that the
DATELASTPINORDER be
used instead.
Provided if VERSION=2
included in request
LASTPINMAILERSTATUS Status of last PIN mailer Alpha 1
Provided if VERSION=2
included in request
LASTPLASTIC Date of last Plastic Date 6
Provided if VERSION=2 CCMMD
included in request D
LASTPLASTICADDRESS1 Address Line 1 of last Alpha 52
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS2 Address Line 2 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
Page 181
OdsPscu TAG NAME Description Type Length First Data
Screen
LASTPLASTICADDRESS3 Address Line 3 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS4 Address Line 4 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS5 Address Line 5 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS6 Address Line 6 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS7 Address Line 7 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS8 Address Line 8 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS9 Address Line 9 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICADDRESS10 Address Line 10 of last Alpha 40
Plastic mailer
Provided if VERSION=2
included in request
LASTPLASTICSTATUS Status of last plastic Alpha 1
shipped
Provided if VERSION=2
Page 182
OdsPscu TAG NAME Description Type Length First Data
Screen
included in request
The LASTPLASTICSTATUS
field is the Code
representing the Card
Issuance Unit (CIU)
processing status of the
plastics-related product
Valid codes:
C - Product cancelled when
in ordered status
D - CIU in production
process
E - Mailer production is
pending
The plastics associated with
the mailer have been
shipped, and the mailer will
be printed and mailed
based on the setting in the
Pin Mailer Hold Days
parameter in the Mailer
Management section (PP IP
MM) of the Product Control
File.
F - Item is being formatted
for production
G - Items have been purged
by the System, or as the
result of a purge request
I - Product is being inserted
You cannot update a CIU
request with this status.
J - Product request was
rejected by the System
L - Product request is on the
Page 183
OdsPscu TAG NAME Description Type Length First Data
Screen
last day in hold status
Requests on hold are listed
on the ED-706, Card
Issuance Hold Report for a
maximum of 14 days. If the
request is on hold beyond
14 days, it will be rejected,
aged off the ED-706 report,
and listed on the ED-705,
Card Issuance Decline
Report.
A CIU request in production
status that is placed on hold
by the production facility is
excluded from the 14-day
maximum.
N - Reserved for future use
O - Product has been
ordered
P - A purge request has
been generated and
confirmation of the purge is
pending
Q - Mailer was ordered for a
client that does not use the
PIN mailer hold
days option. If you use the
PIN mailer hold days option,
you can enter this status to
speed up the printing of a
PIN mailer. This action
includes the mailer record
in the next file sent to the
production facility. If you
enter this
code before 2:00P.M.
Page 184
OdsPscu TAG NAME Description Type Length First Data
Screen
central time, the mailer will
be printed that day.
You can only enter this code
if the status of the PIN
mailer is one of the
Following:
E
O
This status also indicates
that a mailer-only request
was made for one
of the following types of
mailers.
PIN
Post
Acknowledgement
S - Product has been
shipped
This is the final CIU status
for plastics for Fiserv
embossing clients. This
is the final CIU status for all
mailers and letters.
T - Product record sent for
processing
This is the final CIU status
for plastics for non-Fiserv
embossing clients.
W - An embossing rerun
was created to replace this
CIU that was produced
and shipped
X - An embossing rerun was
created to replace this CIU
that was produced,
Page 185
OdsPscu TAG NAME Description Type Length First Data
Screen
but not shipped
Valid codes:
1 - Use the largest of the
following three amounts for
the minimum payment.
The amount in the
Amount parameter
in the Minimum
Payment Due
section (CP PO MP)
of the Product
Page 186
OdsPscu TAG NAME Description Type Length First Data
Screen
Control File
The calculated
amount based on
either the amount in
the Percent
parameter in the
Minimum Payment
Due section (CP PO
MP) of the
Product Control File
or the cardholder
minimum payment
rate field on
the NM CL1 screen
multiplied by the
statement balance
The sum of the
account's cycle-to-
date billed interest
and fees
2 - Allow cardholder to set
the minimum payment.
The amount the cardholder
selects must be greater than
the amount in the Amount
parameter and the amount
in the Percent parameter
multiplied by the
cardholder's current
balance. The percent
selected must be greater
than the amount in the
Percent parameter.
MINPAYDUESTART Date the minimum Numeric 6 NM CL1
payment will start being
calculated by the method
Page 187
OdsPscu TAG NAME Description Type Length First Data
Screen
determined
MINPAYPCT Percent parameter used in Numeric 8 NM CL1
MINPAYOVERCD
PRIMARYPIID Plastic Identifier (card Numeric 16 PIR
number) for the primary
cardholder. This feature is
only valid for Separate
Entity clients when PIID=Y
is included in the request.
PRIMARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
OPENDATE Date the credit account Numeric 4 BS
was opened, in MMYY
format
SECONDARYPIID Plastic Identifier (card Numeric 16 PIR
number) for the secondary
cardholder
SECONDARYPIIDSTAT Status of the primary PIID Alpha 1 PID
Values:
Blank – Normal
A – Auth blocked
USERFLAGS1THRU4 Current activation status of Alpha 1 BS
the plastic, one character
code for the activation
status – please see
Appendix C of this
document for further
information
USF14 Four character userflags Alpha 4 BS
string
Page 188
7.11 Statement Balances and Summary Data
The Statement Balances and Summary Data request returns the Statement Balance data
from the last three cycles and summary account data. This information is similar to the
information found on several of the BS and CSS screens in the First Data System. If an
account did not generate a statement for one of the last three cycles, then the nodes
related to that specific statement cycle will not be returned in the XML response
document.
Page 189
7.11.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=1
02&FUNCTIONID=1433&REQUESTID=102&CARDNUMBER=9999999999999999
&CLIENTID=9999&ADDLDATA=Y&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>009DB131-E210-D12E-1B8B-7A3BB88E5A05</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1433</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">0000000000099999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST MI</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELINQ">999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">0000000000099999.99</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LAST,FIRST MI</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">0000000000099999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE3">999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE2">999</odsPscuTAG>
<odsPscuTAG NAME="INTSTATUSCODE" />
<odsPscuTAG NAME="CYCLE1">999</odsPscuTAG>
<odsPscuTAG NAME="EXTSTATUSCODE"/>
Page 190
<odsPscuTAG NAME="USERFLAGS1THRU4">X</odsPscuTAG>
<odsPscuTAG
NAME="DATELASTPLASTICORDER">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="CONTROL">9</odsPscuTAG>
<odsPscuTAG NAME="EXPIREDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">0000000099999.99</odsPscuTAG>
<odsPscuTAG NAME="PURCHASEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="CASHADVANCEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="HISTORY">XXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTPREVBAL">0000000000099999.99</ods
PscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTTOTCASHADV">0000000000099999.99
</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTTOTPURCH">0000000000099999.99</o
dsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTTOTCREDITS">0000000000099999.99</
odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTTOTPMTS">0000000000099999.99</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTTOTFCPUR">0000000000099999.99</o
dsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTTOTFCCASH">0000000000099999.99</
odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTBALANCE">0000000000099999.99</od
sPscuTAG>
Page 191
<odsPscuTAG
NAME="CURRENTSTATEMENTMINPAY">0000000000099999.99</ods
PscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTPMTDUEDT">MMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTPREVBAL">0000000000099999.99</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTTOTCASHADV">0000000000099999.99
</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTTOTPURCH">0000000000099999.99</
odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTTOTCREDITS">0000000000099999.99<
/odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTTOTPMTS">0000000000099999.99</o
dsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTTOTFCPUR">0000000000099999.99</o
dsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTTOTFCCASH">0000000000099999.99</
odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTBALANCE">0000000000099999.99</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTMINPAY">0000000000099999.99</ods
PscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTPMTDUEDT">MMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
Page 192
<odsPscuTAG
NAME="PASTSTATEMENTPREVBAL">0000000000099999.99</odsPscu
TAG>
<odsPscuTAG
NAME="PASTSTATEMENTTOTCASHADV">0000000000099999.99</od
sPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTTOTPURCH">0000000000099999.99</odsPs
cuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTTOTCREDITS">0000000000099999.99</odsP
scuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTTOTPMTS">0000000000099999.99</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTSTATEMENTTOTFCPUR">0000000000099999.99</odsPs
cuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTTOTFCCASH">0000000000099999.99</odsP
scuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTBALANCE">0000000000099999.99</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTSTATEMENTMINPAY">0000000000099999.99</odsPscu
TAG>
<odsPscuTAG
NAME="PASTSTATEMENTPMTDUEDT">MMDD</odsPscuTAG>
<odsPscuTAG NAME="YTDINTPAID">000000000999.99</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 193
</GETDATAXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 194
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
format
CONTROL Reissue control flag, this Alpha 1 BS
code controls reissue
processing - please see
Appendix B of this document
for further information. This
value is updated in real-time
when a card is activated.
CREDITAVAIL Dollar amount of the Numeric 16 BS
account's unused credit as
of the indicated date, shown
as a signed whole number
without decimal places
CREDITLIMIT The maximum credit Numeric 16 BS
extended to the account
(this amount, less the
current balance and any
outstanding authorizations,
gives the available credit on
the account), shown as a
whole number without
decimal places
CURRENTBALANCE Current balance on account, Numeric 16 BS
shown as a signed number
with 2 decimal places and
the decimal point in the
response
CURRENTSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement
date, shown as a signed
number with 2 decimal
places and decimal point
shown in response
CURRENTSTATEMENTDATE Date of the last statement, Numeric 8 CCD
Page 195
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
in CCYYMMDD format
CURRENTSTATEMENTMINPAY The minimum payment due Numeric 19 CSS
for the statement, shown as
a signed number with 2
decimal places and decimal
point shown in response
CURRENTSTATEMENTPMTDUEDT The date the minimum Numeric 4 CSS
payment is due for the
statement period, in MMDD
format
CURRENTSTATEMENTPREVBAL Previous balance shown on Numeric 19 CSS
the account as of the
statement date, shown as a
signed number with 2
decimal places and decimal
point shown in response
CURRENTSTATEMENTTOTCASHADV Total amount of the cash Numeric 19 CSS
advances that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
CURRENTSTATEMENTTOTCREDITS Total amount of the credits Numeric 19 CSS
that occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
CURRENTSTATEMENTTOTFCCASH Total amount of the finance Numeric 19 CSS
charges for cash advances
that occurred during the
statement cycle, shown as a
signed number with 2
Page 196
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
decimal places and decimal
point shown in response
CURRENTSTATEMENTTOTFCPUR Total amount of the finance Numeric 19 CSS
charges for purchases that
occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
CURRENTSTATEMENTTOTPMTS Total amount of the Numeric 19 CSS
payments that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
CURRENTSTATEMENTTOTPURCH Total amount of the Numeric 19 CSS
purchases that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
CYCLE1 Count of times the account Numeric 3 BS
has been one-cycle
delinquent in the last two
years plus year to date.
Each time the account
becomes one-cycle
delinquent; the First Data
System adds one to this
field. If the cardholder clears
the delinquency within this
cycle, the number in this
field remains. If the account
Page 197
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
moves to the next higher
delinquency level, the FD
System subtracts one from
the counter in this field and
adds one to the counter at
the next higher delinquency
level.
CYCLE2 Count of times the account Numeric 3 BS
has been two cycles
delinquent in the last two
years plus year to date.
Each time the account
becomes two cycles
delinquent, the First Data
System adds one to this
field. If the cardholder clears
the delinquency within this
cycle, the number in this
field remains. If the account
moves to the next higher
delinquency level, the FD
System subtracts one from
the counter in this field and
adds one to the counter at
the next higher delinquency
level.
CYCLE3 Count of times the account Numeric 3 BS
has been three-or-more-
cycles delinquent in the last
two years plus year to date.
Each time the account
becomes three-or-more-
cycles delinquent, the FD
System adds one to this
field. If the cardholder clears
Page 198
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
the delinquency within this
cycle, the number in this
field remains. If the account
moves to the next higher
delinquency level, the FD
System adds one to this
field. For example, if the
account moves from three-
cycles to four-cycles
delinquent, the FD System
adds one to this field.
DATELASTPLASTICORDER Date of the last order of Numeric 6 PIR
plastics on the account, in
YYMMDD format (Note:
Some situations may return
000000 as the value)
DAYSDELINQ Number of Days the account Numeric 3 BS
is delinquent
EXPIREDATE Date the plastic expires, in Numeric 4 BS
MMYY format
EXTSTATUSCODE External Status Code as Alpha 1 BS
found within the First Data
system, one character -
Issuer-assigned status code
determining specific account
processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited
(I)
Page 199
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
FULLMINPAYDUE Full minimum payment due Numeric 19 CSS
as calculated at statement
cycle.
Format:
9999999999999999.99
HISTORY Identifier of the 12-month Alpha 12 BS
account activity history. The
12 status flags rotate when
the account cycles so that
the leftmost flag indicates
the account’s status during
the last cycle and the
rightmost flag indicates the
account’s status during the
current cycle one year ago.
Page 200
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
first position. Each of the
other flags shift one position
to the right, with the
rightmost flag dropping out
of the activity history.
Page 201
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
PASTSTATEMENTDATE Date of the next previous Numeric 8 CSS
statement (3 statements
ago), in CCYYMMDD format
PASTSTATEMENTMINPAY The minimum payment due Numeric 19 CSS
for the statement, shown as
a signed number with 2
decimal places and decimal
point shown in response
PASTSTATEMENTPMTDUEDT The date the minimum Numeric 4 CSS
payment is due for the
statement period, in MMDD
format
PASTSTATEMENTPREVBAL Previous balance shown on Numeric 19 CSS
the account as of the
statement date, shown as a
signed number with 2
decimal places and decimal
point shown in response
PASTSTATEMENTTOTCASHADV Total amount of the cash Numeric 19 CSS
advances that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
PASTSTATEMENTTOTCREDITS Total amount of the credits Numeric 19 CSS
that occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
PASTSTATEMENTTOTFCCASH Total amount of the finance Numeric 19 CSS
charges for cash advances
that occurred during the
Page 202
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
PASTSTATEMENTTOTFCPUR Total amount of the finance Numeric 19 CSS
charges for purchases that
occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
PASTSTATEMENTTOTPURCH Total amount of the Numeric 19 CSS
purchases that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
PREVIOUSSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement
date, shown as a signed
number with 2 decimal
places and decimal point
shown in response
PREVIOUSSTATEMENTDATE Date of the previous Numeric 8 CSS
statement (2 statements
ago), in CCYYMMDD format
PREVIOUSSTATEMENTMINPAY The minimum payment due Numeric 19 CSS
for the statement, shown as
a signed number with 2
decimal places and decimal
point shown in response
PREVIOUSSTATEMENTPMTDUEDT The date the minimum Numeric 4 CSS
payment is due for the
Page 203
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
statement period, in MMDD
format
PREVIOUSSTATEMENTPREVBAL Previous balance shown on Numeric 19 CSS
the account as of the
statement date, shown as a
signed number with 2
decimal places and decimal
point shown in response
PREVIOUSSTATEMENTTOTCASHADV Total amount of the cash Numeric 19 CSS
advances that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
PREVIOUSSTATEMENTTOTCREDITS Total amount of the credits Numeric 19 CSS
that occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
PREVIOUSSTATEMENTTOTFCCASH Total amount of the finance Numeric 19 CSS
charges for cash advances
that occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
point shown in response
PREVIOUSSTATEMENTTOTFCPUR Total amount of the finance Numeric 19 CSS
charges for purchases that
occurred during the
statement cycle, shown as a
signed number with 2
decimal places and decimal
Page 204
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
point shown in response
PREVIOUSSTATEMENTTOTPMTS Total amount of the Numeric 19 CSS
payments that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
PREVIOUSSTATEMENTTOTPURCH Total amount of the Numeric 19 CSS
purchases that occurred
during the statement cycle,
shown as a signed number
with 2 decimal places and
decimal point shown in
response
PURCHASEAPR Annual Percentage Rate Numeric 6 NM SA1
applying to purchases and
merchandise, shown as a
percentage with 3 decimal
places
USERFLAGS1THRU4 Current activation status of Alpha 1 BS
the plastic using the First numeric
Data code – please see
Appendix C of this document
for further information
YTDINTPAID Year to Date Interest Paid Numeric 15 BS
Page 205
7.12 Statement Data, Last Cycle
The Statement Data, Last Cycle request returns the Statement data from the last cycle.
This information is similar to the information found on the CSS screens in the First Data
System. The XML nodes related to the internal status, statement balance and statement
date and the XML collections for the transaction detail will only be returned when data
is present for the statement cycle in the First Data System. If there is no data on file,
these nodes are not returned in the response document. If there was activity on the
account for the given statement cycle, each activity line item from the statement will be
returned in a separate collection.
Dynamic fee information will also be returned if the Credit Union participates in the First
Data program and the optional parameter is passed in the URL request. See Recent
Activity Information for additional information regarding Dynamic Fees. Contact your
PSCU Account Executive to for more information on Dynamic Fees and to enroll in the
Dynamic Fees solution.
Refer to Appendix J – Statement Data for detail information regarding the collections
returned by this request.
Note: Filtering is applied for special characters in the DTLDESC field. Please reference
the Tag and Property Reference Table for allowable special characters.
Page 206
7.12.1 Request Parameters
Page 207
Parameter Description Type Required Length
/
Optional
BSCR Y-Include Behavior Score in the Fixed Optional 1
response
CASHADV Y – Include cash advance Fixed Optional 1
information
COMPINFO Y – Company name and Fixed Optional 1
company account type
included in the response
DYNAMICFEES ON – Use to indicate Dynamic Fixed Optional 2
Fees are to be returned in the
transaction collection
EXTSTAT Y – include date and reason Fixed Optional 1
code for external status
OPA Y – include OPA in response Fixed Optional 1
PET Y-Include the Personal Emboss Fixed Optional 1
Text in the response
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) associated with
the transaction
PS Y – Include pricing strategy Fixed Optional 1
PYI Y-Include previos years interest Fixed Optional 1
billed and paid in the response
SHOWMERCHCODE ON – Use to indicate Merchant Fixed Optional 2
Code is to be returned in the
transaction collection
TRANACCT Y – Include PIID of the Fixed Optional 1
transaction when the control
account is the CARDNUMBER
TRANTYPE Y – Include transaction type Fixed Optional 1
code in transaction collection
XREF Y – Include cross reference Fixed Optional 1
numbers
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
Page 208
Parameter Description Type Required Length
/
Optional
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1411&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1411</ods:FUNCTIONID>
Page 209
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTBALANCE">9999999.99</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTDATE">CCYYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
Page 210
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">SECOND TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME=" EXPNRFRNNR"/>
<odsPscuTAG NAME="DTLAUTHNUM"/>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="EMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
Page 211
<odsPscuTAG NAME="DTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
Page 212
OdsPscu TAG NAME Description Type Length First
Data
Screen
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 213
OdsPscu TAG NAME Description Type Length First
Data
Screen
ADDLNONMON parameter is included
in the request
CREDITLINECD Code representing the type of the last Alpha- 1 TBD
credit line change. This value will be Numeric
returned when the ADDLNONMON
parameter is included in the request
Valid codes:
A - Automatic
C - Permanently deferred
D - Adaptive Control decrease
I - Adaptive Control increase
M - Manual
O - Never increased
R - Adaptive Control increase or
decrease using the LSX transaction
S - Automatic increase due to check
transaction maximum line without an
available credit buffer
T - Increase due to additional deposit
for secured account
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to check
transaction maximum line with an
available credit buffer
3 - Decrease due to mid-cycle credit
line processing via Adaptive Control
4 - Increase due to mid-cycle credit line
processing via Adaptive Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was established. Numeric 2 TBD
This value will be returned when the
ADDLNONMON parameter is included
in the request
Format: MMYY
DATELASTPLASTICORDER Date of the last order of plastics on Numeric 6 PIR
the account, in YYMMDD format
Page 214
OdsPscu TAG NAME Description Type Length First
Data
Screen
(Note: Some situations may return
000000 as the value)
Available when ACCTSUM=ON
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
Available when ACCTSUM=ON
DTLAUTHNUM Authorization number provided to Numeri 6 CDE
the merchant for the item, typically c
only available for retail / POS
purchases where an authorization
was obtained prior to the
transaction posting
DTLDESC Description of the item; allowable Alpha 40 CSS
characters are ! @ # $ & * ( ) _ . , ‘ *
- and white space
DTLEXPREF Expanded reference number Numeric 17 CDE
DTLMERCHCATCODE Merchant Code for the transaction; Numeric 5 CDE
included in response when
SHOWMERCHCODE=ON included in
the request
DTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
DTLMERCHSTATE Merchant State Alpha 2 CDE
DTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
DTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value)
DTLSEQNUM Sequence Number Numeric 5 CDE
DTLINDTRANID Transaction indicator Numeric 16 CDE
DTLTRANACCT PIID of the plastic used for the Numeric 16 CDE
transaction when the
CARDNUMBER in the request
EMAILADDR Email address Alpha Variabl NM EP
Numeric e
Page 215
OdsPscu TAG NAME Description Type Length First
Data
Screen
EMBEDDEDFEEAMT The Dynamic Fees value that will Numeric 15 CSS
display if the DYNAMICFEES=ON is
included in the URL request
ESTATEMENTENROLLMENTSTAT Only Valid for SCS eStatement Alpha 1 NM
US participating Credit Unions EBP
Valid Codes:
B – Cardholder receives both Paper
and Electronic Statements
D – Cardholder receives both Paper
and Electronic Statements and
currently is subject to delinquency
processing
E – Cardholder receives Electronic
Statements
L - The cardholder receives both
electronic and paper statements
and is billed additionally for paper
statements.
Blank – The cardholder is not
enrolled in eStatements
Available when ACCTSUM=ON
EXPIREDATE Date the credit account expires, in Numeric 4 BS
MMYY format
Available when ACCTSUM=ON
EXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item numeric
FRAUDSCORE Fraud Score Numeric 3 NM CR
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM CR
Format: YYMMDD
FRAUDSTRAT Current fraud strategy assigned to the Numeric 2 NM CR
account
FRAUDSTRATDT Date current fraud strategy assigned to Numeric 6 NM CR
Page 216
OdsPscu TAG NAME Description Type Length First
Data
Screen
the account
Format: YYMMDD
FRAUDSUSPENDSTARTDT Start date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may be
null.
Format:
YYMMDD
FRAUDSUSPENDSTRATEGY Strategy that will be enforced during Numeric 2 NM CR
time period defined by start and end
date
FRAUDSUSPENDENDDT End date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may be
null.
Format:
YYMMDD
INTCODE Internal Status Code for this Alpha 1 BS
statement period, one character -
System-assigned code determining
specific account processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTERNALSTATUS Internal Status Code for this Alpha 30
statement period, in Words (for
valid descriptions, see INTCODE)
LASTCREDITLINEDATE Date of the last credit limit Numeric 4 BS
adjustment, in MMYY format
Available when ACCTSUM=ON
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
MISC1 Miscellaneous field 1. This value will be AlphaNu 4 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC2 Miscellaneous field 2. This value will be AlphaNu 5 NM CS
Page 217
OdsPscu TAG NAME Description Type Length First
Data
Screen
returned when the ADDLNONMON meric
parameter is included in the request
MISC3 Miscellaneous field 3. This value will be AlphaNu 7 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC4 Miscellaneous field 4. This value will be AlphaNu 10 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC5 Miscellaneous field 5. This value will be AlphaNu 8 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC6 Miscellaneous field 6. This value will be AlphaNu 12 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC7 Miscellaneous field 7. This value will be AlphaNu 10 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC8 Miscellaneous field 8. This value will be AlphaNu 10 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC9 Miscellaneous field 9. This value will be AlphaNu 10 NM CS
returned when the ADDLNONMON meric
parameter is included in the request
MISC10 Miscellaneous field 10. This value will AlphaNu 10 NM CS
be returned when the ADDLNONMON meric
parameter is included in the request
MISC13 Miscellaneous field 13. This value will AlphaNu 50 NM CS
be returned when the ADDLNONMON meric
parameter is included in the request
MOBILEPHONE Mobile phone Numeric 10 NM EP
NUMPLASTICS Number of plastics that are issued Numeric 3 BS
on the account
Available when ACCTSUM=ON
OPA Account number, mostly relevant Numeric 16 BS
to separate entity
OPENDATE Date the credit account was Numeric 4 BS
opened, in MMYY format
Available when ACCTSUM=ON
OPENDATEDAY Day of the month the account was Numeric 2 BS9
opened
Page 218
OdsPscu TAG NAME Description Type Length First
Data
Screen
PERSONZN Personal Emboss Text Alpha Up to PID
Included when PET=Y is in the Numeri 26
request c
PIID Plastic Identifier (card number) Numeri 16 CDE
associated with the transaction c
PRICINGSTRATEGY Pricing strategy on the account Alpha 4 NM ST
Numeri
c
PRIN Client-defined identifier of the level Numeric 4 BS6
within a System Bank Identifier
that is used
to group Agent Bank Identifiers
together for processing and
reporting
PYIBLLDAMT Previous years interest billed Numeric 13 NM
Included when PYI=Y is in the PH
request
PYIPDAMT Previous years interest paid Numeric 13 NM
Included when PYI=Y is in the PH
request
PURCHASEAPR Annual Percentage Rate applying Numeric 6 NM
to purchases and merchandise, SA2
shown as a percentage with 3
decimal places.
Available when ACCTSUM=ON
SPCLFLAGS Special Flags 5 – 8. This value will be Alpha 4 BS
returned when the ADDLNONMON
parameter is included in the request
STATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement date,
shown as a signed number with 2
decimal places and decimal point
shown in response
STATEMENTDATE Date of the statement, in Numeric 8 CCD
CCYYMMDD format
Page 219
OdsPscu TAG NAME Description Type Length First
Data
Screen
STATUS External Status Code as found Alpha 1 BS
within the First Data system, one
character – see valid codes listed
above in EXTCODE node
Available when ACCTSUM=ON
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and
reporting
TRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point shown
in the response
TRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value)
TRANTYPE Transaction type code; refer to Numeric 3 CDE
Appendix N for transaction type
code definition
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of the Alpha 25 BS
plastic, described in words with
the First Data code for the
activation status following the
description in parenthesis – please
see Appendix C of this document
for further information.
Available when ACCTSUM=ON
USF14 Four character Userflags string Alpha 4 BS
Page 220
7.13 Statement Data, One (1) Prior Cycle
The Statement Data, One (1) Prior Cycle request returns the Statement data from the
prior cycle. This information is similar to the information found on the CSS screens in
the First Data System. The XML nodes related to the internal status, statement balance
and statement date and the XML collections for the transaction detail will only be
returned when data is present for the statement cycle in the First Data System. If there
is no data on file, these nodes are not returned in the response document.
If there was activity on the account for the given statement cycle, each activity line item
from the statement will be returned in a separate collection.
Dynamic fee information will also be returned if the Credit Union participates in the First
Data program and the optional parameter is passed in the URL request. See Recent
Activity Information for additional information regarding Dynamic Fees. Contact your
PSCU Account Executive to for more information on Dynamic Fees and to enroll in the
Dynamic Fees solution.
Refer to Appendix J – Statement Data for detail information regarding the collections
returned by this request.
Note: Filtering is applied for special characters in the DTLDESC field. Please reference
the Tag and Property Reference Table for allowable special characters.
Page 221
7.13.1 Request Parameters
Page 222
Parameter Description Type Required Length
/
Optional
BSCR Y-Include behavior score in the Fixed Optional 1
response
CASHADV Y – Include cash advance Fixed Optional 1
information
COMPINFO Y – Include company name and Fixed Optional 1
account type in response
DYNAMICFEES ON – Use to indicate Dynamic Fixed Optional 2
Fees are to be returned in the
transaction collection
EXTSTAT Y – Include date and reason Fixed Optional 1
code for external status
OPA Y – Include OPA in response Fixed Optional 1
PET Y-Include the Personal Emboss Fixed Optional 1
Text in the response
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) associated with
the transaction
PS Y – Include pricing strategy Fixed Optional 1
PYI Y-Include the previous years Fixed Optional 1
interest billed and paid in the
response
SHOWMERCHCODE ON – Use to indicate Merchant Fixed Optional 2
Code is to be returned in the
transaction collection
TRANACCT Y – Include PIID of the Fixed Optional 1
transaction when the control
account is the CARDNUMBER
TRANTYPE Y – Include transaction type Fixed Optional 1
code; refer to Appendix N for
list of transaction types
XREF Y – Include cross reference Fixed Optional 1
numbers
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Page 223
Parameter Description Type Required Length
/
Optional
Userflags value
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1412&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
Page 224
<ods:FUNCTIONID>1412</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTBALANCE">9999999.99</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTDATE">CCYYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
Page 225
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">SECOND TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME=" EXPNRFRNNR "/>
<odsPscuTAG NAME="DTLAUTHNUM"/>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
Page 226
<odsPscuTAG
NAME="EMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
Page 227
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 228
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
CR
CREDITLINEAM Amount of the previous credit line This Numeric 15 TBD
value will be returned when the
ADDLNONMON parameter is included
in the request
CREDITLINECD Code representing the type of the last Alpha- 1 TBD
credit line change. This value will be Numeric
returned when the ADDLNONMON
parameter is included in the request
Valid codes:
A - Automatic
C - Permanently deferred
D - Adaptive Control decrease
I - Adaptive Control increase
M - Manual
O - Never increased
R - Adaptive Control increase or
decrease using the LSX transaction
S - Automatic increase due to check
transaction maximum line without an
available credit buffer
T - Increase due to additional deposit
for secured account
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to check
transaction maximum line with an
available credit buffer
3 - Decrease due to mid-cycle credit
line processing via Adaptive Control
4 - Increase due to mid-cycle credit
line processing via Adaptive Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was Numeric 2 TBD
established. This value will be
returned when the ADDLNONMON
parameter is included in the request
Page 229
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
Format: MMYY
DATELASTPLASTICORDER Date of the last order of plastics on the Numeric 6 PIR
account, in YYMMDD format (Note:
Some situations may return 000000 as
the value)
Available when ACCTSUM=ON
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
Available when ACCTSUM=ON
DTLAUTHNUM Authorization number provided to Alpha 6 CDE
the merchant for the item,
typically only available for retail /
POS purchases where an
authorization was obtained prior
to the transaction posting
DTLDESC Description of the item; allowable Alpha 40 CSS
characters are ! @ # $ & * ( ) _ . , ‘
* - and white space
DTLEXPREF Expanded reference number Numeric 17 CDE
DTLINDTRANID Transaction indicator Numeric 16 CDE
DTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in response
when SHOWMERCHCODE=ON
included in the request
DTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
DTLMERCHSTATE Merchant State Alpha 2 CDE
DTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
DTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value)
DTLSEQNUM Sequence Number Numeric 5 CDA
CSS
DTLTRANACCT PIID of the plastic used for the Numeric 16 CDE
transaction when the
Page 230
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
CARDNUMBER in the request
EMBEDDEDFEEAMT The Dynamic Fees value that will Numeric 15 CSS
display if the DYNAMICFEES=ON is
included in the URL request
EMAILADDR Email address Alpha Variab NM
Numeric le EP
ESTATEMENTENROLLMENTSTATU Only Valid for SCS eStatement Alpha 1 NM
S participating Credit Unions EBP
Valid Codes:
B – Cardholder receives both Paper
and Electronic Statements
D – Cardholder receives both Paper
and Electronic Statements and
currently is subject to delinquency
processing
E – Cardholder receives Electronic
Statements
L - The cardholder receives both
electronic and paper statements and
is billed additionally for paper
statements.
Blank – The cardholder is not enrolled
in eStatements
Available when ACCTSUM=ON
EXPIREDATE Date the credit account expires, in Numeric 4 BS
MMYY format
Available when ACCTSUM=ON
EXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item numeric
EXTSTATDT Date the external status changed Numeric 6 NM
SA1
EXTSTATRESCD Reason for the external status Numeric 2 NM
change SA1
FRAUDSCORE Fraud Score Numeric 3 NM
CR
Page 231
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM
Format: YYMMDD CR
FRAUDSTRAT Current fraud strategy assigned to the Numeric 2 NM
account CR
FRAUDSTRATDT Date current fraud strategy assigned Numeric 6 NM
to the account CR
Format: YYMMDD
FRAUDSUSPENDSTARTDT Start date for the suspension of the Numeric 6 NM
fraud strategy. This parameter may be CR
null.
Format:
YYMMDD
FRAUDSUSPENDSTRATEGY Strategy that will be enforced during Numeric 2 NM
time period defined by start and end CR
date
FRAUDSUSPENDENDDT End date for the suspension of the Numeric 6 NM
fraud strategy. This parameter may be CR
null.
Format:
YYMMDD
INTCODE Internal Status Code for this Alpha 1 BS
statement period, one character -
System-assigned code
determining specific account
processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTERNALSTATUS Internal Status Code for this Alpha 30
statement period, in Words (for
valid descriptions, see INTCODE)
LASTCREDITLINEDATE Date of the last credit limit adjustment, Numeric 4 BS
in MMYY format
Available when ACCTSUM=ON
Page 232
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
MISC1 Miscellaneous field 1. This value will AlphaNum 4 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC2 Miscellaneous field 2. This value will AlphaNum 5 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC3 Miscellaneous field 3. This value will AlphaNum 7 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC4 Miscellaneous field 4. This value will AlphaNum 10 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC5 Miscellaneous field 5. This value will AlphaNum 8 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC6 Miscellaneous field 6. This value will AlphaNum 12 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC7 Miscellaneous field 7. This value will AlphaNum 10 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC8 Miscellaneous field 8. This value will AlphaNum 10 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC9 Miscellaneous field 9. This value will AlphaNum 10 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC10 Miscellaneous field 10. This value will AlphaNum 10 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MISC13 Miscellaneous field 13. This value will AlphaNum 50 NM CS
be returned when the ADDLNONMON eric
parameter is included in the request
MOBILEPHONE Mobile phone Numeric 10 NM
EP
NUMPLASTICS Number of plastics that are issued on Numeric 3 BS
the account
Available when ACCTSUM=ON
OPA Account number, mostly relevant Numeric 16 BS
Page 233
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
to separate entity
OPENDATE Date the credit account was opened, Numeric 4 BS
in MMYY format
Available when ACCTSUM=ON
OPENDATEDAY Day of the month the account Numeric 2 BS9
was opened
PERSONZN Personal Emboss Text Alpha Up to PID
Included when the PET=Y is Numeric 26
included in the request
PIID Plastic Identifier (card number) Numeric 16 CDE
associated with the transaction
PRICINGSTRATEGY Pricing strategy on the account Alpha 4 NM ST
Numeric
PRIN Client-defined identifier of the Numeric 4 BS6
level within a System Bank
Identifier that is used
to group Agent Bank Identifiers
together for processing and
reporting
PURCHASEAPR Annual Percentage Rate applying Numeric 6 NM
to purchases and merchandise, SA2
shown as a percentage with 3
decimal places.
Available when ACCTSUM=ON
PYIBLLDAMT Previous years interest billed Numeric 13 NM
Included when PYI=Y is in the PH
request
PYIPDAMT Previous years interest paid Numeric 13 NM
Included when PYI=Y is in the the PH
request
SPCLFLAGS Special Flags 5 – 8. This value will Alpha 4 BS
be returned when the
ADDLNONMON parameter is
included in the request
Page 234
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
STATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement date,
shown as a signed number with 2
decimal places and decimal point
shown in response
STATEMENTDATE Date of the statement, in Numeric 8 CCD
CCYYMMDD format
STATUS External Status Code as found within Alpha 1 BS
the First Data system, one character –
see valid codes listed above in
EXTCODE node
Available when ACCTSUM=ON
SYSTEM First Data-assigned identifier of Numeric 4 BS6
the level used to group Principal
Bank Identifiers
together for processing and
reporting
TRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value)
TRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point shown
in the response
TRANTYPE Transaction Type – Refer to Numeric 3 CDE
Appendix N for a list of
transaction types
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of the Alpha 25 BS
plastic, described in words with
the First Data code for the
activation status following the
Page 235
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
description in parenthesis –
please see Appendix C of this
document for further
information.
Available when ACCTSUM=ON
USF14 Four character Userflags string Alpha 4 BS
Page 236
7.14 Statement Data, Two (2) Prior Cycles
The Statement Data, Two(2) Prior Cycles request returns the Statement data from the
two prior cycles. This information is similar to the information found on the CSS screens
in the First Data System. The XML nodes related to the internal status, statement
balance and statement date and the XML collections for the transaction detail will only
be returned when data is present for the statement cycle in the First Data System. If
there is no data on file, these nodes are not returned in the response document.
If there was activity on the account for the given statement cycle, each activity line item
from the statement will be returned in a separate collection.
Dynamic fee information will also be returned if the Credit Union participates in the First
Data program and the optional parameter is passed in the URL request. See Recent
Activity Information for additional information regarding Dynamic Fees. Contact your
PSCU Account Executive to for more information on Dynamic Fees and to enroll in the
Dynamic Fees solution.
Refer to Appendix J – Statement Data for detail information regarding the collections
returned by this request.
Note: Filtering is applied for special characters in the DTLDESC field. Please reference
the Tag and Property Reference Table for allowable special characters.
Page 237
7.14.1 Request Parameters
Page 238
Parameter Description Type Required Length
/
Optional
BSCR Y-Include behavior score in Fixed Optional 1
response
CASHADV Y – Include cash advance Fixed Optional 1
information
DYNAMICFEES ON – Use to indicate Dynamic Fixed Optional 2
Fees are to be returned in the
transaction collections
EXTSTAT Y – include date and reason Fixed Optional 1
code foe external status
OPA Y – Include OPA in response Fixed Optional 1
PET Y-Include Personal Emboss Text Fixed Optional 1
in the response
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) associated with
the transaction
PS Y – Include Pricing Strategy Fixed Optional 1
PYI Y-Include previous years Fixed Optional 1
interest billed and paid in the
response
SHOWMERCHCODE ON – Use to indicate Merchant Fixed Optional 2
Code is to be returned in the
transaction collection
TRANACCT Y – Include PIID of the Fixed Optional 1
transaction when the control
account is the CARDNUMBER
TRANTYPE Y – Include transaction type in Fixed Optional 1
response
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
XREF Y – Include cross reference Fixed Optional 1
numbers
Page 239
7.14.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1413&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1413</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
Page 240
<odsPscuTAG
NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTBALANCE">9999999.99</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTDATE">CCYYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">SECOND TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
Page 241
<odsPscuTAG NAME=" EXPNRFRNNR "/>
<odsPscuTAG NAME="DTLAUTHNUM"/>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="EMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
Page 242
7.14.3 Tag and Property Reference
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 243
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Page 244
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to check
transaction maximum line with an
available credit buffer
3 - Decrease due to mid-cycle credit
line processing via Adaptive Control
4 - Increase due to mid-cycle credit
line processing via Adaptive Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was Numeric 2 TBD
established. This value will be
returned when the ADDLNONMON
parameter is included in the request
Format: MMYY
DATELASTPLASTICORDER Date of the last order of plastics Numeric 6 PIR
on the account, in YYMMDD
format (Note: Some situations
may return 000000 as the value)
Available when ACCTSUM=ON
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
Available when ACCTSUM=ON
DTLAUTHNUM Authorization number provided Numeric 6 CDE
to the merchant for the item,
typically only available for retail /
POS purchases where an
authorization was obtained prior
to the transaction posting
DTLDESC Description of the item; allowable Alpha 40 CSS
characters are ! @ # $ & * ( ) _ . , ‘
* - and white space
DTLINDTRANID Transaction indicator Numeric 16 CDE
Page 245
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
DTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in response
when SHOWMERCHCODE=ON
included in the request
DTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
DTLMERCHSTATE Merchant State Alpha 2 CDE
DTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
DTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value)
DTLTRANACCT PIID of the plastic used for the Numeric 16 CDE
transaction when the
CARDNUMBER in the request
EMAILADDR Email address Alpha Varia NM EP
Numeric ble
EMBEDDEDFEEAMT The Dynamic Fees value that will Numeric 15 CSS
display if the DYNAMICFEES=ON
is included in the URL request.
ESTATEMENTENROLLMENTSTAT Only Valid for SCS eStatement Alpha 1 NM EBP
US participating Credit Unions
Valid Codes:
B – Cardholder receives both
Paper and Electronic Statements
D – Cardholder receives both
Paper and Electronic Statements
and currently is subject to
delinquency processing
E – Cardholder receives Electronic
Page 246
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Statements
L - The cardholder receives both
electronic and paper statements
and is billed additionally for
paper statements.
Blank – The cardholder is not
enrolled in eStatements
Available when ACCTSUM=ON
EXTSTATDT Date the external status changed Numeric 6 NM SA1
EXTSTATRESCD Reason for the external status Numeric 2 NM SA1
change
EXPIREDATE Date the credit account expires, Numeric 4 BS
in MMYY format
Available when ACCTSUM=ON
EXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item numeric
FRAUDSCORE Fraud Score Numeric 3 NM CR
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM CR
Format: YYMMDD
FRAUDSTRAT Current fraud strategy assigned to the Numeric 2 NM CR
account
FRAUDSTRATDT Date current fraud strategy assigned Numeric 6 NM CR
to the account
Format: YYMMDD
FRAUDSUSPENDSTARTDT Start date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may
be null.
Format:
YYMMDD
FRAUDSUSPENDSTRATEGY Strategy that will be enforced during Numeric 2 NM CR
time period defined by start and end
date
FRAUDSUSPENDENDDT End date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may
be null.
Format:
YYMMDD
INTCODE Internal Status Code for this Alpha 1 BS
Page 247
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
statement period, one character -
System-assigned code
determining specific account
processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTERNALSTATUS Internal Status Code for this Alpha 30
statement period, in Words (for
valid descriptions, see INTCODE)
LASTCREDITLINEDATE Date of the last credit limit Numeric 4 BS
adjustment, in MMYY format
Available when ACCTSUM=ON
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
AFFINITYNUMBER Affinity number on the account. This Numeric 16 NM CS
value will be returned when the
ADDLNONMON parameter is
included in the request.
MISC1 Miscellaneous field 1. This value will AlphaNum 4 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC2 Miscellaneous field 2. This value will AlphaNum 5 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC3 Miscellaneous field 3. This value will AlphaNum 7 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC4 Miscellaneous field 4. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
Page 248
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
MISC5 Miscellaneous field 5. This value will AlphaNum 8 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC6 Miscellaneous field 6. This value will AlphaNum 12 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC7 Miscellaneous field 7. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC8 Miscellaneous field 8. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC9 Miscellaneous field 9. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC10 Miscellaneous field 10. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC13 Miscellaneous field 13. This value will AlphaNum 50 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MOBILEPHONE Mobile phone Numeric 10 NM EP
NUMPLASTICS Number of plastics that are Numeric 3 BS
issued on the account
Available when ACCTSUM=ON
OPA Account number, mostly relevant Numeric 16 BS
to separate entity
OPENDATE Date the credit account was Numeric 4 BS
opened, in MMYY format
Available when ACCTSUM=ON
OPENDATEDAY Day of the month the account Numeric 2 BS9
was opened
PERSONZN Personal Emboss Text Alpha Up to PID
Page 249
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Included when PET=Y is in the Numeric 26
request
PIID Plastic Identifier (card number) Numeric 16 CDE
associated with the transaction
PRICINGSTRATEGY Pricing strategy on the account Alpha 4 NM ST
Numeric
PRIN Client-defined identifier of the Numeric 4 BS6
level within a System Bank
Identifier that is used
to group Agent Bank Identifiers
together for processing and
reporting
PURCHASEAPR Annual Percentage Rate applying Numeric 6 NM SA2
to purchases and merchandise,
shown as a percentage with 3
decimal places.
Available when ACCTSUM=ON
PYIBLLDAMT Previous years interest billed Numeric 13 NM PH
Included when PYI=Y is in the
request
PYIPDAMT Previous years interest paid Numeric 13 NM PH
Included when PYI=Y is in the
request
SPCLFLAGS Special Flags 5 – 8. This value will be Alpha 4 BS
returned when the ADDLNONMON
parameter is included in the request
STATEMENTDATE Date of the statement, in Numeric 8 CCD
CCYYMMDD format
STATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement date,
shown as a signed number with 2
decimal places and decimal point
shown in response
STATUS External Status Code as found Alpha 1 BS
within the First Data system, one
Page 250
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
character – see valid codes listed
above in EXTCODE node
Available when ACCTSUM=ON
SYSTEM First Data-assigned identifier of Numeric 4 BS6
the level used to group Principal
Bank Identifiers
together for processing and
reporting
TRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value)
TRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point shown
in the response.
TRANTYPE Transacation Type code – Refer Numeric 3 CDE
to Appendix N for list of
transaction type codes
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of the Alpha 25 BS
plastic, described in words with
the First Data code for the
activation status following the
description in parenthesis –
please see Appendix C of this
document for further
information.
Available when ACCTSUM=ON
USF14 Four character Userflags string Alpha 4 BS
Page 251
7.15 Statement Data, Single Specified Cycle
The Statement Data, Single Specified Cycle request returns Statement data for a single
cycle, based on the date specified in the request. This information is similar to the
information found on the CSS screens in the First Data System. This function is required
to obtain CSS information greater than three cycles past.
If there was activity on the account for the given statement cycle, each activity line item
from the statement will be returned in a separate collection.
Dynamic fee information will also be returned if the Credit Union participates in the First
Data program and the optional parameter is passed in the URL request. See Recent
Activity Information for additional information regarding Dynamic Fees. Contact your
PSCU Account Executive to for more information on Dynamic Fees and to enroll in the
Dynamic Fees solution.
Refer to Appendix J – Statement Data for detail information regarding the collections
returned by this request.
IMPORTANT NOTE: This request requires that a statement date be provided in the URL.
If the statement date provided is not correct for the cardholder or if the statement is no
longer available through the CSS region at First Data, the response XML will be
“java.lang.Exception: Problem getting statements with specified statement date.”.
First Data allows between 3 and 12 months of cardholder statement transaction history
to be stored on CSS. Most financial institutions only store 3 months. However, if your
Page 252
institution has selected to store more than 3 months, statement detail can be retrieved
for the additional statements housed in CSS. If the exact statement date is not known, a
list of the last 12 statement dates can be obtained by accessing Function 1436 prior to
issuing Function 1437. However, if the exact statement date is known, it is not
necessary to issue a Function 1436 request.
Note: Filtering is applied for special characters in all *DESC fields. Please reference the
Tag and Property Reference Table for allowable special characters.
Page 253
Parameter Description Type Required Length
/
Optional
(card number) associated with
the transaction
PS Y – Include Pricing Strategy Fixed Optional 1
STATEMENTDATE Statement Date Required 8
Format: CCYYMMDD
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1437&REQUESTID=102&CARDNUMBER=9999999999999999&STATE
MENTDATE=CCYYMMDD&CLIENTID=9999&PIID=Y&
Page 254
1437&REQUESTID=102&CARDNUMBER=9999999999999999&STATEMENTDATE=CCYYM
MDD&CLIENTID=9999&DYNAMICFEES=ON
The following is an example of the XML data provided from the URL above when
the statement detail was found:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1437</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
Page 255
<odsPscuTAG
NAME="STATEMENTBALANCE">9999999.99</odsPscuTAG>
<odsPscuTAG
NAME="STATEMENTDATE">CCYYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">SECOND TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME=" EXPNRFRNNR "/>
<odsPscuTAG NAME="DTLAUTHNUM"/>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
Page 256
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="EMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
The following is an example of the XML data provided from the URL above when the
statement detail was not found:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
Page 257
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1437</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">XXXX</odsPscuTAG>
<odsPscuTAG NAME="PRIN">XXXX</odsPscuTAG>
<odsPscuTAG NAME="AGENT">XXXX</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 258
OdsPscu TAG NAME Description Type Length First
Data
Screen
to group accounts together for
processing and reporting
CARDTYPE Description of the Card program – Alpha 25
Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 259
OdsPscu TAG NAME Description Type Length First
Data
Screen
prior to the transaction posting
DTLDESC Description of the item; allowable Alpha 40 CSS
characters are ! @ # $ & * ( ) _ . , ‘ * -
and white space
DTLINDTRANID Transaction indicator Numeric 16 CDE
DTLMERCHCATCODE Merchant Code for the transaction; Numeric 5 CDE
included in response when
SHOWMERCHCODE=ON included in
the request
DTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
DTLMERCHSTATE Merchant State Alpha 2 CDE
DTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
DTLPOSTDATE Posting Date of the item, in YYMMDD Numeric 6 CSS
format (Note: Some situations may
return 000000 as the value)
DTLTRANACCT PIID of the plastic used for the Numeric 16 CDE
transaction when the CARDNUMBER in
the request
EMAILADDR Email address Alpha Variable NM EP
Numeric
EMBEDDEDFEEAMT The Dynamic Fees value will display if Numeric 15 CSS
the DYNAMICFEES=ON is included in
the URL request
EXPNRFRNNR Reference number for the transaction Alpha 17 CSS
item numeric
EXTSTATDT Date the external status changed Numeric 6 NM SA1
EXTSTATRESCD Reason for the external status change Numeric 2 NM SA1
INTCODE Internal Status Code for this statement Alpha 1 BS
period, one character - System-
assigned code determining specific
account processing
Valid codes:
Page 260
OdsPscu TAG NAME Description Type Length First
Data
Screen
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTERNALSTATUS Internal Status Code for this statement Alpha 30
period, in Words (for valid
descriptions, see INTCODE)
MOBILEPHONE Mobile phone Numeric 10 NM EP
OPA Account number, mostly relevant to Numeric 16 BS
separate entity
OPENDATEDAY Day of the month the account was Numeric 2 BS9
opened
PIID Plastic Identifier (card number) Numeric 16 CDE
associated with the transaction
PRICINGSTRATEGY Pricing strategy on the account Alpha 4 NM ST
Numeric
PRIN Client-defined identifier of the level Numeric 4 BS6
within a System Bank Identifier that is
used
to group Agent Bank Identifiers
together for processing and reporting
STATEMENTDATE Date of the statement, in CCYYMMDD Numeric 8 CCD
format
STATEMENTBALANCE Outstanding balance on the account as Numeric 19 CSS
of the statement date, shown as a
signed number with 2 decimal places
and decimal point shown in response
SYSTEM First Data-assigned identifier of the Numeric 4 BS6
level used to group Principal Bank
Identifiers
together for processing and reporting
TRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
Page 261
OdsPscu TAG NAME Description Type Length First
Data
Screen
situations may return 000000 as the
value)
TRANAMT Amount of the item, shown as a signed Numeric 15 CSS
number with 2 decimal places and a
decimal point shown in the response
TRANTYPE Transaction Type Code – refer to Numeric 3 CDE
Appendix N for list of transaction type
codes
Page 262
7.16 Statement Data, Last Three (3) Cycles
The Statement Data, Last Three (3) Cycles request returns Statement data from the last
three cycles. This single request returns the aggregated data from functions 1411, 1412
and 1413. This information is similar to the information found on the CSS screens in the
First Data System. The XML nodes for statement balances and statement dates and the
XML collections for the transaction detail will only be returned when data is present in
the First Data System. If there is no data on file, these nodes are not returned in the
response document.
If there was activity on the account for the given statement cycle, each activity line item
from the statement will be returned in a separate collection.
Dynamic fee information will also be returned if the Credit Union participates in the First
Data program and the optional parameter is passed in the URL request. See Recent
Activity Information for additional information regarding Dynamic Fees. Contact your
PSCU Account Executive to for more information on Dynamic Fees and to enroll in the
Dynamic Fees solution.
Refer to Appendix J – Statement Data for detail information regarding the collections
returned by this request.
Note: Filtering is applied for special characters in all *DESC fields. Please reference the
Tag and Property Reference Table for allowable special characters.
Page 263
7.16.1 Request Parameters
Page 264
Parameter Description Type Required Length
/
Optional
information
COMPINFO Y – Include the company name Fixed Optional 1
and company account type
DYNAMICFEES ON – Use to indicate Dynamic Fixed Optional 2
Fees are to be returned in the
transaction collection
EXTSTAT Y – Include date and reason Fixed Optional 1
code for external status
OPA Y – Include OPA in response Fixed Optional 1
PET Y-Include the Personal Emboss Fixed Optional 1
Text in the response
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) associated with
the transaction
PS Y – Include pricing strategy Fixed Optional 1
PYI Y-Include the previous years Fixed Optional 1
interest billed and paid in the
response
SHOWMERCHCODE ON – Use to indicate Merchant Fixed Optional 2
Code is to be returned in the
transaction collection
TRANTYPE Y – Include transaction type Fixed Optional 1
code in response
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
XREF Y – Include cross reference Fixed Optional 1
numbers
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
Page 265
UNCTIONID=1431&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1431</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="INTERNALSTATUS">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
Page 266
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTBALANCE">9999999.99</odsPscu
TAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTDATE">CCYYMMDD</odsPscuTAG
>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTBALANCE">9999999.99</odsPscu
TAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTDATE">CCYYMMDD</odsPscuTA
G>
<odsPscuTAG
NAME="PASTSTATEMENTBALANCE">9999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
Page 267
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME=" CURRENTEXPNRFRNNR "/>
<odsPscuTAG NAME="CURRENTDTLAUTHNUM"/>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">000000000000.00</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
Page 268
<odsPscuTAG NAME="PREVIOUSDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME=" PREVIOUSEXPNRFRNNR "/>
<odsPscuTAG NAME="PREVIOUSDTLAUTHNUM"/>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">000000000000.00</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
Page 269
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME=" PASTEXPNRFRNNR "/>
<odsPscuTAG NAME="PASTDTLAUTHNUM"/>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">MESSAGE LINE
INFORMATION</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
Page 270
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
Page 271
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PASTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
Page 272
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
AFR
AFFINITYNUMBER Affinity number on the account. Numeric 16 NM CS
This value will be returned
when the ADDLNONMON
parameter is included in the
request.
AGENT Client-defined identifier of Numeric 4 BS6
the level within a Principal
Bank Identifier that is used
to group accounts together
for processing and
reporting
ALTSTMT Alternate Statement Code Numeric 1 NM
CS
ANNUALACT Annual Activity CD Numeric 1 NM
AF
BILLINGCYCLE Billing Cycle code. This value Numeric 2 NM CS
will be returned when the
ADDLNONMON parameter is
included in the request
BSCR Behavior Score Numeric 3 BS
Included when PET=Y is in
the request
CASHADVOUTBAL Cash advance outstanding Numeric BS5
balance
CASHADVLIMIT Cash advance open to buy Numeric BS5
CARDTYPE Description of the Card Alpha 25
program – Some valid
entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
Page 273
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 274
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
A - Automatic
C - Permanently deferred
D - Adaptive Control decrease
I - Adaptive Control increase
M - Manual
O - Never increased
R - Adaptive Control increase
or decrease using the LSX
transaction
S - Automatic increase due to
check transaction maximum
line without an
available credit buffer
T - Increase due to additional
deposit for secured account
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to
check transaction maximum
line with an
available credit buffer
3 - Decrease due to mid-cycle
credit line processing via
Adaptive Control
4 - Increase due to mid-cycle
credit line processing via
Adaptive Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was Numeric 2 TBD
established. This value will be
returned when the
ADDLNONMON parameter is
included in the request
Format: MMYY
CURRENTDTLAUTHNUM Authorization number Alpha 6 CDE
provided to the merchant
Page 275
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
for the item, typically only
available for retail / POS
purchases where an
authorization was
obtained prior to the
transaction posting -
transaction on last
statement
CURRENTDTLDESC Description of the item; Alpha 40 CSS
allowable characters are !
@ # $ & * ( ) _ . , ‘ * - and
white space
CURRENTDTLEXPREF Expanded reference Alpha 21 CDE
number Numeric
CURRENTDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
CURRENTDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
CURRENTDTLMERCHSTATE Merchant State Alpha 2 CDE
CURRENTDTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
CURRENTDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note:
Some situations may
return 000000 as the
value) - transaction on last
statement
CURRENTDTLSEQNUM Transaction Sequence Numeric 8 CSS
Number
CURRENTEMBEDDEDFEEAMT The Dynamic Fees value Numeric 15 CSS
that will display if the
Page 276
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
DYNAMICFEES=ON is
included in the URL
request - transaction on
last statement
CURRENTEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item – numeric
transaction on last
statement
CURRENTINDTRANID Transaction indicator Alpha 17 CDE
numeric
CURRENTPIID PIID associated with the Numeric 16 CDE
transaction
CURRENTSTATEMENTBALANCE Outstanding balance on Numeric 19 CSS
the account as of the
statement date, shown as
a signed number with 2
decimal places and decimal
point shown in response
CURRENTSTATEMENTDATE Date of the last statement, Numeric 8 CCD
in CCYYMMDD format
CURRENTTRANAMT Amount of the item, Numeric 15 CSS
shown as a signed number
with 2 decimal places and
a decimal point shown in
the response - transaction
on last statement
CURRENTTRANDATE Transaction date for the Numeric 6 CSS
item, in YYMMDD format
(Note: Some situations
may return 000000 as the
value) - transaction on
last statement
CURRENTTRANTYPE Transaction Type Code – Numeric 3 CDE
Page 277
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
refer to Appendix N for list
of transaction type codes
EMAILADDR Email address Alpha Variabl NM EP
Numeric e
EXTSTATDT Date the external status Numeric 6 NM
changed SA1
EXTSTATRESCD Reason for the external Numeric 2 NM
status change SA1
FRAUDSCORE Fraud Score Numeric 3 NM CR
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM CR
Format: YYMMDD
FRAUDSTRAT Current fraud strategy Numeric 2 NM CR
assigned to the account
FRAUDSTRATDT Date current fraud strategy Numeric 6 NM CR
assigned to the account
Format: YYMMDD
FRAUDSUSPENDSTARTDT Start date for the suspension Numeric 6 NM CR
of the fraud strategy. This
parameter may be null.
Format:
YYMMDD
FRAUDSUSPENDSTRATEGY Strategy that will be enforced Numeric 2 NM CR
during time period defined by
start and end date
FRAUDSUSPENDENDDT End date for the suspension of Numeric 6 NM CR
the fraud strategy. This
parameter may be null.
Format:
YYMMDD
FULLMINPAYDUE Full Min Pay Due in dollars Numeric Up to
and cents 19
INTCODE Internal Status Code for Alpha 1 BS
this statement period, one
character - System-
assigned code determining
specific account processing
Page 278
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit
(X)
Normal ()
Overlimit (O)
INTERNALSTATUS Internal Status Code for Alpha 30
this statement period, in
Words (for valid
descriptions, see INTCODE)
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
MISC1 Miscellaneous field 1. This AlphaNume 4 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC2 Miscellaneous field 2. This AlphaNume 5 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC3 Miscellaneous field 3. This AlphaNume 7 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC4 Miscellaneous field 4. This AlphaNume 10 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC5 Miscellaneous field 5. This AlphaNume 8 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC6 Miscellaneous field 6. This AlphaNume 12 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC7 Miscellaneous field 7. This AlphaNume 10 NM CS
value will be returned when the ric
Page 279
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
ADDLNONMON parameter is
included in the request
MISC8 Miscellaneous field 8. This AlphaNume 10 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC9 Miscellaneous field 9. This AlphaNume 10 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC10 Miscellaneous field 10. This AlphaNume 10 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MISC13 Miscellaneous field 13. This AlphaNume 50 NM CS
value will be returned when the ric
ADDLNONMON parameter is
included in the request
MOBILEPHONE Mobile phone Numeric 10 NM EP
OPA Account number, mostly Numeric 16 BS
relevant to separate entity
OPENDATEDAY Day of the month the Numeric 2 BS9
account was opened
PASTDTLAUTHNUM Authorization number Alpha 6 CDE
provided to the merchant
for the item, typically only
available for retail / POS
purchases where an
authorization was
obtained prior to the
transaction posting -
transaction on next
previous statement
PASTDTLDESC Description of the item; Alpha 40 CSS
allowable characters are !
@ # $ & * ( ) _ . , ‘ * - and
white space
Page 280
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
PASTDTLEXPREF Expanded Reference Alpha 21 CDE
Number Numeric
PASTDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
PASTDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
PASTDTLMERCHSTATE Merchant State Alpha 2 CDE
PASTDTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
PASTDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note:
Some situations may
return 000000 as the
value) - transaction on
next previous statement
PASTDTLSEQNUM Transaction Sequence Numeric 8 CSS
Number
PASTEMBEDDEDFEEAMT The Dynamic Fees value Numeric 15 CSS
that will display if the
DYNAMICFEES=ON is
included in the URL
request.
PASTEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item - numeric
transaction on next
previous statement
PASTINDTRANID Transaction indicator Alpha 17 CDE
numeric
PASTPIID Presentation Id associated Numeric 16 CDE
with the transaction
PASTSTATEMENTBALANCE Outstanding balance on Numeric 19 CSS
Page 281
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
the account as of the
statement date, shown as
a signed number with 2
decimal places and decimal
point shown in response
PASTSTATEMENTDATE Date of the next previous Numeric 8 CCD
statement (3 statements
ago), in CCYYMMDD
format
PASTTRANAMT Amount of the item, Numeric 15 CSS
shown as a signed number
with 2 decimal places and
a decimal point shown in
the response - transaction
on next previous
statement
PASTTRANDATE Transaction date for the Numeric 6 CSS
item, in YYMMDD format
(Note: Some situations
may return 000000 as the
value) - transaction on
next previous statement
PASTTRANTYPE Transaction Type Code – Numeric 3 CDE
refer to Appendix N for list
of transaction type codes
PERSONZN Personal Emboss Text Alpha Up to PID
Included when PET=Y is in Numeric 26
the request
PREVIOUSDTLAUTHNUM Authorization number Alpha 6 CDE
provided to the merchant
for the item, typically only
available for retail / POS
purchases where an
Page 282
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
authorization was
obtained prior to the
transaction posting -
transaction on previous
statement
PREVIOUSDTLDESC Description of the item; Alpha 40 CSS
allowable characters are !
@ # $ & * ( ) _ . , ‘ * - and
white space
PREVIOUSDTLEXPREF Expanded Reference Alpha 21 CDE
Number Numeric
PREVIOUSDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
PREVIOUSDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
PREVIOUSDTLMERCHSTATE Merchant State Alpha 2 CDE
PREVIOUSDTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
PREVIOUSDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note:
Some situations may
return 000000 as the
value) - transaction on
previous statement
PREVIOUSDTLSEQNUM Sequence Number Numeric 8 CSS
PREVIOUSEMBEDDEDFEEAMT The Dynamic Fees value Numeric 15 CSS
that will display if the
DYNAMICFEES=ON is
included in the URL
request transaction on
previous statement
Page 283
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
PREVIOUSEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item - numeric
transaction on previous
statement
PREVIOUSINDTRANID Transaction indicator Alpha 17 CDE
numeric
PREVIOUSPIID Presentation Identifier Numeric 16 CDE
PREVIOUSSTATEMENTBALANCE Outstanding balance on Numeric 19 CSS
the account as of the
statement date, shown as
a signed number with 2
decimal places and decimal
point shown in response
PREVIOUSSTATEMENTDATE Date of the previous Numeric 8 CCD
statement (2 statements
ago), in CCYYMMDD
format
PREVOUSTRANAMT Amount of the item, Numeric 15 CSS
shown as a signed number
with 2 decimal places and
a decimal point shown in
the response - transaction
on previous statement
PREVIOUSTRANDATE Transaction date for the Numeric 6 CSS
item, in YYMMDD format
(Note: Some situations
may return 000000 as the
value) - transaction on
previous statement
PREVIOUSTRANTYPE Transaction Type Code – Numeric 3 CDE
refer to Appendix N for list
of transaction type codes
PRICINGSTRATEGY Pricing strategy on the Alpha 4 NM
Page 284
OdsPscu TAG NAME Description Type Length First
Data
Scree
n
account Numeric ST
PRIN Client-defined identifier of Numeric 4 BS6
the level within a System
Bank Identifier that is used
to group Agent Bank
Identifiers together for
processing and reporting
PYIBLLDAMT Previous years interest Numeric 13 NM
billed PH
Included when PYI=Y is in
the request
PYIPDAMT Previous years interest Numeric 13 NM
paid PH
Included when PYI=Y is in
the request
SPCLFLAGS Special Flags 5 – 8. This Alpha 4 BS
value will be returned
when the ADDLNONMON
parameter is included in
the request
SYSTEM First Data-assigned Numeric 4 BS6
identifier of the level used
to group Principal Bank
Identifiers
together for processing
and reporting
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USF14 Four character Userflags Alpha 4 BS
string
Page 285
7.17 Statement Data, Last Three (3) Cycles and Recent Activity
The Statement Data, Last Three (3) Cycles and Recent Activity request returns
Statement data from the last three cycles and the transactions and authorizations
posted to the account since the last statement cycle. This single request returns the
aggregated data from functions 1411, 1412, 1413 and 1415. This information is similar
to the information found on the CSS and CDA screens in the First Data System. The
collections containing information regarding an authorization will contain 13 separate
nodes for each authorization item. Authorizations for posted transactions are cleaned
up on the First Data system once a week. Throughout the week the Recent Activity
Information may contain authorizations and their corresponding transactions.
For recent activity transactions:
Transactions can be identified by existence of a value in EXPNRFRNNR node and a
TRANAMT not equal to zero.. Statement messages can be identified by a blank value in
EXPNRFRNNR and a TRANSAMT of zero. Foreign Currency Conversion information can
be identified by a value in EXPNRFRNNR that matches the value of EXPNRFRNNR for the
associated transactions, and a TRANAMT of zero. Note this is different from identifying
Foreign Currency Conversion information in the Recent Activity transactions. Additional
information regarding foreign transactions can be found in Appendix I – Foreign
Transaction Handling.
Transactions will have EXPNRFRNNR populated with a value; and TRANAMT <> 0
Statement Messages will have empty EXPNRFRNNR and AUTHNUM nodes, and
TRANAMT = 0
Currency Conversion Information will an EXPNRFRNNR value that matches the
EXPNRFRNNR value of the associated transaction and TRANAMT = 0
The XML nodes for statement balances and statement dates and the XML collections for
the transaction detail will only be returned when data is present in the First Data
System. If there is no data on file, these nodes are not returned in the response
document.
If there was activity on the account for the given statement cycle, each activity line item
from the statement will be returned in a separate collection.
Page 286
For statemented transactions:
Transactions can be identified by existence of a value in EXPNRFRNNR node. Statement
messages can be identified by a blank value in EXPNRFRNNR and AUTHNUM, and a
TRANSAMT of zero. Foreign Currency Conversion information can be identified by a
blank EXPNRFRNNR value, an AUTHNUM value that matches the AUTHNUM value of the
associated transaction and a TRANAMT of zero. Note this is different from identifying
Foreign Currency Conversion information in the Recent Activity transactions. Additional
information regarding foreign transactions can be found in Appendix I – Foreign
Transaction Handling.
Dynamic fee information will also be returned if the Credit Union participates in the First
Data program and the optional parameter is passed in the URL request. See Recent
Activity Information for additional information regarding Dynamic Fees. Contact your
PSCU Account Executive to for more information on Dynamic Fees and to enroll in the
Dynamic Fees solution.
Refer to Appendix J – Statement Data for detail information regarding the collections
returned by this request.
Note: Filtering is applied for special characters in all *DESC fields. Please reference the
Tag and Property Reference Table for allowable special characters.
Page 287
Parameter Description Type Required Length
/
Optional
ACCTSUM ON – include account summary Fixed Optional 2
information
ADDLAUTH Y – include additional Fixed Optionnal 1
information about the
authorization including time
and AGED status
X – Include auth time, auth
aged status, auth description,
auth pin verification code, auth
tran type
Z – includes information from X
and Y, and authorization
expiration date and PI Type
A – includes information from
X, Y and Z plus original
authorization amount and PIID
for authorization
ADDLNONMON Y – Include additional NonMon Fixed Optional 1
information in the response
X – Include Last NonMon, Last
NonMon Date, Address Change
Date
Z – also include the open day,
email address, mobile number
and credit score
A – Include above and the
address verification flag
ADDLTRAN Y – include the expanded Fixed Optional 1
reference number and
sequence number in the
posted transaction collections
X – Also include the merchant
state and city, and point of sale
entry mode
A – also include greater than
Page 288
Parameter Description Type Required Length
/
Optional
500 transactions
ALTSTMT Y – Include alternate statement Fixed Optional 1
code in the response
APR Y to receive the APR Fixed Optional 1
information in the response
BSCR Y-include the behavior score in Fixed Optional 1
the response
CASHADV Y – Include cash advance Fixed Optional 1
information
COMPINFO Y – Include company name and Fixed Optional 1
company account type
DYNAMICFEES ON – Include dynamic fees Fixed Optional 2
EXTSTAT Y – Include date and reason Fized Optional 1
code for external status
FULLMINPAYDUE Y - Include the full minimum Fixed Optional 1
payment due in dollars and
cents
OPA Y – Include OPA in response Fixed Optional 1
PET Y-Include Personal Emboss Text Fixed Optional 1
in the response
PIID Y – Returns Plastic Identifier Fixed Optional 1
(card number) associated with
the transaction
PS Y – Include pricing strategy Fixed Optional 1
PYI Y-Include the previous years Fixed Optional 1
interest billed and paid in the
response
SHOWMERCHCODE ON – Use to indicate Merchant Fixed Optional 2
Code is to be returned in the
transaction collection
SHOWAUTHNUM ON – Use to indicate Fixed Optional 2
Authorization Number is to be
returned in the transaction
collection
Page 289
Parameter Description Type Required Length
/
Optional
STMTDATE ON – Use to indicate Statement Fixed Optional 2
data is to be returned in the
transaction collection
TRANACCT Y – Include the actual PIID used Fixed Optional 1
for the transaction when the
CARDNUMBER parameter is a
control account
TRANTYPE Y – Include transaction type in Fixed Optional 1
response
UPC UPC=ON Fixed Optional 2
UPC codes 1 -12 will be include
in the response
UPGDDT Y – Include Upgrade Date Fixed Optional 1
USF Y - Include four character Fixed Optional 1
Userflags value
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
XREF Y – Include cross reference Fixed Optional 1
numbers
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1432&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
Page 290
1432&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&SHOWM
ERCHCODE=ON&SHOWAUTHNUM=ON
A sample request that includes Statement Date as part of the transaction collections:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONID=
1432&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&STMTDA
TE=ON
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>C4A63942-369F-AB91-CA02-06981AD1189D</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1432</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE" />
<odsPscuTAG
NAME="PREVIOUSSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG
NAME="LASTBALANCE">9999999999999999.99</odsPscuTAG>
Page 291
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="INTCODE" />
<odsPscuTAG NAME="NEXTPAYDATE">MM-DD-YY</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="YTDINTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="EXTSTATUSCODE">DESCRIPTION</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="RECENTDTLDESC">RECENT TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="RECENTEXPNRFRNNR">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
Page 292
<odsPscuTAG
NAME="RECENTTRANAMT">99999999999999.99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="RECENTDTLDESC">RECENT TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="RECENTEXPNRFRNNR">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANAMT">99999999999999.99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="RECENTMERCHCITY">MERCHANT
CITY</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHNAME">MERCHANT
NAME</odsPscuTAG>
<odsPscuTAG NAME="RECENTZIP">999999999</odsPscuTAG>
<odsPscuTAG
NAME="RECENTMERCHNMBR">99999999999</odsPscuTAG>
<odsPscuTAG
NAME="RECENTAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="RECENTPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG NAME="RECENTACTCODE" />
<odsPscuTAG NAME="RECENTMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="RECENTTRANS">XX</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHSTATE">XX</odsPscuTAG>
<odsPscuTAG NAME="RECENTDECLINEREASONCODE" />
<odsPscuTAG NAME="RECENTREF">999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
Page 293
<odsPscuTAG NAME="PASTDTLDESC">PAST TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTDATE">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">PAST TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLAUTHNUM" />
<odsPscuTAG
NAME="PASTTRANAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTDATE">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PREVIOUSDTLDESC">PREVIOUS
TRANSACTION DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
Page 294
<odsPscuTAG
NAME="PREVIOUSSTATEMENTDATE">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREVIOUSEXPNRFRNNR" />
<odsPscuTAG
NAME="PREVIOUSTRANAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PREVIOUSDTLDESC">MESSAGE
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PREVIOUSDTLAUTHNUM" />
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTDATE">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CURRENTDTLDESC">CURRENT TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTDATE">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">99999999999999.99</odsPscuTAG>
Page 295
<odsPscuTAG NAME="CURRENTDTLDESC">CURRENT TRANSACTION
DESCRPTION</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTDATE">YYYYMMDD</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
<COLLECTION>
<odsPscuTAG
NAME="RECENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsP
scuTAG>
<odsPscuTAG
NAME="RECENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="RECENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANAMT">999999999999.99</odsPscuTAG>
Page 296
<odsPscuTAG NAME="RECENTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="RECENTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
Page 297
<odsPscuTAG
NAME="PREVIOUSEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PASTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="OPA">9999999999999999</odsPscuTAG>
</COLLECTION>
Page 298
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Identifier that is used
to group accounts together for
processing and reporting
ALTSTMT Alternate Statement Code Numeric 1 NM
CS
AMTPAST_DUE Amount past due, if any, in Numeric 16 BS
whole dollars
Available when ACCTSUM=ON
ANNUALACT Annual Activity CD Numeric 1 NM AF
BILLINGCYCLE Billing Cycle code. This value will Numeric 2 NM
be returned when the CS
ADDLNONMON parameter is
included in the request
BSCR Behavior score Numeric 3 BS
Included when BSCR=Y is in the
request
CARDTYPE Description of the Card program Alpha 25
– Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 299
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
shown as a percentage with 3
decimal places
Available when APR=Y
CASHADVOUTBAL Cash advance outstanding Numeric BS5
balance
CASHADVLIMIT Cash advance open to buy Numeric BS5
CHNAME Primary Cardholder’s name in Alpha 26 NM
LastName,FirstName MI format CSR
CHSECONDARY Secondary Cardholder’s name in Alpha 26 NM
LastName,FirstName MI format CSR
CLIENTID PSCU assigned client identifier Numeric 6
CMPYACCTTYPE Company account type when Alpha 1 NM
COMPINFO=Y is included in the AC
request
S – Sub Account
C – Countrol Account
CMPYNAME Company Name when Alpha 12 NM
COMPINFO=Y Numeric AC
CRDTBURSCOR Credit bureau score Numeric 3 NM
CR
CREDITAVAIL Dollar amount of the account's Numeric 16 BS
unused credit as of the
indicated date, shown as a
whole number without decimal
places
CREDITLIMIT The maximum credit extended Numeric 16 BS
to the account (this amount,
less the current balance and any
outstanding authorizations,
gives the available credit on the
account), shown as a whole
number without decimal places
CREDITLINEAM Amount of the previous credit line This Numeric 15 TBD
value will be returned when the
ADDLNONMON parameter is
Page 300
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
included in the request
CREDITLINECD Code representing the type of the last Alpha- 1 TBD
credit line change. This value will be Numeric
returned when the ADDLNONMON
parameter is included in the request
Valid codes:
A - Automatic
C - Permanently deferred
D - Adaptive Control decrease
I - Adaptive Control increase
M - Manual
O - Never increased
R - Adaptive Control increase or
decrease using the LSX transaction
S - Automatic increase due to check
transaction maximum line without an
available credit buffer
T - Increase due to additional deposit
for secured account
X - Reserved for restricted use
Y - Reserved for restricted use
0 - Reserved for future use
1 - Reserved for future use
2 - Automatic increase due to check
transaction maximum line with an
available credit buffer
3 - Decrease due to mid-cycle credit
line processing via Adaptive Control
4 - Increase due to mid-cycle credit
line processing via Adaptive Control
5 - Reserved for future use
6 - Reserved for future use
7 - Reserved for future use
8 - Reserved for restricted use
9 - Reserved for restricted use
CREDITLINEDT Date the previous line was Numeric 2 TBD
established. This value will be
returned when the ADDLNONMON
parameter is included in the request
Format: MMYY
CURRENTBALANCE Current balance on account, Numeric 16 BS
shown as a signed number with
2 decimal places and the
Page 301
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
decimal point in the response
CURRENTDTLAUTHNUM Authorization number provided Numeric 6 CDE
to the merchant for the item,
typically only available for retail
/ POS purchases where an
authorization was obtained
prior to the transaction posting
- transaction on last statement
CURRENTDTLDESC Description of the item; Alpha 40 CSS
allowable characters are ! @ # $
& * ( ) _ . , ‘ * - and white space
CURRENTDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
CURRENTDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
CURRENTDTLMERCHSTATE Merchant State Alpha 2 CDE
CURRENTDTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
CURRENTDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on last
statement
CURRENTDTLEXPREF Expanded reference number Numeric 17 CDE
CURRENTDTLSEQNUM Sequence number Numeric 5 CDA
CURRENTDTLTRANACCT PIID of the actual plastic used for Numeric 16 CDE
the transaction when the
CARDNUMBER is a control account
CURRENTEMBEDDEDFEEAMT The Dynamic Fees value that will Numeric 15 CSS
display if the DYNAMICFEES=ON
is included in the URL request
CURRENTEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item – transaction numeric
Page 302
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
on last statement
CURRENTINDTRANID Transaction indicator Alpha 17 CDE
numeric
CURRENTSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement
generated on
CURRENTSTATEMENT date,
shown as a signed number with
2 decimal places and decimal
point shown in response
CURRENTSTATEMENTDATE Date of the last statement, in Numeric 8 CCD
CCYYMMDD format
CURRENTTRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point
shown in the response -
transaction on last statement
CURRENTTRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on last
statement
CURRENTTRANTYPE Transaction Type Code – refer to Numeric 3 CDE
Appendix N for list of
transaction type codes
DATELASTPLASTICORDER Date of the last order of plastics Numeric 6 PIR
on the account, in YYMMDD
format (Note: Some situations
may return 000000 as the value)
Available when ACCTSUM=ON
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
Available when ACCTSUM=ON
EMAILADDR Email address Alpha Variabl NM
Page 303
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Numeric e EP
ESTATEMENTENROLLMENTSTATUS Only Valid for SCS eStatement Alpha 1 NM
participating Credit Unions EBP
Cardholder’s current
eStatement Enrollment Status
Valid Codes:
B – Cardholder receives both
Paper and Electronic Statements
D – Cardholder receives both
Paper and Electronic Statements
and currently is subject to
delinquency processing
E – Cardholder receives
Electronic Statements
L - The cardholder receives both
electronic and paper statements
and is billed additionally for
paper statements.
Blank – The cardholder is not
enrolled in eStatements
Available when ACCTSUM=ON
EXPIREDATE Date the credit account expires, Numeric 4 BS
in MMYY format
Available when ACCTSUM=ON
EXTCODE External Status Code as found Alpha 1 BS
within the First Data system,
one character - Issuer-assigned
status code determining specific
account processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Page 304
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited (I)
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
EXTSTATUSCODE External Status Code, described Alpha 30
in Words (for valid descriptions,
see EXTCODE)
EXTSTATDT Date the external status Numeric 6 NM
changed SA1
EXTSTATRESCD Reason for the external status Numeric 2 NM
change SA1
FRAUDSCORE Fraud Score Numeric 3 NM CR
FRAUDSCOREDT Date Fraud Score changed Numeric 6 NM CR
Format: YYMMDD
FRAUDSTRAT Current fraud strategy assigned to the Numeric 2 NM CR
account
FRAUDSTRATDT Date current fraud strategy assigned Numeric 6 NM CR
to the account
Format: YYMMDD
FRAUDSUSPENDSTARTDT Start date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may be
null.
Format:
YYMMDD
FRAUDSUSPENDSTRATEGY Strategy that will be enforced during Numeric 2 NM CR
time period defined by start and end
date
FRAUDSUSPENDENDDT End date for the suspension of the Numeric 6 NM CR
fraud strategy. This parameter may be
null.
Format:
YYMMDD
FULLMINPAYDUE Full minimum payment due as Numeric 19 CSS
calculated at statement cycle.
Page 305
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
Format:
9999999999999999.99
INTCODE Internal Status Code as found Alpha 1 BS
within the First Data system,
one character - System-assigned
code determining specific
account processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTSTATUSCODE Current Internal Status Code, in Alpha 30
Words (for valid descriptions,
see INTCODE)
LASTBALANCE Outstanding balance on the last Numeric 19 BS
statement, shown as a signed
number with 2 decimal places
and decimal point shown in
response
LASTCREDITLINEDATE Date of the last credit limit Numeric 4 BS
adjustment, in MMYY format
Available when ACCTSUM=ON
LASTNM Last NonMon transaction Numeric 3 BS
LASTNMDT Last NonMon Date Numeric 6 BS
LASTPAYAMT Amount of the last payment, in Numeric 19 BS7
dollars and cents with decimal
point shown in response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note: Some
situations may return 000000 as
the value)
Page 306
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
LASTSTMTDATE Date of the last statement, in Numeric 6 BS2
YYMMDD format (Note: Some
situations may return 000000 as
the value)
MINPAYAMT The minimum payment Numeric 16 BS
required to retain a current
status on the account (this
amount may or may not include
overlimit and or past due
amounts) and is shown as a
whole number without decimal
places. This value does reflect
any payment made during the
current cycle.
MISC1 Miscellaneous field 1. This value will AlphaNum 4 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC2 Miscellaneous field 2. This value will AlphaNum 5 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC3 Miscellaneous field 3. This value will AlphaNum 7 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC4 Miscellaneous field 4. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC5 Miscellaneous field 5. This value will AlphaNum 8 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC6 Miscellaneous field 6. This value will AlphaNum 12 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC7 Miscellaneous field 7. This value will AlphaNum 10 NM CS
be returned when the eric
Page 307
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
ADDLNONMON parameter is
included in the request
MISC8 Miscellaneous field 8. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC9 Miscellaneous field 9. This value will AlphaNum 10 NM CS
be returned when the eric
ADDLNONMON parameter is
included in the request
MISC10 Miscellaneous field 10. This value AlphaNum 10 NM CS
will be returned when the eric
ADDLNONMON parameter is
included in the request
MISC13 Miscellaneous field 13. This value AlphaNum 50 NM CS
will be returned when the eric
ADDLNONMON parameter is
included in the request
MOBILEPHONE Mobile phone Numeric 10 NM
EP
NEXTPAYDATE Date the next payment is due Numeric 8 BS4
on the account, in MM-DD-YY
format
Page 308
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
to the merchant for the item,
typically only available for retail
/ POS purchases where an
authorization was obtained
prior to the transaction posting
- transaction on next previous
statement
PASTDTLDESC Description of the item; Alpha 40 CSS
allowable characters are ! @ # $
& * ( ) _ . , ‘ * - and white space
PASTINDTRANID Transaction indicator Alpha 17 CDE
numeric
PASTDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
PASTDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
PASTDTLMERCHSTATE Merchant State Alpha 2 CDE
PASTDTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
PASTDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on next
previous statement
PASTDTLEXPREF Expanded reference number Numeric 17 CDE
PASTDTLSEQNUM Sequence number Numeric 5 CDA
PASTDTLTRANACCT PIID of the actual plastic used for Numeric 16 CDE
the transaction when the
CARDNUMBER is a control account
PASTEMBEDDEDFEEAMT The Dynamic Fees value that Numeric 15 CSS
will display if the
DYNAMICFEES=ON is included
in the URL request
Page 309
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
PASTEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item - transaction numeric
on next previous statement
PASTSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account generated 3 cycles back
on PASTSTATEMENTDATE,
shown as a signed number with
2 decimal places and decimal
point shown in response
PASTSTATEMENTDATE Date of the next previous Numeric 8 CCD
statement (3 statements ago),
in CCYYMMDD format
PASTTRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point
shown in the response -
transaction on next previous
statement
PASTTRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on
next previous statement
PASTTRANTYPE Transaction Type Code – refer Numeric 3 CDE
to Appendix N for list of
transaction type codes
PERSONZN Personal Emboss Text Alpha Up to PID
Included when PET=Y is Numeric 26
included in the request
PIID Plastic Identifier (card number) Numeric 16 CDE
associated with the transaction
PREVIOUSDTLAUTHNUM Authorization number provided Numeric 6 CDE
to the merchant for the item,
typically only available for retail
Page 310
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
/ POS purchases where an
authorization was obtained
prior to the transaction posting
- transaction on previous
statement
PREVIOUSDTLDESC Description of the item; Alpha 40 CSS
allowable characters are ! @ # $
& * ( ) _ . , ‘ * - and white space
PREVIOUSDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
PREVIOUSDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
PREVIOUSDTLMERCHSTATE Merchant State Alpha 2 CDE
PREVIOUSDTLPOSENTRY Point of Sale Entry Method Numeric 2 CDE
PREVIOUSDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on
previous statement
PREVIOUSDTLEXPREF Expanded reference number Numeric 17 CDE
PREVIOUSDTLSEQNUM Sequence number Numeric 5 CDA
PREVIOUSDTLTRANACCT PIID of the actual plastic used for Numeric 16 CDE
the transaction when the
CARDNUMBER is a control account
PREVIOUSEMBEDDEDFEEAMT The Dynamic Fees value that Numeric 15 CSS
will display if the
DYNAMICFEES=ON is included
in the URL request
PREVIOUSEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item - transaction numeric
on previous statement
PREVIOUSINDTRANID Transaction indicator Alpha 17 CDE
Page 311
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
numeric
PREVIOUSSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account generated 2 cycles ago
on the
PREVIOUSSTATEMENTDATE,
shown as a signed number with
2 decimal places and decimal
point shown in response
PREVIOUSSTATEMENTDATE Date of the previous statement Numeric 8 CCD
(2 statements ago), in
CCYYMMDD format
PREVOUSTRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point
shown in the response -
transaction on previous
statement
PREVIOUSTRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on
previous statement
PREVIOUSTRANTYPE Transaction Type Code – refer Numeric 3 CDE
to Appendix N for list of
transaction type codes
PRICINGSTRATEGY Pricing strategy on the account Alpha 4 NM ST
Numeric
PRIN Client-defined identifier of the Numeric 4 BS6
level within a System Bank
Identifier that is used
to group Agent Bank Identifiers
together for processing and
reporting
PURCHASEAPR Annual Percentage Rate Numeric 6 NM
Page 312
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
applying to purchases and SA2
merchandise, shown as a
percentage with 3 decimal
places.
Available when ACCTSUM=ON
PYIBLLDAMT Previous years interest billed Numeric 13 NM PH
Included when PYI=Y is in the
request.
PYIPDAMT Previous years interest paid Numeric 13 NM PH
Included when PYI=Y is in the
request
RECENTACTCODE Not used at this time
RECENTAUTHAGED A - Authorization has a matching Alpha 1 CDE
posted transaction.
D – Authorization was declined
Blank – transaction has not yet
posted.
RECENTAUTHEXPDT Expiration date of the card used Numeric 4 CDE
for the authorizaiton
RECENTAUTHORIGAMT Original authorization amount Numeric CDE
RECENTAUTHNUM Authorization Number for the Numeric 5 CDE
transaction; included in
response when
SHOWAUTHNUM=ON included
in the request
RECENTAUTHPITYPE PI Type of card used for the Numeric 2 CDE
authorization
RECENTAUTHTIME Time of the authorization Numeric 6 CDE
Format: hhmmss
RECENTAUTHDESCR Text description of the authorization Alpha 27 CDA
RECENTAUTHPINVERCD Pin Verification code Alpha 1 CDE
Valid values:
I - Verification performed by
Interchange
O - Verification performed using
method other than PIN
Page 313
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
R - Verification performed by CPU
acquirer
U - First Data unable to perform
verification
V - Verification performed by First
Data
X - Declined PIN on ATM balance
inquiry
blank - Not a PIN Management
System processor
RECENTAUTHTRANACCOUNT PIID of the actual plastic used for Numeric 16 CDE
the transaction when the
CARDNUMBER is a control account
RECENTAUTHTRANCD Type of transaction authorization Alpha 2 CDA
Valid values:
AA - Authorization adjustment
AP - Preauthorization request
approved
CA - Cash advance authorization
approved
CD - Cash advance authorization
declined
CE - Cash advance authorization
approved by expansion
CO - Override declined cash
advance
CP - Cash advance authorization
approved by positive identification
CS - Cash referral
CT - Cash advance authorization
approved by name
CV - Cash approval by VIP
CX - Cash advance authorization
manually declined
DA - Duplicate authorization
DC - Cash authorization approved
without issuer contact
DM - Merchandise authorization
approved without issuer contact
DP - Preauthorization request
denied
IA - Issuer’s adjustment
MA - Merchandise authorization
approved
Page 314
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
MC - In-store return
MD - Merchandise authorization
declined
ME - Merchandise authorization
approved by expansion
MI - Right-time payment
MO - Override declined
merchandise authorization
MP - Merchandise authorization
approved by positive identification
MR - Right-time pay/reversal
MS - Merchandise referral
MT - Merchandise authorization
approved by name
MV - Merchandise approval by VIP
MX - Merchandise authorization
manually declined
PA - Permanent authorization
request
PP - Visa® and Mastercard®
person-to-person payment
transaction approval
PR - Visa and Mastercard person-to-
person payment transaction reversal
PX - Visa and Mastercard person-to-
person payment transaction decline
PZ - Permanent authorization
adjustment
QA - Merchandise Return
Adjustment
QD - Reserved for restricted use
QQ - Reserved for restricted use
QR - Reserved for restricted use
QZ - Merchandise Return
Adjustment Declined
VA - Private label ETC return posted
at the time of return
XC - Manual override cash advance
authorization
XM - Manual override merchandise
authorization
RECENTDTLDESC Description of the item; Alpha 40 CDA
allowable characters are ! @ # $
Page 315
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
& * ( ) _ . , ‘ * - and white space
RECENTDTLINDTRANID Transaction indicator Alpha 17 CDE
numeric
RECENTMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
RECENTDTLPOSTDATE Posting Date of the item, in Numeric 6 CDA
YYMMDD format (Note: Some
situations may return 000000 as
the value)
RECENTDTLEXPREF Expanded reference number Numeric 17 CDE
RECENTDTLSEQNUM Sequence number Numeric 5 CDA
RECENTDTLTRANACCT PIID of the actual plastic used for Numeric 16 CDE
the transaction when the
CARDNUMBER is a control account
RECENTDECLINEREASONCODE Authorization decline reason Alpha 2 CDE
code, returned only for declined
authorizations and represents
the reason for the decline, valid
codes are listed in Appendix E of
this document.
RECENTEMBEDDEDFEEAMT The Dynamic Fees value that Numeric 15 CSS
will display if the
DYNAMICFEES=ON is included
in the URL request
RECENTEXPNRFRNNR Reference number for the Alpha 17 CDA
transaction item
RECENTMERCHCAT Identifier of the code in the Alpha 4 CDA
authorization record identifying
the merchant’s line of
business
RECENTMERCHCITY City of merchant location at Alpha 30 CDE
which the transaction occurred
Page 316
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
CURRENTDTLMERCHCITY Merchant City Alpha 18 CDE
Numeric
RECENTLMERCHSTATE Merchant State Alpha 2 CDE
RECENTPOSENTRY Point of Sale Entry Method Numeric 2 CDE
RECENTMERCHNAME Identifier of the merchant Alpha 30 CDE
location at which the
transaction occurred
RECENTMERCHNMBR Merchant’s assigned credit card Alpha Up to CDE
processing number/identifier Numeric 15
RECENTMERCHSTATE State code of the merchant Alpha 2 CDE
where the authorization took
place, 2 characters
RECENTPOSENTRYMODE Code representing how the Numeric 2 CDE
merchant entered the
transaction. Valid codes
include:
00 Not specified
01 Manual (key entered)
02 Magnetic stripe read (the
merchant has not certified
the magnetic stripe
transmission has been
unaltered)
03 Bar code read
04 OCR coding read
05 Chip/smart card
06 Track 1 read (the
transmission was not sent
to First Data and has not
been certified as being
unaltered)
81 Electronic commerce
(MasterCard only)
90 Entire magnetic stripe read
Page 317
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
and transmitted (the
merchant has certified that
the magnetic stripe
transmission has been
unaltered)
95 Chip/smart card data is
unreliable (Visa only)
RECENTREF System-assigned identifier of Numeric 6 CDA
the authorization approval code
for the approved transaction -
this field is blank if the
authorization was declined.
RECENTTRANAMT Amount of the item, shown as a Numeric 15 CDA
signed number in dollars and
cents with 2 decimal places and
a decimal point shown in the
response
RECENTTRANDATE Transaction date for the item, in Numeric 6 CDA
YYMMDD format (Note: Some
situations may return 000000 as
the value)
RECENTTRANS Transaction codes representing Alpha 2 CDA
the type of authorization action,
valid codes are listed in
Appendix F of this document.
RECENTTRANTYPE Transaction Type Code – refer Numeric 3 CDE
to Appendix N for list of
transaction type codes
RECENTZIP Zip or postal code of the Numeric 9 CDE
merchant where the
authorization took place
SPCLFLAGS Special Flags 5 – 8. This value will Alpha 4 BS
be returned when the
ADDLNONMON parameter is
included in the request
Page 318
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
STATUS External Status Code as found Alpha 1 BS
within the First Data system,
one character – see valid codes
listed above in EXTCODE node
Available when ACCTSUM=ON
SYSTEM First Data-assigned identifier of Numeric 4 BS6
the level used to group Principal
Bank Identifiers
together for processing and
reporting
UPC1 UPC 1 Alpha 1 NM CC
Numeric
UPC2 UPC 2 Alpha 1 NM CC
Numeric
UPC3 UPC 3 Alpha 1 NM CC
Numeric
UPC4 UPC 4 Alpha 1 NM CC
Numeric
UPC5 UPC 5 Alpha 1 NM CC
Numeric
UPC6 UPC 6 Alpha 2 NM CC
Numeric
UPC7 UPC 7 Alpha 2 NM CC
Numeric
UPC8 UPC 8 Alpha 3 NM CC
Numeric
UPC9 UPC 9 Alpha 3 NM CC
Numeric
UPC10 UPC 10 Alpha 4 NM CC
Numeric
UPC11 UPC 11 Alpha 5 NM CC
Numeric
UPC12 UPC 12 Alpha 6 NM CC
Numeric
Page 319
OdsPscu TAG NAME Description Type Lengt First
h Data
Screen
UPGRADEDT Upgrade Date Alpha 8
Included when UPGDDT=Y
USERFLAGS1THRU4 Current activation status of the Alpha 25 BS
plastic, described in words with
the First Data code for the
activation status following the
description in parenthesis –
please see Appendix C of this
document for further
information.
Available when ACCTSUM=ON
USF14 Four character Userflags string Alpha 4 BS
YTDINTBILLED Amount of interest billed on the Numeric 15 BS4
account Year-To-Date
YTDINTPAID Amount of interest paid Year- Numeric 15 BS4
to-Date, in dollars and cents
with decimal point shown in
response
Page 320
7.18 Statement Summaries, All Available
The Statement Summaries, All Available request will return the summary level
information regarding Cardholder Statements for up to the last 12 months of
statements, depending on the Credit Union’s PCF settings, that have cycled on the First
Data System for the account. This information is similar to the information found on
CHD screens in the First Data System. The response to this request will contain several
items that pertain to each cycled statement. The items are organized into separate
collections - where each collection represents a single statement period. Summary data
regarding the current state of the account is also included.
Page 321
7.18.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1436&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>009DB131-E210-D12E-1B8B-7A3BB88E5A05</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1436</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">0000000000099999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST MI</odsPscuTAG>
<odsPscuTAG NAME="DAYSDELINQ">999</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">0000000000099999.99</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LAST,FIRST MI</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">0000000000099999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE3">999</odsPscuTAG>
<odsPscuTAG NAME="CYCLE2">999</odsPscuTAG>
<odsPscuTAG NAME="INTSTATUSCODE" />
<odsPscuTAG NAME="CYCLE1">999</odsPscuTAG>
Page 322
<odsPscuTAG NAME="EXTSTATUSCODE" />
<odsPscuTAG NAME="USERFLAGS1THRU4">X</odsPscuTAG>
<odsPscuTAG
NAME="DATELASTPLASTICORDER">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="CONTROL">9</odsPscuTAG>
<odsPscuTAG NAME="EXPIREDATE">MMYY</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">0000000099999.99</odsPscuTAG>
<odsPscuTAG NAME="PURCHASEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="CASHADVANCEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="HISTORY">XXXXXXXXXXXX</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="DATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TOTCASHADV">0000000000099999.99</odsPscuTAG
>
<odsPscuTAG
NAME="TOTADJ">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTPURCH">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTCREDITS">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTPMTS">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTFCPUR">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTFCCASH">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="BALANCE">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTDUEAMT">0000000000099999.99</odsPscuTAG
>
<odsPscuTAG
NAME="OVERLIMITFEES">0000000000099999.99</odsPscuTA
G>
<odsPscuTAG
NAME="LATEFEES">0000000000099999.99</odsPscuTAG>
Page 323
<odsPscuTAG
NAME="MINPAYAMT">0000000000099999.99</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEDT">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="DATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TOTCASHADV">0000000000099999.99</odsPscuTAG
>
<odsPscuTAG
NAME="TOTADJ">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTPURCH">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTCREDITS">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTPMTS">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTFCPUR">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="TOTFCCASH">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="BALANCE">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTDUEAMT">0000000000099999.99</odsPscuTAG
>
<odsPscuTAG
NAME="OVERLIMITFEES">0000000000099999.99</odsPscuTA
G>
<odsPscuTAG
NAME="LATEFEES">0000000000099999.99</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">0000000000099999.99</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEDT">YYMMDD</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
Page 324
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 325
7.18.3 Tag and Property Reference
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 326
OdsPscu TAG NAME Description Type Length First
Data
Screen
controls reissue processing - please
see Appendix B of this document for
further information. This value is
updated in real-time when a card is
activated.
CREDITAVAIL Dollar amount of the account's Numeric 16 BS
unused credit as of the indicated
date, shown as a signed whole
number without decimal places
CREDITCT Number of credits posted on the Numeric Variable CHD
account during the cycle
CREDITLIMIT The maximum credit extended to Numeric 16 BS
the account (this amount, less the
current balance and any outstanding
authorizations, gives the available
credit on the account), shown as a
whole number without decimal
places
CURRENTBALANCE Current balance on account, shown Numeric 16 BS
as a signed number with 2 decimal
places and the decimal point in the
response
CYCLE1 Count of times the account has been Numeric 3 BS
one-cycle delinquent in the last two
years plus year to date. Each time
the account becomes one-cycle
delinquent; the First Data System
adds one to this field. If the
cardholder clears the delinquency
within this cycle, the number in this
field remains. If the account moves
to the next higher delinquency level,
the FD System subtracts one from
the counter in this field and adds
Page 327
OdsPscu TAG NAME Description Type Length First
Data
Screen
one to the counter at the next higher
delinquency level.
CYCLE2 Count of times the account has been Numeric 3 BS
two cycles delinquent in the last two
years plus year to date. Each time
the account becomes two cycles
delinquent, the First Data System
adds one to this field. If the
cardholder clears the delinquency
within this cycle, the number in this
field remains. If the account moves
to the next higher delinquency level,
the FD System subtracts one from
the counter in this field and adds
one to the counter at the next higher
delinquency level.
CYCLE3 Count of times the account has been Numeric 3 BS
three-or-more-cycles delinquent in
the last two years plus year to date.
Each time the account becomes
three-or-more-cycles delinquent, the
FD System adds one to this field. If
the cardholder clears the
delinquency within this cycle, the
number in this field remains. If the
account moves to the next higher
delinquency level, the FD System
adds one to this field. For example, if
the account moves from three-cycles
to four-cycles delinquent, the FD
System adds one to this field.
DATE Date of the statement, in Numeric 8 CCD
CCYYMMDD format
DATELASTPLASTICORDER Date of the last order of plastics on Numeric 6 PIR
the account, in YYMMDD format
Page 328
OdsPscu TAG NAME Description Type Length First
Data
Screen
(Note: Some situations may return
000000 as the value)
DAYSDELINQ Number of Days the account is Numeric 3 BS
delinquent
EXPIREDATE Date the credit account expires, in Numeric 4 BS
MMYY format
EXTSTATUSCODE External Status Code as found within Alpha 1 BS
the First Data system, one character
- Issuer-assigned status code
determining specific account
processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited (I)
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
FULLMINPAYDUE Full minimum payment due as Numeric 19 CSS
calculated at statement cycle.
Format:
9999999999999999.99
HISTORY Identifier of the 12-month account Alpha 12 BS
activity history. The 12 status flags
rotate when the account cycles so
that the leftmost flag indicates the
account’s status during the last cycle
and the rightmost flag indicates the
account’s status during the current
Page 329
OdsPscu TAG NAME Description Type Length First
Data
Screen
cycle one year ago. The System
automatically changes the first flag
when the account’s status changes
due to an account transfer or due to
the posting of an across-cycle
reversal, adjustment, or interest
charge-off. Only the first flag on the
left (last cycle) changes by these
postings.
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
LATEFEES The total amount of late fees Numeric 19 CHD
assessed on the account during the
statement period, shown as a signed
number with 2 decimal places and a
Page 330
OdsPscu TAG NAME Description Type Length First
Data
Screen
decimal pint shown in response
LASTPAYAMT Amount of the last payment, in Numeric 19 BS7
dollars and cents with decimal point
shown in response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format (Note: Some
situations may return 000000 as the
value)
MINPAYAMT The minimum payment due for the Numeric 19 CSS
statement. This value is a whole
dollar value with no decimal. This
value does reflect any payment
made during the current cycle.
MINPAYDUEDT The date the minimum payment is Numeric 6 CSS
due for the statement period, in
YYMMDD format (Note: Some
situations may return 000000 as the
value)
OVERLIMITFEES The total amount of overlimit fees Numeric 19 CHD
assessed on the account during the
statement period, shown as a signed
number with 2 decimal places and a
decimal pint shown in response
PASTDUEAMT The total amount past due at the Numeric 19 CSS
time of the statement cycle, shown
as a signed number with 2 decimal
places and a decimal point shown in
response
PMNTCT Number of payments posted on the Numeric Variable CHD
account during the cycle
PURCHASEAPR Annual Percentage Rate applying to Numeric 6 NM
purchases and merchandise, shown SA2
as a percentage with 3 decimal
places
Page 331
OdsPscu TAG NAME Description Type Length First
Data
Screen
PURCHCT Number of purchases posted on the Numeric Variable CHD
account during the cycle
TOTADJ Total amount of the adjustments Numeric 19 CHD
that occurred during the statement
cycle, shown as a signed number
with 2 decimal places and decimal
point shown in response
TOTCASHADV Total amount of the cash advances Numeric 19 CHD
that occurred during the statement
cycle, shown as a signed number
with 2 decimal places and decimal
point shown in response
TOTCREDITS Total amount of the credits that Numeric 19 CHD
occurred during the statement cycle,
shown as a signed number with 2
decimal places and decimal point
shown in response
TOTFCCASH Total amount of the finance charges Numeric 19 CHD
for cash advances that occurred
during the statement cycle, shown
as a signed number with 2 decimal
places and decimal point shown in
response
TOTFCPUR Total amount of the finance charges Numeric 19 CHD
for purchases that occurred during
the statement cycle, shown as a
signed number with 2 decimal places
and decimal point shown in
response
TOTPMTS Total amount of the payments that Numeric 19 CHD
occurred during the statement cycle,
shown as a signed number with 2
decimal places and decimal point
shown in response
Page 332
OdsPscu TAG NAME Description Type Length First
Data
Screen
TOTPURCH Total amount of the purchases that Numeric 19 CHD
occurred during the statement cycle,
shown as a signed number with 2
decimal places and decimal point
shown in response
USERFLAGS1THRU4 Current activation status of the Alpha 1 BS
plastic using the First Data code – numeric
please see Appendix C of this
document for further information
Page 333
7.19 CVV2 Validation
The CVV2 function validates the CVV2 value provided in the request.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=1
02&REQUESTID=102&FUNCTIONID=1446&CARDNUMBER=9999999999999999
&CLIENTID=9999&EXPIREDATE=YYMM&CVV2=999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>750CDA14-B419-6485-2F4F-5E7F14A1B8BB</GUID>
Page 334
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1446</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="MATCH">TRUE</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 335
7.20 Promotional / Protected Balances
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONID=
1449&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999
The following is an example of the XML data provided from the URL above when a
successful request has been executed:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
Page 336
<RESPONSE>0</RESPONSE>
<GUID>C1767027-2164-BF3B-777F-D2F7DBCA9718</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1449</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
<odsPscuTAG NAME="PROMOTRANDATE">100416</odsPscuTAG>
<odsPscuTAG NAME="PROMOMONINTRATE">00.638</odsPscuTAG>
<odsPscuTAG NAME="CTDITMFEESAM">00000000000.00</odsPscuTAG>
<odsPscuTAG NAME="UNPDINTRAM">00000000005.93</odsPscuTAG>
<odsPscuTAG NAME="EFFECTIVEDATE">100417</odsPscuTAG>
<odsPscuTAG NAME="PROMOANNINTRATE">007.650</odsPscuTAG>
<odsPscuTAG
NAME="UNPDCRDTLIFEAM">0000000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="PROMOTYPE">M</odsPscuTAG>
<odsPscuTAG NAME="PROMOID">M6JP0960</odsPscuTAG>
<odsPscuTAG NAME="PROMODAILYINTRATE">.02095</odsPscuTAG>
<odsPscuTAG NAME="CURRPRINAM">0000000000001128.41</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 337
7.20.3 Tag and Property Reference
Page 338
OdsPscu TAG NAME Description Type Length First
Data
Screen
Promotional balance
UNPDINTRAM One of four fields used to calculate
Promotional balance
Page 339
7.21 FICO Score
This request will return the last recorded FICO score on the credit card account.
FICO and score providers have requirements and approvals that must be met prior to
displaying the FICO score to the consumer. Please be sure to contact them prior to
implementing this feature in order to not compromise compliance. Here is an example
of the display that meets the Equifax requirements:
Page 340
The Function ID for this request is 1463.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
UPDATE=1&FUNCTIONID=1463&CARDNUMBER=9999999999999999&CLIENTID=9999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1463</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="FICOSCORE">999</odsPscuTAG>
<odsPscuTAG NAME="FICODATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="FICOBUREAU">X</odsPscuTAG>
<odsPscuTAG NAME="FICOREASON1">9</odsPscuTAG>
<odsPscuTAG NAME="FICOREASON2">9</odsPscuTAG>
<odsPscuTAG NAME="FICOREASON3">9</odsPscuTAG>
<odsPscuTAG NAME="FICOREASON4">9</odsPscuTAG>
<odsPscuTAG NAME="FICOREASON5">9</odsPscuTAG>
</odsPscu:DATASTREAM>
Page 341
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 342
7.22 PFM
This function is used by Personal Financial Management tools to obtain credit card
transactions. This function uses the Affinity Number to look up the credit card number.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.x
ml.xmlProcess&RQID=SEARCHXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1800&CLIENTID=9999&ACCOUNTIDENTIFIER=999999999&VENDORID=999
99&STARTDATE=MMDDYYYY&ENDDATE=MMDDYYYY
Page 343
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>C4A63942-369F-AB91-CA02-06981AD1189D</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1800</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="ACCOUNTIDENTIFIER">99999</odsPscuTAG>
<odsPscuTAG NAME="DESCRIPTION">CREDIT_CARD</odsPscuTAG>
<odsPscuTAG NAME="TYPE">CREDIT_CARD</odsPscuTAG>
- <COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="CARDNUMBER">9999</odsPscuTAG>
<odsPscuTAG NAME="INTERESTRATE">99.99</odsPscuTAG>
<odsPscuTAG NAME="BRAND">Visa Classic</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYAMT">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="NEXTPAYDATE">MM-DD-YY</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
- </COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="CARDNUMBER">9999</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONID">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="TRANSACTIONYPE">CREDIT</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TRANSACTIONDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONMERCHCATCODE">9999</odsPscuTAG>
</COLLECTION>
Page 344
- <COLLECTION>
<odsPscuTAG NAME="CARDNUMBER">9999</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONID">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="TRANSACTIONYPE">CREDIT</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TRANSACTIONDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONMERCHCATCODE">9999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="CARDNUMBER">9999</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONID">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="TRANSACTIONYPE">CREDIT</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="TRANSACTIONDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONMERCHCATCODE">9999</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 345
OdsPscu TAG NAME Description Type Length First
Data
Screen
Number
BRAND Description of the Card program – Alpha 25
Some valid entries include:
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
DESCRIPTION CREDIT_CARD Alpha 10 N/A
CREDITLIMIT The maximum credit extended to Numeric 16 BS
the account (this amount, less the
current balance and any
outstanding authorizations, gives
the available credit on the
account), shown as a whole
number without decimal places
CURRENTBALANCE Current balance on account, Numeric 16 BS
shown as a signed number with 2
decimal places and the decimal
point in the response
EXTCODE External Status Alpha 1 BS
Valid codes:
A - Authorization prohibited
B - Bankrupt
Z - Charge off
C - Closed
F- Frozen
I - Interest accrual prohibited
L - Lost
Blank - Normal
Page 346
OdsPscu TAG NAME Description Type Length First
Data
Screen
INTCODE Internal Status Alpha 1 BS
Valid codes:
Blank – Normal
D – Delinquent
O – Over the limit
X – Delinquent and Over the limit
INTERESTRATE Purchase APR Numeric 5 BS2
99.99
MINPAYAMT The minimum payment required to Numeric 16 BS
retain a current status on the
account (this amount may or may
not include overlimit and or past
due amounts) and is shown as a
whole number without decimal
places. This value does reflect any
payment made during the current
cycle.
NEXTPAYDATE Date the next payment is due on Numeric 8 BS4
the account, in MM-DD-YY format
Page 347
OdsPscu TAG NAME Description Type Length First
Data
Screen
included in the request
TRANSACTIONPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format (Note: Some
situations may return 000000 as
the value) - transaction on last
statement
TRANSACTIONTYPE CREDIT / DEBIT based on monetary Alpha 5 N/A
transaction code
TYPE CREDIT_CARD Alpha 10 N/A
Page 348
7.23 Multiple Function Call
The Multiple Function Call request returns the Statement Data, Last 3 Cycles and Recent
Activity, Memos and Reward Activity and History. The Multiple Function Call
encompasses Functions 1432, 1417, and 1407 coded into one call.
The Function ID for this request is 1443.
Page 349
Parameter Description Type Required Length
/
Optional
W Yes – the account is a Fixed Required 3
Wilmington account when the
CARDNU
MBER Is a
Wilmingt
on card
number
YTDINTBILLED YES-Returns the YTDINTBILLED Fixed Optional 2
information
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&REQUESTID=1
02&FUNCTIONID=1443&CARDNUMBER=9999999999999999&CLIENTID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1443</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
Page 350
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="PURCHASEAPR">99.999</odsPscuTAG>
<odsPscuTAG NAME="CASHADVANCEAPR">999.99</odsPscuTAG>
<odsPscuTAG NAME="LASTPAYDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="LASTPAYAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="YTDINTPAID">999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="LASTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITAVAIL">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG
NAME="INTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="INTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="EXTSTATUSCODE">DESCRIPTION</odsPscuTAG>
<odsPscuTAG NAME="EXTCODE">X</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTBALANCE">9999999.99</odsPscu
TAG>
<odsPscuTAG
NAME="CURRENTSTATEMENTDATE">CCYYMMDD</odsPscuTAG
>
Page 351
<odsPscuTAG
NAME="PREVIOUSSTATEMENTBALANCE">9999999.99</odsPscu
TAG>
<odsPscuTAG
NAME="PREVIOUSSTATEMENTDATE">CCYYMMDD</odsPscuTA
G>
<odsPscuTAG
NAME="PASTSTATEMENTBALANCE">9999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTSTATEMENTDATE">CCYYMMDD</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="RECENTMERCHNAME">NAME OF
MERCHANT</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHCITY">MERCHANT’S
CITY</odsPscuTAG>
<odsPscuTAG NAME="RECENTZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHSTATE">XX</odsPscuTAG>
<odsPscuTAG
NAME="RECENTMERCHNMBR">9999999999999999</odsPscu
TAG>
<odsPscuTAG
NAME="RECENTAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG NAME="RECENTACTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="RECENTTRANS">XX</odsPscuTAG>
<odsPscuTAG
NAME="RECENTDECLINEREASONCODE">XX</odsPscuTAG>
<odsPscuTAG NAME="RECENTREF">999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="RECENTMERCHNAME">NAME OF
MERCHANT</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHCITY">MERCHANT’S
CITY</odsPscuTAG>
Page 352
<odsPscuTAG NAME="RECENTZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHSTATE">XX</odsPscuTAG>
<odsPscuTAG
NAME="RECENTMERCHNMBR">9999999999999999</odsPscu
TAG>
<odsPscuTAG
NAME="RECENTAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG NAME="RECENTACTCODE">X</odsPscuTAG>
<odsPscuTAG NAME="RECENTMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="RECENTTRANS">XX</odsPscuTAG>
<odsPscuTAG
NAME="RECENTDECLINEREASONCODE">XX</odsPscuTAG>
<odsPscuTAG NAME="RECENTREF">999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="RECENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsP
scuTAG>
<odsPscuTAG
NAME="RECENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RECENTDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="RECENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsP
scuTAG>
<odsPscuTAG
NAME="RECENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
Page 353
<odsPscuTAG
NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RECENTDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
Page 354
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
Page 355
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKI"D>XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">FIRST MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">SECOND MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
Page 356
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="MEMOSEQUENCE">999</odsPscuTAG>
<odsPscuTAG NAME="MEMOCLKID">XXX</odsPscuTAG>
<odsPscuTAG NAME="MEMODATA">THIRD MEMO LINE
DISPLAYED ON CIS</odsPscuTAG>
<odsPscuTAG NAME="MEMOTYPE">X</odsPscuTAG>
<odsPscuTAG NAME="MEMODATE">YYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ISALLOWEDACCESS">TRUE</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="TOTALPOINTSREDEEMED">99999999.9</odsPscuTAG
>
<odsPscuTAG NAME="DUETOEXPIRE">99999999.9</odsPscuTAG>
<odsPscuTAG
NAME="POINTSPENDING">99999999.9</odsPscuTAG>
<odsPscuTAG
NAME="EXPIRATIONDATE">CCYYMM</odsPscuTAG>
<odsPscuTAG
NAME="REDEEMABLEPOINTS">99999999.9</odsPscuTAG>
<odsPscuTAG
NAME="POINTSEARNED">99999999.9</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 357
Responses when the request URL contains the DYNAMICFEES=ON parameter will
contain the EMBEDDEDFEES tag in the Transaction collections where appropriate.
<COLLECTION>
<odsPscuTAG
NAME="RECENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsP
scuTAG>
<odsPscuTAG
NAME="RECENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="RECENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="RECENTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RECENTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="RECENTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="CURRENTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="CURRENTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
Page 358
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="PREVIOUSEXPNRFRNNR">XXXXXXXXXXXXXXXXX</od
sPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSTRANAMT">999999999999.99</odsPscuTA
G>
<odsPscuTAG NAME="PREVIOUSDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PREVIOUSEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="PASTEXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG
NAME="PASTDTLAUTHNUM">XXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PASTDTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PASTTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="PASTTRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PASTDTLDESC">TRANSACTION
DESCRIPTION</odsPscuTAG>
<odsPscuTAG
NAME="PASTEMBEDDEDFEEAMT">999999999999.99</odsPscuTAG>
</COLLECTION>
Page 359
7.23.3 Tag and Property Reference
Page 360
OdsPscu TAG NAME Description Type Length First
Data
Screen
CURRENTDTLAUTHNUM Authorization number provided to Numeric 6 CDE
the merchant for the item,
typically only available for retail /
POS purchases where an
authorization was obtained prior
to the transaction posting -
transaction on last statement
CURRENTDTLDESC Description of the item, in words Alpha 40 CSS
- transaction on last statement
CURRENTDTLMERCHCATCODE Merchant Code for the Numeric 5 CDE
transaction; included in
response when
SHOWMERCHCODE=ON
included in the request
CURRENTDTLPOSTDATE Posting Date of the item, in Numeric 6 CSS
YYMMDD format - transaction on
last statement
CURRENTEXPNRFRNNR Reference number for the Alpha 17 CSS
transaction item – transaction on numeric
last statement
CURRENTSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement date,
shown as a signed number with
2 decimal places and decimal
point shown in response
CURRENTSTATEMENTDATE Date of the last statement, in Numeric 8 CCD
CCYYMMDD format
CURRENTTRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point
shown in the response -
transaction on last statement
CURRENTTRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format - transaction on
last statement
DUETOEXPIRE The number of points that will Numeric 10 BO2
expire if not redeemed prior to
the expiration date, formatted to
one decimal place with the
decimal point displayed in the
response
EMBEDDEDFEEAMT The Dynamic Fees value that Numeric 15 CSS
Page 361
OdsPscu TAG NAME Description Type Length First
Data
Screen
will display if the
DYNAMICFEES=ON is included
in the URL request.
EXPIRATIONDATE The date in which the points due Numeric 6 BO2
to expire will expire, in CCYYMM
format (please note there is no
day – points typically expire on
the last day of the month)
EXTCODE External Status Code as found Alpha 1 BS
within the First Data system, one
character - Issuer-assigned
status code determining specific
account processing
Valid codes:
Authorization prohibited (A)
Bankrupt (B)
Charge off (Z)
Closed ( C)
Frozen (F)
Interest accrual prohibited (I)
Lost (L)
Normal ()
Revoked (E)
Stolen (U)
EXTSTATUSCODE External Status Code, described Alpha 30
in Words (for valid descriptions,
see EXTCODE)
INTCODE Internal Status Code as found Alpha 1 BS
within the First Data system, one
character - System-assigned
code determining specific
account processing
Valid codes:
Credit balance (N)
Delinquent (D)
Delinquent and overlimit (X)
Normal ()
Overlimit (O)
INTSTATUSCODE Current Internal Status Code, in Alpha 30
Words (for valid descriptions, see
INTCODE)
Page 362
OdsPscu TAG NAME Description Type Length First
Data
Screen
ISALLOWEDACCESS Designates that the card has a Alpha 5
rewards program in place, a
value of TRUE in this node is
expected when a rewards
program is present while a value
of FALSE indicates that there is
not a CU Rewards program
present on the credit account
LASTBALANCE Outstanding balance on the last Numeric 19 BS
statement, shown as a signed
number with 2 decimal places
and decimal point shown in
response
LASTPAYAMT Amount of the last payment, in Numeric 19 BS7
dollars and cents with decimal
point shown in response
LASTPAYDATE Date of the last payment, in Numeric 6 BS7
YYMMDD format
LASTSTMTDATE Date of the last statement, in Numeric 6 BS2
YYMMDD format
MEMOCLKID Initials attached to the memo Alpha 3 CIS
item’s creation – for system
generated (automatic) CIS
memos, this field will not contain
a value
MEMODATA Memo item’s text Alpha 62 CIS
numeric
MEMODATE The date the memo item was Numeric 6 CIS
input into the host system, shown
in YYMMDD format
MEMOSEQUENCE Memo item’s sequence number Numeric 3 CIS
MEMOTYPE Memo type code assigned by Alpha 1 CIS
First Data
Valid codes:
A - Account Level Processing
memos
B - Chargeback memos
C - CIS memos
J - Adjustment memos
N - Non-monetary transaction
memos
P - Payment memos
Page 363
OdsPscu TAG NAME Description Type Length First
Data
Screen
R - Retrieval memos
W - CIMS memos
X - Collections memos
Page 364
OdsPscu TAG NAME Description Type Length First
Data
Screen
PASTTRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point
shown in the response -
transaction on next previous
statement
PASTTRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format - transaction on
next previous statement
POINTSEARNED The number of rewards points Numeric 10 BO4
that have been earned and
credited to the account,
formatted to one decimal place
with the decimal point displayed
in the response
POINTSPENDING The number of points that are Numeric 10 BO4
currently pending being added to
the points earned formatted to
one decimal place with the
decimal point displayed in the
response
PREVIOUSDTLAUTHNUM Authorization number provided to Numeric 6 CDE
the merchant for the item,
typically only available for retail /
POS purchases where an
authorization was obtained prior
to the transaction posting -
transaction on previous
statement
PREVIOUSDTLDESC Description of the item, in words Alpha 40 CSS
- transaction
Page 365
OdsPscu TAG NAME Description Type Length First
Data
Screen
PREVIOUSSTATEMENTBALANCE Outstanding balance on the Numeric 19 CSS
account as of the statement date,
shown as a signed number with
2 decimal places and decimal
point shown in response
PREVIOUSSTATEMENTDATE Date of the previous statement (2 Numeric 8 CCD
statements ago), in CCYYMMDD
format
PREVOUSTRANAMT Amount of the item, shown as a Numeric 15 CSS
signed number with 2 decimal
places and a decimal point
shown in the response -
transaction on previous
statement
PREVIOUSTRANDATE Transaction date for the item, in Numeric 6 CSS
YYMMDD format - transaction on
previous statement
PRIN Client-defined identifier of the Numeric 4 BS6
level within a System Bank
Identifier that is used
to group Agent Bank Identifiers
together for processing and
reporting
PURCHASEAPR APR for purchases Numberic 7 NM
SA2
RECENTACTCODE Not used at this time.
RECENTAMT Amount of the authorization, Numeric 15 CDA
shown as a signed number in
dollars and cents with 2 decimal
places and a decimal point
shown in the response
RECENTAUTHNUM Authorization Number for the Numeric 5 CDE
transaction; included in
response when
SHOWAUTHNUM=ON
included in the request
RECENTDECLINEREASONCODE Authorization decline reason Alpha 2 CDE
code, returned only for declined
authorizations and represents
the reason for the decline, valid
codes are listed in Appendix E of
this document.
RECENTDTLDESC Description of the item, in words Alpha 40 CDA
Page 366
OdsPscu TAG NAME Description Type Length First
Data
Screen
RECENTDTLPOSTDATE Posting Date of the item, in Numeric 6 CDA
YYMMDD format
RECENTEXPNRFRNNR Reference number for the Alpha 17 CDA
transaction item
numeric
RECENTMERCHCATCODE Identifier of the code in the Alpha 4 CDA
authorization record identifying
the merchant’s line of
business
RECENTMERCHCITY City of merchant location at Alpha 30 CDE
which the transaction occurred
RECENTMERCHNAME Identifier of the merchant location Alpha 30 CDE
at which the transaction occurred
RECENTMERCHNMBR Merchant’s assigned credit card Alpha Up to CDE
processing number/identifier Numeric 15
RECENTMERCHSTATE State code of the merchant Alpha 2 CDE
where the authorization took
place, 2 characters
RECENTPOSENTRYMODE Code representing how the Numeric 2 CDE
merchant entered the
transaction.
Valid Codes:
00 Not specified
01 Manual (key entered)
02 Magnetic stripe read (the
merchant has not
certified the magnetic
stripe transmission has
been unaltered)
03 Bar code read
04 OCR coding read
05 Chip/smart card
06 Track 1 read (the
transmission was not
sent to First Data and has
not been certified as
being unaltered)
81 Electronic commerce
Page 367
OdsPscu TAG NAME Description Type Length First
Data
Screen
(MasterCard only)
90 Entire magnetic stripe
read and transmitted
(the merchant has
certified that the
magnetic stripe
transmission has been
unaltered)
95 Chip/smart card data is
unreliable (Visa only)
RECENTREF System-assigned identifier of the Numeric 6 CDA
authorization approval code for
the approved transaction - this
field is blank if the authorization
was declined.
RECENTTRANAMT Amount of the item, shown as a Numeric 15 CDA
signed number in dollars and
cents with 2 decimal places and
a decimal point shown in the
response
RECENTTRANDATE Transaction date for the item, in Numeric 6 CDA
YYMMDD format
RECENTTRANS Transaction code representing Alpha 2 CDA
the type of authorization action;
valid codes are listed in
Appendix F of this document.
RECENTZIP Zip or postal code of the Numeric 10 CDE
merchant where the
authorization took place
REDEEMABLEPOINTS The number of rewards points Numeric 10 BO1
that are able to be redeemed in
the rewards program, formatted
to one decimal place with the
decimal point displayed in the
response
SYSTEM First Data-assigned identifier of Numeric 4 BS6
the level used to group Principal
Bank Identifiers
together for processing and
reporting
Page 368
OdsPscu TAG NAME Description Type Length First
Data
Screen
TOTALPOINTSREDEEMED The number of rewards points Numeric 10 BO2
that have been redeemed in the
rewards program, formatted to
one decimal place with the
decimal point displayed in the
response
YTDINTBILLED Amount of interest billed on Numeric 15 BS
the account Year-To-Date
YTDINTPAID Amount of interest paid Year-to- Numeric 15 BS
Date, in dollars and cents with
decimal point shown in response
This function will provide the history for both Omaha and Wilmington accounts.
Page 369
7.24.2 Sample URL and Response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONID=
1474&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&PROGRA
M=XXXXXXXX&STARTDATE=YYYYMMDD&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1474</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="TRANSACTIONDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONDESC">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PROGRAMNAME">XXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="TRANSACTIONDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONDESC">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
</odsPscuTAG>
<odsPscuTAG
NAME="TRANSACTIONAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LASTSTMTDATE">CCYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="PROGRAMNAME">XXXXXXXX</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 370
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 371
7.25 Cardholder Plastics
The Cardholder Plastics functions returns attribute specific to the plastics on the
account for each cardholder on the account.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1480&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&PREVEXP=Y&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
Page 372
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1480</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="CUSTNM">LAST, FIRST MI</odsPscuTAG>
<odsPscuTAG NAME="MBRSEQ">99999</odsPscuTAG>
<odsPscuTAG NAME="PRSNEMBS">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PIACTIVATION">9</odsPscuTAG>
<odsPscuTAG NAME="PIACTIVATIONDT">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="PIID">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="PISTATUS">C</odsPscuTAG>
<odsPscuTAG NAME="PITYPE">9</odsPscuTAG>
<odsPscuTAG NAME="PLSTCT">999</odsPscuTAG>
<odsPscuTAG NAME="PLSTTYPE">99</odsPscuTAG>
<odsPscuTAG NAME="PIEXPDT">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="REISSUECD">99</odsPscuTAG>
<odsPscuTAG NAME="ROLE">99</odsPscuTAG>
<odsPscuTAG NAME="PI_ISSUANCE">
- <COLLECTION>
<odsPscuTAG NAME="ISSNRESNCD">CC</odsPscuTAG>
<odsPscuTAG NAME="ISSNRESNTX">CC</odsPscuTAG>
<odsPscuTAG NAME="PRDCTX">CCCC</odsPscuTAG>
<odsPscuTAG NAME="SHIPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="SHIPSTAT">CCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ISSNRESNCD">2</odsPscuTAG>
<odsPscuTAG NAME="ISSNRESNCD">2</odsPscuTAG>
<odsPscuTAG NAME="PRDCTX">CCCC</odsPscuTAG>
<odsPscuTAG NAME="SHIPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="SHIPSTAT">CCCC</odsPscuTAG>
</COLLECTION>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="CUSTNM">LAST, FIRST MI</odsPscuTAG>
<odsPscuTAG NAME="MBRSEQ">99999</odsPscuTAG>
<odsPscuTAG NAME="PRSNEMBS">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PIACTIVATIONDT">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="PIACTIVATION">9</odsPscuTAG>
<odsPscuTAG NAME="PIID">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="PISTATUS">C</odsPscuTAG>
<odsPscuTAG NAME="PITYPE">9</odsPscuTAG>
<odsPscuTAG NAME="PLSTCT">999</odsPscuTAG>
Page 373
<odsPscuTAG NAME="PLSTTYPE">99</odsPscuTAG>
<odsPscuTAG NAME="PIEXPDT">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="REISSUECD">99</odsPscuTAG>
<odsPscuTAG NAME="ROLE">99</odsPscuTAG>
<odsPscuTAG NAME="PI_ISSUANCE" />
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="CUSTNM">LAST, FIRST MI</odsPscuTAG>
<odsPscuTAG NAME="MBRSEQ">99999</odsPscuTAG>
<odsPscuTAG NAME="PRSNEMBS">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PIACTIVATION">9</odsPscuTAG>
<odsPscuTAG NAME="PIACTIVATIONDT">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="PIID">9999999999999999</odsPscuTAG>
<odsPscuTAG NAME="PISTATUS">C</odsPscuTAG>
<odsPscuTAG NAME="PITYPE">9</odsPscuTAG>
<odsPscuTAG NAME="PLSTCT">999</odsPscuTAG>
<odsPscuTAG NAME="PLSTTYPE">99</odsPscuTAG>
<odsPscuTAG NAME="PIEXPDT">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="REISSUECD">99</odsPscuTAG>
<odsPscuTAG NAME="ROLE">99</odsPscuTAG>
<odsPscuTAG NAME="PI_ISSUANCE">
- <COLLECTION>
<odsPscuTAG NAME="ISSNRESNCD">CC</odsPscuTAG>
<odsPscuTAG NAME="ISSNRESNTX">CC</odsPscuTAG>
<odsPscuTAG NAME="PRDCTX">CCCC</odsPscuTAG>
<odsPscuTAG NAME="SHIPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="SHIPSTAT">CCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ISSNRESNCD">CC</odsPscuTAG>
<odsPscuTAG NAME="ISSNRESNTX">CC</odsPscuTAG>
<odsPscuTAG NAME="PRDCTX">CCCC</odsPscuTAG>
<odsPscuTAG NAME="SHIPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="SHIPSTAT">CCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ISSNRESNCD">CC</odsPscuTAG>
<odsPscuTAG NAME="ISSNRESNTX">CC</odsPscuTAG>
<odsPscuTAG NAME="PRDCTX">CCCC</odsPscuTAG>
<odsPscuTAG NAME="SHIPDATE">YYYY-MM-DD</odsPscuTAG>
<odsPscuTAG NAME="SHIPSTAT">CCCC</odsPscuTAG>
</COLLECTION>
</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
Page 374
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 375
OdsPscu TAG NAME Description Type Length
available for primary and
secondary cardholders. The value
will be blank for authorized users
PRDCTX Product description – will only have Alpha 4
a value when the PI Status is blank
PRSNEMBS Person Emboss Text Alpha Up to 26
Numeric
PIACTIVATION Activation Status for PIID Numeric 1
0 - No card activation status
1 - Never block for card activation
7 - Positive cardholder identification
and/or verification of plastic receipt
has not yet been established for
this new plastic or plastic issued for
a reason other than reissue.
8 - Positive cardholder identification
and/or verification of plastic receipt
has not yet been established for
this reissued plastic.
9 - Cardholder identification was
established today by First Data
Fraud
Management Services.
PIACTIVATIONDT Activation Date Numeric 8
Format:
YYYY-MM-DD
PIID PIID for the card holder Numeric 16
PIEXPDT PI expiration date Numeric 6
PIFRAUDSUSPENDENDDT End date for strategy suspension Numeric 6
PIFRAUDSUSPENDSTARTDT Start Date for strategy suspension Numeric 6
PIFRAUDSUSPENDSTRATEGY Fraud Suspend Strategy Numeric 2
PISTATUS Status of the PIID Alpha 1
Valid values:
A - Authorization prohibited
C - Closed
F - Frozen
L - Lost
Blank - Normal
U - Stolen
PITYPE PI Type Numeric 2
01 - Plastic card
02 - Contactless chip card
06 - Europay Mastercard Visa
(EMV) Dual Interface (contactless
and
Page 376
OdsPscu TAG NAME Description Type Length
contact) chip card
07 - Mobile device
08 - Europay Mastercard Visa
(EMV) Contact Only chip card
PLSTCT Plastic count for card holder Numeric 4
PLSTTYPE Plastic type code / image code Numeric 2
PIPREVEXPDT Previous PI expiration date Numeric 6
REISSUECD Reissue code Numeric 1
Same as the CONTROL in 1402
ROLE* Customer role code Numeric 2
01 – Primary
02 – Secondary
03 - Authorized
SHIPDATE Plastic ship date – will only have a Numeric 10
value when the PI Status is blank
and a plastic has been recently
been issued
SHIPSTAT Plastic ship status– will only have a Alpha 4
value when the PI Status is blank
and a plastic has recently been
issued
STATDATE PIID date status changed Numeric 10
YYYY-MM-DD
Page 377
7.26 Dispute History
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1479&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1479</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
Page 378
<odsPscuTAG NAME="BALANCEID">CCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="BALANCETYPE">X</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DISPUTECT">99</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEELIGFLG">9</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEPROCDT">MMDDYY</odsPscuTAG>
<odsPscuTAG NAME="DISPUTETYPE">C</odsPscuTAG>
<odsPscuTAG NAME="GRACELIGFLG">9</odsPscuTAG>
<odsPscuTAG NAME="RESLAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RESLDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="RESLFAVRCD">C</odsPscuTAG>
<odsPscuTAG NAME="RESLELIGFLG">C</odsPscuTAG>
<odsPscuTAG NAME="RESLPROCDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="SEQNUM">99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="BALANCEID">CCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="BALANCETYPE">X</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DISPUTECT">99</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEELIGFLG">9</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEPROCDT">MMDDYY</odsPscuTAG>
<odsPscuTAG NAME="DISPUTETYPE">C</odsPscuTAG>
<odsPscuTAG NAME="GRACELIGFLG">9</odsPscuTAG>
<odsPscuTAG NAME="RESLAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RESLDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="RESLFAVRCD">C</odsPscuTAG>
<odsPscuTAG NAME="RESLELIGFLG">C</odsPscuTAG>
<odsPscuTAG NAME="RESLPROCDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="SEQNUM">99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="BALANCEID">CCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="BALANCETYPE">X</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DISPUTECT">99</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEELIGFLG">9</odsPscuTAG>
<odsPscuTAG NAME="DISPUTEPROCDT">MMDDYY</odsPscuTAG>
<odsPscuTAG NAME="DISPUTETYPE">C</odsPscuTAG>
<odsPscuTAG NAME="GRACELIGFLG">9</odsPscuTAG>
<odsPscuTAG NAME="RESLAMT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="RESLDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="RESLFAVRCD">C</odsPscuTAG>
Page 379
<odsPscuTAG NAME="RESLELIGFLG">C</odsPscuTAG>
<odsPscuTAG NAME="RESLPROCDT">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="SEQNUM">99</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 380
OdsPscu TAG NAME Description Type Length First Data
Screen
C – Card holder
Blank – Not provided
RESLELIGFLG Resolved dispute eligibility code Alpha 1 CHD
Y/N
RESLPROCDT Dispute processing resolution date Numeric 6 CHD
YYMMDD
SEQNUM Sequence number system assigned Numeric 2 CHD
Page 381
7.27 Retrieve Emboss requests
This function will retrieve the existing embossing requests for a card number. This
function is only applicable to those credit unions using PSCU for plastic services.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1489&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1489</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="PLSTCT">9999</odsPscuTAG>
Page 382
<odsPscuTAG NAME="PLSTSTAT">CCCC</odsPscuTAG>
<odsPscuTAG NAME="TRANSTS">YYYY-MM-DD-
HH.MI.SS.SSSSSS</odsPscuTAG>
<odsPscuTAG NAME="SEQNUM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRODUCTCD">CC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PLSTCT">9999</odsPscuTAG>
<odsPscuTAG NAME="PLSTSTAT">CCCC</odsPscuTAG>
<odsPscuTAG NAME="TRANSTS">YYYY-MM-DD-
HH.MI.SS.SSSSSS</odsPscuTAG>
<odsPscuTAG NAME="SEQNUM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRODUCTCD">CC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PLSTCT">9999</odsPscuTAG>
<odsPscuTAG NAME="PLSTSTAT">CCCC</odsPscuTAG>
<odsPscuTAG NAME="TRANSTS">YYYY-MM-DD-
HH.MI.SS.SSSSSS</odsPscuTAG>
<odsPscuTAG NAME="SEQNUM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRODUCTCD">CC</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 383
OdsPscu TAG NAME Description Type Length FD Screen -
Field
TimeStamp Numric
Page 384
7.28 Statement History
This function will return statement history information for up to 12 previous cycles.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&REQUESTID=1
02&FUNCTIONID=1430&CLIENTID=9999&CARDNUMBER=XXXXXXXXXXXXXXXX&VENDOR
ID=99999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
Page 385
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1430</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="STMTDATE">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="CASHAPR">999.999</odsPscuTAG>
<odsPscuTAG NAME="MERCHAPR">999.999</odsPscuTAG>
<odsPscuTAG
NAME="AVAILCREDIT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CRDTLIMIT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CASHADVAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CASHADVCT">999</odsPscuTAG>
<odsPscuTAG NAME="ADJCT">999</odsPscuTAG>
<odsPscuTAG NAME="ADJAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CREDITAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CREDITCT">999</odsPscuTAG>
<odsPscuTAG NAME="PYMTAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PYMTCT">999</odsPscuTAG>
<odsPscuTAG NAME="PURCHAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PURCHCT">999</odsPscuTAG>
<odsPscuTAG
NAME="STMTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTDUEAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="OVRLMTFEE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LATEFEE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYDUEAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEDT">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STMTDATE">YYYYMMDD</odsPscuTAG>
Page 386
<odsPscuTAG NAME="CASHAPR">999.999</odsPscuTAG>
<odsPscuTAG NAME="MERCHAPR">999.999</odsPscuTAG>
<odsPscuTAG
NAME="AVAILCREDIT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CRDTLIMIT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CASHADVAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CASHADVCT">999</odsPscuTAG>
<odsPscuTAG NAME="ADJCT">999</odsPscuTAG>
<odsPscuTAG NAME="ADJAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CREDITAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CREDITCT">999</odsPscuTAG>
<odsPscuTAG NAME="PYMTAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PYMTCT">999</odsPscuTAG>
<odsPscuTAG NAME="PURCHAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PURCHCT">999</odsPscuTAG>
<odsPscuTAG
NAME="STMTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTDUEAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="OVRLMTFEE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LATEFEE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYDUEAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEDT">YYYYMMDD</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="STMTDATE">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="CASHAPR">999.999</odsPscuTAG>
<odsPscuTAG NAME="MERCHAPR">999.999</odsPscuTAG>
<odsPscuTAG
NAME="AVAILCREDIT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CRDTLIMIT">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CASHADVAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CASHADVCT">999</odsPscuTAG>
<odsPscuTAG NAME="ADJCT">999</odsPscuTAG>
Page 387
<odsPscuTAG NAME="ADJAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CREDITAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="CREDITCT">999</odsPscuTAG>
<odsPscuTAG NAME="PYMTAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PYMTCT">999</odsPscuTAG>
<odsPscuTAG NAME="PURCHAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PURCHCT">999</odsPscuTAG>
<odsPscuTAG
NAME="STMTBALANCE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PASTDUEAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="OVRLMTFEE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="LATEFEE">9999999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="MINPAYDUEAM">9999999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="MINPAYDUEDT">YYYYMMDD</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Page 388
OdsPscu TAG NAME Description Type Length
AVAILCREDIT Available Credit Numeric 19
CASHADVAM Amount of Cash Advances Numeric 19
CASHAPR Cash Advance APR Numeric 7
CASHADVCT Number of Cash Advance Numeric 3
Transactions
CRDTLIMIT Credit Limit Numeric 19
CREDITAM Amount of Credits Numeric 19
CREDITCT Number of Credit transactions Numeric 3
LATEFEE Late Fee Numeric 19
MERCHAPR Merchandise APR Numeric 7
MINPAYDUEAM Minimum Payment Due Amount Numeric 19
MINPAYDUEDT Minimum Payment Due Date Numeric 8
MNTHCT Months exceeding YEARCT to payoff Numeric 2
balance paying MPD
MPDFULLAMT Total amount paid if paying off by MPD Numeric 19
OVRLMTFEE Over the Limit fee Numeric 19
PASTDUEAM Past Due Amount Numeric 19
PURCHAM Amount of Purchases Numeric 19
PURCHCT Number of Purchase transactions Numeric 3
PYMTAM Amount of Payments Numeric 19
PYMTCT Number of Payment Transactions Numeric 3
STMTBALANCE Statement Balance Numeric 19
STMTDATE Statement Date Numeric 8
YEARCT Number of years to payoff balance Numeric 2
when paying MPD
Page 389
7.29 Credit Bureau Reporting History
This function returns information regarding the credit bureau reporting of a credit card
record.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1492&CLIENTID=9999&CARDNUMBER=XXXXXXXXXXXXXXXX&VENDORID=
XXXXXX
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
Page 390
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1492</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG
NAME="PMTHISTORY24">CCCCCCCCCCCCCCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="FIRSTDELQ">MMDDYYYY</odsPscuTAG>
<odsPscuTAG NAME="RPTDATE">YYYYMMDD</odsPscuTAG>
- </COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PMTHISTORY24">CCCCCCCCCCCCCCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="FIRSTDELQ">MMDDYYYY</odsPscuTAG>
<odsPscuTAG NAME="RPTDATE">YYYYMMDD</odsPscuTAG>
- </COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Page 391
OdsPscu TAG NAME Description Type Length First
Data
Screen
zero balance
61 - Voluntary surrender account
paid in full
62 - Collection account paid in
full
63 - Repossession account paid
in full
64 - Charged-off account paid in
full
65 - Account paid in full for
which foreclosure had been
started
71 - Account 30 days past due
78 - Account 60 days past due
80 - Account 90 days past due
82 - Account 120 days past due
83 - Account 150 days past due
84 - Account 180 days past due
88 - Claim filed with government
for insured portion of balance on
a
defaulted loan
89 - Deed received in lieu of foreclosure
on a defaulted mortgage
93 - Account seriously past due
or assigned to collections
94 - Foreclosure/credit grantor
sold collateral to settle defaulted
mortgage
95 - Voluntary surrender
96 - Merchandise repossessed by
credit grantor; may be a balance
due
97 - Account charged off (unpaid
balance reported as a loss by
credit
Page 392
OdsPscu TAG NAME Description Type Length First
Data
Screen
grantor)
DA - Delete account from credit
bureau files
DF - Delete entire account due to
confirmed fraud
FIRSTDELQ Date of first delinquency Numeric 8 CBR
PMTHISTORY24 24 month payment history Alpha 7 CBR
Valid codes:
Z - Account not statemented because of
zero balance and no activity
0 - 7 - No postings during the cycle
The number indicates the number of
cycles delinquent.
Page 393
OdsPscu TAG NAME Description Type Length First
Data
Screen
Q - X - Both debit and credit postings
during the cycle
Q - Account not delinquent
R - Account one cycle delinquent
S - Account two cycles delinquent
T - Account three cycles delinquent
U - Account four cycles delinquent
V - Account five cycles delinquent
W - Account six cycles delinquent
X - Account seven cycles delinquent
% - Credit balance with no activity
# - Credit balance with debit and credit
activity
+ - Credit balance with debit activity
only
- - Credit balance with credit activity
only
RPTDATE Credit bureau reporting date CBR
Page 394
7.30 Payment Allocation
This function returns information about payments and how they are allocated on the
account.
LIST Option:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1493&CLIENTID=9999&CARDNUMBER=9999999999999999&OPTION=LIST
&
- <INVISION>
- <ACCTXML>
- <VALIDATION>
Page 395
<RESPONSE>0</RESPONSE>
<GUID>603FD542-A09D-CD4D-E408-CA831CE1B30F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1493</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
<odsPscuTAG NAME="PMNTDT">MM/DD/YYYY</odsPscuTAG>
<odsPscuTAG NAME="PMNTAMT">99999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PMNTREFNR">99999999999999999999999</odsPscuTAG>
<odsPscuTAG NAME="PMNTTRANCD">999</odsPscuTAG>
<odsPscuTAG
NAME="PMNTTICKETID">999999999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PMNTDT">MM/DD/YYYY</odsPscuTAG>
<odsPscuTAG NAME="PMNTAMT">99999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PMNTREFNR">99999999999999999999999</odsPscuTAG>
<odsPscuTAG NAME="PMNTTRANCD">999</odsPscuTAG>
<odsPscuTAG
NAME="PMNTTICKETID">999999999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PMNTDT">MM/DD/YYYY</odsPscuTAG>
<odsPscuTAG NAME="PMNTAMT">99999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PMNTREFNR">99999999999999999999999</odsPscuTAG>
<odsPscuTAG NAME="PMNTTRANCD">999</odsPscuTAG>
<odsPscuTAG
NAME="PMNTTICKETID">999999999999999</odsPscuTAG>
</COLLECTION>
Page 396
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
DISPLAY Option:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1493&CLIENTID=9999&CARDNUMBER=9999999999999999&OPTION=DIS
PLAY&PMNTTICKETID=999999999999999
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>603FD542-A09D-CD4D-E408-CA831CE1B30F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1493</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG
NAME="PMNTBALDESC">CCCCCCCCCCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="PMNTBALTYPECD">CCCC</odsPscuTAG>
<odsPscuTAG NAME="PMNTBALID">99999999</odsPscuTAG>
<odsPscuTAG
NAME="PMNTCHGPRIN">999999999999.99</odsPscuTAG>
Page 397
<odsPscuTAG NAME="PMNTFEEADJ">999999.99</odsPscuTAG>
<odsPscuTAG
NAME="PMNTTICKETID">999999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
LIST:
OdsPscu TAG NAME Description Type Length First Data
Screen
PMNTAMT Payment Amount Numeric Up to PAM
15
PMNTDT Payment Date Numeric 10 PAM
PMNTREFNR Payment reference number Numeric 23 PAM
PMNTTICKETID Payment Ticket ID Numeric 15 NA
PMNTTRANCD Payment Transaction code Numeric 3 PAM
DISPLAY:
OdsPscu TAG NAME Description Type Length First Data
Screen
PMNTBALDESC Balance description Char 17 PAD
PMNTBALID Balance Promotion ID Numeric 8 PAD
PMNTBALTYPECD Balance Type Code Char 1 PAD
PMNTCHGPRIN Change to balance principal Numeric 14 PAD
PMNTFEEADJ Payment fee adjustment Numeric 14 PAD
amount
PMNTTICKETID Payment ticket ID Numeric 15 PAD
Page 398
PSCU – Propriety and Confidential Last Revised: 03/31/2023
Version 23.1
Page 399
8 ACCTXML
The ACCTXML requests provide the abilities to create accounts, report declined ICS
applications, perform account transfers, activate an account, order a plastic, order PIN
letter, and change the status of an account. Section 8 of this document provides a
detailed description of each of the ACCTXML functions along with the fixed, required
and variable parameters, a sample search request and response, and a description of
each node within the response.
Contact your PSCU Account Executive for information regarding Instant Issue.
Function ID Description
1440 New Cardholder Account – Creates a new cardholder account on the First
Data platform for single or separate entity credit unions. This function
requires the card number. This function is previously documented as a
GETDATAXML function. Current implementations using GETDATAXML will
continue to work. It is requested that future implementations use the
ACCTXML.
1440 New Generated Cardholder Account – Creates a new cardholder account
on the First Data system for single and separate entity credit unions. This
function generates a card number from the provided system, principal
and agent IDs. This function is previously documented as a GETDATAXML
function. Current implementations using GETDATAXML will continue to
work. It is requested that future implementations use the ACCTXML.
1440 Decline ICS Application – Reports a Declined ICS application on the First
Data system. This function is previously documented as a GETDATAXML
function. Current implementations using GETDATAXML will continue to
work. It is requested that future implementations use the ACCTXML.
1438 Account Transfer – Transfers account within same principals and across
principals on the First Data system. This function is previously
documented as a GETDATAXML function. Current implementations using
GETDATAXML will continue to work. It is requested that future
implementations use the ACCTXML.
1408 Activate Card – Activates a card on the First Data system. This function is
Page 400
previously documented as an ACTIVATEXML function. Current
implementations using ACTIVATEXML will continue to work. It is
requested that future implementations use the ACCTXML.
1409 Order Replacement Card – Orders a replacement card from the First Data
system. This function is previously documented as an ORDERCARDXML
function. Current implementations using ORDERCARDXML will continue
to work. It is requested that future implementations use the ACCTXML.
1416 Order PIN Letter – Orders a letter containing the cardholder’s established
PIN from First Data. This function is previously documented as an
ORDERPINXML function. Current implementations using ORDERPINXML
will continue to work. It is requested that future implementations use the
ACCTXML.
1425 External Status – Sets the external status of an account on the First Data
system. This function is previously documented as a STATUSXML function.
Current implementations using STATUSXML will continue to work. It is
requested that future implementations use the ACCTXML.
1444 Set PIN Offset – EMV Omaha Instant Issue
1445 Set PIN Security – EMV Omaha Instant Issue
1448 Authorization and Transaction Posting – Authorize and post a cash
advance or merchandise transaction to a card holder account.
1450 Redeem Rebates – Redeem rebates in real time for cash or statement
adjustment
1452 Lost – Process an account being reported as either Lost.
1464 Dispute – Dispute Reason Codes
1458 Submit Dispute – Submit Dispute
1478 Account Updater – VAU and MAU
1488 Cancel Emboss Request – Cancel existing emboss request
1490 Refund Rebates – Refund rebates / rewards on an account
1725 Instant Issue EMV Omaha – Data retreival
1726 Instant Issue EMV Omaha – Post Chip Row Data
1727 Instant Issue EMV Omaha – Retrieve current Chip Row Data
1730 Instant Issue EMV Omaha – Data request
Page 401
8.1 New Cardholder Account
The New Cardholder Account request creates a new cardholder account on the First
Data system for single and separate entity credit unions. The account number is
provided in the request. This function emulates the NC and NCA transactions in 3270
screens. Once the account is created it is immediately available for authorizations.
For the creation of a separate entity account the optional parameter SEPARATE_ENTITY
must be included in the request with a value of “Y”.
Page 402
Parameter Description Type Required Length
/
Optional
A house number and a street name
(must have both)
Post office box number
Numeric rural route number
Valid Codes:
CF – Canadian French
EN – American English
SP – Latin American Spanish
APPTYPE Application Type Fixed Required 1
Valid Code:
A – Approved, has credit available
BUSPHONE Business Phone Numeric Optional 10
CARDNUMBER Cardnumber for the new account. Numeric Required 16
Checks for valid or duplicate account
number structure
CHECKINGID Demand Deposit Identifier - Checking Numeric Optional Up to 17
account number
CHRGDDA Automatic Payment Code Alpha Optional 1
Valid Codes:
J – cardholder designated amount (J or
K) (payment source=checking)
K – cardholder designated amount (J or
K) (payment source=savings)
N – Daily Current Balance Option (N or
O) (payment source=checking)
Page 403
Parameter Description Type Required Length
/
Optional
O – Daily Current Balance Option (N or
O) (payment source = savings)
0 – Automatic payment is not set up for
this account
1 – Unpaid Billed Minimum Payment
Due (1 or 5) (payment source=checking)
2 – Full Statemented Balance or Unpaid
Billed Minimum Payment Due (2 or 6)
(payment source = checking)
3 – Reserved for UK processors
4 – Full Statemented Balance (4 or 7)
(payment source=checking)
5 – Unpaid Billed Minimum Payment
Due (1 or 5)(payment source=savings)
6 – Full Statemented Balance or Unpaid
Billed Minimum Payment Due (2 or 6)
(payment source=savings)
7 – Full Statemented Balance (4 or 7)
(payment source=savings)
8 – Reserved for UK processors
CITY Address City Alpha Required Variable
Use ‘%20’ for spaces up to 18
character
s
CMPYID COMMERCIAL CARD ONLY! Alpha Required Variable
Company ID for up to 8
Commerci character
al Card s
CMPYCNTRL COMMERCIAL CARD ONLY! Alpha Optional 16
Company Control Number
Page 404
Parameter Description Type Required Length
/
Optional
CRDTBURRPT Credit Bureau Report Alpha Optional 1
Valid codes:
D - Delete account from credit bureau
files
Q - Account not reported
Z - Account not reported
1 - Individual
2 - Joint contractual liability
3 - Authorized user
5 - Co-maker
7 – Maker
CRDTBURSCOR Credit Bureau Score Numeric Optional 3
CRDTLIFEINS Credit Life Insurance Numeric Optional 1
CRDTLIMTAMT Credit Limit Amount Numeric Optional 13
Valid Codes:
EFC - Equifax Canada
EFX - Equifax
TRC - TransUnion Canada
TRU - TransUnion
TRW - Experian
CRDTRPT Credit Reporting Alpha Optional 1
Valid Codes:
N - No, do not send for more
information request for a credit bureau
report
Y - Yes, send a request for a credit
bureau report
blank - No, do not send a request for a
Page 405
Parameter Description Type Required Length
/
Optional
credit bureau report
HMPHONE Home Phone Numeric Optional 10
Page 406
Parameter Description Type Required Length
/
Optional
emboss plastics on this account
3 - Use the parameters in the Plastic
Products strategy for plastic type 3 to
emboss plastics on this account
4 - Use the parameters in the Plastic
Products strategy for plastic type 4 to
emboss plastics on this account
5 - Use the parameters in the Plastic
Products strategy for plastic type 5 to
emboss plastics on this account
6 - Do not emboss plastics or create
embossing records for this account
7 - Do not emboss plastics or create
embossing records for this account
blank - This field has no entry
PRIMARYNAME Primary cardholder Alpha Required 26 for Visa
24 for MC
Valid format
LAST%20SUFFIX,FIRST%20MI
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
PRIMARYSSN Primary cardholder’s Social Security Numeric Optional 9
Number
PRIDOB Primary cardholder’s Date of Birth Numeric Optional 8
Valid Codes:
C - Sir
F - Ms.
M - Mr.
Page 407
Parameter Description Type Required Length
/
Optional
U - No salutation printed
PRMR_PLST_CT Count of plastics to be issued to the Fixed Optional 1
primary cardholder. – Use for
If there is a value is in Number of separate
Plastics field of the Credit Union’s PCF entity
setting, this field must be blank. If a zero only
is entered, no plastics will be issued
PRMR_PLST_TYPE Type of plastic to be issued to primary Fixed Optional 1
cardholder – Use for
separate
Valid Codes: entity
0 - Do not emboss plastics for the only
principal cardholder on this account
1 - Use the parameters in the Plastic
Products strategy for plastic type 1 to
emboss plastics on this account
2 - Use the parameters in the Plastic
Products strategy for plastic type 2 to
emboss plastics on this account
3 - Use the parameters in the Plastic
Products strategy for plastic type 3 to
emboss plastics on this account
4 - Use the parameters in the Plastic
Products strategy for plastic type 4 to
emboss plastics on this account
5 - Use the parameters in the Plastic
Products strategy for plastic type 5 to
emboss plastics on this account
6 - Do not emboss plastics or create
embossing records for this account
7 - Do not emboss plastics or create
embossing records for this account
blank - This field has no entry
ROUTINGNBR Routing Transit number Numeric Optional 17
RUSHPLST Rush Plastics Indicator Code Alpha Optional 2
Page 408
Parameter Description Type Required Length
/
Optional
Valid Codes:
Rush Plastics Indicator Code
Valid Codes:
AU - Send plastics to you via UPS® Next
Day Air® shipment
BA - Mail plastics to you via DHL*
BC - Mail plastics to you via certified
mail
BF - Mail plastics to you via FedEx
BP - Mail plastics to you via postal
express
BR - Mail plastics to you via registered
mail
BU - Send plastics to you via UPS® Next
Day Air Saver® shipment.
B1 - Mail plastics to you via first class
mail
CA - Mail plastics to cardholder via DHL*
CC - Mail plastics to cardholder via
certified mail
CF - Mail plastics to cardholder via FedEx
CP - Mail plastics to cardholder via
postal express
CR - Mail plastics to cardholder via
registered mail
CU - Send plastics to cardholder via UPS®
Next Day Air Saver®
shipment
C1 - Mail plastics to cardholder via first
class mail.
DU - Send plastics to cardholder via
UPS® Next Day Air® shipment.
XA - Mail plastics to cardholder for
Page 409
Parameter Description Type Required Length
/
Optional
Saturday delivery via Airborne
XF - Mail plastics to cardholder for
Saturday delivery via FedEx
XU - Send plastics to cardholder for
Saturday delivery via UPS® Next
Day Air® shipment.
ZA - Mail plastics to you for Saturday
delivery via Airborne
ZF - Mail plastics to you for Saturday
delivery via FedEx
blank - Do not expedite new plastics
ZU - Send plastics to you for Saturday
delivery via UPS® Next Day Air®
shipment.
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
SCNDSSN Secondary Social Security Number Alpha Optional 9
SCND_PLST_CT Count of plastics to be issued to the Fixed Optional 1
secondary cardholder. – Use for
If there is a value is in Number of separate
Plastics field of the Credit Union’s PCF entity
setting, this field must be blank. If a zero only
is entered, no plastics will be issued
SCND_PLST_TYPE_CD Type of plastic to be issued to secondary Fixed Optional 1
cardholder – Use for
Page 410
Parameter Description Type Required Length
/
Optional
separate
Valid Codes: entity
0 - Do not emboss plastics for the only
principal cardholder on this account
1 - Use the parameters in the Plastic
Products strategy for plastic type 1 to
emboss plastics on this account
2 - Use the parameters in the Plastic
Products strategy for plastic type 2 to
emboss plastics on this account
3 - Use the parameters in the Plastic
Products strategy for plastic type 3 to
emboss plastics on this account
4 - Use the parameters in the Plastic
Products strategy for plastic type 4 to
emboss plastics on this account
5 - Use the parameters in the Plastic
Products strategy for plastic type 5 to
emboss plastics on this account
6 - Do not emboss plastics or create
embossing records for this account
7 - Do not emboss plastics or create
embossing records for this account
blank - This field has no entry
SHAREACCT Share Account Alpha Optional Variable
up to 17
characters
SPCLFLGS Special Flags (6-8) Alpha Optional 3
This controls the setting of special flags 6,
7 and 8.
For example to set special flag 7 to
reflect an employee account:
SPCLFLGS=%20E%20
To set special flag 8 to create a Control
account (commercial accounts):
Page 411
Parameter Description Type Required Length
/
Optional
SPCLFLGS=%20%20C
STATE Address State Alpha Fixed 2
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1440&CLIENTID=9999&APPTYPE=A&CARDNUMBER=9999999999999999&
CRDTLIMTAMT=999999&PLSTEXPDT=MMYY&PLSTCT=X&PLSTTYPE=X&CRDTBURRPT=X
&CRDTBURSCOR=999&PRIMARYNAME=LASTNAME,FIRSTNAME&PRIMARYSSN=9999999
99&PRIDOB=YYYYMMDD&CRDTLIFEINS=X&
PRISLLT=X&MTHRMADN=XXXXXXXX&SCNDCHNAME=LASTNAME,FIRSTNAME&SCNDSSN
=999999999&ADDR1=XXXXXXXXXXXXXXXX&ADDR2=XXXXXXXXXXXXXX&CITY=XXXXXXXX
XX&STATE=XX&ZIP4=XXXXXXXXXX&HMPHONE=9999999999&BUSPHONE=9999999999
&CHECKINGID=XXXXXXXXXXXXXXXXX&CHRGDDA=X&XREFACCTNO=9999999999999999
&SHAREACCT=XXXXXXXXXXXXXXXXX&MISC1=XXXX&MISC2=XXXXX&MISC3=XXXXXXX&
MISC4=XXXXXXXXXX&SPCLFLGS=XXX&RUSHPLST=X&CRDTRPT=X&CRDTOVRD=XXX&CM
Page 412
PYID=XXXXXXXX&CMPYCNTRL=9999999999999999&ALTLNG=X&
ACCTERMS=X&OPENDT=YYYYMMDD
The following is a sample response when the account has been created successfully for
a single entity card program. The STATUS CODE tag contains a value of zero (0)
indicating success.
- <INVISION>
-<ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>4284279C-AA26-CD1C-7AF3-1232836EEB11</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1440</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
The following is a sample response when the account has been created successfully for
a separate entity card program. The STATUS CODE tag contains a value of zero (0)
indicating success.
<INVISION>
<ACCTXML>
<VALIDATION>
Page 413
<RESPONSE>0</RESPONSE>
<GUID>639D0DCE-3C11-19C5-4071-ACD579C46883</GUID>
</VALIDATION>
<V_OLCLASS>
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1440</ods:FUNCTIONID>
<ods:FUNCTIONRS>
<ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<COLLECTION>
<odsPscuTAG
NAME="CUSTEXTRID">C99999999999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CUSTROLEID">01</odsPscuTAG>
<odsPscuTAG NAME="CLNTCNTRCUSTID"> </odsPscuTAG>
<odsPscuTAG NAME="PLSTTYPECD">1</odsPscuTAG>
<odsPscuTAG NAME="PITYPECD">01</odsPscuTAG>
<odsPscuTAG NAME="RUSHPLSTCCD"> </odsPscuTAG>
<odsPscuTAG NAME="ACCTID">9999999999999999 </odsPscuTAG>
<odsPscuTAG NAME="PIID">9999999999999999 </odsPscuTAG>
<odsPscuTAG NAME="ACCTDUALITYCD">0</odsPscuTAG>
<odsPscuTAG NAME="PIPLSTCT">001</odsPscuTAG>
<odsPscuTAG NAME="MLMU">0</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG
NAME="CUSTEXTRID">C99999999999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CUSTROLEID">02</odsPscuTAG>
<odsPscuTAG NAME="CLNTCNTRCUSTID"> </odsPscuTAG>
<odsPscuTAG NAME="PLSTTYPECD">1</odsPscuTAG>
<odsPscuTAG NAME="PITYPECD">01</odsPscuTAG>
<odsPscuTAG NAME="RUSHPLSTCCD"> </odsPscuTAG>
<odsPscuTAG NAME="ACCTID">9999999999999999 </odsPscuTAG>
<odsPscuTAG NAME="PIID">9999999999999999 </odsPscuTAG>
<odsPscuTAG NAME="ACCTDUALITYCD">0</odsPscuTAG>
<odsPscuTAG NAME="PIPLSTCT">000</odsPscuTAG>
<odsPscuTAG NAME="MLMU">0</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
<ods:STATUS><ods:CODE>0</ods:CODE>
</ods:STATUS></ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 414
In the event of a failed account creation, the response will include a tag name
EXCEPTION that contains error information from the First Data system.
Page 415
8.2 New Generated Cardholder Account
The New Generated Cardholder Account request will create anew cardholder account
on the First Data system for single and separate entity credit unions. The account
number will be generated by the First Data system based on the System, Principal and
Agent IDs passed in the URL request and will be returned in the XML response. This
function emulates the NC, NCA and NG transactions in 3270 screens. Once the account
is created it is immediately available for authorizations.
For the creation of a separate entity account the optional parameter SEPARATE_ENTITY
must be included in the request with a value of “Y”.
Note, not all attributes included in the new account request will be reflected on the
account the same day the Data eXchange request is processed. The account does build
in real-time but some attributes, such as credit bureau report flag, may not appear until
next day. Full validation of the new account should be performed the day after the new
account is built.
Page 416
Parameter Description Type Required Length
/
Optional
R – Reserved for restricted use
Y – Terms were accepted
ADDR1 Address line 1 Alpha Required 26 for Visa
Use ‘%20’ for spaces 24 for MC
‘#’ signs are unacceptable
Valid Codes:
CF – Canadian French
EN – American English
SP – Latin American Spanish
APPTYPE Application Type Fixed value – Required 1
A
Valid Value:
A – Approved, has credit approval
BUSPHONE Business Phone Numeric Optional 10
CHECKINGID Checking Account Identifier Numeric Optional 17
CHRGDDA Automatic Payment Code Alpha Optional 1
Valid Codes:
J – Cardholder designated amount
(J or K) (payment
Page 417
Parameter Description Type Required Length
/
Optional
source=checking)
K – Cardholder designated
amount (J or K) (payment
source=savings)
N – Daily Current Balance Option
(N or O) (payment
source=checking)
O – Daily Current Balance Option
(N or O) (payment source =
savings)
0 – Automatic payment is not set
up for this account
1 – Unpaid Billed Minimum
Payment Due (1 or 5) (payment
source=checking)
2 – Full Statemented Balance or
Unpaid Billed Minimum Payment
Due (2 or 6) (payment source =
checking)
3 – Reserved for UK processors
4 – Full Statemented Balance (4 or
7) (payment source=checking)
5 – Unpaid Billed Minimum
Payment Due (1 or 5)(payment
source=savings)
6 – Full Statemented Balance or
Unpaid Billed Minimum Payment
Due (2 or 6) (payment
source=savings)
7 – Full Statemented Balance (4 or
7) (payment source=savings)
8 – Reserved for UK processors
Page 418
Parameter Description Type Required Length
/
Optional
(savings) depending on the
option, must be provided.
CITY Address City Alpha Required Variable up
Use ‘%20’ for spaces to 18
characters
CMPYID COMMERCIAL CARD ONLY! Alpha Required Variable up
Company ID for to 8
Commerci characters
al Card
CMPYCNTRL COMMERCIAL CARD ONLY! Alpha Optional 16
Company Control Number
Valid codes:
D - Delete account from credit
bureau files
Q - Account not reported
Z - Account not reported
1 - Individual
2 - Joint contractual liability
3 - Authorized user
5 - Co-maker
7 – Maker
CRDTBURSCOR Credit Score Numeric Optional 3
CRDTLIFEINS Credit Life Insurance Numeric Optional 1
CRDTLIMTAMT Credit Limit Amount Numeric Optional 13
Page 419
Parameter Description Type Required Length
/
Optional
Valid Codes:
EFC - Equifax Canada
EFX - Equifax
TRC - TransUnion Canada
TRU - TransUnion
TRW - Experian
CRDTRPT Credit Reporting Alpha Optional 1
Valid Codes:
N - No, do not send for more
information request for a credit
bureau report
Y - Yes, send a request for a credit
bureau report
blank - No, do not send a request
for a credit bureau report
HMPHONE Home Phone Numeric Optional 10
Page 420
Parameter Description Type Required Length
/
Optional
blank. If a zero is entered, no only
plastics will be issued
PLSTEXPDT Expiration date for the issued Numeric Optional 4
plastic(s).
Page 421
Parameter Description Type Required Length
/
Optional
Plastic Products strategy for
plastic type 5 to emboss plastics
on this account
6 - Do not emboss plastics or
create embossing records for this
account
7 - Do not emboss plastics or
create embossing records for this
account
blank - This field has no entry
PRIMARYNAME Primary cardholder Alpha Required 24
Valid format
LAST%20SUFFIX,FIRST%20MI
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
PRIMARYSSN Primary cardholder’s Social Numeric Optional 9
Security Number
PRIDOB Primary cardholder‘s Date of Birth Numeric Optional 8
Valid Codes:
C - Sir
F - Ms.
M - Mr.
U - No salutation printed
PRMR_PLST_CT Count of plastics to be issued to Fixed Optional 1
the primary cardholder. – Use for
Page 422
Parameter Description Type Required Length
/
Optional
If there is a value is in Number of separate
Plastics field of the Credit Union’s entity
PCF setting, this field must be only
blank. If a zero is entered, no
plastics will be issued
PRMR_PLST_TYPE Type of plastic to be issued to Fixed Optional 1
primary cardholder – Use for
separate
Valid Codes: entity
0 - Do not emboss plastics for the only
principal cardholder on this
account
1 - Use the parameters in the
Plastic Products strategy for
plastic type 1 to emboss plastics
on this account
2 - Use the parameters in the
Plastic Products strategy for
plastic type 2 to emboss plastics
on this account
3 - Use the parameters in the
Plastic Products strategy for
plastic type 3 to emboss plastics
on this account
4 - Use the parameters in the
Plastic Products strategy for
plastic type 4 to emboss plastics
on this account
5 - Use the parameters in the
Plastic Products strategy for
plastic type 5 to emboss plastics
on this account
6 - Do not emboss plastics or
create embossing records for this
account
Page 423
Parameter Description Type Required Length
/
Optional
7 - Do not emboss plastics or
create embossing records for this
account
blank - This field has no entry
ROUTINGNBR Routing Transit number Numeric Optional 17
RUSHPLST Rush Plastics Indicator Code Alpha Optional 2
Valid Codes:
AU - Send plastics to you via UPS®
Next Day Air® shipment
BA - Mail plastics to you via DHL*
BC - Mail plastics to you via
certified mail
BF - Mail plastics to you via FedEx
BP - Mail plastics to you via postal
express
BR - Mail plastics to you via
registered mail
BU - Send plastics to you via UPS®
Next Day Air Saver® shipment.
B1 - Mail plastics to you via first
class mail
CA - Mail plastics to cardholder
via DHL*
CC - Mail plastics to cardholder via
certified mail
CF - Mail plastics to cardholder via
FedEx
CP - Mail plastics to cardholder via
postal express
CR - Mail plastics to cardholder
via registered mail
CU - Send plastics to cardholder
via UPS® Next Day Air Saver®
shipment
Page 424
Parameter Description Type Required Length
/
Optional
C1 - Mail plastics to cardholder via
first class mail.
DU - Send plastics to cardholder
via UPS® Next Day Air® shipment.
XA - Mail plastics to cardholder
for Saturday delivery via Airborne
XF - Mail plastics to cardholder for
Saturday delivery via FedEx
XU - Send plastics to cardholder
for Saturday delivery via UPS®
Next
Day Air® shipment.
ZA - Mail plastics to you for
Saturday delivery via Airborne
ZF - Mail plastics to you for
Saturday delivery via FedEx
blank - Do not expedite new
plastics
ZU - Send plastics to you for
Saturday delivery via UPS® Next
Day Air® shipment.
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
SCNDSSN Secondary Social Security Number Alpha Optional 9
SCND_PLST_CT Count of plastics to be issued to Fixed Optional 1
Page 425
Parameter Description Type Required Length
/
Optional
the secondary cardholder. – Use for
If there is a value is in Number of separate
Plastics field of the Credit Union’s entity
PCF setting, this field must be only
blank. If a zero is entered, no
plastics will be issued
SCND_PLST_TYPE_CD Type of plastic to be issued to Fixed Optional 1
secondary cardholder – Use for
separate
Valid Codes: entity
0 - Do not emboss plastics for the only
principal cardholder on this
account
1 - Use the parameters in the
Plastic Products strategy for
plastic type 1 to emboss plastics
on this account
2 - Use the parameters in the
Plastic Products strategy for
plastic type 2 to emboss plastics
on this account
3 - Use the parameters in the
Plastic Products strategy for
plastic type 3 to emboss plastics
on this account
4 - Use the parameters in the
Plastic Products strategy for
plastic type 4 to emboss plastics
on this account
5 - Use the parameters in the
Plastic Products strategy for
plastic type 5 to emboss plastics
on this account
6 - Do not emboss plastics or
create embossing records for this
Page 426
Parameter Description Type Required Length
/
Optional
account
7 - Do not emboss plastics or
create embossing records for this
account
blank - This field has no entry
SEPARATE_ENTITY Indicates the request is for a Fixed Required 1
separate entity credit union. for
Valid Codes: separate
Y=Yes entity
SHAREACCT Share Account (aka Savings Numeric Optional Variable up
account) to 17 digits
SPCLFLGS Special Flags (6-8) Alpha Optional 3
This controls the setting of special
flags 6, 7 and 8.
For example to set special flag 7 to
reflect an employee account:
SPCLFLGS=%20E%20
To set special flag 8 to create a
Control account (commercial
accounts):
SPCLFLGS=%20%20C
STATE Address State Alpha Fixed 2
Page 427
Parameter Description Type Required Length
/
Optional
used when replacing an existing
account due to Lost/Stolen
statusing.
ZIP4 Zip Code Numeric Required 5 or 9
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1440&CLIENTID=9999&APPTYPE=A&SYSTEM=9999&PRIN=9999&AGENT=
9999&CRDTLIMTAMT=999999&PLSTEXPDT=MMYY&PLSTCT=X&PLSTTYPE=X&CRDTBUR
RPT=X&CRDTBURSCOR=999&PRIMARYNAME=LASTNAME,FIRSTNAME&PRIMARYSSN=99
9999999&PRIDOB=YYYYMMDD&CRDTLIFEINS=X&PRISLLT=X&MTHRMADN=XXXXXXXX&
SCNDCHNAME=LASTNAME,FIRSTNAME&SCNDSSN=999999999&ADDR1=XXXXXXXXXXXX
XXXX&ADDR2=XXXXXXXXXXXXXX&CITY=XXXXXXXXXX&STATE=XX&ZIP4=XXXXXXXXX&HM
PHONE=9999999999&BUSPHONE=9999999999&CHECKINGID=XXXXXXXXXXXXXXXXX&C
HRGDDA=X&XREFACCTNO=9999999999999999&SHAREACCT=XXXXXXXXXXXXXXXXX&MI
SC1=XXXX&MISC2=XXXXX&MISC3=XXXXXXX&MISC4=XXXXXXXXXX&SPCLFLGS=XXX&RUS
HPLST=X&CRDTRPT=X&CRDTOVRD=XXX&CMPYID=XXXXXXXX&CMPYCNTRL=999999999
9999999&ALTLNG=X&ACCTERMS=X&OPENDT=YYYYMMDD
The following is a sample response when an account for single entity processing has
been created successfully.
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>7B6B3E28-496B-FD1D-E6A8-80BD6DB9E3F4</GUID>
Page 428
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1440</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG
NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
The following is an example of the response when an account has been created
successfully for separate entity processing:
<INVISION>
<ACCTXML>
<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E0321EB0-CE1F-FCB6-B650-B5821277A19A</GUID>
</VALIDATION>
<V_OLCLASS>
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1440</ods:FUNCTIONID>
<ods:FUNCTIONRS>
<ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<COLLECTION>
Page 429
<odsPscuTAG NAME="CUSTEXTRID">C9999999999999999999999</
odsPscuTAG>
<odsPscuTAG NAME="CUSTROLEID">99</odsPscuTAG>
<odsPscuTAG NAME="CLNTCNTRCUSTID">
</odsPscuTAG>
<odsPscuTAG NAME="PLSTTYPECD">9</odsPscuTAG>
<odsPscuTAG NAME="PITYPECD">99</odsPscuTAG>
<odsPscuTAG NAME="RUSHPLSTCCD">CC</odsPscuTAG>
<odsPscuTAG NAME="ACCTID">9999999999999999 </odsPscuT
AG>
<odsPscuTAG NAME="PIID">999999999999999 </odsPscuTAG>
<odsPscuTAG NAME="ACCTDUALITYCD">9</odsPscuTAG>
<odsPscuTAG NAME="PIPLSTCT">999</odsPscuTAG>
<odsPscuTAG NAME="MLMU">9</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG NAME="CUSTEXTRID">
C9999999999999999999999</odsPscuTAG>
<odsPscuTAG NAME="CUSTROLEID">99</odsPscuTAG>
<odsPscuTAG NAME="CLNTCNTRCUSTID">
</odsPscuTAG>
<odsPscuTAG NAME="PLSTTYPECD">9</odsPscuTAG>
<odsPscuTAG NAME="PITYPECD">99</odsPscuTAG>
<odsPscuTAG NAME="RUSHPLSTCCD">CC</odsPscuTAG>
<odsPscuTAG NAME="ACCTID">9999999999999999 </odsPscuT
AG>
<odsPscuTAG NAME="PIID">9999999999999999 </odsPscuTAG
>
<odsPscuTAG NAME="ACCTDUALITYCD">9</odsPscuTAG>
<odsPscuTAG NAME="PIPLSTCT">999</odsPscuTAG>
<odsPscuTAG NAME="MLMU">9</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
Page 430
</INVISION>
In the event of a failed account creation, the response will include a tag name
EXCEPTION that contains error information from the First Data system.
Page 431
8.3 Declined ICS Application
The Declined ICS Application request will report a declined ICS application to the First
Data system. This function emulates the ICD transaction in 3270 environment(s).
Valid Value:
R – Declined, has credit
approval
BIN BIN value Numeric Required 6
for VISA
CITY Address City Alpha Required Variable up
to 14
Page 432
Parameter Description Type Required Length
/
Optional
Use ‘%20’ for spaces characters
HOMEPHONE Home Phone Number Numeric Required 10
PRIMARYNAME Primary account name Alpha Required Variable up
to 17
Valid format is characters
LAST%20SUFFIX,FIRST%20MI
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
PRIMARYSOC Primary SSN Numeric Required 9
PRIN Principle number Numeric Required 4
STATE Address State Alpha Required 2
SYSTEM System number Numeric Required 4
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
ZIP4 Address Zip Code Numeric Required 5 or 9
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1440&CLIENTID=9999&APPTYPE=R&SYSTEM=9999&PRIN=9999&PRIMAR
YNAME=LASTNAME,FIRSTNAME&PRIMARYSOC=999999999&ADDR1=XXXXXXXXXXXXXX
XX&ADDR2=XXXXXXXXXXXXXX&CITY=XXXXXXXXXX&STATE=XX&ZIP4=XXXXXXXXXX&HO
MEPHONE=9999999999
The following is a sample response when the account has been created successfully. The
STATUS CODE tag contains a value of zero (0) indicating success.
- <INVISION>
Page 433
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>35A663D4-1B4A-F7FA-7A16-7175DF84B7B4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1440</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
In the event of a failed account creation, the response will include a tag name
EXCEPTION that contains error information from the First Data system.
Page 434
8.4 Account Transfer
The Account Transfer function provides the ability to transfer accounts within the same
principal or across principals. Existing accounts must have at least one (1) monetary
value processed in order to combine existing accounts.
Valid Codes:
Page 435
Parameter Description Type Required Length
/
Optional
Blank – Option not used
Y – Perform authorizations against new
account
CARDNUMBER Old Presentation Instrument Identifier Numeric Required 16
CRDTLIMIT Credit Limit Amount Numeric Required Up to 13
Whole dollar amount for Type =
N
EXCLCUST Exclude cardholder Indicator; If you leave Alpha Required 1
this field blank, the System transfers
cardholder and presentation instrument
information from the “from” account to
the “to” account.
Valid Codes:
E - Exclude cardholder and presentation
instrument information from the account
transfer
Y
LETTERNO Letter Identifier; Edited for any Alpha Optional 4
combination of letters and numbers
NEWCARDNUMBER New Presentation Instrument Identifier Numeric Required 16
unless
TRNSTYPE
=N
NEWAGENT Agent for the new account Numeric Required 4
for Type N
NEWNAME Last name only including any suffix of the Alpha Required Up to 26
primary cardholder on the NEW account.
NEWPRIN Prin for the new account Numeric Required 4
for Type N
NEWSYS System for the new account Numeric Required 4
for Type N
OLDNAME Last name only including the suffix of the Alpha Required Up to 26
primary cardholder on the OLD account
PRDCPLST Produce New Plastic Indicator Alpha Optional 1
Page 436
Parameter Description Type Required Length
/
Optional
Valid Codes:
N - Do not produce a plastic
Y - Produce a plastic
PRIMARYNAME Old Principal cardholder Name Alpha Required 26
LAST NAME ONLY Including suffix!
RUSHPLST Rush Plastics Indicator Code Alpha Optional 2
Valid Codes:
AU - Send plastics to you via UPS® Next
Day Air® shipment
BA - Mail plastics to you via Airborne
BC - Mail plastics to you via certified mail
BF - Mail plastics to you via FedEx
BP - Mail plastics to you via postal
express
BR - Mail plastics to you via registered
mail
BU - Send plastics to you via UPS® Next
Day Air Saver® shipment.
B1 - Mail plastics to you via first class mail
CA - Mail plastics to cardholder via
Airborne
CC - Mail plastics to cardholder via
certified mail
CF - Mail plastics to cardholder via FedEx
CP - Mail plastics to cardholder via postal
express
CR - Mail plastics to cardholder via
registered mail
CU - Send plastics to cardholder via UPS®
Next Day Air Saver®
shipment
C1 - Mail plastics to cardholder via first
class mail.
DU - Send plastics to cardholder via UPS®
Page 437
Parameter Description Type Required Length
/
Optional
Next Day Air® shipment.
XA - Mail plastics to cardholder for
Saturday delivery via Airborne
XF - Mail plastics to cardholder for
Saturday delivery via FedEx
XU - Send plastics to cardholder for
Saturday delivery via UPS® Next
Day Air® shipment.
ZA - Mail plastics to you for Saturday
delivery via Airborne
ZF - Mail plastics to you for Saturday
delivery via FedEx
blank - Do not expedite new plastics
ZU - Send plastics to you for Saturday
delivery via UPS® Next Day Air®
shipment.
blank - Do not expedite new plastics
TRNSTYPE Account Transfer Type Code Alpha Required 1
Valid Codes:
B - Reallocate and combine two existing
accounts
C - Combine two existing accounts
N – Transfer to a new account
U – Separate Entity account transfer
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
Page 438
8.4.2 Sample URL and Response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&FUNCTIONID=143
8&REQUESTID=102&CARDNUMBER=9999999999999999&NEWCARDNUMBER=9999999
999999999&TRNSTYPE=X&PRIMARYNAME=TESTACCOUNT&NEWNAME=TESTACCOUNT
&OLDNAME=TESTACCOUNT&PRDCPLST=X&EXCLCUST=X&AUTHFROMNEW=X&CLIENTID
=9999
The following is an example of the XML response for a successful Account Transfer
Request. The STATUS CODE tag contains a value of zero (0) indicating success.
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>72C559AB-6318-7B38-5186-91B32AAA72D0</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1438</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu"/>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>1</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
In the event of a failed account creation, the response will include a tag name
EXCEPTION that contains error information from the First Data system.
Page 439
Sample response for request to transfer to a new account.
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>72C559AB-6318-7B38-5186-91B32AAA72D0</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1438</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="NEWACCOUNT">9999999999999999</odsPscuTAG>
<odsPs cuTAG NAME="CHNAME">TESTACCOUNT,
PRIMARY</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 440
8.5 Activate/Deactivate Card
The Activate Card request activates a card on the First Data System if the PCF activation
option (Customer User Flag ID in RF AM CA) is in use for the Credit Union. The
activation to the account is occurs in real-time. However, the card activation status
found in the USERFLAGS1THRU4 parameter of the 1402 function does not reflect the
activation until after overnight processing. Data eXchange function 1435 with
NONMONNBR=102 can be used to update the USERFLAGS1THRU4 in real-time.
VERIFICATIONCD=V
to deactivate
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
NOTE: In previous versions of this document, the RQID for this function was
ACTIVATEXML. Current implementations that use the RQID= ACTIVATEXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
Page 441
8.5.2 Sample URL and Response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1408&CLIENTID=9999&CARDNUMBER=9999999999999999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>603FD542-A09D-CD4D-E408-CA831CE1B30F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1408</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY" />
<odsPscuTAG NAME="SYSTEM">5356</odsPscuTAG>
<odsPscuTAG NAME="PRIN">0000</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">TESTACCOUNT,
PRIMARY</odsPscuTAG>
<odsPscuTAG NAME="AGENT">0000</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="ISALLOWEDACCESS">AUTO</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
Page 442
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 443
8.6 Order Replacement Card
The Order Replacement Card request provides the ability to order a replacement card
for the cardholder or an authorized user. This function will not work when there is an
external status on the account (Single Entity) or on the plastic (Separate Entity).
NOTE: There is the possibility that the replacement card will be mailed as active if the
expiration date is not updated prior to ordering the replacement card. The expiration
date can be changed using the Data eXchange function 1435 with NONMONNBR=14 and
PARAM1=new expiration date (MMYYY).
Valid Codes:
0 - Force emboss all cards on
the account
1 - Primary Cardholder only
2 - Secondary Cardholder only
3 - Authorized User – see below
EMBOSSNAME Name to emboss on the card Alpha Required 26 for
when Visa
Valid format: EMBOSSCODE 24 for MC
Page 444
Parameter Description Type Required / Length
Optional
LAST%20SUFFIX,FIRST%20MI =3
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
REPLACEMENTFEE Replacement Fee Indicator Alpha Optional 1
Valid Codes:
Y – Yes, charge replacement fee
defined in the PCF setting Card
Replacement Fee of the
Miscellaneous Charges section (CP
IO MC). If the PCF setting is zero,
Yes is an invalid code.
Page 445
Parameter Description Type Required / Length
Optional
BR – Registered Mail
BP – Postal Express
BF – Federal Express
ZF – Federal Express Saturday
delivery
BA – DHL
ZA – DHL Saturday delivery
Valid Codes:
0 - Regular - Order replacement
card with regular delivery
1 - Plastics Same Day - Order
before 1:00PM CT to guarantee
tomorrow shipment. Otherwise,
receive in 3 business days
2 - Rush order - Guarantee
shipment in 3 business days
UPDATE 1 Fixed Required 1
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
NOTE: In previous versions of this document, the RQID for this function was
ORDERCARDXML. Current implementations that use the RQID= ORDERCARDXML will
continue to perform properly. It is requested that future implementations of this
function use the RQID=ACCTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1409&CARDNUMBER=9999999999999999&CLIENTID=9999&EMBOSSCOD
E=9&EMBOSSNAME=LASTNAME,FIRSTNAME%20MI&RUSHMAILIND=XX&REPLACEMENT
FEE=X&SHIPTYPE=9&UPDATE=1&
Page 446
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1409</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="CHSECONDARY">LASTTWO,FIRST</odsPscuTAG>
<odsPscuTAG NAME="CHADDR1">STREET ADDRESS LINE
1</odsPscuTAG>
<odsPscuTAG NAME="CHADDR2">STREET ADDRESS LINE
2</odsPscuTAG>
<odsPscuTAG NAME="CHCITY">CITYNAME</odsPscuTAG>
<odsPscuTAG NAME="CHZIPCODE">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="CHSTATE">ST</odsPscuTAG>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 447
</ACCTXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 448
OdsPscu TAG NAME Description Type Length First
Data
Screen
CONFIRMATION Indicates the request was Alpha 10 NA
successful
Page 449
8.7 Order PIN Letter
The Order PIN Letter request will order a letter with the established PIN in place on the
cardholder’s account in the First Data system. This request does not generate a new PIN,
nor does it allow a cardholder-selected PIN to be set in the First Data System. The PIN
letter generated as a result of this request will be sent to the address on file for the
cardholder. The letter is typically mailed within one business day. The First Data System
will only process this request when the cardholder’s external status code is blank.
This function only works for Single Entity processors. Separate Entity processors will
need to use function 1435 with PI NONMON 42.
NOTE: In previous versions of this document, the RQID for this function was
ORDERPINXML. Current implementations that use the RQID=ORDERPINXML will
continue to perform properly. It is requested that future implementations of this
function use the RQID=PINXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1416&CARDNUMBER=9999999999999999&CLIENTID=9999
Page 450
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>5EDC5818-C0F6-9165-E270-32306BEE5EE6</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1416</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CARDTYPE">Visa Gold</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="SPAID">9999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST MI</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
MI</odsPscuTAG>
<odsPscuTAG NAME="CHADDR1">ADDRESS LINE 1</odsPscuTAG>
<odsPscuTAG NAME="CHADDR2">ADDRESS LINE 2</odsPscuTAG>
<odsPscuTAG NAME="CHCITY">CITY NAME</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="ISALLOWEDACCESS">0</ods
PscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 451
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 452
OdsPscu TAG NAME Description Type Length First
Data
Screen
CSR
ISALLOWEDACCESS Indicates whether the cardholder is Numeric 1
allowed access to Order the Letter.
Valid Codes:
0 – Yes
1 – No
PRIN Principal Number Numeric 4 BS6
SPAID PSCU Internal Designation for the Numeric 5
System, Prin and Agent values
SYSTEM System Number Numeric 4 BS6
Page 453
8.8 External Status
The External Status request provides the ability to change the external status code
currently in place on a cardholder’s account in the First Data System. This change is
made immediately and may impact the cardholder’s ability to use their credit card.
Using this function to change the external status to “L” will not trigger the events to
transfer the account and issue a new plastic.
If this function is being used to allow the card holder to block / unblock the credit card
be sure to set an indicator in a MISC field to indicate that the card holder turned off the
card. The card holder should only be allowed to turn the card back on when the card
holder turned the card off.
This transaction is only relevant for Single Entity clients. The status of a plastic belonging
to a Separate Entity account can be set using function 1435 to execute PI NONMON 782
with sub transaction code 16.
Valid Code:
CH – Closed by Cardholder
Page 454
Parameter Description Type Required / Length
Optional
CU – Closed by Credit Union
EXTERNALSTATUS External Status Code Alpha Required 1
L and U statuses should not
be processed with this
function. Instead use
function 1452.
Valid Codes:
A* - Authorization
Prohibited
B - Bankrupt
C - Closed
E - Revoked
F - Frozen
I - Interest Accrual Prohibited
Blank - Normal
MEMO Memo text Alpha Optional Up to
This memo will appear on 63
the account after overnight
processing.
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
NOTE: In previous versions of this document, the RQID for this function was
STATUSXML. Current implementations that use the RQID= STATUSXML will continue to
perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
*An external status of A will not block recurring payments from the credit card such as
monthly Netflix memberships.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1425&MEMO= Escaped%20Memo%20Text%20to%20be%20entered
&CARDNUMBER=9999999999999999&CLIENTID=9999&EXTERNALSTATUS=C&CLREASO
NCODE=CU
Page 455
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1425</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="ISALLOWEDACCESS">AUTO</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 456
8.8.3 Tag and Property Reference
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 457
8.9 Authorization and Transaction Posting
If the cardholder is registered in a PSCU alerts solution, this feature will NOT work as
expected. The authorization will be routed to the alert engine for decisioning yet the
response to the Data eXchange function will indicate the authorization was not
successful. Once the authorization has passed through the alert engine if approved it
will impact available credit but no transaction will post to impact the balance.
This function emulates the 3270 AR transaction. If you are experiencing difficulties
implementing this feature, it is helpful to test the parameters included in the request
using the AR transaction.
NOTE: The First Data system that support the Authorization and Transaction Posting
function (1448) enters system maintenance at 6pm central every day. The duration of
the maintenance varies but appears to be between 15 and 30 minutes. If the
Authorization and Transaction Posting request is executed during this time the
authorization will succeed and the posting of the transaction will fail. The cardholder
account will be negatively impacted because the success of the authorization will adjust
the available credit by the amount request. The authorization will not drop off the
account until weekly maintenance is performed on the First Data platform.
There is no means within the Data eXchange API to compensate for this error at this
time. A future enhancement is planned to add a DX function to remove an
Authorization.
When testing this functionality in Data eXchange Pilot, it may be necessary to suspend
the fraud strategy on the test account for the authorization to succeed.
Page 458
The authorization requested through this Data eXchange call will bypass all
authorization validation such as a limit on the percentage of credit available for cash
advance. It is possible to perform these validations in advance of issueing this request
using information returned from other Data eXchange calls.
NOTE: The Authorization response will be FALSE if the account is registered in Alerts.
The Function ID for this request is 1448.
Page 459
Parameter Description Type Required / Length
Optional
tran code and sys/prin of the
cardnumber
TRANCODE Transaction Type Code Numeric Required 3
Value Codes:
253 - Merchandise
254 – Cash Advance
280 – Credit Adjustment
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1448&CLIENTID=9999&CARDNUMBER=XXXXXXXXXXXXXXXX&CHECK_AVAI
L=Y&AMOUNT=99900&MERCHANT=XXXXXXXXXXXXXXX&EXP_DT=MMYY&TRANCODE=X
XX&DESCRIPTION=TEXT
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1448</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="AR_A_STAT">CMPLT</odsPscuTAG>
<odsPscuTAG NAME="AR_B_MSG_NMBR">1234</odsPscuTAG>
Page 460
<odsPscuTAG NAME="AR_C_SEVERITY">X</odsPscuTAG>
<odsPscuTAG NAME="AR_D_REF_NMBR">99</odsPscuTAG>
<odsPscuTAG NAME="AR_E_ACTION_CODE">X</odsPscuTAG>
<odsPscuTAG NAME="AR_F_AUTH_NMBR">1234</odsPscuTAG>
<odsPscuTAG NAME="AR_H_ADD_ACTION_IND">X</odsPscuTAG>
<odsPscuTAG NAME="AR_I_TRANSFER_OPT">X</odsPscuTAG>
<odsPscuTAG NAME="AR_J_MSG_TEXT">This is a message</odsPscuTAG>
<odsPscuTAG NAME="AUTHORIZATION">PASSED</odsPscuTAG>
<odsPscuTAG NAME="TRANS_POSTED">TRUE</odsPscuTAG>
<odsPscuTAG NAME="CREDIT_AVAIL">TRUE</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Valid codes:
CMPLT – successful completion
ERROR – failed to complete
AR_B_MSG_NMBR System assigned identifier of any error Alpha Variable NA
message numeric
AR_C_SEVERITY Identifier of the severity of the error Alpha Variable NA
message numeric
AR_D_REF_NMBR First Data Use Only Numeric Variable NA
AR_E_ACTION_CODE Code representing the action the Alpha 2 NA
System will take on this account. See numeric
Page 461
OdsPscu TAG NAME Description Type Length First
Data
Screen
section 8.9.4 for descriptions
AR_F_AUTH_NMBR Authorization code assigned by the Alpha Variable NA
issuer numeric
AR_H_ADD_ACTION_IND Code identifying supplemental Alpha 2 NA
information related to numeric
@AR_E_ACTION_CODE. See section
8.9.4 for description.
AR_I_TRANSFER_OPT Code representing the reason for Alpha NA
transferring an authorization call numeric
AR_J_MSG_TEXT Message text-message indicating the Alpha Variable NA
nature of the error
AUTHORIZATION Code representing results of the Alpha 6 NA
authorization request
Valid responses:
PASSED – Authorization passed
FAILED – Authorization failed, and
transaction was not executed
CREDIT_AVAIL Results of the check for available credit Alpha 4/5 NA
TRUE – Credit available
FALSE – Credit not available
NOT CHECKED – Credit Limit was not
checked
If CHECK_AVAIL=Y and there is not
enough available credit for the amount
requested, this will be the only tag in
the response and will contain a value of
FALSE.
TRANS_POSTED Indicates whether or not the transaction Alpha 4/5
successfully posted.
TRUE – Transaction posted
FALSE – Transaction did not post
The following error codes will provide insight into why an authorization failed.
Page 462
AR_E_ACTION_CODE
AR_E_ACTION_CODE Description
00 Approve
01 Reject
02 Decline
03 Internal Delay
04 External Delay – Description will include
the following “* AUTHORIZATION
REQUEST SENT TO * BAS0 *”. This
indicates the MCC is incorrect for the
merchant number in the request. The
merchant number for the request must
have an MCC of 0009 OR the description
will include “"* AUTHORIZATION REQUEST
SENT TO * CP *” indicating the account
participates in an alert solution and the alert
platform must be checked for approval
05 External Delay Extension
06 Aborted Merchant Call
Many of the following error codes only apply to authorizations where the plastic is
present and has been swiped.
AR_H_ADD_ACTION_IND Description
00 No additional action specified
01 Authorization by expansion
02 Get new address
03 Get positive identification
04 Call me
05 Pick up card
06 Invalid card number
07 Invalid merchant number
08 Invalid amount
09 Merchant not on file
Page 463
AR_H_ADD_ACTION_IND Description
0A Non-FDR cardholder and merchant
0B Processor record not found
0C Invalid merchant assessment code
0D Closed merchant
0E Invalid expiration date
0F Invalid mail order flag
10 Over single authorization limit
11 Over cash advance single limit
12 Under cash advance minimum
13 Overlimit
14 File error
15 Cardholder record not found
16 Excessing transactions
17 Over cash Advance total limit
18 Use external status as reason
19 Use external status as reason
1A Invalid ETC (Electronic Ticket Capture)
transaction type
1B Not ETC merchant
1C Ask for transaction type
1D Only ETC transaction type 4 valid
1E Cardholder invalid for merchant
1F Attala box down
20 Aborted call
21 VIP Status
22 Transmit name BASE/INAS
23 Center closed
24 Card number on negative file
25 Communication line down
26 Bad read CVV
27 Bad stripe CVV
28 COV – MCC/CITY/ZIP
29 Invalid PINpoint phone number
2A Merchant on wrong system
2B Cardholder on wrong system
2C Over daily spending limit
Page 464
AR_H_ADD_ACTION_IND Description
2D BASE response – below minimum
2E Invalid PIN number
2F PIN service unavailable
30 Excessive PIN transactions
31 BASE I System error
32 Card usaer exceeded maximum
33 Rejected PIN
34 Authorization approval of partial amount
35 Rejected PIN for invalid block format
36 Rejected for invalid encrypted PIN
37 INAS – invalid ATM terminal identification
38 Invalid transaction type
39 Function unavailable
3A Referral
3B Have merchant do CALL ME
3C Display optional data only
3D ETC files disabled
3E Manual decline
3F Exceeds commercial card spending limit
40 Commercial card – company overlimite
41 Diversion account delinquent
42 INAS manual reject – Invalid PIN
43 Diversion account overlimit
44 Diversion account delinquent and
overlimit
45 Diversion account exceeds spending limit
46 Relationship Processing service –
overlimit/family level
47 Relationship Processing service – family
not active
48 Diversion account
49 Invalid CVV2/CVC2 value entered
4A Name mismatch track one
4B Verify order
4C Payment reversal does not match to
payment
Page 465
AR_H_ADD_ACTION_IND Description
4D ETC Plus credit item gap > 200
4E Invalid loan officer identification
4F Duplicate authorization
50 Not signed
51 Authorization System malfunction
52 Invalid prefix for DES PIN
53 Message format problem
54 Decline reason set
55 Service not available
56 Over merchandise total limit
57 Display name meets counterfeit
parameters
58 On Combined Warning Bulletin flag was
set
59 Invalid SE number – AMEX
5A New/reissue declined
5B New/reissue get positive identification
5C Issuer center down
5D Invalid department code
5E ETC retry code
5F Decline ‘Y’ authorization flag
60 No matching detail ETC void/reversal
61 Lost card
62 Stolen card
63 Stop payment on check
64 Unable to authorize
65 Vendor not on company card vendor list
66 ETC – invalid batch
67 ETC – batch has reached item limit
68 Over JCB limit-transfer to Jesta network
69 Invalid service restriction code
6A Invalid CVV value
6B Rejected CVV
6C Invalid ticket terms
6D Consecutive authorizations over PCF cash
limit
Page 466
AR_H_ADD_ACTION_IND Description
6E Authorization prior to valid date
6F Issuer not permitted ATM inquiries
70 COV – HIGH/LOW
71 No match on preapproved authorization
72 Excessive transactions, get positive
identification
73 Excessive PIN attempts, get positive
identification
74 Card verification declined
75 Card verification, get positive
identification
76 Do not honor
77 Insufficient funds
78 Account closed
79 Card statused severity 1
7A Card statused severity 4
7B Card statused severity 4
7C Account statused
7D Less than minimum amount required
7E Card statused severity 2
7F Card statused severity 5
80 Re-enter transaction active
81 File temporarily unavailable
82 Card expired on Master file
83 Mismatched expiration date
84 Decline for NRI (not received as issued)
85 NRI get positive identification
86 Decline counterfeit – typically indicating
the expiration date in the request does
not match the expiration date in the
request.
87 Counterfeit get positive identification
88 Decline kiting
89 Kiting get positive identification
8A Decline lost/stolen
8B Lost/stolen get positive identification
Page 467
AR_H_ADD_ACTION_IND Description
8C Invalid item count
8D Invalid type change
8E Always Refer Flag set
8F Chip card authentication failure
90 Invalid fleet ID
91 Invalid fleet driver ID
92 Invalid fleet vehicle ID
93 Force standin at Association (Visa/MC)
94 Rejected 3D secure CAVV value
95 Invalid 3D secure CAVV value
96 Invlaid PI external status
97 PI not on file
98 Ticket terms not active
99 Invalid ticket terms amount
9A Invalid MC UCAF value
9B No match found on ‘Q’ request
9C Declined stop recurring payment
9D Invalid claim number
9E Reserved for restricted use
9F Reserved for restricted use
A0 Reserved for restricted use
A1 Reserved for restricted use
A2 Reserved for restricted use
A3 Client-defined decline reason code
A4 Reserved for healthcare processors
A5 Excessive transactions – PI
A6 Account day hour restricted
A7 ID day hour restricted
A8 Reserved for healthcare processors
A9 Reserved for healthcare processors
AA Chip record not found
AB Invalid ARQC
AC Check not activated
AD Real time decisioning decline
Page 468
AR_J_MSG_TEXT Decline Message
AR_J_MSG_TEXT Description
* AUTHORIZATION REQUEST The Merchant Category Code (MCC) of
SENT TO * BAS0 *
the Merchant Number used in the request
is greater than 0999. Thus, the
authorization has been sent to Visa for
approval and an immediate response was
not available.
Page 469
8.10 Submit Disputes
The functions described below for submitting a dispute for processing. Do not use this
process to submit transactions being disputed due to a Lost card. Those transactions are
submitted in the Lost function 1452 Memo Line 1, 2 & text fields.
The Disputes Reason Codes function will return back the reason codes and descriptions
applicable for the card type – Visa or MasterCard. The card type will be determined in
the decode process that is executed when the request is received.
The Function ID for this request is 1464.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1464&CARDNUMBER=9999999999999999&CLIENTID=9999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
Page 470
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1464</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="REASONCODE">XXX</odsPscuTAG>
<odsPscuTAG
NAME="REASONDESCRIPTION">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</o
dsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 471
OdsPscu TAG NAME Description Type Length First Data
Screen
REASONCODE Reason Code Numeric 3 NA
REASONDESCRIPTION Description of the reason code Alpha 50 NA
The Submit Dispute function will submit the necessary data to PSCUs Disputes team for
processing.
Page 472
Parameter Description Type Required / Length
Optional
Format:
YYMMDD
REASONCODE Dispute reason code Numeric Required 3-6
REASONDESCRIPTION Text description of reason for dispute Alpha Required 50
TRANAMT Amount of the transaction in dispute Numeric Required 60
Format:
99999999.99
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1458&CARDNUMBER=9999999999999999&CLIENTID=9999&CHNAME=TE
ST,%20ACCOUNT&HOMEPHONE=9999999999&[email protected]&MERCH
NAME=XXXXXXXXXXXXXXXXXXXX&TRANAMT=99999.99&POSTDATE=YYMMDD&EXPNRF
RNNR=XXXXXXXXXXXXXXXXX&FULLPARTIAL=X&REASONCODE=999&REASONDESCRIPTI
ON=CCCCCCCCCCCCCCCCCC&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1458</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 473
</ACCTXML>
</INVISION>
Page 474
8.11 Lost
The Lost Stolen request processes an account that is being reported Lost or Stolen. This
function emulates the SL transactions in 3270 screens.
It is highly recommended that the consuming application ask the cardholder in the
workflow if the card is still in their possession. This assists the PSCU Fraud team in cases
where a card has been counterfeited. This information once captured should be
included in the MEMO_LINE_TX_1 field.
Page 475
Parameter Description Type Required Length
/
Optional
cash advances
C - Allow expedited cash
advances
P - Allow expedited plastics
ADDR_IN Code representing whether the Alpha Optional 1
address is valid.
Valid codes:
N – No
Y – Yes
Blank - Yes
AREA_LOST_CD Code representing where the Alpha Required 2
plastic was lost or stolen
The value of this field is the
state abbreviation.
BSNS_PHON_ID Business phone Numeric Optional 10
CRDS_ISSD_CT Count of presentation Numeric Required Up to 2
instruments issued to the
cardholder account
CRDS_LOST_CT Number of cards lost Numeric Required Up to 2
EXPD_ACCT_XFER_IN Indicator designating whether Alpha Optional 1
an expedited account transfer is
allowed
Valid values:
N - An expedited account
transfer is not allowed
Y - An expedited account
transfer is allowed
EXPN_DT Card expiration date Numeric Optional 4
FORMAT: MMYY
EXTR_STTS_CD External Status Code Alpha Required 1
Valid Code:
L - Lost
FRAD_AREA_CD Area lost code Optional 2
Refer to Appendix M
Page 476
Parameter Description Type Required Length
/
Optional
Enter region code with a
leading zero
FRAD_INCS_ID Fraud investigator identifier Alpha Optional 2
Page 477
Parameter Description Type Required Length
/
Optional
Merchant name, amount, date
MEMO_LINE_2_TX Memo line 2 text Alpha Optional 75
Can be used to include Numeric
fraudulent transactions –
Merchant name, amount, date
MEMO_LINE_3_TX Memo line 3 text Alpha Optional 70
Can be used to include Numeric
fraudulent transactions –
Merchant name, amount, date
Page 478
Parameter Description Type Required Length
/
Optional
N - No fraudulent activity is
suspected.
Y - The cardholder reports that
there are possible fraudulent
charges on
the lost/stolen plastic.
Valid Codes:
AU - Send plastics to you via
UPS® Next Day Air® shipment
BA - Mail plastics to you via DHL*
BC - Mail plastics to you via
certified mail
BF - Mail plastics to you via FedEx
BP - Mail plastics to you via postal
express
BR - Mail plastics to you via
registered mail
BU - Send plastics to you via
UPS® Next Day Air Saver®
shipment.
B1 - Mail plastics to you via first
class mail
CA - Mail plastics to cardholder via
DHL*
CC - Mail plastics to cardholder via
certified mail
CF - Mail plastics to cardholder via
FedEx
Page 479
Parameter Description Type Required Length
/
Optional
CP - Mail plastics to cardholder via
postal express
CR - Mail plastics to cardholder via
registered mail
CU - Send plastics to cardholder
via UPS® Next Day Air Saver®
shipment
C1 - Mail plastics to cardholder via
first class mail.
DU - Send plastics to cardholder
via UPS® Next Day Air® shipment.
XA - Mail plastics to cardholder for
Saturday delivery via Airborne
XF - Mail plastics to cardholder for
Saturday delivery via FedEx
XU - Send plastics to cardholder for
Saturday delivery via UPS® Next
Day Air® shipment.
ZA - Mail plastics to you for
Saturday delivery via Airborne
ZF - Mail plastics to you for
Saturday delivery via FedEx
blank - Do not expedite new
plastics
ZU - Send plastics to you for
Saturday delivery via UPS® Next
Day Air® shipment.
Page 480
Parameter Description Type Required Length
/
Optional
for MasterCard.
993 - Account remains on the
Visa exception file for 30 days
with a response code of 01.
994 - Account remains on the
Visa exception file for 30 days
with a response code of 05.
995 - Account remains on the
Visa exception file for 60 days
with a response code of 01.
996 - Account remains on the
Visa exception file for 60 days
with a response code of 05.
997 - Account remains on the
Visa exception file for 90 days
with a response code of 01.
998 - Account remains on the
Visa exception file for 90 days
with a response code of 05.
999 - Account remains on the
respective MasterCard or Visa
file until the plastic expires. This
applies to response codes 04,
07, 41, and 43 for Visa, and C, F,
O, and X for MasterCard.
WIFE_MADN_NM Wife’s maiden name Alpha Optional 10
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1452&CLIENTID=9999&CARDNUMBER=9999999999999999&AREA_LOST_
CD=XX&CRDS_ISSD_CT=9&CRDS_LOST_CT=9&EXPN_DT=MMYY&EXTR_STTS_CD=X&FRA
Page 481
D_TYPE_CD=99&LOSS_LCTN_CD=9&LOST_STLN_DT=MMDDYY&PIN_LOST_IN=X&PSSB_
FRAD_ACTY_CD=X&WB_CD=999
The following is a sample response when the account has been created successfully.
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>7B6B3E28-496B-FD1D-E6A8-80BD6DB9E3F4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1452</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG
NAME="NEW_ACCOUNT_NUMBER">9999999999999999</od
sPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 482
8.11.3 Tag and Property Reference
The response to a new account request for separate entity will be different than that of
a single entity request. For each cardholder provided in the request a collection of data
will be returned with the following parameters.
Page 483
8.12 Instant Issue EMV/Contactless Omaha
There are two methods for EMV Omaha Instant Issue: 1) request the chip row data from
FD and 2) push the chip row data to FD. In the first method, functions 1730 and 1735
are used. In the second method, functions 1726 and 1727 are used. In either scenario
function 1444 and 1445 are used.
The functions 1720 and 1735 are the same function. The IDs are different to distinguish
between Credit and Debit for reporting purposes. These functions will create the new
account and set the PIN information.
When implementing an instant issue solution for credit cards that are processed as
Separate Entity the PIID value must be used for the CARDNUMBER parameters in the
instant issue functions.
This function combines the New Cardholder Account request with the two required PIN
requests.
Page 484
Parameter Description Type Required Length
/
Optional
Y – Terms were accepted
Blank
ADDR1 Address line 1 Alpha Required 26 for
Use ‘%20’ for spaces Visa
24 for MC
Checks for 1 of the following:
A house number and a street name
(must have both)
Post office box number
Numeric rural route number
Valid Codes:
CF – Canadian French
EN – American English
SP – Latin American Spanish
APPTYPE Application Type Fixed Required 1
Valid Code:
A – Approved, has credit available
BUSPHONE Business Phone Numeric Optional 10
CARDNUMBER Cardnumber for the new account. Numeric Required 16
Checks for valid or duplicate account
number structure
CHECKINGID Demand Deposit Identifier - Checking Numeric Optional 17
account number
CHRGDDA Automatic Payment Code Alpha Optional 1
Valid Codes:
Page 485
Parameter Description Type Required Length
/
Optional
J – cardholder designated amount (J or K)
(payment source=checking)
K – cardholder designated amount (J or
K) (payment source=savings)
N – Daily Current Balance Option (N or O)
(payment source=checking)
O – Daily Current Balance Option (N or O)
(payment source = savings)
0 – Automatic payment is not set up for
this account
1 – Unpaid Billed Minimum Payment Due
(1 or 5) (payment source=checking)
2 – Full Statemented Balance or Unpaid
Billed Minimum Payment Due (2 or 6)
(payment source = checking)
3 – Reserved for UK processors
4 – Full Statemented Balance (4 or 7)
(payment source=checking)
5 – Unpaid Billed Minimum Payment Due
(1 or 5)(payment source=savings)
6 – Full Statemented Balance or Unpaid
Billed Minimum Payment Due (2 or 6)
(payment source=savings)
7 – Full Statemented Balance (4 or 7)
(payment source=savings)
8 – Reserved for UK processors
CITY Address City Alpha Required Variable
Use ‘%20’ for spaces up to 18
character
s
CMPYID COMMERCIAL CARD ONLY! Alpha Required Variable
Company ID for up to 8
Commerci character
al Card s
CMPYCNTRL COMMERCIAL CARD ONLY! Alpha Optional 16
Page 486
Parameter Description Type Required Length
/
Optional
Company Control Number
Valid codes:
D - Delete account from credit bureau
files
Q - Account not reported
Z - Account not reported
0 - Undesignated
1 - Individual
2 - Joint contractual liability
3 - Authorized user
5 - Co-maker
7 – Maker
CRDTBURSCOR Credit Bureau Score Numeric Optional 3
CRDTLIFEINS Credit Life Insurance Numeric Optional 1
CRDTLIMTAMT Credit Limit Amount Numeric Optional 13
Valid Codes:
EFC - Equifax Canada
EFX - Equifax
TRC - TransUnion Canada
TRU - TransUnion
TRW - Experian
CRDTRPT Credit Reporting Alpha Optional 1
Valid Codes:
N - No, do not send for more information
request for a credit bureau report
Page 487
Parameter Description Type Required Length
/
Optional
Y - Yes, send a request for a credit bureau
report
blank - No, do not send a request for a
credit bureau report
HMPHONE Home Phone Numeric Optional 10
Valid Codes:
0001 – Primary
0002 – Secondary
MISC1 Misc field 1 Alpha Optional 4
MISC2 Misc field 2 Alpha Optional 5
MISC3 Misc field 3 Alpha Optional 7
MISC4 Misc field 4 Alpha Optional 10
MTHRMADN Mother’s Maiden Name Alpha Optional 8
OPENDT Account Open Date Numeric Optional 8
Valid format is CCYYMMDD
PIN_VER_NBR PIN Verification Number Numeric Required 5
Format:
‘1’ followed by the four digit PIN
i.e. if the PIN is 9876 the
PIN_VER_NBR=19876
PLSTCT Count of plastics to be issued Numeric Optional 1
If there is a value is in Number of Plastics
field of the Credit Union’s PCF setting,
this field must be blank. If a zero is
entered, no plastics will be issued
PLSTEXPDT Expiration date for the issued plastic(s). Numeric Optional 4
Page 488
Parameter Description Type Required Length
/
Optional
Checked for valid month and year gather
than or equal to current date; First Data
also accepts spaces, all nines, or zeros
PLSTTYPE Type of plastic to be issued to primary Numeric Optional 1
cardholder
Valid Codes:
0 - Do not emboss plastics for the
principal cardholder on this account
1 - Use the parameters in the Plastic
Products strategy for plastic type 1 to
emboss plastics on this account
2 - Use the parameters in the Plastic
Products strategy for plastic type 2 to
emboss plastics on this account
3 - Use the parameters in the Plastic
Products strategy for plastic type 3 to
emboss plastics on this account
4 - Use the parameters in the Plastic
Products strategy for plastic type 4 to
emboss plastics on this account
5 - Use the parameters in the Plastic
Products strategy for plastic type 5 to
emboss plastics on this account
6 - Do not emboss plastics or create
embossing records for this account
7 - Do not emboss plastics or create
embossing records for this account
blank - This field has no entry
PRIMARYNAME Primary cardholder Alpha Required 26 for Visa
24 for MC
Valid format
Page 489
Parameter Description Type Required Length
/
Optional
LAST%20SUFFIX,FIRST%20MI
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
PRIMARYSSN Primary cardholder’s Social Security Numeric Optional 9
Number
PRIDOB Primary cardholder’s Date of Birth Numeric Optional 8
Valid Codes:
C - Sir
F - Ms.
M - Mr.
U - No salutation printed
ROLE_CODE Code determining which Role the PIN Numeric Required 2
belongs to.
Valid Codes:
01 – Primary
02 – Secondary
RUSHPLST Rush Plastics Indicator Code Alpha Optional 2
Valid Codes:
BA - Mail plastics to you via Airborne
BC - Mail plastics to you via certified mail
BD - Reserved for future use
BF - Mail plastics to you via FedEx
BP - Mail plastics to you via postal
express
BR - Mail plastics to you via registered
Page 490
Parameter Description Type Required Length
/
Optional
mail
B1 - Mail plastics to you via first class mail
CA - Mail plastics to cardholder via
Airborne
CC - Mail plastics to cardholder via
certified mail
CD - Reserved for future use
CF - Mail plastics to cardholder via FedEx
CP - Mail plastics to cardholder via postal
express
CR - Mail plastics to cardholder via
registered mail
C1 - Mail plastics to cardholder via first
class mail.
XA - Mail plastics to cardholder for
Saturday delivery via Airborne
XD - Reserved for future use
XF - Mail plastics to cardholder for
Saturday delivery via FedEx
ZA - Mail plastics to you for Saturday
delivery via Airborne
ZD - Reserved for future use
ZF - Mail plastics to you for Saturday
delivery via FedEx
blank - Do not expedite new plastics
SCNDCHNAME Secondary Cardholder Name Alpha Optional 26 for Visa
24 for MC
Valid format is
LAST%20SUFFIX,FIRST%20MI
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
SCNDSSN Secondary Social Security Number Alpha Optional 9
Page 491
Parameter Description Type Required Length
/
Optional
SEC_CODE PIN offset value Numeric Required 6
If using an
offset of
less than
6 digits,
pad the
end with
trailing
0’s.
SHAREACCT Share Account Alpha Optional Variable
up to 17
characters
SPCLFLGS Special Flags Alpha Optional 3
STATE Address State Alpha Fixed 2
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ACCTXML.
Page 492
8.12.1.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1720&CLIENTID=9999&APPTYPE=A&CARDNUMBER=9999999999999999&
CRDTLIMTAMT=999999&PLSTEXPDT=MMYY&PLSTCT=X&PLSTTYPE=X&CRDTBURRPT=X
&CRDTBURSCOR=999&PRIMARYNAME=LASTNAME,FIRSTNAME&PRIMARYSSN=9999999
99&PRIDOB=YYYYMMDD&CRDTLIFEINS=X&
PRISLLT=X&MTHRMADN=XXXXXXXX&SCNDCHNAME=LASTNAME,FIRSTNAME&SCNDSSN
=999999999&ADDR1=XXXXXXXXXXXXXXXX&ADDR2=XXXXXXXXXXXXXX&CITY=XXXXXXXX
XX&STATE=XX&ZIP4=XXXXXXXXXX&HMPHONE=9999999999&BUSPHONE=9999999999
&CHECKINGID=XXXXXXXXXXXXXXXXX&CHRGDDA=X&XREFACCTNO=9999999999999999
&SHAREACCT=XXXXXXXXXXXXXXXXX&MISC1=XXXX&MISC2=XXXXX&MISC3=XXXXXXX&
MISC4=XXXXXXXXXX&SPCLFLGS=XXX&RUSHPLST=X&CRDTRPT=X&CRDTOVRD=XXX&CM
PYID=XXXXXXXX&CMPYCNTRL=9999999999999999&ALTLNG=X&ACCTERMS=X&OPENDT
=YYYYMMDD&ROLE_CODE=99&SEC_CODE=999999&
PIN_VER_NBR=99999&MBRSEQ=9999&
The following is a sample response when the account has been created successfully. The
STATUS CODE tag contains a value of zero (0) indicating success.
- <INVISION>
-<ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>4284279C-AA26-CD1C-7AF3-1232836EEB11</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1720</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 493
</ACCTXML>
</INVISION>
In the event of a failed account creation, the response will include a tag name EXCEPTION that
contains error information from the First Data system.
The Set PIN Offset request provides the ability to set the PIN offset on a cardholder’s
plastic for an account on the Omaha platform. This feature is typically used when the
cardholder has chosen their PIN at the Credit Union. This function will update the
number on the FDR system so that it is available for PIN mailers and mag stripe
encoding for reissued cards.
If the PIN is stored on the EMV card, the ability to support a PIN change during instant
issue of a replacement / reissue is not supported. This function will not support a PIN
changes for EMV cards where the PIN is stored on the EMV card through any solution.
If the PIN is not stored this function and the PIN Security function 1445 will work to
change the PIN through any solution.
Page 494
Parameter Description Type Required Length
/
Optional
offset of less
than 6 digits,
pad the end
with trailing
0’s.
ROLE_CODE Code determining which Numeric Required 2
Role the PIN belongs to.
Valid Codes:
01 – Primary
02 – Secondary
03 - Authorized
MBRSEQ Member Sequence Code Numeric Required 4
Valid Codes:
0001 – Primary
0002 – Secondary
0003 – 0999 – Authorized
user
VENDORID Vendor Identifier Alpha Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PINXML&APPID=106&APPLICATIONID=102&REQUESTID=102&F
UNCTIONID=1444&CARDNUMBER=9999999999999999&CLIENTID=9999&SEC_CODE=12
3400&ROLE_CODE=99&MBRSEQ=9999
The following is a sample response when the PIN offset has been set successfully. The STATUS
CODE tag contains a value of zero (0) indicating success.
- <INVISION>
- <PINXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>CD0ABEA6-1299-7302-6E7F-F7412161E0CE</GUID>
</VALIDATION>
Page 495
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1444</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PINXML>
</INVISION>
In the event of a failure to set the PIN offset, the response will include a tag name EXCEPTION
that contains error information from the First Data system.
Submitting the PIN Offset after the creation of the chip row data will result in an error message of
“CAPA OTHER ERR”. The PIN Offset must happen prior to the generation of the chip data.
Page 496
8.12.3 PIN Verification Number
The PIN Verification Number request enables the ability to set the PIN Verification
Number on a cardholder’s account. The PIN Verification Number is used to authorize
PIN transactions. This function works with the 1444 PIN Offset function and the same
limitations apply when changing the PIN as it relates to the PIN being stored on the EMV
card.
Format:
‘1’ followed by the four digit
PIN Offset
i.e. if the PIN Offset is 9876 the
PIN_VER_NBR=19876
ROLE_CODE Code determining which Role Numeric Required 2
the PIN belongs to.
Valid Codes:
01 – Primary
02 – Secondary
03 – Authorized user
MBRSEQ Member Sequence Code Numeric Required 4
Valid Codes:
Page 497
Parameter Description Type Required / Length
Optional
0001 – Primary
0002 – Secondary
0003 – 0999 – Authorized User
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
The following is an example of the XML data provided from the URL above:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PINXML&APPID=106&APPLICATIONID=102&REQUESTID=102&F
UNCTIONID=1445&CARDNUMBER=9999999999999999&CLIENTID=9999&PIN_VER_NBR
=12345&ROLE_CODE=99&MBRSEQ=9999
The following is a sample response when the PIN Verification Number has been set successfully.
The STATUS CODE tag contains a value of zero (0) indicating success.
- <INVISION>
- <PINXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>CD0ABEA6-1299-7302-6E7F-F7412161E0CE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1445</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PINXML>
</INVISION>
Page 498
In the event of a failure to set the PIN offset, the response will include a tag name EXCEPTION
that contains error information from the First Data system.
Page 499
8.12.4 EMV Data Request
The EMV Data Requests initiates the creation of the data on the First Data platform.
This function pertains to method 1 discussed in section 8.12
In order to use the EMV instant issue requests the credit union must update their PCF
settings as follows:
PF PC RF Instant Issuance Code to 2
AO AC EM Inst Issuance File Retention to a value between 1 and 30
PP IP NE File Layout Format Number 034
When this request is made no plastic will be shipped from FD. The correct plastic count
will be placed on the account for reissue and account transfer purposes automatically as
a result of issuing this request.
If the PIN is also going to be set that needs to be done with functions 1444 and 1445
prior to making these requests for EMV chip data.
Page 500
Parameter Description Type Required / Length
Optional
1 – Primary
2 – Secondary
3 - Authorized
MBRSEQ Member Sequence code Numeric Required 5
Valid Codes: with
Primary – 00001 EMBOSSCD=
Secondary – 00002 3
Authorized – 00003 -
00999
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1730&CARDNUMBER=9999999999999999&CLIENTID=9999&EMBOSSCD=
9&MBRSEQ=99999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1730</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
Page 501
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
This function is used to obtain the data necessary to build the data set for the EMV chip
as part of the Instant Issue process.
Page 502
Parameter Description Type Require/ Length ODS
Optional Parameter
MBRSEQ Member sequence number Numeric Required 3 MBR_SQNC_ID
Primary = 001
Secondary = 002
Authorizes = 003 – 099
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1725&CARDNUMBER=9999999999999999&CLIENTID=9999&MBRSEQ=99
9
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ALERTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>37CCE46C-D312-CBBF-D7FA-67B27B671CC4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1725</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="DATASTATUS">X</odsPscuTAG>
<odsPscuTAG
NAME="REASONCODE">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG
NAME="DATATEXT1">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT2">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
Page 503
NAME="DATATEXT3">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT4">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT5">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT6">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT7">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT8">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT9">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXXX
X</odsPscuTAG>
NAME="DATATEXT10">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT11">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT12">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT13">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT14">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT15">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT16">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT17">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
Page 504
NAME="DATATEXT18">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT19">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
NAME="DATATEXT20">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxXXXX
XX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
This request may need to be run multiple times to obtain the data. While the data is
being built, an error message will be received containint the following:
“INST ISSU PENDING PLEASE RETRY”. This indicates the application should wait and try
again after x seconds.
<INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>6B7350EA-6780-0433-FCDF-AB9C39696C13</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1725</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
Page 505
<odsPscuTAG NAME="EXCEPTION
OCCURRED">com.pscu.ejb.hostbean.CleanRemoteException:
"ERROR",0331,2,"SYSTEM ERROR: PI EMBOSS SERVICE",1,,,,"V3OSPIRV
12","INSTANT_ISSUANCE_DETAIL","09/22/15 09:58:16","2@N6 GXG",,"C$CBC27A"in
com.pscu.ejb.hostbean.ods.ODSCardholderPlasticsViews.getInstantIssuanceDetailsQu
ery Executed :SELECT ACCT_ID, AGNT_ID, ENTR_ID, RQST_STTS_CD,
SPCL_ACTN_RESN_TX, INST_ISSU_DATA_01_TX, INST_ISSU_DATA_02_TX,
INST_ISSU_DATA_03_TX, INST_ISSU_DATA_04_TX, INST_ISSU_DATA_05_TX,
INST_ISSU_DATA_06_TX, INST_ISSU_DATA_07_TX, INST_ISSU_DATA_08_TX,
INST_ISSU_DATA_09_TX, INST_ISSU_DATA_10_TX, INST_ISSU_DATA_11_TX,
INST_ISSU_DATA_12_TX, INST_ISSU_DATA_13_TX, INST_ISSU_DATA_14_TX,
INST_ISSU_DATA_15_TX, INST_ISSU_DATA_16_TX, INST_ISSU_DATA_17_TX,
INST_ISSU_DATA_18_TX, INST_ISSU_DATA_19_TX, INST_ISSU_DATA_20_TX,
MBR_SQNC_ID, PRIN_ID, SYS_ID FROM INSTANT_ISSUANCE_DETAIL WHERE ENTR_ID
= 'XXXXXXXXXXXX0244' AND MBR_SQNC_ID = '001'; nested exception is:
com.pscu.ejb.hostbean.CleanRemoteException: "ERROR",0331,2,"SYSTEM ERROR: PI
EMBOSS SERVICE",1,,,,"V3OSPIRV 12","INSTANT_ISSUANCE_DETAIL","09/22/15
09:58:16","2@N6 GXG",,"C$CBC27A"; nested exception is:
com.pscu.ejb.hostbean.CleanRemoteException: "ERROR",0331,2,"INST ISSU PENDING
PLEASE RETRY",1,,,,"V3OSPIRV 12","INSTANT_ISSUANCE_DETAIL","09/22/15
09:58:16","2@N6 GXG",,"C$CBC27A"</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>1</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 506
OdsPscu TAG Description Type Length ODS Parameter
NAME
DATASTATUS Status of the data Alpha 1 RQST_STTS_CD
Valid codes:
O – Ordered
D – Production in process
E – Pending; Data generated and
ready for Issuer
T – Data has been retrieved by the
Issuer
C – Process has failed (error
message is provided)
DATATEXT1 Data elements for the data set for Alpha Up to 255 INST_ISSU_DATA_01_TX
thru the EMV chip. These parameters thru
DATATEXT20 will contain data when the INST_ISSU_DATA_20_TX
DATASTATUS is T
REASONCODE This parameter will contain data Alpha 30 SPCL_ACTN_RESN_TX
when the DATASTATUS is C, G, or
J
At this time only DATATEXT1 is returning data. The following is the content of the data
returned in DATATEXT1:
Page 507
Valid codes for first position:
1 - International card
2 - International card -
alternative technology
5 - National use only
6 - National use only -
alternative technology
7 - Private card
Valid codes for second
position:
0 - Normal
authorization
2 - Online
authorization mandatory
Valid codes for third position:
0 - PIN required
1 - Normal cardholder
verification
2 - Reserved for future
use
3 - ATM only
5 - Reserved for future
use
Page 508
0103 2 LCOL Lower Consecutive Off-Line
Limit Count: this is the
number of offline
transactions that can happen
before the card has to go
online.
0105 2 UCOL Upper Consecutive Off-Line
Limit Count: this is the
number of offline authorized
transactions that can happen
before the transaction is
denied by the chip if the chip-
enabled terminal is unable to
execute an online
authorization
0107 12 LCOTA Lower Cumulative Off-Line
Transaction Amount: this is
amount the of transactions
authorized offline that can
occur before the chip card
automatically requests an
online authorization via the
chip-enabled terminal.
0119 12 UCOTA Upper Cumulative Off-Line
Transaction Amount: this is
the total amount of
transactions authorized
offline that can occur before
a transaction is denied by the
chip if the chip enabled
terminal is unable to execute
an online authorization
0131 2 Language Code Language code
0133 1 Member Role Code Member Role Code:
P – Primary
S – Secondary
A – Authorized
Page 509
0134 5 Member sequence number Member sequence number:
00001 – Primary
00002 – Secondary
00003 – 99999 - Authorized
This function will retrieve the Chip Row details for an EMV credit card.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&FUNCTIONID=172
7&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&
Page 510
<RESPONSE>0</RESPONSE>
<GUID>47DF121E-19CB-4D42-555A-9DF19F87CE3D</GUID>
</VALIDATION><V_OLCLASS>
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1727</ods:FUNCTIONID>
<ods:FUNCTIONRS>
<ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu"/>
</ods:FUNCTIONDATARS>
<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 511
<odsPscuTAG NAME=" TIMESTAMP ">YYYY-MM-DD-
HH.MM.SS.SSSSSS</odsPscuTAG>
<odsPscuTAG NAME=" NXTCARDPROFILEID ">XXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" RPLCSEQNR ">9999</odsPscuTAG>
<odsPscuTAG NAME=" SCRIPTPNDIN ">X</odsPscuTAG>
<odsPscuTAG NAME=" SUBAPPNM ">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" UPDCARDPROFILECD ">X</odsPscuTAG>
<odsPscuTAG NAME=" MBRSEQ">99999</odsPscuTAG>
<odsPscuTAG NAME=" ROLECD ">99</odsPscuTAG>
<odsPscuTAG NAME="ENCRCHIPPINBLK"> </odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 512
OdsPscu TAG NAME Description Type Length
SUBAPPNM Sub-application name Alpha Numeric 16
TIMESTAMP Maintenance Timestamp Numeric 26
Format:
YYYY-MM-DD-HH.MM.SS.SSSSSS
UPDCARDPROFILECD Update Card profile code Alpha 1
This function will post the EMV Chip Row data to the FD record.
Page 513
Parameter Description Type Required / Length
Optional
date does
not change.
KEYINDEXNUM Index Number provided by the Numeric Required 2
Instant Issue device
MEMBERSEQCD Member Sequence Code: Numeric Required 5
00001-Primary
00002-Secondary
00003-99999 – Authorized
PITYPE Plastic Type Numeric Required 2
06 – both EMV & Contactless
08 - EMV
PROFILEID Card Profile ID Alpha Required 12
Numeric
RPLCSEQNR Sequence number for the plastic Numeric Required 2
ROLECD Cardholder Role Code: Numeric Required 2
01-Primary
02-Secondary
03-Authorized
VENDORID Id assigned to the vendor Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&FUNCT
IONID=1726&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=99
99&RPLCSEQNR=99&ROLECD=99&MEMBERSEQCD=99999&KEYINDEXNUM=99&E
MVAPPLNM=XXXXXXXXXXXXXX&CHIPTYPE=XXX&PROFILEID=XXXXXXXXXXXX&PITY
PE=99&ENCRCHIPPINBLK=Y&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
Page 514
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1726</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">XXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 515
8.13 Redeem Rebates
The Redeem Rewards function will decrement the account rebates for statement credit
or cash. The rebates will immediately reflect the redemption. Statement Credit will be
posted on the account when the parameter RDMPTYPE=DC. The statement credit
however will not appear in the transactions or impact the balance until after two
processing nights. If the redemption is for cash the money (RDMPTYPE=DA or DS), the
funds will need to be placed in the draft account via either a manual transaction, or a
call to the core’s API.
Step 1:
o SF000545 Standard Form – Rewards Multi Distribution Document Request Form
o Completed by PSCU SE and CU
o SF000545 form submitted to FD for programming via FD Service Center
Step 2:
o CU approves associated FD development hours
o FD slots request for scheduled M and C-cycle release dates
o FD provides PSCU team with timing for request completion
Step 3:
o PSCU Rewards Implementation team sets up/modifies program based on timing
information provided by FD
For DC:
A FD programming request will be required to add the rebate program to the control
card for statement credits. This request typically requires 60-90 days for processing.
Please contact PSCU Account Executive and Service Executive for the set up and
programming request in advance of implementing this feature.
The posting of the statement credit may take up to two processing nights.
For DA or DS:
Rebate redemption for cash deposit does not require a programming request when the
deposit is limited to the credit union. The Data eXchange function will deduct the
rebates in real-time. Additional programming with the core will be required to deposit
the funds into the requested account – C or Savings.
Page 516
Distribution Flag parameter:
The Distribution Flag parameter for the ZZ program needs to be a 0.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&APPID=106&APPLICATIONID=102&REQUESTID=102&F
UNCTIONID=1450&CARDNUMBER=9999999999999999&CLIENTID=9999&BONPGM=XX
XXXXXX&BONRDMPAM=999999999&RDMTYPE=DC
Page 517
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>72C559AB-6318-7B38-5186-91B32AAA72D0</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1450</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Error Description
NOT ELIGIBLE TO REDEEM, REWARD CONTROL- The number of cycles delinquent excludes the
10 account from rewards distribution based on your
Distribution Maximum Cycles Delinquent
parameter setting.
NOT ELIGIBLE TO REDEEM, REWARD CONTROL- The percentage overlimit excludes the account
20 from rewards distribution based on your
Distribution Maximum Overlimit Percentage
Page 518
Error Description
parameter setting.
NOT ELIGIBLE TO REDEEM, REWARD CONTROL- The current redeemable balance excludes the
30 account from rewards distribution based on your
Distribution Minimum Bonus Amount parameter
setting.
NOT ELIGIBLE TO REDEEM, REWARD CONTROL- The external status excludes the account from
40 rewards distribution based on your setting in the
Distribution External Status Code A, B, C, E, F, I, L,
and U parameter and a Distribution External Status
parameter setting of 1.
NOT ELIGIBLE TO REDEEM, REWARD CONTROL- One of the following conditions exist.
50 • The rewards program you entered excludes the
account from rewards distribution based on one of
the following.
- The account-level termination date for the
rewards program matches the current processing
date.
- The program-level termination date for the
rewards program matches the current processing
date.
- The account’s rewards strategy changed, and the
rewards program is not part of the new strategy.
• The Rewards Offline Exclusion Code on the
program account record excludes the account from
rewards distribution.
Refer to the Restricting Rewards Processing on CLR
Accounts heading in the Optional Rewards Features
chapter for more information about the Rewards
Offline Exclusion Code.
Page 519
8.14 Account Updater
The Account Updater function will provide the ability to opt-out of the account updater
functionality for the merchants offering recurring automatic billing.
Reason* Visa MC
Close Account (C) Issuer Segment ID Old Account
Old Acct Number
Old Exp Date
Page 520
Service Identifier = C
Opt In/Out= I/O
Change Expiration Issuer Segment ID Old Account
(E) Old Acct Number Old Exp
Old Exp Date New Account
New Acct Number = Old Acct New Exp
Number
New Exp Date
Service Identifier = E
Opt In/Out= I/O
Transfer Account Issuer Segment ID
Old Acct Number
Old Exp Date
Service Identifier = O
Opt In/Out = O opts out of both
Opt Out (O) Issuer Segment ID Account number to opt out
Old Acct Number Old Exp = Exp Date
Old Exp Date
New Acct Number = Old Acct
Number
New Exp Date
Service Identifier = E
Opt Out = O
Brand Flip to MC (B) Old Account
Old Exp
New Acct
New Exp
New Account (R) Old Account
New Acct
New Exp
Replacement Card Old Account
(R) Old Exp
New Account
New Exp
Upd to New Card (X) Old Account
Old Exp
New Account
Page 521
New Exp
Upd to Old Card (Y) Old Account
Old Exp
New Account
New Exp
*For VAU, the reason code is determined by the Service Identifier. For Master Card, the
reason code is in parenthesis in the Reason column of the table.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1478&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&OLDEXPRDT=YYMM&OPTOUT=X&REASONCD=X&SEGMENTID=99999
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1478</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">XXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 522
8.14.3 Tag and Property Reference
Page 523
8.15 Authorization
This function will request an authorization on the credit card account in real-time. The
authorization will appear in the recent activity whether approved or declined. If
approved, the available credit will be decreased by the amount requested.
The authorization requested through this Data eXchange call will bypass all
authorization validation such as a limit on the percentage of credit available for cash
advance. It is possible to perform these validations in advance of issueing this request
using information returned from other Data eXchange calls.
Page 524
Parameter Description Type Required / Length
Optional
EXP_DT Expiration Date of the plastic Numeric Required 4
Format:
MMYY
MERCHANT Credit Union’s Merchant Numeric Required 15
Number for the appropriate
tran code and sys/prin of the
cardnumber and must have
and MCC of 0009 for cash
advances
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1485&CLIENTID=9999&CARDNUMBER=XXXXXXXXXXXXXXXX&CHECK_AVAI
L=Y&AMOUNT=99900&MERCHANT=XXXXXXXXXXXXXXX&EXP_DT=MMYY&ETC=X&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1485</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="AR_A_STAT">CMPLT</odsPscuTAG>
<odsPscuTAG NAME="AR_B_MSG_NMBR">1234</odsPscuTAG>
Page 525
<odsPscuTAG NAME="AR_C_SEVERITY">X</odsPscuTAG>
<odsPscuTAG NAME="AR_D_REF_NMBR">99</odsPscuTAG>
<odsPscuTAG NAME="AR_E_ACTION_CODE">X</odsPscuTAG>
<odsPscuTAG NAME="AR_F_AUTH_NMBR">1234</odsPscuTAG>
<odsPscuTAG
NAME="AR_G_PHONE">999999999999</odsPscuTAG>
<odsPscuTAG NAME="AR_H_ADD_ACTION_IND">X</odsPscuTAG>
<odsPscuTAG NAME="AR_I_TRANSFER_OPT">X</odsPscuTAG>
<odsPscuTAG NAME="AR_J_MSG_TEXT">This is a
message</odsPscuTAG>
<odsPscuTAG NAME="AUTHORIZATION">PASSED</odsPscuTAG>
<odsPscuTAG NAME="CREDIT_AVAIL">TRUE</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Valid codes:
CMPLT – successful completion
ERROR – failed to complete
AR_B_MSG_NMBR System assigned identifier of any error Alpha Variable NA
message numeric
AR_C_SEVERITY Identifier of the severity of the error Alpha Variable NA
message numeric
AR_D_REF_NMBR FDR Use Only Numeric Variable NA
Page 526
OdsPscu TAG NAME Description Type Length First
Data
Screen
AR_E_ACTION_CODE Code representing the action the Alpha 2 NA
System will take on this account. See numeric
section 8.9.4 for descriptions
AR_F_AUTH_NMBR Authorization code assigned by the Alpha Variable NA
issuer numeric
AR_G_PHONE Referral telephone number supplied by Numeric 10 NA
the issuer
AR_H_ADD_ACTION_IND Code identifying supplemental Alpha 2 NA
information related to numeric
@AR_E_ACTION_CODE. See section
8.9.4 for description.
AR_I_TRANSFER_OPT Code representing the reason for Alpha NA
transferring an authorization call numeric
AR_J_MSG_TEXT Message text-message indicating the Alpha Variable NA
nature of the error
AUTHORIZATION Code representing results of the Alpha 6 NA
authorization request
Valid responses:
PASSED – Authorization passed
FAILED – Authorization failed, and
transaction was not executed
CREDIT_AVAIL Results of the check for available credit Alpha 4/5/11 NA
TRUE – Credit available
FALSE – Credit not available
NOT CHECKED – Credit Limit was not
checked
If CHECK_AVAIL=Y and there is not
enough available credit for the amount
requested, this will be the only tag in
the response and will contain a value of
FALSE.
Page 527
8.16 Post Transaction
This function will post a transaction on the account that will impact the current balance.
The transaction will post as an adjustment. The posting will occur during overnight
processing.
Value Codes:
253 - Merchandise
254 – Cash Advance
280 – Credit Adjustment
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
Page 528
8.16.2 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1486&CLIENTID=9999&CARDNUMBER=XXXXXXXXXXXXXXXX&DESCRIPTIO
N=CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC&AMOUNT=99900&MERCHANT=XXXXXX
XXXXXXXXX&TRANCODE=999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1486</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="TRANS_POSTED">TRUE</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Page 529
8.16.3 Tag and Property Reference
Page 530
8.17 Cancel Emboss requests
This function will cancel the existing embossing requests for a card number. Existing
emboss requests can be retrieved from the Data eXchange function 1487 in Section
7.27.
*This function may return a successful response even when the Transaction Time Stamp is
inaccurate. When implementing this function extra care should be taken to ensure the
Transaction Time Stamp is exactly as returned by the Retreive Emboss Request (function 1487)
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1488</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">CCCCCCC</odsPscuTAG>
</odsPscu:DATASTREAM>
Page 531
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 532
8.18 EMV PIN Change
This request will change the PIN on an Omaha EMV plastic. The use of this function
requires the encrypted PIN block. The encrypted PIN block is obtained from the
Hardware Security Module (HSM). Integration with the HSM is required using APIs
exposed by the HSM provider. The PTK (Pin Transit Key) is used to generate the
encrypted PIN block.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1481&REQUESTID=102&CARDNUMBER=9999999999999999&CL
IENTID=9999&PINBLCK=CCCCCCCCCCCCCCCC&PISEQNUM=999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
Page 533
<ods:FUNCTIONID>1481</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">CCCCCCC</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 534
8.19 Refund Rebates
This function supports the ability to refund rebates / rewards on an account. The change
of the rebates/rewards is reflected on the account in real-time.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1490&CARDNUMBER=9999999999999999&CLIENTID=9999&BONPGM=XX
XXXXXX&BONRFNDAM=999999999&ACTION=X&
- <INVISION>
- <ACCTXML>
Page 535
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>72C559AB-6318-7B38-5186-91B32AAA72D0</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1490</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 536
8.20 Omaha PIN Resets
This function will reset the PIN count on a plastic processing on the Omaha / Optis
platform.
Page 537
Parameter Description Type Required / Length
Optional
Authorizations RPCs chapter
in the Open Data Streams
manual for more
information.
Valid codes:
E - Reset the excessive
authorizations counter
and/or the count of invalid
CVV/CVC and CVV2/CVC2
attempts allowed.
If you use the PI identifier to
enter the transaction and
you track authorizations at
the PI level, the System
resets this counter at the PI
level. Otherwise, it resets it
at the account level.
J - Reset the total adjustment
counter to zero.
The System resets this
counter at the account level
only.
P - Reset the excessive PIN
attempts counter.
If you are a separate-entity
processor, the System resets
this counter at the PI level.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
Page 538
FUNCTIONID=1491&CLIENTID=9999&CARDNUMBER=XXXXXXXXXXXXXXXX&COUNTER=C
&VENDORID=XXXXXX
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1491</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">CCCCCCC</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Page 539
PSCU – Propriety and Confidential Last Revised: 03/31/2023
Version 23.1
Page 540
9 CompDataXML
CompDataXML functions are those that perform an action – create, update, or delete -
on the company characteristics.
Function ID Description
1540 Create Company - provides the ability to create a COMPANY level
account.
1503 Delete Company - provide the ability to delete a COMPANY level account.
1504 Update Company - provides the ability to update a COMPANY record.
1501 Company Accounts – provides information about the accounts associated
with the COMPANY
1502 Company Information – provides information about the COMPANY
1517 Company Memos – returns the memos on the COMPANY record
1515 Company Recent Activity – provides transactions and pending
authorizations for all accounts within the company
1518 Add Company Memo - provides the ability to add a memo at to the
company account.
Page 541
9.1 Create Company
This functionality will provide the ability to create a COMPANY level account.
Page 542
Parameter Description Type Required Length
/
Optional
A – Annually
M - Monthly
S – SemiAnnual
Q – Quarterly
CC180FRQNCD CC/CM-180 Frequency Required 1
Code
A – Annually
M - Monthly
S – SemiAnnually
Q - Quarterly
CC807FRQNCD CC/CM-807 Frequency Alpha Required 1
Code
A – Annually
M - Monthly
S – SemiAnnual
Q - Quarterly
CHDCLEXCPPRCNRT Cardholder Credit Line Numeric Required 3
Exception Percentage 999
Rate
CMPNCONTCEXPRDT Company Contract Date Required 6
Expiration Date MMYYYY
CMPNCRDTEXCPPRCNRT Company Credit Line Numeric Required 3
Exception Percentage 999
Rate
COADDR1 Address Line 1 AlphaNumeric Required Up to 26
Page 543
Parameter Description Type Required Length
/
Optional
COCRDTLINEAM Company Credit Line Numeric Required Up to 15
Amount 999999999999999
COEXTSTATUS Code indicating how to Numeric Optional 1
report balances of
accounts with
external statuses on the
YBS and YCL screens; valid
codes:
0 – include in GOOD
STATUS column
1 – include in the EXT
STATUS column
COMPANYID Company ID AlphaNumeric Required Up to 8
COMPANYNAME Company Name AlphaNumeric Required Upto 26
COSTATE State Alpha Required 2
Page 544
Parameter Description Type Required Length
/
Optional
not prorate the annual fee
amount if you use this
option.
1 - Use the annual fee
amount on the Company
Card Master File and bill
the individual cardholders.
The System does not
prorate the annual fee
amount if you use this
option.
2 - Use the sliding scale
amount on the Lvl 1
Charge through Lvl 10
Charge parameters in the
Commercial Card (AO AC
CC) section of
the Product Control File
and bill the account
identified in the BILLING
ACCT NO field. The System
does not prorate the
annual fee amount if
you use this option.
3 - Use the sliding scale
amount on the LVL 1
CHARGE through LVL 10
CHARGE parameters and
bill the individual
cardholders. The System
does not prorate the
annual fee amount if you
use this option.
blank - Use fees set on the
Product Control File and
Page 545
Parameter Description Type Required Length
/
Optional
bill the individual
cardholders.
FSCLYEARENDCD Fiscal Year End Code Numeric Required 2
Valid Codes:
01 – January
02 – February
03 – March
04 – April
05 – May
06 – June
07 – July
08 – August
09 – September
10 – October
11 – November
12 – December
INCTMNTHCD Inactive Months Count Numeric Required 2
99
MNTHRPRTCD Monthly Report Code, Alpha Required 1
Code representing when
monthly reports
generate.
Valid Codes:
C - Produce the reports
when the account cycles.
M - Produce the reports at
month end.
NEXTREVWDT Next Review Date Numeric Required 2
MM
PRINCIPALOFFICER Principal Officer Alpha Required Up to 26
PRINID Principal Numeric Required 4
RPRTLEVLCD Reporting Level Code Alphanumeric Required 1
Valid codes:
C - Total reports at the
Page 546
Parameter Description Type Required Length
/
Optional
company level only
1-5 - Number of reporting
levels in the company
hierarchy
SYSID System Numeric Required 4
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1540&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&AGENTID=9999&P
RINID=9999&SYSID=9999&BALPRCNUNITAVRGRT=999&CA012FRQNCD=X&CC163FRQN
CD=X&CA012FRQNCD=X&CC180FRQNCD=X&CC807FRQNCD=X&CHDCLEXCPPRCNRT=99
9&CMPNCONTCEXPRDT=MMYYYY&CMPNCRDTEXCPPRCNRT=999&COADDR1=XXXXXXX
XXXXXXXXXXXXXXXXXXX&COBLLNCYCLCD=99&COCITY=XXXXXXXXXXXXXXXXXX&COSTAT
E=XX&COCRDTLINEAM=999999999999999&COMPANYNAME=XXXXXXXXXXXXXXXXXXXX
XXXXXX&COZIP=99999&FSCLYEARENDCD=99&INCTMNTHCD=99&NEXTREVWDT=MMYY
YY&PRINCIPALOFFICER=XXXXXXXX&MNTHRPRTCD=X&RPRTLEVLCD=X&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <COMPDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1540</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
Page 547
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</COMPDATAXML>
</INVISION>
Page 548
9.1.3 Tag and Property Reference
Page 549
9.2 Delete Company
This functionality will provide the ability to delete a COMPANY level account.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1503&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&
AGENTID=9999&PRINID=9999&SYSID=9999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
Page 550
- <COMPDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1503</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</COMPDATAXML>
</INVISION>
Page 551
9.3 Update Company
Page 552
Parameter Description Type Required Length
/
Optional
S – SemiAnnually
Q - Quarterly
CC807FRQNCD CC/CM-807 Frequency Alpha Optional 1
Code
A – Annually
M - Monthly
S – SemiAnnual
Q - Quarterly
CHDCLEXCPPRCNRT Cardholder Credit Line Numeric Optional Up to 3
Exception Percentage 999
Rate
CMPNCONTCEXPRDT Company Contract Date Optional 6
Expiration Date MMYYYY
CMPNCRDTEXCPPRCNRT Company Credit Line Numeric Optional Up to 3
Exception Percentage 999
Rate
COADDR1 Address Line 1 AlphaNumeric Optional Up to 26
Page 553
Parameter Description Type Required Length
/
Optional
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1504&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&AGENTID=9999&P
RINID=9999&SYSID=9999&BALPRCNUNITAVRGRT=999&CA012FRQNCD=X&CA012FRQN
CD=X&CC180FRQNCD=X&CC807FRQNCD=X&CHDCLEXCPPRCNRT=999&CMPNCONTCEX
PRDT=MMYYYY&CMPNCRDTEXCPPRCNRT=999&COADDR1=XXXXXXXXXXXXXXXXXXXXXX
Page 554
XXXX&COBLLNCYCLCD=99&COCITY=XXXXXXXXXXXXXXXXXX&COCRDTLINEAM=99999999
9999999&COMPANYNAME=XXXXXXXXXXXXXXXXXXXXXXXXXX&COZIP=99999&FSCLYEAR
ENDCD=99&INCTMNTHCD=99&NEXTREVWDT=MMYYYY&PRINCIPALOFFICER=XXXXXXXX
&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <COMPDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1504</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</COMPDATAXML>
</INVISION>
Page 555
9.3.3 Tag and Property Reference
Page 556
9.4 Company Accounts
The company accounts function will return a list of the accounts associated with a
company.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1501&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&
AGENTID=9999&PRINID=9999&SYSID=9999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
Page 557
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1501</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG
NAME="COMPANYNAME">XXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="COMPANYID">XXXXXXXX</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="ACCTRLTNCD">X</odsPscuTAG>
<odsPscuTAG
NAME="ACCTAUTHSTRAT">XXXX</odsPscuTAG>
<odsPscuTAG
NAME="ACCTNUMBER">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="ACCTCHNAME">LASTNAME,FIRSTNAME</odsPscuTAG>
<odsPscuTAG
NAME="ACCTCREDITLIMIT">9999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="ACCTBALANCE">9999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="ACCTEXTSTAT">X</odsPscuTAG>
<odsPscuTAG NAME="ACCTINTSTAT">X</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
Page 558
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 559
9.5 Company Information
The Company Information request returns the general information for the specified
company account.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1502&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&
AGENTID=9999&PRINID=9999&SYSID=9999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
Page 560
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1502</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG
NAME="COMPANYNAME">XXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="COADDR1">XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTA
G>
<odsPscuTAG
NAME="COADDR2">XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTA
G>
<odsPscuTAG
NAME="COCITY">XXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="COSTATE">XX</odsPscuTAG>
<odsPscuTAG NAME="COZIP">99999</odsPscuTAG>
<odsPscuTAG
NAME="COCONTACT">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=”COTELEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="COOPENDT">MMDDYYYY</odsPscuTAG>
<odsPscuTAG
NAME="CONEXTBILLINGDATE">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="COCYCLECODE">99</odsPscuTAG>
<odsPscuTAG
NAME="COLASTBILLINGDATE">YYYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="COAVAILCREDIT">0000000000099999</odsPscuTAG>
<odsPscuTAG
NAME="COCREDITLINE">0000000000009999.99</odsPscuTAG>
Page 561
<odsPscuTAG
NAME="COAVGBALANCE">0000000000009999.99</odsPscuTAG
>
<odsPscuTAG NAME="COGOODACCTS">999</odsPscuTAG>
<odsPscuTAG
NAME="COGOODOUTBAL">0000000000009999.99</odsPscuTA
G>
<odsPscuTAG
NAME="COGOODCREDITLINE">0000000000009999.99</odsPscu
TAG>
<odsPscuTAG
NAME="COGOODAVAILCREDIT">0000000000009999.99</odsPs
cuTAG>
<odsPscuTAG
NAME="COGOODDELAMOUNT">0000000000009999.99</odsPs
cuTAG>
<odsPscuTAG NAME="COEXTSACCTS">999</odsPscuTAG>
<odsPscuTAG
NAME="COEXTSOUTBAL">0000000000009999.99</odsPscuTAG
>
<odsPscuTAG
NAME="COEXTSCREDITLINE">0000000000009999.99</odsPscuT
AG>
<odsPscuTAG
NAME="COEXTSAVAILCREDIT">0000000000009999.99</odsPscu
TAG>
<odsPscuTAG
NAME="COEXTSDELAMOUNT">0000000000009999.99</odsPscu
TAG>
<odsPscuTAG NAME="COPARENTID">XXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="COPARENTSYS">9999</odsPscuTAG>
<odsPscuTAG NAME="COPARENTPRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="COPARENTAGENT">9999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 562
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 563
OdsPscu TAG NAME Description Type Length First
ODS View Parameter Data
Screen
accounts with an EXTERNAL Status
COGOODACCTS Number of accounts in GOOD Numeric 18 YBS
Status
COGOODAVAILCREDIT Total available credit for all Numeric 18 YBS
accounts in GOOD Status
COGOODCREDITLINE Total Credit Line for all accounts in Numeric 18 YBS
GOOD Status
COGOODDELAMOUNT Total delinquent amount for all Numeric 18 YBS
accounts in GOOD Status
COGOODOUTBAL Total outstanding balance for all Numeric 18 YBS
accounts in GOOD Status
COLASTBILLINGDATE Last billing date Date 8 YCI
Page 564
9.6 Company Memos
The Company Memos function will return the memos on the Company account.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1517&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&
AGENTID=9999&PRINID=9999&SYSID=9999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
Page 565
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1517</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG
NAME="COMPANYNAME">XXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="COMPANYID">XXXXXXXX</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="COMEMODATE">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME="COMEMOSEQ">XXX</odsPscuTAG>
<odsPscuTAG
NAME="COMEMOTEXT">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 566
9.6.3 Tag and Property Reference
Page 567
9.7 Company Recent Activity
The Company Recent Activity function will return the recent activity for all accounts in
the company. This will require two processing steps: 1) obtain the list of accounts within
the company using the Data eXchange function 1501 and 2) cycle through the list and
call the 1415 function for each account to obtain the transactions and authorizations.
The collection of transactions returned in the 1415 function will need to be edited to
also include the card number so that the transactions can be associated with the
appropriate account by the consuming application.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1515&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&
AGENTID=9999&PRINID=9999&SYSID=9999&
Page 568
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1515</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="COMPANYID">XXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="COMPANYNAME">XXXXXXXXXXXXXXXXXXXXXXXXX</ods
PscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="AUTHMERCHSTATE">ST</odsPscuTAG>
<odsPscuTAG
NAME="AUTHPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG
NAME="AUTHTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="AUTHAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="AUTHACTCODE"/>
<odsPscuTAG NAME="AUTHMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHCITY">CITY
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHNAME">MERCHANT
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHTRANS">XX</odsPscuTAG>
<odsPscuTAG
NAME="AUTHDECLINEREASONCODE">XX</odsPscuTAG>
<odsPscuTAG NAME="AUTHREF">999999</odsPscuTAG>
Page 569
<odsPscuTAG
NAME="AUTHMERCHNMBR">9999999999999</odsPscuT
AG>
<odsPscuTAG NAME="AUTHZIP">999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="AUTHMERCHSTATE">ST</odsPscuTAG>
<odsPscuTAG
NAME="AUTHPOSENTRYMODE">99</odsPscuTAG>
<odsPscuTAG
NAME="AUTHTRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="AUTHAMT">99999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="AUTHACTCODE"/>
<odsPscuTAG NAME="AUTHMERCHCAT">9999</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHCITY">CITY
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHMERCHNAME">MERCHANT
NAME</odsPscuTAG>
<odsPscuTAG NAME="AUTHTRANS">XX</odsPscuTAG>
<odsPscuTAG
NAME="AUTHDECLINEREASONCODE">XX</odsPscuTAG>
<odsPscuTAG NAME="AUTHREF">999999</odsPscuTAG>
<odsPscuTAG
NAME="AUTHMERCHNMBR">9999999999999</odsPscuT
AG>
<odsPscuTAG NAME="AUTHZIP">999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">FIRST TRANSACTION
DESCRIPTION</odsPscuTAG>
Page 570
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="EXPNRFRNNR">XXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="DTLPOSTDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">YYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="TRANAMT">999999999999.99</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">NEXT TRANSACTION
DESCRIPTION</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 571
OdsPscu TAG NAME Description Type Length First
Data
Screen
record is set to R.
To override the code's effects, take
the following actions.
Set the CORR FLAG
OVERRIDE field on the LT01
03, Letter Definition screen,
to P - Print, for each item
you want printed despite an
Authorization Control Code
of A.
Set the Letter Override
Suppression Flag parameter
in the Operational Controls
section (PF CM OC) of the
Product Control File to Y,
which overrides a Hold
Correspondence Flag of 1.
The System automatically
removes this code when an
address change posts to the
account record. However, if
you use the Automatic Auth
Flag in the Authorization
Settings section (AU BC AS)
of the PCF as part of an
Adaptive Control
Authorization strategy, you
must update the address flag
and/or the home phone flag
as well as entering the new
address or home phone
number.
M - This account has an unresolved
dispute.
This code prohibits the printing of
Page 572
OdsPscu TAG NAME Description Type Length First
Data
Screen
past due letters. This code also
places a hold code on the
statement.
Q - Always authorize unless an
external status prohibits
authorization. This code prohibits
the printing of the following.
Delinquency notification
statements
Statement message
generated from delinquency
message parameters in the
PCF
Delinquency letters
Overlimit courtesy
statements
Statement message
generated from overlimit
message parameters in the
PCF
Overlimit letters
S - Identify all convenience checks as
stop-payments.
V - Prohibit printing of the same
items listed for valid code Q. With a
statement hold code other than Y,
the System sends manually
requested letters.
Y - Always decline authorization.
The System automatically removes
this code when the account is no
longer delinquent. This code does
not apply to airlines.
blank - Normal authorization
Page 573
OdsPscu TAG NAME Description Type Length First
Data
Screen
processing occurs.
Page 574
OdsPscu TAG NAME Description Type Length First
Data
Screen
magnetic stripe transmission
has been unaltered)
03 Bar code read
04 OCR coding read
05 Chip/smart card
06 Track 1 read (the transmission
was not sent to First Data and
has not been certified as being
unaltered)
81 Electronic commerce
(MasterCard only)
90 Entire magnetic stripe read
and transmitted (the merchant
has certified that the magnetic
stripe transmission has been
unaltered)
95 Chip/smart card data is
unreliable (Visa only)
AUTHREF System-assigned identifier of the Numeric 6 CDA
authorization approval code for the
approved transaction - this field is
blank if the authorization was
declined.
AUTHTRANDATE Transaction date for the Numeric 6 CDA
authorization, in YYMMDD format
(Note: Some situations may return
000000 as the value)
AUTHTRANS Transaction code that represents Alpha 2 CDA
the type of authorization action,
valid codes are listed in Appendix F
of this document.
AUTHZIP Zip or postal code of the merchant Numeric 9 CDE
where the authorization took place
DTLAUTHNUM Authorization Number for the Numeric 5 CDE
Page 575
OdsPscu TAG NAME Description Type Length First
Data
Screen
transaction; included in response
when SHOWAUTHNUM=ON
included in the request
DTLDESC Description of the item, in words Alpha 40 CDA
DTLMERCHCATCODE Merchant Code for the transaction; Numeric 5 CDE
included in response when
SHOWMERCHCODE=ON included in
the request
DTLPOSTDATE Posting Date of the item, in Numeric 6 CDA
YYMMDD format (Note: Some
situations may return 000000 as
the value)
EXPNRFRNNR Reference number for the Alpha 17 CDA
transaction item numeric
Page 576
9.8 Add Company Memo
This functionality will provide the ability to add a memo at to the company account.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=COMPDATAXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1518&REQUESTID=102&CLIENTID=9999&COMPANYID=XXXXXXXX&
AGENTID=9999&PRINID=9999&SYSID=9999&COMEMOTXT=XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The following is an example of the XML data provided from the URL above:
- <INVISION>
Page 577
- <COMPDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1518</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</COMPDATAXML>
</INVISION>
Page 578
9.9 Company Payment Information
Payment information for accounts within a company can be obtained using the existing
1414 function.
Credit Line adjustments on the accounts within a COMPANY are handled in the same
manner as credit line adjustments for consumer accounts. The existing 1424 Data
eXchange function will support the ability to adjust credit limits on the individual cards
within the company.
To change the account type (Sub Account to Individual Pay and vice versa) of an account
within a COMPANY use the existing Data eXchange 1435 function to execute NM 694.
Page 579
10 NEWMEMOXML Request
The NEWMEMOXML request provides the abilities to create a CIS Memo in the First
Data system. Section 9 of this document provides a detailed description of the
NEWMEMOXML functions along with the fixed, required and variable parameters, a
sample search request and response, and a description of each node within the
response.
Function ID Description
1418 Create Memo – Creates a CIS Memo on the cardholder’s account on the
First Data system.
Page 580
10.1 Create Memo
The Create Memo request provides the ability to create a CIS Memo on the cardholder’s
account on the First Data System.
This function is supported for both Omaha and Wilmington accounts. However, the
memo is only written to the Omaha platform.
Page 581
Within the First Data system, there are two (2) types of special CIS Memos – Permanent
Memos which will stay on the account indefinitely and Display First which will be
displayed at the top of the memo list. To create a Permanent CIS Memo, the memo text
provided in the CISMEMO parameter must begin with an asterisk (*). To create a
Display First CIS Memo, the memo text provided in the CISMEMO parameter must begin
with an exclamation point (!). When including one of these characters, do not use the
parenthesis to separate the character from the memo text. A space may be used
between the character and the text, but is not necessary. Also, while both upper and
lower case text can be used in the CISMEMO Parameter, the message text will be
converted to uppercase when the message appears in the First Data system. Examples
of CISMEMO parameters are shown below:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=NEWMEMOXML&APPID=106&APPLICATIONID=102&REQUESTID
=102&FUNCTIONID=1418&CARDNUMBER=9999999999999999&CLIENTID=9999&CISME
MO=Escaped%20Memo%20Text%20to%20be%20entered
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <NEWMEMOXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
Page 582
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1418</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="CHSECONDARY">LASTTWO,FIRST</odsPscuTAG>
<COLLECTION/>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</NEWMEMOXML>
</INVISION>
Visa Classic
Visa gold
Page 583
OdsPscu TAG NAME Description Type Length First
Data
Screen
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 584
11 CHUPDATEXML Request
The CHUPDATEXML Request provides the ability to update the cardholder information
found in the First Data system. Section 10 of this document provides a detailed
description of each of the CHUPDATEXML functions along with the fixed, required and
variable parameters, a sample search request and response, and a description of each
node within the response.
Function Description
ID
1404 Update Cardholder Information – Updates the cardholder information on
the First Data system.
1453 Add, View and Update Cardholder attributes – Updates the cardholder
attributes on the First Data system.
Page 585
11.1 Update Cardholder Information
The Update Cardholder Information request provides the ability to update the
cardholder’s information on the First Data System. This change is made immediately.
Page 586
Parameter Description Type Required Length
/
Optional
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
PRIMARYSSN Primary Cardholder Social Numeric Optional 9
Security Number
SECONDARYNAME Secondary Cardholder Name Alpha Optional 26 for
Visa
Valid format: 24 for MC
LAST%20SUFFIX,FIRST%20MI
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
SECONDAYSSN Secondary Cardholder Social Numeric Optional 9
Security Number
STATE Address State Alpha Optional 2
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
WORKPHONE Work Phone Number Numeric Optional 10
ZIP Address Zip Code Numeric Optional 5 or 9
At least one of the optional parameters must be included in the URL request.
Special care should be taken when updating the address in First Data to a non-US
address. Please refer to Appendix D – Foreign Address Handling for specific information.
To remove a value from an existing field in the First Data system when it is no longer
needed or was input in error (such as Mother’s Maiden Name or Address Line 2), send
the parameter followed by the escaped characters for a space. For example, to remove
the Mother’s Maiden Name from the account, the parameter would be:
MOTHERSMAIDENNAME=%20
Page 587
To remove the Secondary Cardholder and all their associated information, simply send
the SECONDAYNAME parameter followed by the escaped characters for a space (%20).
A full request to update home and work phone numbers will appear similar to the
following:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&REQUESTID=1
02&FUNCTIONID=1404&CARDNUMBER=9999999999999999&CLIENTID=9999&PRIMAR
YNAME=LAST,FIRST&HOMEPHONE=999999999&WORKPHONE=9999999999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <CHUPDATEXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1404</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CHZIPCODE">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="MOTHERMAIDENNAME" />
<odsPscuTAG NAME="CHADDR2" />
<odsPscuTAG NAME="CHADDR1">ADDRESS LINE 1</odsPscuTAG>
<odsPscuTAG
NAME="CARDNUMBER">9999999999999999</odsPscuTAG>
Page 588
<odsPscuTAG NAME="SOCSECNBR">999999999</odsPscuTAG>
<odsPscuTAG NAME="CHSTATE">ST</odsPscuTAG>
<odsPscuTAG NAME="CLIENTID">9999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="CHCITY">CITY</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY" />
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</CHUPDATEXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Page 589
OdsPscu TAG NAME Description Type Length First
Data
Screen
This request supports adding and removing an Authorized User on the account. This request will
not generate a plastic for the Authorized User. Using Plastic can be generated using function
1435 with PI_NONMON 13 to set the plastic count. If the authorized user is being added to an
existing account the PI_NONMON 194 to emboss or 200 to rush the emboss will also be
required.
Page 590
.
Data eXchange function 1435 in conjunction with NonMon 90 will create the authorized
user and initiate the creation of plastic.
The following additional parameters are required to be sent for each scenario:
This request will not generate a plastic for the added user. Data eXchange function 1435
in conjunction with NonMon 90 will create the authorized user and initiate the creation
of plastic.
Examples:
SMITH,JOHN
SMITH%20JR,JOHN
SMITH%20JR,JOHN%20L
AUTHSSN Authorized User Social Numeric Optional 9
Security Number
AUTHMBRSEQ Authorized User Member Fixed Required 3
Sequence number
Page 591
A request to add an authorized user will appear similar to the following:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=CHUPDATEXML&APPID=106&APPLICATIONID=102&REQUESTID=
102&FUNCTIONID=1404&CARDNUMBER=9999999999999999&CLIENTID=9999&AUTHN
AME=SMITH,JOHN%20C&AUTHSSN=999999999&AUTHMBRSEQ=NEW
Removing an existing Authorized User will require two special values to be submitted in
the request – AUTHMBRSEQ and AUTHEXTRID. These values can be obtained for every
Authorized User on an account via Function 1423 – Extended Cardholder Information.
To remove an auth user you need to pass the AUTHEXTRID and AUTHMBRSEQ fields
specific to that user. These will need to be hidden params associated with each in the
list of auth users to potentially delete.
A request to remove an existing authorized user will appear similar to the following:
Page 592
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=CHUPDATEXML&APPID=106&APPLICATIONID=102&REQUESTID=
102&FUNCTIONID=1404&CARDNUMBER=9999999999999999&CLIENTID=9999&AUTHN
AME=%20&AUTHSSN=999999999&AUTHMBRSEQ=999&AUTHEXTRID=C1231231231231
2312312313
Updating an existing Authorized User will require two special values to be submitted in the
request – AUTHMBRSEQ and AUTHEXTRID. These values can be obtained for every
Authorized User on an account via Function 1423 – Extended Cardholder Information. To update
an auth user you need to pass the AUTHEXTRID and AUTHMBRSEQ fields specific to that user.
NOTE: The AUTHDOB and/or the AUTHSSN must be included in the request.
A request to update an existing authorized user will appear similar to the following:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.xml.xmlPr
ocess&RQID=CHUPDATEXML&APPID=106&APPLICATIONID=102&REQUESTID=102&FUNC
TIONID=1404&CARDNUMBER=9999999999999999&CLIENTID=9999&AUTHDOB=YYYYM
MDD&AUTHSSN=999999999&AUTHEXTRID=C12312312312312312312313&AUTHUPDA
TE=Y
Page 593
11.2 Add, Update, View Cardholder Information
This function will provide the ability to add, update, and view cardholder specific
information. The ODS call will be determined by the input parameters.
The Function ID for this request is 1453.
The view cardholder information will obtain the all the card holders on the account
along with the current value of each attribute. For Separate Entity processors the
CARDNUMBER must be the account number (OPA) and not a PIID.
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
Page 594
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1453</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="ROLE">99</odsPscuTAG>
<odsPscuTAG NAME="MBRSEQ">999</odsPscuTAG>
<odsPscuTAG NAME="SSN">999999999</odsPscuTAG>
<odsPscuTAG NAME="NAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="CUSTEXTRID">XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DATEOFBIRTH">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="ADDR1">XXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="ADDR2">XXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CITY">XXXXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="STATE">XX</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="MOBILEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MOBILEPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="CBFLG">X</odsPscuTAG>
<odsPscuTAG NAME="MOTHERSMAIDEN">XXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="HOMEEMAIL">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="HOMEEMAILIND">X</odsPscuTAG>
<odsPscuTAG NAME="WORKEMAIL">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="WORKEMAILIND">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ROLE">99</odsPscuTAG>
<odsPscuTAG NAME="ROLESTART">CCYY-MM-DD-
99.99.99.999999</odsPscuTAG>
<odsPscuTAG NAME="ROLEEND">CCYY-MM-DD-
99.99.99.999999</odsPscuTAG>
Page 595
<odsPscuTAG NAME="MBRSEQ">999</odsPscuTAG>
<odsPscuTAG NAME="SSN">999999999</odsPscuTAG>
<odsPscuTAG NAME="NAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="CUSTEXTRID">XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DATEOFBIRTH">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="ADDR1">XXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CITY">XXXXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="STATE">XX</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="MOBILEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MOBILEPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="CBFLG">X</odsPscuTAG>
<odsPscuTAG NAME="MOTHERSMAIDEN">XXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="HOMEEMAIL">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="HOMEEMAILIND">X</odsPscuTAG>
<odsPscuTAG NAME="WORKEMAIL">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="WORKEMAILIND">X</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ROLE">99</odsPscuTAG>
<odsPscuTAG NAME="MBRSEQ">999</odsPscuTAG>
<odsPscuTAG NAME="SSN">999999999</odsPscuTAG>
<odsPscuTAG NAME="NAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG
NAME="CUSTEXTRID">XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="DATEOFBIRTH">CCYYMMDD</odsPscuTAG>
<odsPscuTAG
NAME="ADDR1">XXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CITY">XXXXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="STATE">XX</odsPscuTAG>
<odsPscuTAG NAME="ZIP">99999-9999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="HOMEPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="WORKPHONEFLG">X</odsPscuTAG>
<odsPscuTAG NAME="MOBILEPHONE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MOBILEPHONEFLG">X</odsPscuTAG>
Page 596
<odsPscuTAG NAME="CBFLG">X</odsPscuTAG>
<odsPscuTAG NAME="MOTHERSMAIDEN">XXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="HOMEEMAIL">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="HOMEEMAILIND">X</odsPscuTAG>
<odsPscuTAG NAME="WORKEMAIL">[email protected]</odsPscuTAG>
<odsPscuTAG NAME="WORKEMAILIND">X</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 597
OdsPscu TAG NAME Description Type Length First Data
Screen
HOMEPHONE** Home phone Numeric 10 CU3
Not available for authorized users
HOMEPHONEFLG Home Phone Flag Alpha 1 CU3
Valid codes:
B - The phone number is valid and
the account holder has provided
express consent for SMS (short
message service) text messages
and voice contact. Phone numbers
with this setting can be contacted
by auto-dial methods dependent
upon the value for the device type
setting for this number.
C - Do not contact cardholder at
this telephone number because a
cease and desist agreement has
been filed. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
D - This number has been
disconnected. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
E - The cardholder is no longer at
this number.
G - Cardholder agrees to
portability. The phone number is
valid and the account holder has
provided express consent for voice
contact. Phone numbers with this
setting can be contacted by auto-
dial methods dependent upon the
value for the device type setting for
this number.
H - Cardholder does not agree to
portability. Phone numbers with this
setting do not have express
consent to be contacted by auto-
dial methods.
N - The phone number is not valid.
Phone numbers with this setting do
not have express consent to be
contacted by auto-dial methods.
S - The phone number is valid and
Page 598
OdsPscu TAG NAME Description Type Length First Data
Screen
available for SMS (short message
service) text messages only. Phone
numbers with this setting do not
have express consent to be
contacted by auto-dial methods.
U - The phone number is unlisted.
Phone numbers with this setting do
not have express consent to be
contacted by auto-dial methods.
V - The phone number is not
verified. Phone numbers with this
setting do not have express
consent to be contacted by auto-
dial methods.
X - Do not contact the cardholder at
this number. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
Y - The phone number is valid but
the account holder has not
provided express consent for auto-
dial contact and must be contacted
at this phone number manually and
not by auto-dial methods.
blank - Telephone number not
present.
This field defaults to a value of Y if
a phone number is populated.
Page 599
OdsPscu TAG NAME Description Type Length First Data
Screen
with this setting can be contacted
by auto-dial methods dependent
upon the value for the device type
setting for this number.
C - Do not contact cardholder at
this telephone number because a
cease and desist agreement has
been filed. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
D - This number has been
disconnected. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
E - The cardholder is no longer at
this number.
G - Cardholder agrees to
portability. The phone number is
valid and the account holder has
provided express consent for voice
contact. Phone numbers with this
setting can be contacted by auto-
dial methods dependent upon the
value for the device type setting for
this number.
H - Cardholder does not agree to
portability. Phone numbers with this
setting do not have express
consent to be contacted by auto-
dial methods.
N - The phone number is not valid.
Phone numbers with this setting do
not have express consent to be
contacted by auto-dial methods.
S - The phone number is valid and
available for SMS (short message
service) text messages only. Phone
numbers with this setting do not
have express consent to be
contacted by auto-dial methods.
U - The phone number is unlisted.
Phone numbers with this setting do
not have express consent to be
contacted by auto-dial methods.
Page 600
OdsPscu TAG NAME Description Type Length First Data
Screen
V - The phone number is not
verified. Phone numbers with this
setting do not have express
consent to be contacted by auto-
dial methods.
X - Do not contact the cardholder at
this number. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
Y - The phone number is valid but
the account holder has not
provided express consent for auto-
dial contact and must be contacted
at this phone number manually and
not by auto-dial methods.
blank - Telephone number not
present.
This field defaults to a value of Y if
a phone number is populated.
Page 601
OdsPscu TAG NAME Description Type Length First Data
Screen
Not available for authorized users
WORKPHONEFLG Work Phone flag Alpha 1 CU3
Valid codes:
B - The phone number is valid and
the account holder has provided
express consent for SMS (short
message service) text messages
and voice contact. Phone numbers
with this setting can be contacted
by auto-dial methods dependent
upon the value for the device type
setting for this number.
C - Do not contact cardholder at
this telephone number because a
cease and desist agreement has
been filed. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
D - This number has been
disconnected. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
E - The cardholder is no longer at
this number.
G - Cardholder agrees to
portability. The phone number is
valid and the account holder has
provided express consent for voice
contact. Phone numbers with this
setting can be contacted by auto-
dial methods dependent upon the
value for the device type setting for
this number.
H - Cardholder does not agree to
portability. Phone numbers with this
setting do not have express
consent to be contacted by auto-
dial methods.
N - The phone number is not valid.
Phone numbers with this setting do
not have express consent to be
contacted by auto-dial methods.
S - The phone number is valid and
available for SMS (short message
Page 602
OdsPscu TAG NAME Description Type Length First Data
Screen
service) text messages only. Phone
numbers with this setting do not
have express consent to be
contacted by auto-dial methods.
U - The phone number is unlisted.
Phone numbers with this setting do
not have express consent to be
contacted by auto-dial methods.
V - The phone number is not
verified. Phone numbers with this
setting do not have express
consent to be contacted by auto-
dial methods.
X - Do not contact the cardholder at
this number. Phone numbers with
this setting do not have express
consent to be contacted by auto-
dial methods.
Y - The phone number is valid but
the account holder has not
provided express consent for auto-
dial contact and must be contacted
at this phone number manually and
not by auto-dial methods.
blank - Telephone number not
present.
This field defaults to a value of Y if
a phone number is populated.
**If there are multiple authorized users there is no way to distinguish phone numbers, if
different, for each authorized user. If different phone numbers were entered for each
authorized user, the Data eXchange response does not reflect them accurately.
Page 603
11.2.2 Add Cardholder
This function will add a new card holder to the credit card account but it will not trigger the
generation of the plastic.Plastic can be generated using function 1435 with PI_NONMON 13 to
set the plastic count. If the authorized user is being added to an existing account (versus added
during new account creation) the PI_NONMON 13 must be followed by PI_NONMON 194 or 200
to the emboss.
Page 604
Parameter Description Type Required / Length
Optional
Format
CCYYMMDD
HOMEEMAIL Home email address Alpha Numeric Optional 50
HOMEEMAILIND Home email indicator Alpha Optional 1
HOMEPHONE** Home phone Numeric Optional 10
HOMEPHONEFLG Home Phone Flag Alpha Optional 1
MOBILEPHONE** Mobile phone Numeric Optional 10
MOBILEPHONEFLG Mobile Phone Flag Alpha Optional 1
MOTHERSMAIDEN Mother’s maiden name Alpha Optional 8
NAME Cardholder name Alpha Required 26
LASTNAME, FIRSTNAME MI
ROLE Cardholder Role Numeric Required 2
01 – Primary
02 – Secondary
03 – Authorized
SSN Cardholder social security number Numeric Optional 9
STATE* State Alpha Optional 2
SUFFIX Suffix Alpha Optional 3
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
WORKEMAIL Work email address Alpha Numeric Optional 50
WORKEMAILIND Work email indicator Alpha Optional 1
WORKPHONE** Work phone Numeric Optional 10
WORKPHONEFLG Work Phone flag Alpha Optional 1
ZIP* Zip Code Numeric Optional 5 or 10
Valid format
99999
99999-9999
*All address attributes must be included when the address information is included in
the request.
**If there are multiple authorized users there is no way to distinguish phone numbers, if
different, for each authorized user.
Page 605
=X&HOMEPHONE=9999999999&HOMEPHONEFLG=X&MOBILEPHONE=99999999
99&MOBILEPHONEFLG=X&MOTHERSMAIDEN=XXXXXXXX&NAME=XXXXXXXXXXXX
XXXXX&ROLE=99&SSN=999999999&STATE=XX&[email protected]&
WORKEMAILIND=X&WORKPHONE=9999999999&WORKPHONEFLG=X&ZIP=99999
-9999
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1453</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
<odsPscuTAG
NAME="CUSTEXTRID">XXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="MBRSEQ">999</odsPscuTAG>
<odsPscuTAG NAME="PIID">XXXXXXXXXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 606
OdsPscu TAG NAME Description Type Length First Data
Screen
MBRSEQ Member Sequence Number Numeric 3 ANS
PIID Presentation Instrument Identifier Numeric 3 PIR
Page 607
11.2.3 Update Cardholder
Do not use this function to update the address information for the primary card holder.
Page 608
Parameter Description Type Required / Length
Optional
HOMEEMAIL Home email address Alpha Numeric Optional 50
HOMEEMAILIND Home email indicator Alpha Optional 1
HOMEPHONE** Home phone Numeric Optional 10
HOMEPHONEFLG Home Phone Flag Alpha Optional 1
MOBILEPHONE** Mobile phone Numeric Optional 10
MOBILEPHONEFLG Mobile Phone Flag Alpha Optional 1
MOTHERSMAIDEN Mother’s maiden name Alpha Optional 8
NAME Cardholder name Alpha Optional 26
ROLE Cardholder Role Numeric Required 2
01 – Primary for Credit
02 – Secondary Bureau
03 – Authorized score
update
SSN Cardholder social security number Numeric Optional 9
STATE* State Alpha Optional 2
SUFFIX Suffix Alpha Optional 3
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
WORKEMAIL Work email address Alpha Numeric Optional 50
WORKEMAILIND Work email indicator Alpha Optional 1
WORKPHONE** Work phone Numeric Optional 10
WORKPHONEFLG Work Phone flag Alpha Optional 1
ZIP* Zip Code Numeric Optional 5 or 10
Valid format:
99999-9999
*Address information can only be updated for secondary and authorized card holders. If
any address attribute is to be updated, all address information must be included in the
request. Use function 1404 to update the address for the primary card holder.
**If there are multiple authorized users there is no way to distinguish phone numbers, if
different, for each authorized user.
Page 609
ERSMAIDEN=XXXXXXXX&NAME=XXXXXXXXXXXXXXXXX&ROLE=99&SSN=99999999
9&STATE=XX&[email protected]&WORKEMAILIND=X&WORKPHONE
=9999999999&WORKPHONEFLG=X&ZIP=99999-9999&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1453</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 610
11.2.4 Delete Cardholder
Request Parameters
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xxm.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1453&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&ACTION=DELETE&CUSTEXTID=XXXXXXXXXXXXXXXXXXXXXXX&CUSTROLE
CD=99&MBRSEQ=999
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
Page 611
<ods:FUNCTIONID>1453</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 612
12 CLADJUSTXML Request
The CLADJUSTXML request provides the ability to update an account’s credit limit on the
First Data system. Section 11 of this document provides a detailed description of each
CLADJUSTXML function along with the fixed, required and variable parameters, a sample
request and response, and a description of each node of the response.
Function Description
ID
1424 Credit Limit Adjustment – Updates an account’s credit limit on the First
Data system.
Page 613
12.1 Credit Limit Adjustment
The Credit Limit Adjustment request provides the ability to update an account’s credit
limit. It is important to note that performing this function will immediately update the
credit limit and the new limit will be made available to the cardholder, although certain
fields within the First Data system (those indicating that a credit limit adjustment was
made) are not updated until the nightly batch process at First Data. The Credit Limit
Adjustment function creates a CIS Memo on the account record at First Data.
Another important aspect of this request is the ability to adjust the credit limit down
from its current amount. This means that if the new credit limit sent in the request is
less than the current limit, the request will be processed and the cardholder’s credit
limit will be decreased. This may create an overlimit situation if the cardholder’s current
balance is greater than the new credit limit being set. Caution should be exercised
when issuing this request to ensure the desired effect is achieved. A GETDATAXML
request utilizing FUNCTIONID 1402 sent prior to sending a Credit Limit Adjustment will
retrieve the current balance on the account.
All limit changes are governed by PCF (product control file) settings at First Data. These
PCF settings specify the maximum credit limit allowed for any given card program and
are usually set at the system/prin level or system/prin/agent level. If a requested limit
exceeds these governing PCF limits, the limit change will not be made.
Page 614
Parameter Description Type Required / Length
Optional
BALANCE Current outstanding balance Numeric Required 13
on the account.
Format: 9999999999.99
Note: this is an exact
amount.
CL_INCREASE Amount of the adjustment Numeric Required 10
Format: 9999999999
Note this is a whole number
LETTER Request Letter to be sent to Alpha Optional 1
cardholder.
Valid Value= Y
NEWCREDITLINE Amount of the adjusted Numeric Required 10
Credit Line
Format: 9999999999
Note: this is a whole number
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
A full request to update the credit limit on an account (with a $750.27 outstanding
balance) from $1,000 to $1,500 will appear similar to the following:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=CLADJUSTXML&APPID=106&APPLICATIONID=102&REQUESTID=1
Page 615
02&FUNCTIONID=1424&CARDNUMBER=9999999999999999&CLIENTID=9999&CL_INCR
EASE=9999999999&NEWCREDITLINE=9999999999&BALANCE=99999999.99&LETTER=Y
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <CLADJUSTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1424</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME=”CARDTYPE”>Visa Classic</odsPscuTAG>
<odsPscuTAG NAME=”SPAID”>9999</odsPscuTAG>
<odsPscuTAG NAME=”SYSTEM”>9999</odsPscuTAG>
<odsPscuTAG NAME=”PRIN”>9999</odsPscuTAG>
<odsPscuTAG NAME=”AGENT”>9999</odsPscuTAG>
<odsPscuTAG NAME=”CHNAME”>LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME=”CHSECONDARY”>LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME=”ODSMESSAGE”>SUCCESS</odsPscuTAG>
<odsPscuTAG NAME=”ODSMESSAGE STATUS”>0</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="CLAPASSED">TRUE</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
Page 616
</PscuFS>
</V_OLCLASS>
</CLADJUSTXML>
</INVISION>
The following is an example of the XML response when the limit request was not
successful at First Data because it exceeded the maximum set in PCF for the card
program:
<INVISION>
- <CLADJUSTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1424</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME=”CARDTYPE”>Visa Classic</odsPscuTAG>
<odsPscuTAG NAME=”SPAID”>9999</odsPscuTAG>
<odsPscuTAG NAME=”SYSTEM”>9999</odsPscuTAG>
<odsPscuTAG NAME=”PRIN”>9999</odsPscuTAG>
<odsPscuTAG NAME=”AGENT”>9999</odsPscuTAG>
<odsPscuTAG NAME=”CHNAME”>LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME=”CHSECONDARY”>LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME=”ODSMESSAGE”>CREDIT LINE OUTSIDE CREDIT
LIMIT PARAMETERS</odsPscuTAG>
<odsPscuTAG NAME=”ODSMESSAGE STATUS”>1</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 617
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</CLADJUSTXML>
</INVISION>
Visa Classic
Visa gold
Visa Platinum
Visa Business
MasterCard Standard
MasterCard gold
MasterCard Platinum
MasterCard Business
Valid codes:
0 – Successful credit limit adjustment
Page 618
OdsPscu TAG NAME Description Type Length First
Data
Screen
1 – Failed credit limit adjustment
PRIN Principal Number Numeric 4 BS5
SPAID PSCU Internal Designation for the Numeric 5
System, Prin and Agent values
SYSTEM System Number Numeric 4 BS5
Page 619
13 PAYXML Request
The PAYXML Requests provide the ability to make payments to the cardholder account
using the Payment on Demand feature or Right Time Payment feature, Reverse a Right
Time Payment and execute a Balance Consolidation making a payment from the
cardholder account. Section 13 of this document provides a detailed description of each
PAYXML function along with the fixed, required and variable parameters, a sample
request and response, and a description of each node of the response.
Function ID Description
1410 Payment on Demand – Uses the Payment on Demand feature to post a
payment to the account on the First Data system. AutoPay must be active
for the Credit Union for this feature to be used.
1441 Right Time Payment – Uses the Right Time Payment feature to post a
payment to the account on the First Data system. The Credit Union must
be enrolled in Right Time Payment for this feature to be used. This
function is previously documented as a GETDATAXML function. Current
implementations using GETDATAXML will continue to work. It is requested
that future implementations use the PAYXML.
1447 Reverse Right Time Payment – Remove a Right Time Payment that was
posted to an account in the same day.
1439 Balance Consolidation – Provides the ability to transfer a cardholder’s
balance(s) from other financial institutions to the account with the Credit
Union. This function is previously documented as a GETDATAXML
function. Current implementations using GETDATAXML will continue to
work. It is requested that future implementations use the PAYXML.
1455 Automatic Payment – Provides the ability to set up autmatic payments on
a cardholders account. AutoPay must be set up at First Data for this
function to work.
1459 OneTime Future Payment – Submit one time future payment
1460 List One Time Future Payments – List of one time future payments
1461 Delete One Time Furture Payment – Delete an existing One Time Future
Payment
1470, 1471, eBalCon – Provides the functions necessary to support eBalCon solution.
1472
Page 620
PSCU – Propriety and Confidential Last Revised: 03/31/2023
Version 23.1
Page 621
13.1 Payment on Demand
The Payment on Demand Request provides the ability to enter a Demand Payment for a
cardholder. This functionality in the First Data system is associated with the First Data
AutoPay function. AutoPay must be active for the Credit Union for this feature to work.
The individual cardholder does not have to be an AutoPay user, however – if the
cardholder does use AutoPay, care should be exercised in using this functionality.
Certain changes may affect the source of the cardholder’s Autopay payment and change
future scheduled payments. The Demand Payment function is in addition to any
regularly scheduled AutoPay payments and does not change the AutoPay flag in place
on the cardholder’s account.
The Demand Payment feature supports a payment amount that is equal to or less than
the current balance on the account. The Demand Payment function can’t create a credit
balance and the First Data system will automatically adjust the requested amount down
if the system determines that processing the requested amount may create a credit
balance. Demand Payments are processed in the First Data system as the last Non-Mon
during the nightly batch cycle process. Other payments that were made during the day,
credits that posted during the day or other items that affect the balance can cause the
amount requested in the Demand Payment to be reduced.
Once a Demand Payment request is made, there is NO way to stop the payment
processing from happening during the next scheduled batch process at First Data.
Additionally, only the last Demand Payment request made in any First Data processing
window will actually be processed. If several Demand Payment requests are made in
the same processing window, the last request will be the one that is actually applied to
the account. For example, if a Demand Payment request is made at 7:00pm ET Friday
and another request is issued at 4:00pm Saturday and a third request is made at 5:00pm
Sunday – only the request made on Sunday will be processed. The others will be
ignored. The DEMANDPAYAMT field in the 1426 response will indicate whether or not a
payment has already been submitted for the current processing day.
To check the existing settings on the account, the first step is to execute a request to
obtain the data currently in the First Data System using the Data eXchange Payment on
Demand – Get Information request. This data is returned from a GETDATAXML request
with the FUNCTIONID of 1426. A sample request will appear as follows:
Page 622
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&REQUESTID=1
02&FUNCTIONID=1426&CLIENTID=9999&CARDNUMBER=9999999999999999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <PAYXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<odsPscuTAG NAME="CARDTYPE">Visa Classic</odsPscuTAG>
<odsPscuTAG NAME="SYSTEM">9999</odsPscuTAG>
<odsPscuTAG NAME="PRIN">9999</odsPscuTAG>
<odsPscuTAG NAME="AGENT">9999</odsPscuTAG>
<odsPscuTAG NAME="CHNAME">LAST,FIRST M</odsPscuTAG>
<odsPscuTAG NAME="CHSECONDARY">LASTTWO,FIRST
M</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYFLAG">X</odsPscuTAG>
<odsPscuTAG NAME="AUTOPAYRT">999999999</odsPscuTAG>
<odsPscuTAG
NAME="AUTOPAYDDA">99999999999999999</odsPscuTAG>
<odsPscuTAG
NAME="SHAREACCOUNT">99999999999999999</odsPscuTAG>
<odsPscuTAG NAME="DEMANDPAYCD">X</odsPscuTAG>
<odsPscuTAG
NAME="DEMANDPAYAMT">9999999999999.99</odsPscuTAG>
<odsPscuTAG
NAME="CURRENTBALANCE">9999999999999.99</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="ISALLOWEDACCESS">TRUE</odsPscuTAG>
<odsPscuTAG NAME="AUTOFLAGXFER">NONE</odsPscuTAG>
</COLLECTION>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
Page 623
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
If values are returned in the DEMANDPAYCD and DEMANDPAYAMT nodes, this indicates
that a current demand payment is pending at First Data and has not yet been applied to
the account. A new demand payment will overwrite this information if it is before the
daily cut-off.
After identifying the current settings for the DDA number, Routing & Transit number,
outstanding balance and the AutoPay Flag value, the Payment on Demand request can
be issued.
Valid format
$$$$$$$$$$$$$$$$.cc
AUTOPAYFLAG Autopay Flag from the Alphanumeric Required 1
response to the 1426
Page 624
Parameter Description Type Required / Length
Optional
request. If this value is not 0,
the TYPE will be set based
on the Payment Source
associated with the
AUTOPAYFLAG value.
Valid Values:
C – Checking Account
S – Savings Account, see
below for further details
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&TYPE=C&APPID=106&APPLICATIONID=102&REQUESTI
D=102&FUNCTIONID=1410&CARDNUMBER=9999999999999999&CLIENTID=9999&DDA
NBR=999999&RTNNBR=999999999&AMOUNT=99999.99&AUTOPAYFLAG=9&TYPE=C
The following is an example of the XML data provided from the URL above for
successful execution of a Payment on Demand request:
Page 625
- <INVISION>
- <PAYXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1410</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG
NAME="CONFIRMATION">SUCCESS<
/odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
In the event of a failed Payment on Demand request, the response will include a tag
name EXCEPTION that contains error information from the First Data system.
Page 626
13.1.3 Tag and Property Reference
It is possible to make a Payment on Demand request from a Savings account using the
existing Data eXchange functions as follows:
1. Execute the Payment on Demand – Get Information function 1426 to obtain the
current AutoPay Flag, Savings Account Number and Routing Number on the
cardholder account.
2. If the AutoPay Flag is set to a Checking Account option the Payment on Demand
from the Savings. Account cannot be done and the process should be aborted,
otherwise continue.
3. If the Savings Account needs to be changed from its current value, execute a
Data eXchange function 1435 with the appropriate parameters to set the Savings
Account number to the value to be used for the Payment on Demand.
4. Execute the Payment on Demand function as defined above with the TYPE
parameter set to S and the RTNNBR to the Routing Number for the Savings
Account. The DDANBR parameter must be the Checking account DDA number.
The current Data eXchange function 1410 to execute a Payment On Demand has
business logic embedded in the request that may not be desirable to new
implementations. The 1410 function only allows payment on demand from the checking
account on the account and resets the autopay flag value. In most implementations this
is fine. However, for those wanting to decouple the autopay flag from the payment on
demand the existing function does not work.
An alternative way to process the Payment on Demand is using the Data eXchange 1435
function for NonMon processing. The 1435 request can be used to set the checking,
savings and routing numbers and then issue the Demand ACH payment request with
NonMon 759.
NonMon 759 requires three parameters:
PARAM1=01 (always a value of 01)
Page 627
PARAM2= Amount of the payment
PARAM3=Code indicating which account to withdrawal the funds from: C for checking, S
for Savings.
NOTE: The checking, savings and routing numbers used for Payment On Demand are the
same numbers used for AutoPay processing. Extreme care should be taken when
modifying these values for an account with an AutoPay flag <> 0.
Page 628
13.2 Right Time Payment
Contact your PSCU Account Executive to enroll in the Right Time Payment application.
The Right Time Payment request enables cardholders to make payments through their
credit union and have the payment immediately impact their available credit and
delinquency status by posting an authorization on the account. The actual payment will
still be posted to the account in nightly batch processing of the payments file.
There is an option for RTP, where the “real” time payment posting, that will reflect the
payment in the current balance in real-time as well as the available credit. The In Store
attribute of the merchant number (on the MGI screen) will need to be set to S. If this
option is in use, the payment will not be included in the payment (TAPTRANS) file. It
will post automatically on the account during nightly processing. If the payment is
included in the payment file, the payment will double post to the account.
This function does not emulate any existing First Data 3270 transactions.
Page 629
Parameter Description Type Required / Length
Optional
Value Codes:
00 – Unknown (Default
Value)
01 – Teller
02 – ATM
03 – Retailer
04 – Online banking
05 – Mail
06 – Western Union
07 – 49 are reserved values
for future use at First Data
PYMTYPE Type of Payment Numeric Required 2
Value Codes:
00 – Unknown (Default
Value)
01 – Check
02 – Money Order
03 – Cash
04 – Credit Card
05 – Debit Card
06 – Electronic funds
transfer (EFT)
07 – Wire Transfer
08 – Coupon
09 – 49 are reserved values
for future use at First Data
TRANAMT Transaction Amount Numeric Required Up to 13
Format: digits
$$$$$$$$$$$$$$$¢¢
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
Page 630
to perform properly. It is requested that future implementations of this function use the
RQID=PAYXML
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&APPID=106&APPLICATIONID=102&FUNCTIONID=1441
&REQUESTID=102&CARDNUMBER=9999999999999999&MRCHNO=9999999999999999
&TRANAMT=9999999999999&PYMTSOURCE=99&PYMTYPE=99&CLIENTID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <PAYXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1441</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="AR_A_STAT">CMPLT</odsPscuTAG>
<odsPscuTAG NAME="AR_B_MSG_NMBR">1234</odsPscuTAG>
<odsPscuTAG NAME="AR_C_SEVERITY">X</odsPscuTAG>
<odsPscuTAG NAME="AR_D_REF_NMBR">9999</odsPscuTAG>
<odsPscuTAG NAME="AR_E_ACTION_CODE">X</odsPscuTAG>
<odsPscuTAG NAME="AR_F_AUTH_NMBR">1234</odsPscuTAG>
<odsPscuTAG
NAME="AR_G_PHONE">999999999999</odsPscuTAG>
<odsPscuTAG NAME="AR_H_ADD_ACTION_IND">X</odsPscuTAG>
<odsPscuTAG NAME="AR_I_TRANSFER_OPT">X</odsPscuTAG>
<odsPscuTAG NAME="AR_J_MSG_TEXT">This is a
message</odsPscuTAG>
</odsPscu:DATASTREAM>
Page 631
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Valid codes:
CMPLT – successful completion
ERROR – failed to complete
AR_B_MSG_NMBR System assigned identifier of any error Alpha
message Numeric
AR_C_SEVERITY Identifier of the severity of the error message Alpha
Numeric
AR_D_REF_NMBR Code representing whether the Numeric
authorization request went outside
First Data for processing
Any value greater than zero indicates
this authorization request was processed
outside First Data. To find out the result
of the authorization request you must
perform the AUTHREPLY RPC.
Value Codes:
00 – Unknown (Default Value)
01 – Teller
Page 632
OdsPscu TAG NAME Description Type Length First
Data
Screen
02 – ATM
03 – Retailer
04 – Online banking
05 – Mail
06 – Western Union
07 – 49 are reserved values for future
use at First Data
AR_E_ACTION_CODE* Code representing the action the System Alpha
will take on this account Numeric
AR_F_AUTH_NMBR Authorization code assigned by the Alpha
issuer Numeric
AR_G_PHONE Referral telephone number supplied by Numeric
the issuer
AR_H_ADD_ACTION_IND* Code identifying supplemental Alpha
information related to Numeric
@AR_E_ACTION_CODE
AR_I_TRANSFER_OPT Code representing the reason for Alpha
transferring an authorization call Numeric
AR_J_MSG_TEXT Message text-message indicating the Alpha
nature of the error
Page 633
13.3 Reverse Right Time Payment
Contact your PSCU Account Executive to enroll in the Right Time Payment application.
The Reverse Right Time Payment request enables cardholders to reverse a Right Time
Payment that was made the same day.
Value Codes:
00 – Unknown (Default
Value)
01 – Teller
02 – ATM
03 – Retailer
04 – Online banking
05 – Mail
06 – Western Union
07 – 49 are reserved values
for future use at First Data
Page 634
Parameter Description Type Required / Length
Optional
PYMTYPE Type of Payment Numeric Required 2
Value Codes:
00 – Unknown (Default
Value)
01 – Check
02 – Money Order
03 – Cash
04 – Credit Card
05 – Debit Card
06 – Electronic funds
transfer (EFT)
07 – Wire Transfer
08 – Coupon
09 – 49 are reserved values
for future use at First Data
TRANAMT Transaction Amount Numeric Required 13
Format:
$$$$$$$$$$$$$$$¢¢
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&APPID=106&APPLICATIONID=102&FUNCTIONID=1447
&REQUESTID=102&CARDNUMBER=9999999999999999&MRCHNO=9999999999999999
&TRANAMT=9999999999999&PYMTSOURCE=99&PYMTYPE=99&CLIENTID=9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <PAYXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
Page 635
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1447</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="AR_A_STAT">CMPLT</odsPscuTAG>
<odsPscuTAG NAME="AR_B_MSG_NMBR">1234</odsPscuTAG>
<odsPscuTAG NAME="AR_C_SEVERITY">X</odsPscuTAG>
<odsPscuTAG NAME="AR_D_REF_NMBR">9999</odsPscuTAG>
<odsPscuTAG NAME="AR_E_ACTION_CODE">X</odsPscuTAG>
<odsPscuTAG NAME="AR_F_AUTH_NMBR">1234</odsPscuTAG>
<odsPscuTAG
NAME="AR_G_PHONE">999999999999</odsPscuTAG>
<odsPscuTAG NAME="AR_H_ADD_ACTION_IND">X</odsPscuTAG>
<odsPscuTAG NAME="AR_I_TRANSFER_OPT">X</odsPscuTAG>
<odsPscuTAG NAME="AR_J_MSG_TEXT">This is a
message</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Page 636
OdsPscu TAG NAME Description Type Length First
Data
Screen
request succeeded or failed.
Valid codes:
CMPLT – successful completion
ERROR – failed to complete
AR_B_MSG_NMBR System assigned identifier of any error Alpha
message Numeric
AR_C_SEVERITY Identifier of the severity of the error Alpha
message Numeric
AR_D_REF_NMBR Code representing whether the Numeric
authorization request went outside
First Data for processing
Any value greater than zero indicates this
authorization request was processed
outside First Data. To find out the result of
the authorization request you must
perform the AUTHREPLY RPC.
Value Codes:
00 – Unknown (Default Value)
01 – Teller
02 – ATM
03 – Retailer
04 – Online banking
05 – Mail
06 – Western Union
07 – 49 are reserved values for future use
at First Data
AR_E_ACTION_CODE Code representing the action the System Alpha
will take on this account Numeric
AR_F_AUTH_NMBR Authorization code assigned by the issuer Alpha
Numeric
AR_G_PHONE Referral telephone number supplied by Numeric
the issuer
AR_H_ADD_ACTION_IND Code identifying supplemental Alpha
Page 637
OdsPscu TAG NAME Description Type Length First
Data
Screen
information related to Numeric
@AR_E_ACTION_CODE
AR_I_TRANSFER_OPT Code representing the reason for Alpha
transferring an authorization call Numeric
AR_J_MSG_TEXT Message text-message indicating the Alpha
nature of the error
Page 638
13.4 Balance Consolidation
DO NOT USE THIS FUNCTION FOR eBalCon. This function is solely for the eBalCon
VENDORS USAGE.
The Balance Consolidation function enables you to transfer a cardholder's balance from
an account with another lender to an account with your financial institution. A Balance
Consolidation can only be made on accounts that exist in the Cardholder Masterfile,
thus a balance consolidation is not available on an account the same day the account is
created. If the Balance Consolidation is attempted prior to the account existing in the
Cardholder Masterfile an error “INVALID ACCOUNT NUMBER”. This function emulates
the BC transaction.
The Balance Consolidation function enables you to transfer a cardholder's balance from
an account with another lender to an account with your financial institution. This
function emulates the BC transaction.
Page 639
Parameter Description Type Required / Length
Optional
field
ACTNCD Action code; this code Alpha Required 1
represents whether this is
an inquiry or a release
Valid Codes:
I – Inquiry prompts the
System to compare the dollar
amount of the check request
entered against the
cardholder CASH CREDIT or
TOTAL credit, the amount
available for balance
consolidation will be
returned in BAL_CNSL_AM
Page 640
Parameter Description Type Required / Length
Optional
Consolication will be process
for the amount of credit
available.
CHCKSEND Code representing where Alpha Required 1
the check should be mailed.
Valid Codes:
L – Lender
C – Cardholder
PAYEE Name of the lending Alpha Required Variable up
institution the cardholder to 26
wishes to pay through characters
balance consolidation
Page 641
Parameter Description Type Required / Length
Optional
institution is located set to L
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=PAYXML
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&APPID=106&APPLICATIONID=102&FUNCTIONID=1439
&REQUESTID=102&ACTNCD=X&CARDNUMBER=9999999999999999&PAYEE=XXXXXXXX
XXXXXXXXXXXXXXXXXX&PAYEEADDR=XXXXXXXXXXXXXXXXXXXXXXXXXX&PAYEECITY=XXX
XXXXXXXXXXXXXXX&PAYEESTATE=XX&PAYEEZIP=999999999&PAYEEACCT=XXXXXXXXXX
XXXXXXXXXXX&AMOUNT=999999999999999&CHCKSEND=C&TCKTRMS=XXXX&CLIENTI
D=9999
Page 642
The following is an example of the XML data provided from the URL above when a
successful Balance Consolidation request has been executed:
- <INVISION>
- <PAYXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1439</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="AVLB_CRDT_USE_CD">9999</odsPscuTAG>
<odsPscuTAG
NAME="BAL_CNSL_AM">9999999999999</odsPscuTAG>
<odsPscuTAG NAME="LNDR_INST_ADDR_TX">123 MAIN
ST</odsPscuTAG>
<odsPscuTAG
NAME="LNDR_INST_CITY_TX">ANYTOWN</odsPscuTAG>
<odsPscuTAG NAME="LNDR_INST_NM">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="LNDR_INST_ST_CD">FL</odsPscuTAG>
<odsPscuTAG
NAME="LNDR_INST_ZIP_CD">999999999</odsPscuTAG>
<odsPscuTAG NAME="LNDR_PI_ID">99999999</odsPscuTAG>
<odsPscuTAG NAME="PYMN_RFRN_CD">99999999</odsPscuTAG>
<odsPscuTAG
NAME="TOTL_AVLB_CRDT_AM">9999999999999</odsPscuTAG
>
<odsPscuTAG
NAME="CASH_AVLB_CRDT_AM">9999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
Page 643
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
The following parameters will be returned when the Action Code is sent as Inquiry.
OdsPscu TAG NAME Description Type Length First
Data
Screen
AVLB_CRDT_USE_CD Available credit use code – code Alpha 1
indicating whether cash or total
available credit was used when
analyzing the balance
consolidation
request
C - Cash available credit
T - Total available credit
BAL_CNSL_AM Amount of the account being Numeric 15
consolidated to the cardholder’s
account
CASH_AVLB_CRDT_AM Cash advance available credit limit
LNDR_INST_ADDR_TX Lender’s Street Address Alpha 26
LNDR_INST_CITY_TX Lender’s City Alpha 21
LNDR_INST_NM Lender Institution’s Name Alpha 21
LNDR_INST_ST_CD Lender’s State Alpha 2
LNDR_INST_ZIP_CD Lender’s Zip Code Numeric 5 or 9
LNDR_PI_ID Account number of the account Alpha 21
being consolidated to the
cardholder’s account
PYMN_RFRN_CD Payment reference code – code Alpha 1
indicating whether the balance
consolidation check will be denied,
or will be in the full or partial
Page 644
OdsPscu TAG NAME Description Type Length First
Data
Screen
amount of the request
D - Payment denied
F - Full payment
P - Partial payment
TOTL_AVLB_CRDT_AM Total available credit after the Numeric 16
consolidation
Page 645
13.5 Automatic Payments
The Automatic Payments function provides the ability to modify the current Automatic
Payments settings. This function will be used to set up automatic payments by
modifying the AutoPay flag to a value other than 0, and used to cancel automatic
payments by modifying the AutoPay flag to a value of 0.
The ability to use this function and the available AutoPay flags are dependent upon the
Credit Unions participation in AutoPay and the associated PCF settings. Data eXchange
will not validate participation or any of the data elements passed in the request.
If Terms & Conditions apply and the card holder must accept, the application must be
responsible for presenting and recording acceptance.
Page 646
Parameter Description Type Required / Optional Length
Format: $$$$$¢¢
PAYMENTTYPE Code representing whether Alpha Required 1
the cardholder account is set numeric
up for recurring automatic
payments.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&APPID=106&APPLICATIONID=102&FUNCTIONID=1455
&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&DDAACCOUN
T=99999999999999999&PAYMENTTYPE=X&ROUTINGNBR=999999999&SVGSACCOUNT
=99999999999999&PAYMENTAMOUNT=9900
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <PAYXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
Page 647
<ods:FUNCTIONID>1455</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</PAYXML>
</INVISION>
Page 648
13.6 eBalcon
There are three functions that support the eBalcon solution. eBalcon does require an
enrollment and PCF changes. Please contact your Service Executive prior to
implementation of these eBalcon functions.
Optional, use the Data eXchange 1471 request to confirm the entered
State and Zip are valid.
The UI should allow the user to enter multiple Balance Consolidation requests and
change them – amounts or delete before submitting.
Execute the 1472 Data eXchange request for each balance consolidation request using
the appropriate “RPPS” parameters for those lenders that are available as electronic, or
the “H” parameters for those vendors that are not available electronically.
Page 649
13.6.2 Lender Lookup
The Lender Lookup request looks up the lender in the RPPS tables and returns any and
all matches.
Please be aware that it is possible for multiple RPPS collections to be returned in this
response. When that occurs, this will need to be handled in the application so that the
appropriate RPPS biller ID is selected to ensure the correct biller is included in the 1472
request. There are multiple ways to handle this and it is up to the consuming application
to implement. A couple suggestions include:
1) Present all the returned billers to the user and allow the user to select which
one.
2) In the user interface, always capture the full address from the user prior to
submitting the 1470 function. Compare the address information returned by the
1470 function to the information provided by the user to find a match.
Page 650
Parameter Description Type Required / Length
Optional
the likelihood of obtaining
the one correct biller.
Format:
99999
99999-9999
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1470</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="BILLERSFOUND">X</odsPscuTAG>
<odsPscuTAG NAME="EXCEPTIONOCCURRED">X</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG
NAME="ADDR1">XXXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="ADDR2"> XXXXXXXXXXXXXXXXXXXXXXXXXX
</odsPscuTAG>
Page 651
<odsPscuTAG
NAME="CITY">XXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="CLASS">LASTNAME,FIRSTNAME</odsPscuTAG>
<odsPscuTAG NAME="RPPSID">99999</odsPscuTAG>
<odsPscuTAG
NAME="NAME">XXXXXXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG
>
<odsPscuTAG NAME="STATE">XX</odsPscuTAG>
<odsPscuTAG NAME="ZIP">999999999</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 652
OdsPscu TAG NAME Description Type Length
ODS View Parameter
STATE Lender’s State Alpha 2
ZIP Zip code Numeric 5/10
When the Biller is not found in the RPPS tables the state/zip combination is validated.
The only validation is that the zip code provided belongs to the state provided.
Page 653
02&FUNCTIONID=1471&REQUESTID=102&CLIENTID=9999&BILLERSTATE=XX
&BILLERZIPCODE=999999999&CARDNUMBER=9999999999999999&
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1471</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="RESULT">XXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 654
13.6.4 Submit eBalCon Request
The submit eBalCon request will send a Balance Consolidation request for processing.
Only one BalCon request is submitted – either a request to be processed via check or a
request to be processed via RPPS.
If the Balance Consolidations are processed as Cash Advances, as defined by PCF, and if
the available Cash Advance limit on the account is less than the available credit on the
account, also defined by PCF, and if the amount of the Balance Consolidation exceeds
the availabl Cash Advance limit on the account the Balance Consolidation will succeed
but the authorization and amount posted on the account as a result of the authorization
will be limited to the Cash Advance limit amount. Please take this into consideration
when working through the use case if the credit union uses these PCF settings.
Page 655
Parameter Description Type Required / Length
Optional
CCITY Card holder’s city Alpha Required 50
CSTATE Card holder’s state Alpha Required 2
CUSTOMERNAME Customer name Alpha Required 25
Format:
Lastname, Firstname
CZIP Card holder’s zip Numeric Required 5/10
Format
99999
99999-9999
FIRSTNMSUBMIT First name of the Alpha Required 18
submitter – user name
The combined length of
this field and the
LASTNMSUBMIT field
must be less than 25
HACCOUNTNMBR Account number of Alpha Numeric Required if Variable
lender to be paid by Minimum of 3 Harland up to 21
Harland digits
HAMOUNT Amount to send lender Number Required if 11
via Harland, Value must Harland
be greater than or
equal to 100
Format:
$$$$$$$$$¢¢
No decimal
HADDR1 Address Line 1 of Alpha Numeric Required if 26
Lender paid by Harland Harland
HBILLERNAME Lender’s Name Alpha Required if 26
Harland
HCITY Lender’s billing address Alpha Required if 50
Harland
HSTATE Lender’s billing state Alpha Required if 2
Harland
HZIP Lender’s billing zip Numeric Required if 5/10
Format: Harland
Page 656
Parameter Description Type Required / Length
Optional
99999
99999-9999
LASTNMSUBMIT Last name of submitter Alpha Required 18
– user name
The combined length of
this field and the
FIRSTNMSUBMIT field
must be less than 25
VENDORID PSCU assigned Vendor Numeric Optional 2-6
ID
Page 657
Parameter Description Type Required / Length
Optional
Lastname, Firstname
CZIP Card holder’s zip Numeric Required 5/10
Format
99999
99999-9999
FIRSTNMSUBMIT First name of the Alpha Required 18
submitter – user name
The combined length of
this field and the
LASTNMSUBMIT field
must be less than 25
LASTNMSUBMIT Last name of submitter Alpha Required 18
– user name
The combined length of
this field and the
FIRSTNMSUBMIT field
must be less than 25
RPPSACCOUNTNMBR Lender Account number AlphaNumeric Required if Variable
Minimum of 3 RPPS to 21
digits
RPPSAMOUNT Amount to pay Numeric Required if 11
Amount must be RPPS
greater than 100
($1.00)
Format:
$$$$$$$$$$$¢¢
No decimal
RPPSBILLERID ID of the Lender AlphaNumeric Required if 10
RPPS
RPPSBILLERNAME Lender’s Name AlphaNumeric Required if 26
RPPS
RPPSSTATE Lender’s State Alpha Required if 2
RPPS
RPPSZIPCODE Lender’s Zip Numeric Required if 5/10
Format: RPPS
Page 658
Parameter Description Type Required / Length
Optional
99999
99999-9999
VENDORID PSCU assigned Vendor Numeric Optional 2-6
ID
RPPS:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.
JServer.xml.xmlProcess&RQID=ACCTXML&APPID=106&APPLICATIONID=102&
FUNCTIONID=1472&REQUESTID=102&CLIENTID=9999&CADDR1=XXXXXXXX
XXXXXXXXXXXX&CADDR2=XXXXXXXXXXXXXXXXXXXX&CARDNUMBER=99999
99999999999&CCITY=XXXXXXXXXXXXXXXXXX&CSTATE=XX&CZIP=99999&FI
RSTNMSUBMIT=XXXXXXXX&LASTNMSUBMIT=XXXXXXXXXXXX&RPPSACCOUNT
NMBR=999999999999999&RPPSAMOUNT=99999999&RPPSBILLERID=99999&
RPPSBILLERNAME=XXXXXXXXXXXXXX&RPPSSTATE=XX&RPPSZIPCODE=99999
-9999&CUSTOMERNAME=XXXXXXXXXX&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
Page 659
<ods:FUNCTIONID>1472</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG
NAME="TRANSACTIONID">XXXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
If the data submitted is in error an error message will be returned. The following table
maps the error number to the data element in error.
Page 660
Error Number Data element
2000 Biller Id
2001 Biller Name
2003 Biller State
2004 Biller Zip Code
2005 Account Number
2006 Amount
3001 Biller Address
3002 Biller City
3005 Account Number
Duplicate submission – same biller, account, and
6000
amount within 1 hour
Duplicate submission of the balance consolidation
BALCON_NOT_AUTHORIZED
request within the past 1 hour
The CARDNUMBER entered in the request is a
INVALID ACCOUNT NUMBER
statused cardnumber.
HOME ADDRESS UPDATE NM NA screen, address did not pass PCF address
REQUIRED validations and needs to be updated
This error indicates the same balcon request –
Posting Balanace Consolidation amount, biller, biller account number – has been
Transaction failed submitted within the past 1 hour and is considered
an unintended duplicate
Page 661
13.7 Onetime Future Payments
The onetime future payment functionality allows members to schedule payments for a
future date. These payments are stored in a repository at PSCU. The payments are
processed as Payments On Demand (ACH Payments) on the day scheduled. The
payment will be made from the source account on the credit card record. The checking,
savings and routing numbers can all be updated with Data eXchange function 1435.
Please refer to Appendix K for the appropriate NM numbers for each.
This request will enter the One Time Future Payment into the PSCU repository for processing on
the date requested.
NOTE: At this time, this function cannot be tested in the Data eXchange pilot environment.
Valid format
999999999999999.99
PMNTDATE Date the payment is to be made Numeric Required 8
Valid format:
MMDDYYYY
TYPE Indicates which account (checking Alpha Required 1
or savings) the payment will be
made from
C-Checking
S- Savings
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
Page 662
13.7.1.2 Sample URL and Response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=PAYXML&APPID=106&APPLICATIONID=102&REQUESTID=102&F
UNCTIONID=1459&CARDNUMBER=9999999999999999&CLIENTID=9999&AMOUNT=99
99999999.99&PMNTDATE=MMDDYYYY&TYPE=C
The following is an example of the XML data provided from the URL above:
- <INVISION
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1459</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATIONNUMBER">9999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
This request will return all the future dated unprocessed payments submitted for One
Time Future Payments. Payments that have been posted or cancelled will not be
included in the response.
Page 663
.
The Function ID for this request is 1460.
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1460</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
Page 664
- <COLLECTION>
<odsPscuTAG
NAME="CONFIRMATIONNUMBER">9999999999999</odsPscuTAG>
<odsPscuTAG NAME="AMOUNT">99999999999.99</odsPscuTAG>
<odsPscuTAG NAME="PMNTDATE">MMDDYYYY</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 665
Parameter Description Type Required / Length
Optional
APPLICATIONID 102 Fixed Required 3
REQUESTID 102 Fixed Required 3
FUNCTIONID 1461 Fixed Required 4
CLIENTID PSCU assigned Client ID number Numeric Required 2–6
CARDNUMBER Credit Card Number Numeric Required 16
CONFIRMATIONNUMBER Confirmation number for the OTFP Numeric Required NA
payment
PMNTDATE The date the payment is scheduled Numeric Required NA
in the future.
Format:
MMDDYYYY
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1461</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 666
</ACCTXML>
</INVISION>
Page 667
14 SENDDATAXML Request
Numbered First Data NonMon Transactions
Please note, not all NonMon updates are reflected on the account in real-time. The
request will process in real-time but the update may not be reflected until the next day.
Function Description
ID
1435 Non-Monetary Transaction – Executes various .non-monetary
transactions on the cardholder’s account. Appendix K contains a table of
currently available non-monetary transactions.
Page 668
14.1 Non-Monetary Transaction
Page 669
Parameter Description Type Required / Length
Optional
Appendix K
&NONMONNBR=999&PARAM1=500&PARAM2=XYZ&PARAM3=A&PARAM4=94900
All named parameters must also then be preceded with “PARAM-“, followed by the
name of the parameter exactly as required by First Data. For instance to use PI NonMon
13 to set the number of plastics, the parameters PI_PLST_CD, CUST_ROLE_CD, and
MBR_SQNC_ID are required, thus the request would be:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&APPID=106&APPLICATIONID=102&REQUESTID=102&FUNCTIONID=143
5&CARDNUMBER=9999999999999999&CLIENTID=9999&RQID=SENDDATAXML&NONM
Page 670
ONNBR=13&PARAM-PI_PLST_CT=99&PARAM-CUST_ROLE_CD=9&PARAM-
MBR_SQNC_ID=99999&PINONMON=Y
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&REQUESTID=
102&FUNCTIONID=1435&CLIENTID=9999&CARDNUMBER=9999999999999999&NONM
ONNBR=999&PARAM1=XXX&PARAM2=XXX
The following is a sample response when the NonMon has been successfully executed
on the account. The STATUS CODE tag contains a value of zero (0) indicating success.
- <INVISION>
- <SENDDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1435</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu"
/>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SENDDATAXML>
Page 671
</INVISION>
In the event of a failure, the response will include a tag name EXCEPTION that contains
error information from the First Data system.
Page 672
14.1.3 Setting Alternate Addresses
First Data supports alternate addresses for billing and reference purposes for the
primary and secondary card holders. This data is stored and displayed on the NM*EA
screen in First Data. It is important to note that although multiple addresses can be
entered, there is only one primary “mailing” address for statements and cardholder
correspondence. To update the primary mailing address, refer to Section 10 –
CHUPDATEXML.
Non-Mon 698 has 30 different parameters that are submitted when adding or updating
an alternate address. Several of the parameters do not currently contain data, however
they must all be submitted for First Data to process the request. The Non-Monetary
Transaction parameters for NonMon 698 that include variable data are:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&REQUESTID=
102&FUNCTIONID=1435&CARDNUMBER=99999999999999999&CLIENTID=99999&NON
MONNBR=698&
PARAM1=00&
PARAM2=ROLE CODE& 01 for primary, 02 for secondary
PARAM3=Address indicator& RFRN – Reference or BLL1 - Billing
PARAM4=F&
PARAM5=&
PARAM6=&
PARAM7=&
PARAM8=&
PARAM9=&
PARAM10=&
PARAM11=Address Line 1&
PARAM12=Address Line 2&
PARAM13=&
PARAM14=&
PARAM15=City&
PARAM16=State Abbreviation&
PARAM17=3 char country code&
PARAM18=zip&
PARAM19=&
Page 673
PARAM20=&
PARAM21=&
PARAM22=&
PARAM23=T&
PARAM24=Effective Date& MMDDYYYY
PARAM25=End Date& MMDDYYYY
PARAM26=&
PARAM27=Member Sequence& 00001 – Primary, 00002 – Secodary
PARAM28=&
PARAM29=&
PARAM30=&
Page 674
PARAM25=MMDDYYYY& expiration date - 12311999 for permanent
PARAM26=&
PARAM27=&
PARAM28=&
PARAM29=&
Page 675
14.1.4 Travel Notifications
Travel Notifications for both Omaha and Wilmington accounts are accomplished by
suspending the fraud strategy during the duration of travel and posting a memo. The
fraud strategy suspension is achieved using NonMon 238 for Single Entity and PI
NonMon 782 for separate entity, documented in Appendix K. The memo is achieved
using function 1418, documented in section 10. Both of these transactions are posted
on the account in real-time. If the NonMon 238 does not contain a start date the
suspension also occurs in real-time.
There is only one location on the account to record the suspending of the fraud
strategy. This means if the account is already in a suspended strategy or has an
upcoming suspension scheduled sending another NonMon request will overwrite the
existing settings. There are two ways to handle this: 1) only allow the members to enter
one travel notification at a time or 2) create a repository to store all travel notifications
entered by the member. In the first scenario, the account summary function should be
called in advance to determine if there is data in the fraud suspension fields. In scenario
two, all channels (IVR, branch, etc) that accept travel notification information from the
member will need to access the repository.
When there is a need to change the travel information on the account record, simply
send the 1435 function with NonMon 238, or PI NonMon 782. The fraud suspension
information will be overwritten on the account with the parameters included.
When there is a need to cancel an upcoming travel notification, for single entity simply
send the 1435 function with NonMon 238 setting the strategy start date and end date to
the same value. For separate entity send the PI NonMon 782 , send the subtrans 48
with the same expiration date followed by the subtrans 47 with the standard fraud
strategy and the same start date.
Page 676
15 ESTMTXML
Contact your PSCU Account Executive to enroll in eStatements. An error of Unable to
locate the account with accountClass indicates the card program is not set up / configured in the
eMessenger platform for eStatements. Please reach out to your PSCU Service Executive for
assistance with enrollment or adding card programs to an existing enrollment.
Data eXchange only supports the electronic delivery of Super Cool Statements (SCS).
The ESTMTXML Requests provide the ability for a cardholder to enroll in eStatements,
modify and cancel enrollment, provide a list of available eStatements to the cardholder
and present the cardholder’s selected eStatement. Section 15 of this document provides
a detailed description of each ESTMTXML function along with the fixed, required and
variable parameters, a sample request and response, and a description of each node of
the response.
The testing of eStatement functionality in the Data eXchange pilot can be slightly
challenging based on the way the multiple platforms are maintained. Please contact
PSCU Product Architecture ([email protected]) to have accounts conditioned
properly for testing.
Function Description
ID
1608 eStatement Enrollment – Enrolls the cardholder into eStatements.
1609 Cancel eStatement Enrollment – Cancel the cardholder’s eStatement
participation.
1610 Modify eStatement Settings – Change the cardholder’s eStatement
settings.
1612 Available eStatements – Returns a list of the available eStatements.
1615 eStatement Presentment – Presents the cardholder selected eStatement.
1620 eStatement Enrollment Status – Returns the cardholder’s current
eStatement enrollment status.
NOTE: In previous versions of this document, the RQID for these functions was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
Page 677
to perform properly. It is requested that future implementations of these functions use
the RQID=ESTMTXML.
Page 678
15.1 eStatement Enrollment
The eStatment Enrollment request provides the ability for cardholder to enroll in the
SCS eStatement solution.
If Terms & Conditions apply and the card holder must accept, the application must be
responsible for presenting and recording acceptance.
Valid Code
2 - Electronic Statements
SRN N – Supress the Statement Fixed Optional 1
Ready Notification sent
when the account cycles
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
Page 679
to perform properly. It is requested that future implementations of this function use the
RQID=ESTMTXML.
This request will always enroll the cardholder in eStatements regardless of their current
eStatement enrollment status. The current eStatement enrollment status can be
checked using Data eXchange request 1620 prior to executing the eStatement
Enrollment request.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1608&EMAIL=my
[email protected]&ENROLLMENT_OPTION=2
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ESTMTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>0F990DD2-B120-F0FD-05D8-2C791699BF62</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1608</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="ENROLLED">TRUE</odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE">SCS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
Page 680
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Valid Codes:
SCS – SCS Statements from
eMessenger
Page 681
15.2 Cancel eStatement Enrollment
The Cancel eStatement Enrollment request cancel the cardholder’s enrollment in the
SCS eStatement solution.
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ESTMTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1609
The following is an example of the XML data provided from the URL above:
-<INVISION>
-<ESTMTXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
Page 682
<GUID>C0026248-AE5E-C24D-3885-87FCF833FD0F</GUID>
</VALIDATION>
-<V_OLCLASS>
-<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1609</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
-<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CANCELLED">TRUE</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Page 683
15.3 Modify eStatement Settings
The Modify eStatement Settings request provides the ability to modify the cardholder’s
eStatement settings.
Valid Codes:
2 - Electronic Statements
VENDORID PSCU assigned Vendor ID Numeric Optional 2-6
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ESTMTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1610&EMAIL=my
[email protected]&ENROLLMENT_OPTION=2
Page 684
The following is an example of the XML data provided from the URL above:
-<INVISION>
-<ESTMTXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>63E32822-E81E-5F75-AF7A-26DA9FCC0DB5</GUID>
</VALIDATION>
-<V_OLCLASS>
-<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1610</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
-<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="ENROLLMENT_MODIFIED">TRUE</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Valid Codes:
Page 685
OdsPscu TAG NAME Description Type Length First
Data
Screen
TRUE – Cardholder’s settings have been
modified
FALSE – Cardholder’s settings have not
been modified
Page 686
15.4 Available eStatements
The Available eStatements request returns a list of statements that are currently
available electronically. Up to twenty-four (24) months of eStatements may be available
and begin accruing at cardholder enrollment.
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ESTMTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1612&
-<INVISION>
-<ESTMTXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
Page 687
<GUID>63E32822-E81E-5F75-AF7A-26DA9FCC0DB5</GUID>
</VALIDATION>
-<V_OLCLASS>
-<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1612</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
-<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="ESTATEMENTS"/>
<odsPscuTAG NAME="NUM_STATEMENTS">9</odsPscuTAG>
-<COLLECTION>
<odsPscuTAG
NAME="DESTADDR”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CC</odsPscuTAG>
<odsPscuTAG
NAME="DOCID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC</
odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE”>SMS</odsPscuTAG>
<odsPscuTAG NAME="STMTDATE”>CCYY-MM-DD
HH:MM:SS</odsPscuTAG>
<odsPscuTAG NAME="FDRCLIENTID"/>9999</odsPscuTAG>
<odsPscuTAG
NAME="MSGID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC<
/odsPscuTAG>
</COLLECTION>
-<COLLECTION>
<odsPscuTAG
NAME="DESTADDR”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CC</odsPscuTAG>
<odsPscuTAG
NAME="DOCID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC</
odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE”>SMS</odsPscuTAG>
<odsPscuTAG NAME="STMTDATE”>CCYY-MM-DD
HH:MM:SS</odsPscuTAG>
<odsPscuTAG NAME="FDRCLIENTID"/>9999</odsPscuTAG>
Page 688
<odsPscuTAG
NAME="MSGID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC<
/odsPscuTAG>
</COLLECTION>
-<COLLECTION>
<odsPscuTAG
NAME="DESTADDR”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CC</odsPscuTAG>
<odsPscuTAG
NAME="DOCID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC</
odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE”>SMS</odsPscuTAG>
<odsPscuTAG NAME="STMTDATE”>CCYY-MM-DD
HH:MM:SS</odsPscuTAG>
<odsPscuTAG NAME="FDRCLIENTID"/>9999</odsPscuTAG>
<odsPscuTAG
NAME="MSGID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC<
/odsPscuTAG>
</COLLECTION>
-<COLLECTION>
<odsPscuTAG
NAME="DESTADDR”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CC</odsPscuTAG>
<odsPscuTAG
NAME="DOCID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC</
odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE”>SMS</odsPscuTAG>
<odsPscuTAG NAME="STMTDATE”>CCYY-MM-DD
HH:MM:SS</odsPscuTAG>
<odsPscuTAG NAME="FDRCLIENTID"/>9999</odsPscuTAG>
<odsPscuTAG
NAME="MSGID”>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC<
/odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 689
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Page 690
15.5.1 Request parameters
Valid Codes:
PDF
Format:
CCYY-MM-DD%20HH:MM:SS
Be sure to include the %20
STMTSOURCE Source for eStatements Alpha Required 3 / 10
Valid Codes:
SCS – SCS Statements from eMessenger
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
Page 691
to perform properly. It is requested that future implementations of this function use the
RQID=ESTMTXML.
The parameters to retrieve the eStatement for presentation are obtainable from the
Data eXchange 1612 function that returns a list of available eStatements and the
associated values.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1615&STMTDATE
=CCYY-MM-
DD%20HH:MM:SS&STMTSOURCE=XXXXXXXXX&OUTPUTTYPE=X&FDRCLIENTID=99999&
DESTADDR=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&DOCI
D=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&MSGID=XXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ESTMTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>D57427F9-B116-8A08-BA50-34AB83354C9A</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1615</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
Page 692
<odsPscuTAG
NAME="STMTDATA">JSVFIE1FRElBOiBQS1BNLkNIRDcyNkEuUERGT1VUMDEuWjY
xMTRMVkcu+YTdlTEE/ZSlIP0A6L1QtcjRxYzxDUG0qYUs7OC8rJ04vT0QxMnRPXlpe
dDx1L3IiQkgkS1ZvLzopKiJKL1Q+
…..
MF5SJTtLUSFTLPgpzdGFydHhyZWYKMTA3NTkxCiUlRU9GCg==</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Note: The STMTDATA portion of this response has been abbreviated for the sake of
space otherwise this portion of the document would be disportionately long. Please
refer to Section 15.5.4 for information on decoding the STMTDATA.
Below is a returned XML response data stream sample which will be sent to the
cardholder’s Credit Union. Note the encoded STMTDATA field. This code will not have
carriage returns as shown below; this is for documentation purposes only. This code will
appear as a single line of data in which the Credit Union will need to decode the Base64
encoding. This can be done with just one (1) line of code, if Java is being used. The CU
internal code must include the Apache Commons Codec library
(http://commons.apache.org/codec/ ), and then the byte array can be decoded as
shown below.
Page 693
byte decodedBytes[] =
org.apache.commons.codec.binary.Base64.decodeBase64(encoded
Bytes);
Afterwards, a byte array of binary PDF data can stream from the User's browser.
Here's the sample XML response:
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1615</ods:FUNCTIONID>
<ods:FUNCTIONRS>
<ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<COLLECTION>
<odsPscuTAG
NAME="STMTDATA">JVBERi0xLjQKJeLjz9MKMiAwIG9iaiA8PC9GaWx0ZXI
vRmxhdGVEZWNvZGUvTGVuZ3RoIDEyMzI+PnN0cmVhbQp4nJ1XTXPaSBC98y
v64EOSMq
DRN3vZGoRskxWCSALvVuUii7HRRkiUJNj4329LM2BIMMnQLluf7n7T3fP6K
e8oECWd/h0BgmfPeNn8lC+dYdQh7Tk+UWFg6xCtOx9AxqjjTOd+BOF8MqHB
Px+jfztu
9LsBLVU6IE2SYpvXkG/XT6w83DZ0QwfDUtCzrhhgEaLJQTGVFspsCsPp36A
RlZgAEZ3MKNx5oGmmRrpae/NgPvsPnuIszhN2HuuNeqsNlJ6pyEHRbemsTN
I8XW/XsI
lf1wyzs9z+COk6KJopDWUWVzx+vG4LdTYrNunZAzkoKm9O5zGM3DAChwajh
6k3cgOivw/lLRvLuD5TJcXoE6Wv2HJQCG9bGkV+DyI3cEMKj2PPwxt9Zx7I
OVN44xnY
gLgm9DL1YUaDvx6p3Gaybd42mJuZi6DC4Ty4571rEbNL1IEu58+6ovYZiys
G6/gbg9diWx76EY/xU8agLv6QA2Hyqs9CZ96dUCx90BS+vxhjyt8Dge/C3d
invjOmHo
RusBg7bigX11B/ogM5Bzov6ymDXM4eXS5LVlXgrOL8hf2JR5Z8g6fiew9mZ
dpwHhJOzF+SA6PKM0qcL6FmGdusipzt2bbIkfAQU/EM9Sqt4Lko1z0pKJbN
8zJidZys
0EvTExvYFGWdovcmasnqbZkfWmdbpfkLsDzJioot8WTHsmKDkArIcE+X6CP
O5TCYPB0GksJrBU8Ml8FaKHuikFyTfsXcfLOwxojtUpslNos94ipF76vSBG
VpgqDOz0
Page 694
puZyameDIr2S4tttW54XYdeVsqr7pTsmVaQ5au0zOD4SQOuVUQmgDEW6Fq2
yNpfVQnbys9RW6wWQpvAbqL06xlJu72EiS/2QgC0LZMVsh01XvvSgMyB5xt
fzk9he3L
IC6duFohNeyacp0FJQ9IiEHKcRQ7bKDkQvmI0BfikvOvC84DDe7d8GdAds8
icoCuEItHdkmsXafTTCEZv2xZ1ZBXhYwdl8tVkS0xVyErd+khFvZyV/zuM3
RRsl0H6F
g4egU2UoE46iJjeYvsJP0IxjDMrmFatrh1US1dJZRMIR8RxmOZ1kxu9pt7x
Tf1FyhnxqiLujCd0Ad6C74r50qIrIA1nbvPuKwYMYTCOv1GEHY66OX8CrER
BdQPqRPh
SuXUiiHERsgYVIdp0k5qHG3Avm+w7+N2wOLkvkvzdhegzChfkPjiLNlm7VO
5sWcIVSFIfc+JP/ivDgFwePNZPmH1qlgC7XHekgtKeEtRznUSwaTC6INryA
a1v/uI8j
SE2XTsRyE0xVyMIzkhr5vyam3o3o99f+zfw5B6LfE2pim3RDfkghtXqH6+W
JcGvjs6fqDbcqJZv0JIieCBO3LdyWl4OfbUNfmS78u8oGOPDj2e9SbtshSg
K79Z87tp
cNxmwfQ+oBP4MsdP4oY28BPS8+DrB6T3rx+Rf62uZalypK2JwR+VcY5SYtb
MkYMF7JmVrNlw/kFTjliVlOmmpZdfG9cTcojE5Fe0vqJiWflB2KdTpfGpLc
s8wKuwlR
03Wk/XMC3hA9DRQmyNG7WnDo5AGT1LlYKkCsY9ODCtQTPb/c9NBzbfeVbzV
7EVXW0HvufPYiRb0hDwG3ii26T9N0rIlFC6d9OYwPM/u7s7mgplbmRzdHJl
YW0KZW5k
b2JqCjQgMCBvYmo8PC9UeXBlL1BhZ2UvQ29udGVudHMgMiAwIFIvUGFyZW5
0IDMgMCBSL1Jlc291cmNlczw8L1Byb2NTZXQgWy9QREYgL1RleHQgL0ltYW
dlQiAvSW
1hZ2VDIC9JbWFnZUldL0ZvbnQ8PC9GMSAxIDAgUj4+Pj4vTWVkaWFCb3hbM
CAwIDcyMCAxMDA4XT4+CmVuZG9iago1IDAgb2JqIDw8L0ZpbHRlci9GbGF0
ZURlY29k
ZS9MZW5ndGggMTEwMz4+c3RyZWFtCnicpVhbb+I4FH7nV5yVVtrdkZo6ITf
6sjKJgayCg2yn3T5mGaZlBUHiMtL8+z3OhSEUWtw9iNaxk/Mdfzk3U/YIqH
nvfmSDja
NveKk/25feUPXsaowrDgxCF9S69zvMZJTDKOGURwlNQTLxmERM/qH+7TF1q
7LAqZRFT1IxqSCiIp5kacyE7cJlofP55lDugR/W/yy2D8d5z/Vc8AKCml3i
QWDbfTNT
nGZfF6SyTWW4RwbJCNQkkTBlUtIxAzqbMSokZBwiKUFGgjFumUHbzlXoi5K
Oc66YUEYooX99g5ek3aBM/jbD8Yx2c4Rhj4ybAbnkM0AsGU8MmXPCzwDxhD
MzHNv/1B
tShsQFgytvSGUKI/lLHdQMogkVY/YFYJikKYsh4eAQEp488KtN+pZvm6H7N
ZszkU0zlWQcIYc01YhmySNwzRy6I3yzXpbFygywf5tn0++LbfGyqF7Rpty/
rn7oSc5z
Page 695
mprhObc5eFwsKwiU2WK73HxdznHERMS40v4hFutiWS7LlyZdm3llQG7z/mG
xKsp5tWtR7Bf1pKCKvbmh9isjI/ym6jSOAkpQLkdMVIojKidHM4iFJaAden
rs40w71S
c/1/XIzIimWn1khEfeN+J03bE818wIv3YKOWNV3T1lGGa5QHIlkx8zYf8vJ
t4pltfkJCqScr/YLnb7i7fN54f1YYUe9NXMpBuLqNoW5a6Y75eb8jRw5L7Y
anvexEq1
+pm48clt0UvXVT9TyUkMxW0MnYVNfeMnQsgL6uoyIBDTZ+xU6BS7F9mNHug
6BmBvYvkOekj/noT3g/DnjBZiuR60Q0MX8pqi2i02WGNGmZhSXRcucHWa1N
DvzeqFR2
qnbR2xfvsNvQ8wO2znr8VusauQ/NCzQtwuLctDsdJ5db4o9/qxKrl1b27FN
yXBvVaJ33WYyyZFxe717c3mJoXkPZa6KK5X+0pb5o7l5x2SQOciM5N8o/6r
ltrurkGX
KQKL2L5rdlpwvTqY4uLHDpYlDJerlU4aNd4FjL5Zk+Q2vc3R/hF2KzoLRK/
F9uUNtX30VTP9TStzTf8ZU64VGvLTtC5qs0dXhW6Qy4dzdkIrMOOnP6j55x
lmAchGmD
fwQITHNDMtQSf84gyesxwm9BEtzbDlxTQzzHIeg1R5jHlH/gm0OveOJDwmk
gIe9uKkPraaAfvd2hBRDoxPKo7QBNEC/iZhlKtcsBYJs17Cx9hMxjBk48Ss
7++7nTga
5kkaa21qwhLRIuDZVmXi2YIxU3plirZQobD9x4yM1yAyarjZ/vmxBo/SJz8
c5BF2/tKCRG8XCxKj8ln/p3fDuwioahj/xQy006FENE0RFeue1hcScud53h
3R3VAm9K
vEjedSryH5ZjgftB1PbIjKmVb99PRk1Vuxomxq9hOBc3YE9fxgoM3nf8V4Z
eM30H9JSHTkoaR8prO3A5tv4Bytsd3Qrh6jtp3ZlLZqtDT2/AeZn8BXCmVu
ZHN0cmVh
bQplbmRvYmoKNiAwIG9iajw8L1R5cGUvUGFnZS9Db250ZW50cyA1IDAgUi9
QYXJlbnQgMyAwIFIvUmVzb3VyY2VzPDwvUHJvY1NldCBbL1BERiAvVGV4dC
AvSW1hZ2
VCIC9JbWFnZUMgL0ltYWdlSV0vRm9udDw8L0YxIDEgMCBSPj4+Pi9NZWRpY
UJveFswIDAgNzIwIDEwMDhdPj4KZW5kb2JqCjEgMCBvYmo8PC9UeXBlL0Zv
bnQvQmFz
ZUZvbnQvQ291cmllci9TdWJ0eXBlL1R5cGUxL0VuY29kaW5nL1dpbkFuc2l
FbmNvZGluZz4+CmVuZG9iagozIDAgb2JqPDwvQ291bnQgMi9UeXBlL1BhZ2
VzL0tpZH
NbNCAwIFIgNiAwIFJdPj4KZW5kb2JqCjcgMCBvYmo8PC9UeXBlL0NhdGFsb
2cvUGFnZXMgMyAwIFI+PgplbmRvYmoKOCAwIG9iajw8L1N1YmplY3QoKS9D
cmVhdGlv
bkRhdGUoRDoyMDA4MDcwMTE0MzQ0NC0wNCcwMCcpL1RpdGxlKEdlbmVyYXR
lZCBQREYgRG9jdW1lbnQpL0F1dGhvcihDaGVja0ZyZWUgaS1Tb2x1dGlvbn
MpL1Byb2
Page 696
R1Y2VyKGlUZXh0IDEuNCBcKGJ5IGxvd2FnaWUuY29tXCkpL0NyZWF0b3IoI
DUuNi4wKS9Nb2REYXRlKEQ6MjAwODA3MDExNDM0NDQtMDQnMDAnKT4+CmVu
ZG9iagp4
cmVmCjAgOQowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAwMDI4MDAgMDAwMDA
gbiAKMDAwMDAwMDAxNSAwMDAwMCBuIAowMDAwMDAyODg1IDAwMDAwIG4gCj
AwMDAwMD
EzMTUgMDAwMDAgbiAKMDAwMDAwMTQ3MiAwMDAwMCBuIAowMDAwMDAyNjQzI
DAwMDAwIG4gCjAwMDAwMDI5NDEgMDAwMDAgbiAKMDAwMDAwMjk4NSAwMDAw
MCBuIAp0
cmFpbGVyCjw8L0lEIFs8NjkzMjFkNjRhOGY3ZDZhNzA2ZjViZDFlZTFkMmU
1YTg+PDYyNzgwNTQ5ZjdlNmM5ZDE5NjEyMDJiMWE3MmIxMjU4Pl0vUm9vdC
A3IDAgUi
9TaXplIDkvSW5mbyA4IDAgUj4+CnN0YXJ0eHJlZgozMjAwCiUlRU9GCg==<
/odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
This is a partial sample of an SCS statement that has been decoded from an XML
response stream to an SCS eStatement URL request. This sample was not produced from
the above STMTDATA. The account number, logos and Credit Union information has
been masked for security reasons.
Page 697
PSCU – Propriety and Confidential Last Revised: 03/31/2023
Version 23.1
Page 698
15.5.6 Sample URL and response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1612
The following is an example of the XML data provided from the URL above:
-<INVISION>
-<ESTMTXML>
-<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>FEDF261C-70F1-7B0A-BADE-755A23E18FDA</GUID>
</VALIDATION>
-<V_OLCLASS>
-<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1612</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
-<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="ESTATEMENTS" />
<odsPscuTAG NAME="NUM_STATEMENTS">2</odsPscuTAG>
-<COLLECTION>
<odsPscuTAG
NAME="DOCID">ZzREaFRPOWx6OFFseTBoTHBrYzBwaGpEcEd3PQ==</odsPscuTA
G>
<odsPscuTAG NAME="FDRCLIENTID">9999</odsPscuTAG>
<odsPscuTAG
NAME="MSGID">PE9DTUQuMTA4MDcwOTIxNTYwOS41LjE5MjIyQHNydnNlZDA0
Pg==</odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE">SCS</odsPscuTAG>
Page 699
<odsPscuTAG NAME="STMTDATE">2008-07-09
00:00:00</odsPscuTAG>
<odsPscuTAG
NAME="DESTADDR">c2hhcmVkK2dlbmVyaWMvNDQyODY4MDAwMDkwMjQ5O
UBwc2N1NjExNA==</odsPscuTAG>
</COLLECTION>
-<COLLECTION>
<odsPscuTAG
NAME="DOCID">S0taYzMzQ2FGWjY2ZXEvbnJEU01qc3ZydFN3PQ==</odsPscuTAG
>
<odsPscuTAG NAME="FDRCLIENTID">9999</odsPscuTAG>
<odsPscuTAG
NAME="MSGID">PE9DTUQuMTA4MDcxMTIyNDIzNi4yNS4xOTIyMkBzcnZzZWQw
ND4=</odsPscuTAG>
<odsPscuTAG NAME="STMTSOURCE">SCS</odsPscuTAG>
<odsPscuTAG NAME="STMTDATE">2008-07-11
00:00:00</odsPscuTAG>
<odsPscuTAG
NAME="DESTADDR">c2hhcmVkK2dlbmVyaWMvNDQyODY4MDAwMDkwMjQ5O
UBwc2N1NjExNA==</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
-<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Page 700
OdsPscu TAG NAME Description Type Length First Data
Screen
eStatement document. Variabl
e
DOCID Document ID of the SCS eStatement Alpha Variabl
document e
FDRCLIENTID Credit Union’s FDR Client ID Numeric 4-5
MSGID Message ID of the SCS eStatement Alpha
document Variabl
e
NUM_STATEMENTS Number of eStatements available for Numeric 2
viewing
STMTDATE eStatement Date Datetim 21
e
STMTSOURCE Source for eStatements Alpha 3 / 10
Valid Codes:
SCS – SCS Statements from eMessenger
Page 701
15.6 eStatement Enrollment Status Request
The eStatement Enrollment Status request retrieves the current eStatement status of
the cardholder.
NOTE: In previous versions of this document, the RQID for this function was
GETDATAXML. Current implementations that use the RQID=GETDATAXML will continue
to perform properly. It is requested that future implementations of this function use the
RQID=ESTMTXML.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=ESTMTXML&APPID=106&APPLICATIONID=102&REQUESTID=102
&CARDNUMBER=9999999999999999&CLIENTID=9999&FUNCTIONID=1620
The following is an example of the XML data provided from the URL above:
<INVISION>
- <ESTMTXML>
- <VALIDATION>
Page 702
<RESPONSE>0</RESPONSE>
<GUID>4F49A188-BABD-8C77-8F19-2969CD9AB068</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1620</ods:FUNCTIONID>
-<ods:FUNCTIONRS>
-<ods:FUNCTIONDATARS>
-<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="ESTMTCUPARTICIPATION">0</odsPscuTAG>
<odsPscuTAG NAME="ESTMTCHOPTION">2</odsPscuTAG>
<odsPscuTAG NAME="ESTMTCUOPTION">4</odsPscuTAG>
<odsPscuTAG
NAME="ESTMTEMAIL">[email protected]</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ESTMTXML>
</INVISION>
Page 703
OdsPscu TAG NAME Description Type Length First
Data
Screen
c
Valid codes:
-1 – Not participating
0 – Cancelled participation
1 – Paper Statements
2 - Electronic Statements
3 – Both, paper and electronic
Statements
ESTMTCUOPTION Credit Union’s enrollment status Numeri 1 N/A
c
Valid codes:
-1 – Not participating
1 – Paper Statements only
2 – Electronic Statements only
3 – Both, paper and electronic
Statements
4 – Either, paper or electronic
Statements
ESTMTEMAIL Email address on record for card holder Alpha Variable NM EBP
if one exists, if not this tag will not be numeric
returned.
Page 704
16 DYOCXML
Contact your PSCU Account Executive to enroll in Design Your Own Card.
The DYOCXML Request provides the ability for a cardholder to participate in the Design
Your Own Card program. The Design Your Own Card program provides the Credit Union
members with the option to personalize their card(s) by using a personalized photo card
image.
This section of the document provides a detailed description of the DYOCXML Request
along with the fixed, required and variable parameters, a sample search request and
response, and a description of each node within the response.
Function ID Description
1700 Design Your Own Card – Redirect the Cardholder to the Design Your
Own Card program.
Page 705
16.1 Design Your Own Card (DYOC) Function
The Design Your Own Card Request establishes a session to the Design Your Own Card
web site that allows a member to build a personalized card.
If Terms & Conditions apply and the card holder must accept, the application must be
responsible for presenting and recording acceptance.
Page 706
Parameter Description Type Required/ Length
Optional
003-009 – Authorized User -
this value cannot exceed 009.
The maximum number of
accounts permitted to be set
up is 9.
* The Cardholder role for an Authorized User can be obtained using the 1423 function.
The value will be returned in the AUTHMBRSEQ tag.
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xml.xmlProcess&RQID=DYOCXML&APPID=106&APPLICATIONID=102&REQUESTID=102&
FUNCTIONID=1700&CARDNUMBER=9999999999999999&CLIENTID=9999&ORDERNAME
=JSmith&ORDERTYPE=001&DYOCPRICE=0
The following is an example of the XML data provided from the URL above:
<INVISION>
<DYOCXML>
<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>89F1F415-293C-DF43-68A2-40F2FFEB745E</GUID>
</VALIDATION>
<V_OLCLASS>
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
Page 707
<ods:FUNCTIONID>1700</ods:FUNCTIONID>
<ods:FUNCTIONRS>
<ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG
NAME="DYOC_URL">http://pscu.prod01.itsmyca.com?k=02765272-2cc1-43df-9292-
6704c2ef588c</odsPscuTAG>
<odsPscuTAG NAME="DESIGN_RESTRICTION">0</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</DYOCXML>
</INVISION>
Valid Codes:
0 – No restrictions
1 – Indicates a card has recently
been designed and processed.
Access to design a card again is
denied.
DYOC_URL The DYOC URL string to Myca that Alpha Variable n/a
returns a design session Numeri
c
Page 708
PSCU – Propriety and Confidential Last Revised: 03/31/2023
Version 23.1
Page 709
17 Alerts
Contact your PSCU Account Executive to enroll in the Alert solutions.
The ALERTXML Requests provides the ability for a cardholder to participate in the Alert
solutions.
This section of the document provides a detailed description of the ALERTXML Request
along with the fixed, required and variable parameters, a sample search request and
response, and a description of each node within the response.
Function ID Description
1476 Alert History
1477 Control History
1750 Visa Transaction Alerts – Provides the cardholder access to the Visa
Transaction Alerts website for enrollment and alert management.
1751 Member Alerts and Controls – Credit Union partipation in Member
Alerts and Controls
1752 Member Alerts and Controls – Cardholder participation in Member
Alerts and Controls
1753 Member Alerts and Controls – Add/Update cardholder participation in
Member Alerts and Controls
1754 Member Alerts and Controls – Add / Update alerts and controls to a
cardholder registration in Member Alerts and Controls
1755 Ondot Alerts and Controls - Create the subscription for the user,
update card list on subscription and deactivate all cards on the
subscription
1756 Ondot Alerts and Controls - Obtain session id required for other
functions
1757 Ondot Alerts and Controls - Update subscription with destination
information
1760 Ondot Alerts and Controls - Retrieve details for the registration
1758 Ondot Alerts and Controls - Retrieve list of available alerts and controls
1759 Ondot Alerts and Controls - Retrieve alerts and controls along with
thresholds and settings for a registration
Page 710
1762 Ondot Alerts and Controls - Set alerts and controls along with
thresholds and settings based on user selections
1765 Ondot Alerts and Controls - Retrieve notifications previously sent to
user
ATTENTION: The Member Alerts and Controls solution will be sunset by Fiserv / FD and
PSCU in March 2023. At this time, PSCU is no longer enrolling financial institutions in
this solution. The Data eXchange functions will remain in the spec for reference to those
vendors and financial institutions that have previously implemented this solution. These
functions will be removed from this document when the Member Alerts and Controls
solution is sunset.
Enrollment in the PSCU Member Alerts and Controls solution is required. Please contact
your Account Executive for pricing and enrollment procedures.
These services support Member Alerts & Controls for both Omaha and Wilmington
accounts.
When converting from the FD hosted site for Wilmington / debit Alerts & Controls,
please contact you Service Executive to open a ticket. A configuration change at FD and
PSCU is required for the Data eXchange functions to work.
For assistance in design and development using the Data eXchange functions, please
contact PSCU Product Architecture ([email protected])
If Terms & Conditions apply and the card holder must accept, the application must be
responsible for presenting and recording acceptance.
These functions do not support the Ondot Alerts and Controls solution offered by
PSCU.
1. Get existing accounts for associated with a credit card (function 1752
REQUESTTYPE=LIST)
Page 711
2. If no accounts exist
a. Get client’s participation (function 1751)
b. Collect registration information and alert preferences and thresholds (not a DX
function)
c. Submit new registration and destination information (function 1753)
d. Submit preferences (function 1754)
3. If accounts exist, Get account participation (function 1752 REQUESTTYPE=ALL)
a. Collect alert preferences and thresholds (not a DX function)
b. Add / Update / Delete preferences (function 1754)
This function is used to obtain the Alerts and Controls that the credit union is enrolled
in.
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ALERTXML>
- <VALIDATION>
Page 712
<RESPONSE>0</RESPONSE>
<GUID>37CCE46C-D312-CBBF-D7FA-67B27B671CC4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1751</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEAREA">XXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCENAME">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X9999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID">X999X99</odsPscuTAG>
<odsPscuTAG
NAME="THREHOLDNAME">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="THREHOLDREQUIRED">XXXXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEAREA">XXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCENAME">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X9999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDSEQ1">99</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDREQ1">99</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID1">X999X99</odsPscuTAG>
<odsPscuTAG
NAME="THREHOLDNAME1">XXXXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEAREA">XXXXX</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCENAME">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X999</odsPscuTAG>
<odsPscuTAG
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 713
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
NOTE: If there are multiple thresholds for a given preference the response will contain a
collection (above) for each threshold repeating the Preference information in each
collection.
Page 714
OdsPscu TAG NAME Description Type Length
Preference
THRESHOLDSEQ1 Sequence number for the threshold 2 Numeric Up to 10
– if there is a second threshold for
the Preference
This function is used to obtain the cardholders registration status and if the cardholder
is already enrolled, this request will return the alert preferences the cardholder has
selected.
Page 715
The following is an example of the XML data provided from the URL above when the
REQUESTTYPE=LIST:
- <INVISION>
- <ALERTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>37CCE46C-D312-CBBF-D7FA-67B27B671CC4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1752</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
<odsPscuTAG
NAME="REGISTRATIONSTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG
NAME="ACCOUNTNAME">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="REGISTRATIONID">999999999999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="REGISTRATIONSTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG
NAME="ACCOUNTNAME">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="REGISTRATIONID">999999999999999999</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
Page 716
If the account is not registered the following response will be returned:
<INVISION>
<ALERTXML>
<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>4A8B3A68-40BE-AB72-6CD4-42473C7EED63</GUID>
</VALIDATION>
<V_OLCLASS>
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1752</ods:FUNCTIONID>
<ods:FUNCTIONRS><ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu"/>
</ods:FUNCTIONDATARS>
<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
The following is an example of the XML data provided from the URL above when the
REQUESTTYPE=ALL
- <INVISION>
- <ALERTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
Page 717
<GUID>37CCE46C-D312-CBBF-D7FA-67B27B671CC4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1752</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
<odsPscuTAG
NAME="DESTINATIONSTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG NAME="DESTINATIONMODE">XXX</odsPscuTAG>
<odsPscuTAG
NAME="DESTINATIONADDRESS">9999999999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREFERENCESTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEAREA">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X9999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDSEQ1">9</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID1">X9999999</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME1">XXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDVALUE1">XX9999999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDREQ1">XXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREFERENCESTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEAREA">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X9999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDSEQ1">9</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID1">X9999999</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME1">XXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDVALUE1">XX9999999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDREQ1">XXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
Page 718
<odsPscuTAG
NAME="PREFERENCESTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEAREA">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X9999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDSEQ1">9</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID1">X9999999</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME1">XXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDVALUE1">XX9999999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDREQ1">XXXXXXXX</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="PREFERENCESTATUS">ACTIVATED</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEAREA">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCEID">X9999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDSEQ1">9</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID1">X9999999</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME1">XXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDVALUE1">XX9999999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDREQ1">XXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDSEQ2">9</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID2">X9999999</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME2">XXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDVALUE2">XX9999999</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDREQ2">XXXXXXXX</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
Page 719
NOTE: If there are multiple thresholds for a given preference the response will contain a
collection (above) for each threshold repeating the Preference information in each
collection.
Page 720
OdsPscu TAG NAME Description Type Length
OPTIONAL
THRESHOLDREQ2 Indicates if the threshold is required- Alpha 8
if there is a second threshold for the
Preference
Values:
REQUIRED
OPTIONAL
THRESHOLDSEQ1 Sequence identifier for the Numeric Up to 10
Threshold– if there is a threshold for
the Preference
THRESHOLDSEQ2 Sequence identifier for the Numeric Up to 10
Threshold- if there is a second
threshold for the Preference
When the destination mode is SMS and the address is entered as a ten digit phone
number, FD adds a +1 to the address. If an update request is submitted to change the
address and the value is the same as the value currently on the registration, the
registration will return to a pending status but no SMS message will be sent out to
change the status from “Pending” to “Active”. Be sure any code to update a registration
takes this into consideration.
Page 721
17.1.4.1 Request Parameters
Parameter Description Type Required/ Length
Optional
RQID ALERTXML Fixed Required 11
APPID 106 Fixed Required 3
APPLICATIONID 102 Fixed Required 3
REQUESTID 102 Fixed Required 3
FUNCTIONID 1753 Fixed Required 4
CLIENTID PSCU assigned Client ID Numeric Required 2–6
number
CARDNUMBER Card Number Numeric Required 20
ACCOUNTNAME Alerts account name as Aplha Required 20
defined by cardholder Numeric
DEACTIVATE Y-Deactivate registration Fixed Optional 1
DESTINATIONMODE Values: Alpha Required 3/5
EMAIL – delivery of alerts
through email
SMS – delivery of alerts to
mobile
DESTINATIONADDR Email address or mobile Alpha Required Upto 50
number Numeric chars for
email; 10
digits for
mobile
number
REGISTRATIONID Identifier of the account Alpha Required to 18
registration obtained from Numeric update an
function 1752 with existing
REQUESTTYPE=LIST Registration
or
deactivating
a registration
The following is an example of the XML data provided from the URL above:
- <INVISION>
- <ALERTXML>
- <VALIDATION>
Page 722
<RESPONSE>0</RESPONSE>
<GUID>37CCE46C-D312-CBBF-D7FA-67B27B671CC4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1753</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
<odsPscuTAG
NAME="REGISTRATIONID">999999999999999999</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
If an Alert is added or updated and requires a threshold, the action will fail if the
necessary threshold(s) is not also provided in the request.
Page 723
Only optional thresholds can be deleted from an active alert.
Page 724
Parameter Description Type Required/ Length
Optional
associated with an alert there are two
thresholds
for the alert
THRESHOLDSEQ1 Sequence identifier for the Numeric Required if Up to 10
threshold there is a
threshold
associated
with the
Preference
THRESHOLDSEQ2 Used when the threshold Numeric Required Up to 10
requires a pair of values such when the
as start time and end time. threshold
requires a
pair of
values
THRESHOLDVALUE1 Value of the threshold Alpha Required if Variable
Numeric there is a
threshold
associated
with the
Preference
and the
Preference
is being
added or the
value being
updated
THRESHOLDVALUE2 Used when the threshold Required
requires a pair of values such when the
as start time and end time. threshold
requires a
pair of
values
The following is an example of the XML data provided from the URL above:
Page 725
- <INVISION>
- <ALERTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>37CCE46C-D312-CBBF-D7FA-67B27B671CC4</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1753</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
Page 726
17.1.6 Alert History
This function will return a the history of alerts delivered to the cardholder.
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1476</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME=" EVENTTYPE ">XXXXXX</odsPscuTAG>
Page 727
<odsPscuTAG NAME=" ALERTDESC
">XXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" ALERTDT ">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME=" ALERTTM ">HHMMSS</odsPscuTAG>
<odsPscuTAG NAME=" ALERTST ">XXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" ALERTMSG
">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</odsPsc
uTAG>
<odsPscuTAG NAME=" DELIVRYADNM ">XXXXX</odsPscuTAG>
<odsPscuTAG NAME=" DELIVERYAD ">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" DELIVERYMODE ">XXXXX</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 728
OdsPscu TAG NAME Description Type Lengt First
h Data
Scree
n
DELIVERYAD Delivery Address Alpha 50 ALH
Numeric
DELIVERYMODE Deliver mode Alpha 5 ALH
SMS
EMAIL
Page 729
17.1.7 Control History
Add a new Data exchange that will return the control history for a cardnumber. This will
be an addition to the Host & Props libraries, both Sybase and M-Queue.
SELECT EVNT_TYPE_CD, CNTL_DT, CNTL_THRS_1_TX
FROM CONSUMER_CONTROL_HISTORY
WHERE ENTR_ID = "0220020039140001"
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1477</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
Page 730
<odsPscuTAG NAME=" EVENTTYPE ">XXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" CONTROLDESC
">XXXXXXXXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME=" CONTROLDT ">YYYYMMDD</odsPscuTAG>
<odsPscuTAG NAME=" CONTROLTM ">HHMMSS</odsPscuTAG>
<odsPscuTAG NAME=" CONTROLST ">XXXXXXX</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 731
17.1.8 Omaha (credit/debit) Alerts / Preference Definitions
The following table contains the Omaha credit / debit Alert / Preference ID, description,
and associated thresholds. Only those Alerts/Preferences that the credit union is
enrolled in will be available. Please confirm which credit alerts the credit union has
enrolled in through their PSCU enrollment.
Page 732
(outside “everyday”
alert category. This alert
will trigger for any MCC
EXCEPT 5411,5451,5462,
5499, 5542, 5541, 5912,
7523. )
AUTHS A0007 Time of day State time in End time in
central time central time
Format Format
HH:MM HH:MM
AUTHS A0008 Online activity NA NA
AUTHS A0009 Authorization declined NA NA
AUTHS A0010 Fuel dispenser NA NA
AUTHS A0011 Out of State State Code 1 State Code 2
Format: Format:
Two Character Two
abbreviation Character
abbreviation
AUTHS A0012 Declined due to NA NA
cardholder activated
control
AUTHS A0013 Balance Transfer NA NA
AUTHS A0014 Card not present NA NA
CYCL C0001 Payment due Number of NA
days prior to
payment due
date. Valid
values are 3 –
20.
CYCL C0002 Past due at cycle NA NA
CYCL C0003 Overlimit at cycle NA NA
CYCL C0004 Balance at cycle NA NA
E0001* New user enrolled in NA NS
Alert registration
E0002* Alert Preference change NA NA
E0003* User enrolled in Alert NA NA
registration deleted
Page 733
E0005* Modification to Alert NA NA
registration
NONMON N0001 Name change NA NA
NONMON N0002 Address change NA NA
NONMON N0003 Home or business phone NA NA
change
NONMON N0004 Email address change NA NA
NONMON N0007 SSN change NA NA
The following table contains the Omaha (credit / debit) Controls / Preference ID,
description, and associated thresholds. Please confirm which credit controls the credit
union has enrolled in through their PSCU enrollment.
Preference Alert / Description Threshold 1 Threshold 2
Area Preference
ID
AUTHCNTRL AC000 Card on/off NA NA
This will block all
authorizations EXCEPT
for those that are
considered “pre-auths”
for recurring
payments, such as
monthly Netflix
membership.
AUTHCNTRL AC001 Large Transaction Amount NA
Format:
Whole Dollar
AUTHCNTRL AC002 International NA NA
transaction
determined by
merchant’s POS
location
AUTHCNTRL AC005 Merchant State List State 1 State 2
Format: Format:
Page 734
Two Character Two Character
abbreviation abbreviation
AUTHCNTRL AC009 Internet transactions NA
AUTHCNTRL AC010 Time of day range Start time End time.
Format: Format:
HH:MM HH:MM
The following table contains the Wilmington (debit/credit) Alert / Preference ID,
description, and associated thresholds. Only those Alerts/Preferences that the credit
union is enrolled in will be available. Please confirm which credit alerts the credit union
has enrolled in through their PSCU enrollment.
Preference Alert / Description Threshold 1 Threshold 2
Area Preference
ID
DBTAUTH D0001 International
Transactionn
determined by
merchant’s POS
location
DBTAUTH D0005 Online Transactions
DBTAUTH D0006 Declined Transactions
DBTAUTH D0008 Withdrawal More than
amount
Whole Dollar
DBTAUTH D0009 Transfer More than
amount
Whole Dollar
DBTAUTH D0010 PIN Purchase More than
amount
Whole Dollar
DBTAUTH D0012 Deposit
DBTAUTH D0013 Deposit with cash back
DBTAUTH D0014 Balance Inquiry
DBTAUTH D0015 Transaction greater More than
than amount
Page 735
Whole Dollar
Page 736
17.2 Ondot Alerts and Controls
Enrollment in the PSCU Ondot offering must be completed prior to the use of these Data
eXchange functions. Please contact PSCU Account Executive to initiate the enrollment.
Once the enrollment is submitted, PSCU web implementation project manager will set
up the credit union in the PSCU Ondot solution as well as provide solution overview and
training of the administrative tool. At completion of implementation, these Data
eXchange functions will begin returning information.
OnDot Hierarchy
Subscriber ID 1 Subscriber ID 2
Unique identifier for Unique identifier for
the subscriber. the subscriber.
PSCU PSCU
implementation will implementation will
use application use application
login with Client ID login with Client ID
appended to end appended to end
Page 737
17.2.1 Terms and Conditions
PSCU strongly recommends that the application present Terms and Conditions to the
user for acceptance. PSCU can provide sample language that is being used in our
applications as a reference. The acceptance or decline of the Terms and Conditions
should be recorded in an internal repository in the event of an audit.
Used to create new users / registrations in the Ondot product. It is up to the consuming
application to determine which accounts qualify for registration. For example an
account in a closed status (includes B (Bankrupt), C (Closed), E (Revoked), L (Lost), U
(Stolen), Z (Charged off)), and has a plastic count will not be accepted in the registration.
The API will return a successful response when card numbers for these statused
accounts are included in the response. However, the backend validation process
between Ondot and FD will immediately remove these cards from the registration.
If the SUBSCRIBERID already exists, the card numbers in the request will be appended to
the current card numbers associated with the subscriber ID if ADDLCARDS=True. If the
SUBSCRIBERID already exists and the ADDLCARDS=False, the card numbers in the
request will replace the card numbers on the subscription.
If a subscription is deactivated, it can be reactivated by adding registering the valid user
again.
A successful registration may result in the policy being set with ALL alerts (A030) or
NONE alerts (A029). It is recommended that this preference be disabled immediately
after the subscription is created for each card in the subscription using function 1762. If
this is done when the subscription is created it eliminates processing further
downstream. The Get Policy and Set Policy functions will support this.
Warning alerts will be sent to all registrations even if no alerts are enabled in the
registration. Warning alerts are sent when a transaction is declined for any reason and
when the card status changes from an active (normal) status to an inactive (lost, blocked
by defense edge, closed, etc) and vice versa.
Separate Entity consideration – There is a setting within Ondot known as the “Multi-
Card method”. If this setting is “Standard” then all PIIDs associated with the account will
be included in the registration. If this setting is “Explicit” then only the PIID included in
the CARDNUMBERS list will be included based on the ADDLCARDS function
The exception trapping for both SUBSCRIBER_801 and LOGIN_103 is recommended as
both of these indicate subscriber does not exist.
Page 738
When the FI is processing credit and debit with PSCU and the debit card program is
processed on the Wilmington/Star Station platform it is recommended that a subscriber
be created for each platform. This will allow the ability to remove a card from one of the
subscriptions in the future should the user elect to do so.
Page 739
Parameter Description Type Req / Length
Opt
subscription. No error will be
returned.
ADDLCARDS True - add the cards in the Alpha Req 4/5
CARDNUMBERS list
False – Set the list to the
CARDNUMBERS parameter
Default is false.
Page 740
17.2.2.2 Sample URL and Response
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=ALERTXML&APPID=106&APPLICATIONID=102&FUNC
TIONID=1755&REQUESTID=102&CARDNUMBERS=9999999999999999,999999999
9999999&CLIENTID=9999&SUBSCRIBERID=CCCCCCCCCCCCCCC&ENCRYPT=N&ADD
LCARDS=CCCCC&
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1755</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">XXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
17.2.2.4 Exceptions
ID MESSAGE_CODE MESSAGE
Page 741
Services unavailable. Please try again later or contact
Customer Support
238 LOGIN_105 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
An error occurred while changing the card setting. Please try
again later or contact Customer Support
<ONDOT_INFO>FI_CONTACT</ONDOT_INFO>.
159 SUBSCRIBER_801 This error may also indicate the subscriber ID does not exist.
Page 742
17.2.3.1 Request Parameters
Parameter Description Type Req / Length
Opt
RQID ALERTXML Fixed Req 10
APPID 106 Fixed Req 3
APPLICATIONID 102 Fixed Req 3
REQUESTID 102 Fixed Req 3
FUNCTIONID 1757 Fixed Req 4
CLIENTID PSCU assigned Client ID number Numeric Req 2–6
CARDNUMBER Card number to for the decode Numeric Req 16
process
EMAIL Email address for delivery of alerts Alpha Opt Up to 24
%20 to remove email for subscriber numeric
FULLNAME Full Name of subscriber Alpha Opt
PHONENUMBER Phone number for delivery of Alerts Numeric Opt 10
%20 to remove phone number for
subscriber
SESSIONID Session ID obtained from Create Alpha Req Up to 100
Session function Numeric
SUBSCRIBERID Subscriber ID Alpha Req Unlimited
Case sensitive Numeric
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
Page 743
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1757</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">XXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
17.2.3.4 Exceptions
ID MESSAGE_CODE MESSAGE
47 CARD_200 Card details have been updated successfully.
An error occurred while updating the card information. Please
try again later or contact Customer Support
166 CARD_201 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
144 LOGIN_108 Your current session has expired. Please log in again.
We are unable to process your request right now. Please try
again later or contact Customer Support
4 LOGIN_109 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
Page 744
17.2.4 Process Flow
The following Data eXchange functions will be created and used to integrate the Ondot
solution into a third party online and/or mobile banking solutions.
1. Register Valid User -
This function will be used to create a new subscriber on the Ondot platform, and to
update the card numbers associated with the subscription. When the card number(s)
are added to a subscription (creating the subscription or updating the subscription), the
card reference IDs are generated by Ondot.
2. Create Session
This function is required for all Ondot DX functions except those listed in #1-3. A session
is required to interact with the Ondot platform.
3. Update Registration
This function is used to associate destination addresses (mobile number, email address)
to an existing subscription. If both mobile number and email address are set on a
registration (subscription), Ondot will first send any alert notification to the mobile
number. If that fails then Ondot will deliver the alert notification to the email address.
4. Get Assets
This function will retrieve the list of all the available alerts and controls.
5. Get Registration Details
This function will retrieve the destination addresses associated with an existing
subscription.
6. Get Policy
This function will retrieve the current policy (alerts and controls) settings for a
subscription.
7. Update Alert Policy
This function will update the alerts and controls associated with an existing subscription.
A session ID is required for all functions except Create Registrar and Get Assets. A session ID is valid for 15
minutes.
It is recommended that exception trapping for both SUBSCRIBER_801 and LOGIN_103 as
both of these indicate subscriber does not exist.
Page 745
Parameter Description Type Req / Length
Opt
APPID 106 Fixed Req 3
APPLICATIONID 102 Fixed Req 3
REQUESTID 102 Fixed Req 3
FUNCTIONID 1756 Fixed Req 4
CLIENTID PSCU assigned Client ID number Numeric Req 2–6
CARDNUMBER Card number used for the decode Numeric Req 16
process only
SUBSCRIBERID Subscriber Id - Unique ID for the Alpha Req Unlimited
registration. This value must be Numeric
unique within the PSCU OnDot
implementation
Case sensitive
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1756</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="SESSIONID">XXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="SUBSCRIBERID">XXXXXXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
Page 746
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
17.2.5.4 Exceptions
ID MESSAGE_CODE MESSAGE
Services unavailable. Please try again later or contact
Customer Support
238 LOGIN_105 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
An error occurred while changing the card setting. Please try
again later or contact Customer Support
<ONDOT_INFO>FI_CONTACT</ONDOT_INFO>. This error may
159 SUBSCRIBER_801 also indicate the subscriber does not exist.
Login Failed. Please enter a valid username and password. This
could be caused if the FI is not yet set up in Ondot or if the
71 LOGIN_103 Subscriber does not yet exist.
The Get Registration Details function retrieves registration information associated with
the subscriber ID.
Page 747
17.2.6.1 Request Parameters
Parameter Description Type Req / Length
Opt
RQID ALERTXML Fixed Req 10
APPID 106 Fixed Req 3
APPLICATIONID 102 Fixed Req 3
REQUESTID 102 Fixed Req 3
FUNCTIONID 1760 Fixed Req 4
CLIENTID PSCU assigned Client ID number Numeric Req 2–6
CARDNUMBER Card number – required for DX Numeric Req 16
validation steps
SUBSCRIBERID Subscriber ID Alpha Req Unlimited
Case sensitive Numeric
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1760</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="SUBSCRIBERID">CCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="FULLNAME">CCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="PHONENUMBER">9999999999</odsPscuTAG>
<odsPscuTAG NAME="DEVICEUNIQUEID">XXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="SUPPRESSION">CCCCC</odsPscuTAG>
<odsPscuTAG
NAME="SUPRESSIONSTART">9999999999999</odsPscuTAG>
Page 748
<odsPscuTAG NAME="SUPRESSIONSTOP">9999999999999</odsPscuTAG>
<odsPscuTAG NAME="SUPRESSIONZONE">CCC</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
17.2.6.4 Exceptions
ID MESSAGE_CODE MESSAGE
An error occurred while retrieving the card information. Please
try again later or contact Customer Support
<ONDOT_INFO>FI_CONTACT</ONDOT_INFO>. This typically
227 CARD_101 indicates that the card reference ID is invalid.
Page 749
71 LOGIN_103 Subscriber does not exist
144 LOGIN_108 Your current session has expired. Please log in again.
We are unable to process your request right now. Please try
again later or contact Customer Support
4 LOGIN_109 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
The Get Assets function retrieves the available OnDot alerts and controls. This function
does not require a session id from the Create Session request
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
Page 750
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1758</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCECAPTION">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDS"></odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCECAPTION">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDS"></odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCECAPTION">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDS"></odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG NAME="REGIONNAME">99999</odsPscuTAG>
<odsPscuTAG NAME="REGIONRADIUS">999</odsPscuTAG>
<odsPscuTAG NAME="REGIONS">CCCCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="REGIONLAT">99.99</odsPscuTAG>
<odsPscuTAG NAME="REGIONLONG">99.99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCECAPTION">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDS">
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
Page 751
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCECAPTION">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDS">
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
Page 752
</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCECAPTION">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDS">
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="THRESHOLDID">C99</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDNAME">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="THRESHOLDCAPTION">CCCCCCCCCCCC</odsPscuTAG>
</COLLECTION>
</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
Page 753
</GETDATAXML>
</INVISION>
The Get Card List function retrieves policy for each of the cards associated with the
subscriber ID. If the CARDREFID is included in the request, the response contains just
that card’s policy.
The CARDREFID is assigned by Ondot when a card is added to the subscription. There is
a batch process in place between the Ondot platform and the mainframe that will
replace a lost card with the new replacement card. When this happens, Ondot will
generate a new CARDREFID for the replacement card.
The Get Card Policy response may need to be repeated a few times after creating a
subscription or modifying the accounts on the subscription. Once the subscription
completes successfully, there is a load process between the PSCU Ondot platform and
the Fiserv / FD platforms. This load could take a few seconds.
Page 754
Parameter Description Type Req / Opt Length
APPID 106 Fixed Req 3
APPLICATIONID 102 Fixed Req 3
REQUESTID 102 Fixed Req 3
FUNCTIONID 1759 Fixed Req 4
CLIENTID PSCU assigned Client ID number Numeric Req 2–6
CARDNUMBER Card number – required for DX Numeric Req 16
validation steps
CARDREFID Reference ID for the card Numeric Opt Up to 10
FULLNAME Y-Include the FULLNAME in the Alpha Opt 1
response
SESSIONID Session ID obtained from Create Alpha Req Up to
Session function Numeric 100
SUBSCRIBERID Subscriber ID Alpha Req Unlimited
Case sensitive Numeric
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1759</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG NAME="CARDREFID">99999999</odsPscuTAG>
<odsPscuTAG NAME="FULLNAME">CCCCCCCCCCCCCC</odsPscuTAG>
Page 755
<odsPscuTAG NAME="CARDMASK">XXXX XXXX XXXX 9999</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCEEVENTAREA">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ENABLED"></odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCEEVENTAREA">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ENABLED"></odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCEEVENTAREA">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ENABLED"></odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCEEVENTAREA">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ENABLED"></odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID">C99T99</odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDVALUE">CCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCEEVENTAREA">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ENABLED"></odsPscuTAG>
<odsPscuTAG NAME="THRESHOLDID">C99T99</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="REGIONS">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="REGIONNAME">999999</odsPscuTAG>
<odsPscuTAG NAME="REGIONLAT">99.99999</odsPscuTAG>
<odsPscuTAG NAME="REGIONLONG">99.99999</odsPscuTAG>
<odsPscuTAG NAME="REGIONRADIUS">99.99999</odsPscuTAG>
</COLLECTION>
Page 756
- <COLLECTION>
<odsPscuTAG NAME="REGIONS">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="REGIONNAME">999999</odsPscuTAG>
<odsPscuTAG NAME="REGIONLAT">99.99999</odsPscuTAG>
<odsPscuTAG NAME="REGIONLONG">99.99999</odsPscuTAG>
<odsPscuTAG NAME="REGIONRADIUS">99.99999</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="CARDREFID">99999999</odsPscuTAG>
<odsPscuTAG NAME="FULLNAME">CCCCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="CARDMASK">XXXX XXXX XXXX 9999</odsPscuTAG>
- <COLLECTION>
<odsPscuTAG NAME="PREFERENCEID">C99</odsPscuTAG>
<odsPscuTAG NAME="PREFERENCETYPE">CCCCCCCC</odsPscuTAG>
<odsPscuTAG
NAME="PREFERENCEEVENTAREA">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="ENABLED"></odsPscuTAG>
</COLLECTION>
- <COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
The following is a sample of the Get Policy response when the subscription has been deactivate:
<?xml version="1.0"?>
<INVISION>
<ALERTXML>
<VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>FA91CF34-13BE-70A8-7C6A-689C3FF75D60</GUID>
</VALIDATION>
<V_OLCLASS>
<PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1759</ods:FUNCTIONID>
<ods:FUNCTIONRS>
<ods:FUNCTIONDATARS>
Page 757
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu"/>
</ods:FUNCTIONDATARS>
<ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ALERTXML>
</INVISION>
Page 758
OdsPscu TAG NAME Description Type Length
REGIONNAME Region ID assigned by Ondot Numeric
17.2.8.4 Exceptions
ID MESSAGE_CODE MESSAGE
An error occurred while retrieving the card information. Please
try again later or contact Customer Support
<ONDOT_INFO>FI_CONTACT</ONDOT_INFO>. This is typically
227 CARD_101 caused with the CARDREFID is invalid for the subscriber ID.
Spending limits – per transaction and monthly limit are
incorrect. Monthly limit must be greater than or equal to the
CARD_205 per transaction
144 LOGIN_108 Your current session has expired. Please log in again.
We are unable to process your request right now. Please try
again later or contact Customer Support
4 LOGIN_109 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
This function is used to set the policy (alerts and controls) for the card number on the subscription.
Enabling a Control the C05, C06, C07, and C09 will result in the authorization being declined if it meets the
Page 759
criteria. Enabling the C03 and C04 control (transaction type and merchant category) will block all
transaction except for those where the thresholds defining the transaction type and merchant category
are enable.
Page 760
Parameter Description Type Req / Opt Length
PREFERENCEAREA Defines transaction types that the alert / Alpha Condition
control applies to – Refer to the al
PREFERENCETYPE parameter in the Get
Assets response
PREFERENCEID Alert / Control ID Numeric Condition
al
REGIONLAT* Latitude for the region Numeric Condition
al
REGIONLONG* Longitude for the region Numeric Condictio
nal
REGIONNAME* Region reference ID Numeric Condition
Send a value of 0 to have Ondot al
generate the Region reference ID when
adding a NEW region to the policy
Use the value from Get Policy when
updating or deleting the region from the
Policy
REGIONRADIUS* Radius for the region in meters Numeric Condition
Format: al
999.99
REGIONS User defined name of the region Alpha Condition
al
SESSIONID Session ID obtained from the create Alpha Req Up to 100
session request Numeric
SUBSCRIBERID Subscriber Id - Unique ID for the Alpha Req Unlimited
registration. This value must be unique Numeric
within the PSCU OnDot implementation
Case sensitive
THRESHOLDID Threshold ID associated with the Numeric Condition
alert/conrtol; for A03, A04, A06, A09, al
C03, C04, C06, C09; multiple values can
be sent comma delimited for A03, A04,
C03 and C04
THRESHOLDVALUE Value for the threshold Numeric Condition
Required for A06 (A06T01), A09 al
(A09T01), C06 (C06T01), C09 (C09T01)
Page 761
Parameter Description Type Req / Opt Length
Format: Whole dollar
100 = $100.00
Page 762
17.2.9.2 Sample URL and Response
Page 763
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1762</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<odsPscuTAG NAME="CONFIRMATION">XXXXXXXXX</odsPscuTAG>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 764
prevent pre-authorized recurring
transactions, credits / payments, or
balance consolidations.
A02* C02* My Location – within X distance of my
phone
Page 765
transactions for the unselected
Merchant Types will be denied.
Page 766
Whole dollar
amount with no
decimal
Ie. 100 = $100.00
A028** None – including NonPreference
A029** None
A030** All transactions Policy
*Not available at this time. Requires the follow me feature of the update registar which
is not currently implemented.
** None including NonPreference (A028) – need to explicitly disable this preference for
alerts to be sent
** No Alerts Policy (A029) – This is a default policy. If this preference is enabled, the
Ondot service will allow selected alerts to be enabled on the policy BUT when an alert is
triggered it will not be sent. This preference when enabled needs to be explicitly for
alerts to be sent.
** All Transactions Policy (A030) – This is a default policy. This preference indicates that
every transaction will result in an alert being sent. This preference when enabled needs
to be explicitly for alerts to be sent.
*** Controls will not impact recurring payments unless unless the member sets controls
specifically on the recurring payment category
17.2.9.5 Exceptions
ID MESSAGE_CODE MESSAGE
47 CARD_200 Card details have been updated successfully.
An error occurred while updating the card information. Please
try again later or contact Customer Support
166 CARD_201 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
Spending limits – per transaction and monthly limit are
incorrect. Monthly limit must be greater than or equal to the
CARD_205 per transaction
250 DEVICE_203 No Home Country Id present for this card.
179 API_101 The API Version is not supported.
71 LOGIN_103 Subscriber does not exist
144 LOGIN_108 Your current session has expired. Please log in again.
4 LOGIN_109 We are unable to process your request right now. Please try
Page 767
again later or contact Customer Support
<ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
<ONDOT_INFO>FI_NAME</ONDOT_INFO> does not currently
support this app. For further information please contact
customer support
<ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
OR
43 FI_APP_101 App and FI mismatch
- <INVISION>
- <GETDATAXML>
Page 768
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1765</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
- <COLLECTION>
<odsPscuTAG
NAME="SUBSCRIBERID">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="CARDREFID">99999</odsPscuTAG>
<odsPscuTAG NAME="ALERTREFID">99999</odsPscuTAG>
<odsPscuTAG NAME="ALERTTYPECD">CC</odsPscuTAG>
<odsPscuTAG NAME="DELETETIME">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MSGDATE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MSGDESCR">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="MSGREAD">CCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="MSGTYPE">CCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="SUBSCRIBERID">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="CARDREFID">99999</odsPscuTAG>
<odsPscuTAG NAME="ALERTREFID">99999</odsPscuTAG>
<odsPscuTAG NAME="ALERTTYPECD">CC</odsPscuTAG>
<odsPscuTAG NAME="DELETETIME">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MSGDATE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MSGDESCR">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="MSGREAD">CCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="MSGTYPE">CCCCCCCCCC</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG
NAME="SUBSCRIBERID">XXXXXXXXXXXXXXXX</odsPscuTAG>
<odsPscuTAG NAME="CARDREFID">99999</odsPscuTAG>
<odsPscuTAG NAME="ALERTREFID">99999</odsPscuTAG>
<odsPscuTAG NAME="ALERTTYPECD">CC</odsPscuTAG>
<odsPscuTAG NAME="DELETETIME">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MSGDATE">9999999999</odsPscuTAG>
<odsPscuTAG NAME="MSGDESCR">CCCCCCCCCCCC</odsPscuTAG>
<odsPscuTAG NAME="MSGREAD">CCCCCCC</odsPscuTAG>
Page 769
<odsPscuTAG NAME="MSGTYPE">CCCCCCCCCC</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 770
OdsPscu TAG NAME Description Type Length
transactionAlerts
SUBSCRIBERID Subscriber ID Alpha Unlimited
Numeric
17.2.10.4 Exceptions
ID MESSAGE_CODE MESSAGE
144 LOGIN_108 Your current session has expired. Please log in again.
We are unable to process your request right now. Please try
again later or contact Customer Support
4 LOGIN_109 <ONDOT_INFO>FI_CONTACT</ONDOT_INFO>
The PSCU Ondot implementation has two methods for alert delivery – Ondot or Self-
Delivery. With the Ondot delivery method, no additional information or infrastructure is
required. With the self-delivery method, Ondot will send the alert to the credit union or
vendor to be formatted and delivered to the card holder. Ondot will need the URL end
point for delivering the alert to the credit union or vendor along with the credential –
username and password – for the URL.
Page 771
18 Integrated Debit Processing (Sig & PIN)
Contact your PSCU Account Executive for information about the Integrated Debit
Processing solution.
This section of the document provides a detailed description of the DEBTXML Requests
along with the fixed, required and variable parameters, a sample search request and
response, and a description of each node within the response.
Function ID Description
1900 Integrated Debit Processing – Add, update and delete draft accounts
to debit accounts.
1902 Debit Balance Update DDA
Page 772
18.1 Add a new draft account to a Debit PIN card
18.1.1 Request Parameters
Page 773
Parameter Description Type Required / Optional Length
declined. No withdrawals,
deposits, or inquiries are
allowed.
PFIND Primary/Funding indicator Alpha Required 1
Valid codes:
P – Primary funding account
Blank – Not a primary funding
account
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xxm.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1900&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&ACTIO
N=ADD&ACCTDESC=CCCCCCCCCCCCCCCCCCCC&ACCTTYPE=99&DRAFTACCT=999999999
99999999&DRAFTACCTSTATUS=9&PFIND=C&
- <INVISION>
- <SENDDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1900</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SENDDATAXML>
</INVISION>
Page 774
In the event of a failure, the response will include a tag name EXCEPTION that contains
error information from the First Data system.
Page 775
18.2 Delete a draft account from a Debit PIN card
18.2.1 Request Parameters
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xxm.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1900&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&ACTIO
N=DEL&ACCTTYPE=99&DRAFTACCT=99999999999999999&
- <INVISION>
- <SENDDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1900</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
Page 776
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SENDDATAXML>
</INVISION>
In the event of a failure, the response will include a tag name EXCEPTION that contains
error information from the First Data system.
Page 777
18.3 Update draft account to a Debit PIN card
18.3.1 Request Parameters
Page 778
Parameter Description Type Required / Optional Length
PFIND Primary/Funding indicator Alpha Required 1
Valid codes:
P – Primary funding account
Blank – Not a primary funding
account
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xxm.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1900&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&ACTIO
N=UPD&ACCTDESC=CCCCCCCCCCCCCCCCCCCC&ACCTTYPE=99&DRAFTACCT=999999999
99999999&DRAFTACCTSTATUS=9&PFIND=C&
- <INVISION>
- <SENDDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1900</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SENDDATAXML>
</INVISION>
In the event of a failure, the response will include a tag name EXCEPTION that contains
error information from the First Data system.
Page 779
18.4 DDA View
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xxm.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1900&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&ACTIO
N=VIEW&
- <INVISION>
- <ACCTXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>603FD542-A09D-CD4D-E408-CA831CE1B30F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods="ods">
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1900</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu="odsPscu">
- <COLLECTION>
Page 780
<odsPscuTAG NAME="ACCTDESC">CCCCCCCCCCCCCCCCCCCCC
</odsPscuTAG>
<odsPscuTAG NAME="ACCTTYPE" /> 99</odsPscuTAG>
<odsPscuTAG
NAME="DRAFTACCT">99999999999999999</odsPscuTAG>
<odsPscuTAG NAME="DRAFTACCTSTATUS">9</odsPscuTAG>
<odsPscuTAG NAME="PFIND">C</odsPscuTAG>
- </COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="ACCTDESC">CCCCCCCCCCCCCCCCCCCCC
</odsPscuTAG>
<odsPscuTAG NAME="ACCTTYPE" /> 99</odsPscuTAG>
<odsPscuTAG
NAME="DRAFTACCT">99999999999999999</odsPscuTAG>
<odsPscuTAG NAME="DRAFTACCTSTATUS">9</odsPscuTAG>
<odsPscuTAG NAME="PFIND">C</odsPscuTAG>
- </COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</ACCTXML>
</INVISION>
Page 781
DRAFTACCT DDA Account number to be linked to Numeric Required OBD, ODM
the card
DRAFTACCTSTATUS DDA Account Status Numeric Optional OBD, ODM
Valid codes:
0 - Open
The account is open for all types of
transactions. There are no
restrictions.
1 - Deposit and inquiry only
The account can only accept or
respond to deposit transactions.
2 - Inquiry only
The account can only accept or
respond to inquiry transactions.
9 - Closed
All transactions will be declined. No
withdrawals, deposits, or inquiries are
allowed.
PFIND Primary/Funding indicator Alpha Optional OBD, ODM
Valid codes:
P – Primary funding account
Blank – Not a primary funding
account
Page 782
18.5 Debit Balance Update DDA account level
18.5.1 Data eXchange Request Parameters
Page 783
Parameter Description Type Required / Length
Optional
negative include ‘-‘ in amount
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JServer.
xxm.xmlProcess&RQID=SENDDATAXML&APPID=106&APPLICATIONID=102&FUNCTIONI
D=1902&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENTID=9999&AVAIL
FUNDS=$$$$$$$$$$$cc&ACCTTYPE=99&DRAFTACCT=99999999999999999&DRAFTACC
TSTATUS=9&LEDGERBAL=$$$$$$$$$$$$$cc&
- <INVISION>
- <SENDDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>470EC19B-9487-DFB9-C478-B17408F6A39F</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1902</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
<odsPscu:DATASTREAM xmlns:odsPscu="odsPscu" />
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</SENDDATAXML>
</INVISION>
In the event of a failure, the response will include a tag name EXCEPTION that contains
error information from the First Data system.
Page 784
19 Health Check
This function will perform a health check on the Data eXchange environment and the
support systems for Data eXchange functionality.
The Function ID for this request is 1100.
Page 785
Parameter Description Type Required / Length
Optional
This solution has been sunset
EST Estatement service Alpha Optional 1
Valid value:
Y
LENDERACCOUNT Account number associated Alpha- Required if EBAL=Y Variable
NUMBER with the account to be paid by Numeric passed Up to 21
the Balance Consolidation
ZIPCODE Lender’s zip code Numeric Required if EBAL=Y 5 / 9
Format: passed
99999
99999-9999
EXPDATE Card expiration date Numeric Required if VA=Y 4
FORMAT: MMYY passed
This solution has been sunset
ALERTTYPE Type of Alert Numeric Required if VA=Y 1
Valid Values passed
1- Visa Transaction Alerts
This solution has been sunset
VENDORID Id assigned to the vendor Numeric Optional 2-6
Function to be
Parameter Invoked Response Validation By Remarks
DEBIT=Y 1303 CARDNUMBER
CREDIT=Y 1402 CHNAME
EBAL=Y 1470 BILLERSFOUND
If collections available then
look for REGISTRATIONID.
REGISTRATIONID/STATUS Else STATUS code should be
MA=Y 1752 CODE 0
DYOC=Y 1700 DYOC_URL
VISA_URL
VA=Y 1750 This solution has been sunset
EST=Y 1612 NUM_STATEMENTS
Page 786
19.1.3 Steps to be performed to determine the health:
https://pilotdata.epscu.com/servlet/raApp?ServicePageName=com.invisiondev.JS
erver.xml.xmlProcess&RQID=GETDATAXML&APPID=106&APPLICATIONID=102&F
UNCTIONID=1100&REQUESTID=102&CARDNUMBER=9999999999999999&CLIENT
ID=9999&CREDIT=Y&EBAL=Y&MA=Y&DYOC=Y
- <INVISION>
- <GETDATAXML>
- <VALIDATION>
<RESPONSE>0</RESPONSE>
<GUID>E65074F0-A75E-2174-EE7A-C927C6917ABE</GUID>
</VALIDATION>
- <V_OLCLASS>
- <PscuFS xmlns:ods=ods>
<ods:REQUESTORID>102</ods:REQUESTORID>
<ods:APPLICATIONID>102</ods:APPLICATIONID>
<ods:FUNCTIONID>1100</ods:FUNCTIONID>
- <ods:FUNCTIONRS>
- <ods:FUNCTIONDATARS>
- <odsPscu:DATASTREAM xmlns:odsPscu=odsPscu>
<COLLECTION>
<odsPscuTAG NAME="SERVICE">EBALCON</odsPscuTAG>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</COLLECTION>
Page 787
<COLLECTION>
<odsPscuTAG NAME="SERVICE">CREDIT</odsPscuTAG>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG NAME="SERVICE">MEMBER ALERTS</odsPscuTAG>
<odsPscuTAG NAME="CONFIRMATION">FAILURE</odsPscuTAG>
<odsPscuTAG NAME=" EXCEPTION OCCURRED "> java.lang.Exception:
The request timed out. Please try again later. If the error persist,contact
PSCU</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG NAME="SERVICE">DYOC</odsPscuTAG>
<odsPscuTAG NAME="CONFIRMATION">SUCCESS</odsPscuTAG>
</COLLECTION>
</odsPscu:DATASTREAM>
</ods:FUNCTIONDATARS>
- <ods:STATUS>
<ods:CODE>0</ods:CODE>
</ods:STATUS>
</ods:FUNCTIONRS>
</PscuFS>
</V_OLCLASS>
</GETDATAXML>
</INVISION>
Page 788
20 Appendix A – Request and Function ID Quick Reference
The table below is a quick reference guide to understanding the supported requests
and functions available in Data eXchange. Some functions were designed with the
cardholder (or member) in mind, facilitating self-service applications. Other functions
were designed for the Member Service Representative, Financial Institution Employee
or Financial Institution Internal Application. All functions can be made available to all
audiences depending upon how the function is integrated into member-facing and
employee-facing applications, however special care should be made when accessing
certain update functions. In the table below, the column “Audience” delineates which
functions PSCUFS recommends be restricted to internal, or employee, facing
applications and those functions that could be opened to member-facing self-service
applications.
Page 789
will continue to be supported. Future
implementations should use
RQID=SEARCHXML.
GETDATAXML 1402 Card Summary Information – returns summary Member
data on the cardnumber submitted - such as
balances, payment due dates and amounts,
interest rates and status codes
GETDATAXML 1403 Cardholder Information – returns data about Member
the cardholder of the cardnumber submitted -
such as names, addresses, social security
numbers, dates of birth and phone numbers
CHUPDATEXML 1404 Cardholder Information Update - allows Member
cardholder information to be updated and
supports updates to the primary and
secondary cardholder name, address, phone
number, mother’s maiden name and social
security number
GETDATAXML 1407 Rewards Activity and History – returns CU Member
Rewards data for the cardnumber submitted –
includes total points earned, pending,
redeemed, points that are still available for
redemption and point expiration date
ACCTXML 1408 Card Activation – activates the cardnumber Internal
submitted in the request, allowing the card to
be used by the cardholder
Page 790
In previous documents this function had an
RQID=ORDERCARDXML. Current
implementations with RQID=ORDERCARDXML
will continue to be supported. Future
implementations should use RQID=ACCTXML
PAYXML 1410 Demand Payment Request – enables a Member
demand payment to be made on the account
and updates the cardholder’s account level
DDA and ABA numbers.
GETDATAXML 1411 Statement Data, Last Cycle – returns data from Member
the cardholder’s last statement – includes
transactions, payments and fees as well as
statement balance and statement date
GETDATAXML 1412 Statement Data, One Cycle Prior – returns Member
data from the cardholder’s prior statement –
includes transactions, payments and fees as
well as statement balance and statement date
GETDATAXML 1413 Statement Data, Two Cycles Prior – returns Member
data from the cardholder’s next prior
statement – includes transactions, payments
and fees as well as statement balance and
statement date
GETDATAXML 1414 Payment History – returns payment history Internal
data for the cardnumber submitted – includes
the 12 month payment history and recent
detail on payments due and payments made
GETDATAXML 1415 Recent Activity – returns transaction data that Member
has occurred on the account since the
cardholder’s most recent statement – includes
transactions, payments and outstanding
authorizations
ACCTXML 1416 Order PIN Mailer – issues a request to the host Member
system to generate a letter to the cardholder
containing their existing personal
Page 791
identification number (PIN).
Page 792
GETDATAXML 1429 Special Consolidated Account Information – Internal
returns summary data on the cardnumber
submitted - such as balances, payment
amounts, autopay information, account cross
references, status codes, previous high
balance and collector code
GETDATAXML 1430 Statement and Account History Member
GETDATAXML 1431 Statement Data, Last 3 Cycles – returns data Member
from the cardholder’s last three statements –
includes transactions, payments and fees as
well as statement balances and statement
dates
GETDATAXML 1432 Statement Data, Last 3 Cycles and Recent Member
Activity – returns data from the cardholder’s
last three statements, transactions since the
last statement and summary information on
the account – includes outstanding
authorizations, transactions, payments and
fees as well as statement balances and
statement dates
GETDATAXML 1433 Statement Balances and Summary Data – Member
returns summary information from the last
three cycles and current summary account
data – includes totals for transactions,
payments and fees as well as statement
balances and statement dates returned as
discrete nodes
SENDDATAXML 1435 Numbered First Data NonMon Transactions – Internal
allows numbered non-monetary (NonMon)
changes to a cardholder account – for a list of
currently supported numbered NonMons,
please refer to Appendix K in this document.
GETDATAXML 1436 Statement Summaries, All Available – returns Member
summary level information for up to 12
months of stored Cardholder Statements –
includes totals for transactions, payments and
fees as well as statement balances and
Page 793
statement dates organized into collections
GETDATAXML 1437 Statement Data, Single Specified Cycle – Member
returns data from the cardholder’s statement
based on the statement date provided in the
request – includes transactions, payments and
fees as well as statement balance and
statement date
ACCTXML 1438 Account Transfer – transfers accounts within Member
the same principal or across principals.
Page 794
use RQID=ACCTXML
ACCTXML 1440 New Cardholder Account – sends a request to Member
create a new cardholder account on the First
Data system. The account number is provided
in the request. This function emulates the NC
and NCA transactions in 3270 screens. Must
be used with an application type equal to A
and must also include the card/account
number.
Page 795
For separate entity accounts, please note the
use of field SEPARATE_ENTITY.
In previous documents this function had an
RQID=GETDATAXML. Current implementations
with RQID=GETDATAXML will continue to be
supported. Future implementations should
use RQID=ACCTXML
PAYXML 1441 Right Time Payments – enables cardholders to Internal
make payments on their credit card accounts
and have the payment immediately affect
their available credit. Payments submitted
through the ODS RPC must still be posted
through the payment entry system via batch
file transmission or a monetary adjustment.
This function does not emulate any existing
First Data 3270 transactions.
Page 796
transaction to the account. This is most
commonly used for Cash Advances on an
account to cover a Share account overdraft.
GETDATAXML 1449 Promotion/Protected Balance – returns Member
information about existing
promotion/protected balances on an account.
PAYXML 1450 Redeem Rebates for statement credit or cash Member
to draft account
ACCTXML 1452 Lost / Stolen – Processes an account as either Internal
being lost or stolen.
CHUPDATAXML 1453 View, Add, Update Cardholder information Member,
Internal
PAYXML 1455 Automatic Payment – Provides the ability to Member
set up autmativ payments on a cardholders
account. AutoPay must be set up at First Data
for this function to work.
ACCTXML 1458 Submit a dispute Member
PAYXML 1459 Submit a One Time Future Payment Member
PAYXML 1460 List the payments for the One Time Future Member
Payments scheduled for the cardholder
PAYXML 1461 Delete a One Time Future Payment Member
ESTMTXML 1462 Card Summary Information and eStatement Member
Enrollment Status– returns summary data on
the cardnumber submitted - such as balances,
payment due dates and amounts, interest
rates and status codes – and the cardholder’s
eStatement Enrollment Status
GETDATAXML 1463 Obtain FICO score Member
ACCTXML 1464 Obtain Dispute Reason Codes Member
PAYXML 1470 Lender lookup function checks the RPPS tables Member
to see if the lender is available for a BalCon
electronic payoff
PAYXML 1471 The State / Zip validation function ensures the Member
zip code provided belongs to the state.
PAYXML 1472 The Submit eBalcon function submits the Member
Balance Consolidation for processing
GETDATAXML 1474 Rewards and Redemption History Member
Page 797
ALERTXML 1476 Member Alerts and Controls – Cardholder Alert Member
History Internal
ALERTXML 1477 Member Alerts and Controls – Cardholder Member
Control history Internal
ACCTXML 1478 Master Card and Visa Account Updater Internal
GETDATAXML 1479 Dispute History Member
GETDATAXML 1480 Cardholder Plastic information Member
ACCTXML 1485 Authorization Request Member
Internal
ACCTXML 1486 Post Transaction Member
Internal
ACCTXML 1488 Cancel Emboss Requests Internal
GETDATAXML 1489 Retrieve Emboss Requests Internal
ACCTXML 1490 Refund Rebates Internal
ACCTXML 1491 Reset PIN attempts – Optis Member
Internal
GETDATAXML 1492 Credit Bureau Reporting details Internal
GETDATAXML 1501 The Company Accounts function will return a Member
list of the accounts associated with a company.
GETDATAXML 1502 The Company Information request returns the Member
general information for the specified company
account.
COMPDATAXML 1503 This functionality will provide the ability to Internal
delete a COMPANY level account.
COMPDATAXML 1504 This functionality will provide the ability to Internal
update a COMPANY record.
COMPDATAXML 1515 The Company Recent Activity function will Member
return the recent activity for all accounts in the
company. This will require two processing
steps: 1) obtain the list of accounts within the
company using the Data eXchange function
1501 and 2) cycle through the list and call the
1415 function for each account to obtain the
transactions and authorizations. The collection
of transactions returned in the 1415 function
will need to be edited to also include the card
number so that the transactions can be
Page 798
associated with the appropriate account by the
consuming application.
GETDATAXML 1517 The Company Memos function will return the Member
memos on the Company account.
COMPDATAXML 1518 This functionality will provide the ability to add Internal
a memo to the company account.
COMPDATAXML 1540 This functionality will provide the ability to Internal
create a COMPANY level account.
ESTMTXML 1608 eStatement Enrollment – enrolls the Member
cardholder in eStatements. In previous
versions of this document, this function had
an RQID=GETDATAXML. Current
implementations with RQID=GETDATAXML
will continue to be supported. Future
implementations should use
RQID=ESTMTXML.
ESTMTXML 1609 eStatement Cancel –cancels the cardholder’s Member
enrollment in eStatements.
Page 799
In previous versions of this document, this
function had an RQID=GETDATAXML. Current
implementations with RQID=GETDATAXML
will continue to be supported. Future
implementations should use
RQID=ESTMTXML.
ESTMTXML 1615 Statement Retrieval (Presentation) – retrieves Member
a statement for a given date (encoded PDF
format embedded in the XML).
Page 800
ALERTXML 1753 Create / Update Registration – creates or Member
updates a cardholder registration in PSCU
Member Alerts and Controls
ALERTXML 1754 Create / Update Alert and/or Control – Member
creates or updates an Alert and/or Control
within a carholders registration
ALERTXML 1755 Ondot Alerts and Controls - Create the Member
subscription for the user, update card list on
subscription and deactivate all cards on the
subscription
ALERTXML 1756 Ondot Alerts and Controls - Obtain session id Member
required for other functions
ALERTXML 1757 Ondot Alerts and Controls - Update subscription Member
with destination information
ALERTXML 1760 Ondot Alerts and Controls - Retrieve details for Member
the registration
ALERTXML 1758 Ondot Alerts and Controls - Retrieve list of Member
available alerts and controls
ALERTXML 1759 Ondot Alerts and Controls - Retrieve alerts and Member
controls along with thresholds and settings for
a registration
ALERTXML 1762 Ondot Alerts and Controls - Set alerts and Member
controls along with thresholds and settings
based on user selections
ALERTXML 1765 Ondot Alerts and Controls - Retrieve Member
notifications previously sent to user
GETDATAXML 1800 PFM data Vendor
SENDDATXML 1900 Integrated Debit Processing – Add, Update Internal
and delete accounts associated to debit cards
GETDATAXML 1902 Debit Balance Update DDA Member
Internal
Page 801
21 Appendix B – Valid entries for the CONTROL Node
The Card Summary function (Function ID 1402) includes the CONTROL node in the
response document. This node is the code that represents the value found in the
Reissue Control field on the BS screen in First Data. There are many different possible
values for this node.
The meaning of the values displayed in this field depends on whether a 60-day or 90-day
reissue cycle is used.
This field is also used for identification codes if the CUSTOMER USE FLAG ID field of the
Product Control File is set to transfer the first authorization attempt for new or reissued
plastics to First Data Fraud Management Services or you choose not to have First Data
Fraud Management Services verify cardholder identification.
Codes 7 and 8 remain in this field until positive identification is established. When
positive identification is established or you choose not to have First Data Fraud
Management Services verify cardholder identification, the code will immediately change
to reflect a 9.
Page 802
Code 9 is then moved to the USER FLAG field during nightly update. The particular USER
FLAG position in which the 9 appears depends on the valid code you choose in the
CUSTOMER USE FLAG ID field of the Product Control File. The CONTROL field returns to
displaying the code controlling reissue processing.
Page 803
22 Appendix C – Interpreting the USERFLAGS1THRU4 Node
The USERFLAGS1THRU4 node appears in the response document of five Data eXchange
functions: 1402 – Card Summary, 1429 – Special Consolidated Account Information,
1433 – Statement Balances and Summary Data, 1436 – Statement Summaries, All
Available, and 1462 – Card Summary Information and eStatement Enrollment Status.
This node represents a flag assigned by the Issuing Institution to identify special
conditions on a cardholder account. These flags are also used for identification codes if
the CUSTOMER USE FLAG ID field of the Product Control File is set to verify the receipt
of new or reissued plastics. This field can be used to verify receipt of plastics activated
prior to first use or plastics activated at the point of sale when the cardholder first uses
the plastic. Point-of-sale activation is not available for new First Data clients. The
CUSTOMER USE FLAG ID field also determines which user flag has been selected for the
identification codes.
When this field is used to reflect activation status, it does not update in real-time at
activation. Activation of the card does occur in real-time but this field is not updated
until overnight processing.
Page 804
R Positive cardholder identification and verification of plastic receipt has not
yet been established for this reissued plastic.
S Positive cardholder identification and verification of this new/reissued plastic
receipt has been established for the secondary side of a dual account with
plastics for both sides.
V Positive cardholder identification and verification of this new/reissued plastic
receipt has been established. For a dual account with plastics for both sides,
code V indicates that verification has been established for both sides.
Blank The card activation option is not being used.
Page 805
23 Appendix D – Foreign Address Handling
When submitting a foreign address update to the first data system, special rules apply.
All foreign addresses require the name of the country to be sent in the CITY parameter
and the name of the city or province to be sent in the ADDR2 parameter. Certain
countries have unique codes that should be issued in the STATE parameter. Further,
some foreign addresses also require a valid zip code to be issued, appropriate for their
country while others require the zip code of 00000 to be issued. When issuing a zip
code of 00000, include the zip or postal code in the ADDR2 parameter after the name of
the city or province.
The following countries require their special code to be included in the STATE parameter
and also require a valid zip code to be supplied in the ZIP parameter:
Code Country
AS AMERICAN SAMOA
GU GUAM
RS MARSHALL ISLANDS
FM MICRONESIA
MP NORTH MARIANA ISLAND
PW PALAU ISLAND
PR PUERTO RICO
VI U.S. VIRGIN ISLANDS
The countries below require their special code to be included in the STATE parameter
and require a zip code of 00000 to be supplied in the ZIP parameter:
Code Country
CD CANADA
DO DOMINICAN REPUBLIC
FR FRANCE
DF GERMANY
GB GREAT BRITAIN
IE IRELAND
MY MALAYSIA
MX MEXICO
SA SAUDI ARABIA
Page 806
ES SPAIN
For any foreign address in a country not displayed in the lists above, use FC for the
STATE parameter and 00000 for the ZIP parameter.
Page 807
24 Appendix E – Valid entries for the
AUTHDECLINEREASONCODE Node
The Recent Activity function (Function ID 1415) includes the
AUTHDECLINEREASONCODE node in the response document. This node is the code that
represents the reason an authorization request was declined. This node may also be
present in Function 1432 and is named RECENTDECLINEREASONCODE. There are many
different possible values for this node. Valid entries include:
Page 808
Code Short Description Long Description
Value
the available credit is less than the amount of
the authorization. The corporate account
available credit and the overlimit tables are
checked if appropriate.
10 STOLEN CARD Stolen card - cardholder ‘s external status is U
11 DELINQ AND OV LIM Delinquent and overlimit - cardholder ‘s
internal status is X
12 CHARGED OFF ACC Charged off account - cardholder ‘s external
status is Z
13 OVER ADV SING LIM Over cash advance single limit - the amount
requested for cash advance authorization is
over the limit for a single cash advance
authorization
14 OVER ADV TOT LIM Over cash advance total limit - the requested
cash advance authorization, added to
outstanding authorizations, exceeds the total
cash advance limit
15 OVER SINGLE LIMIT Over single limit - the amount requested for a
merchandise authorization is over the limit for
a single merchandise authorization
16 EXCESSIVE AUTHS Excessive authorizations - the number of
authorizations exceeds the number allowed
If the merchant calls into the voice
authorization center, the authorization is
approved and transferred to security to
process the hot call. Positive identification is
requested.
17 UNDER ADVANCE Under cash advance minimum - the
MIN authorization request was for an amount less
than the minimum cash advance
18 AUTH DECLINED Reserved for restricted use
19 P TO P DECLINED Person-to-person payment authorization
declined – the authorization request for a
MasterCard® person-to-person payment
transaction was declined
Page 809
Code Short Description Long Description
Value
20 BAD READ CVV Bad read Card Verification Value - the
authorization failed track 2 data verification
on a swiped card because data was not read
correctly
21 BAD STRIPE CVV Bad stripe Card Verification Value - the
authorization failed track 2 data verification
on a swiped card
22 COV - MCC/CTY/ZIP Commercial card authorization override
parameters - merchant category code/country
code/ZIP code – an authorization has failed
either the commercial card authorization
override merchant category code, country
code, or ZIP code
23 Not used
24 Not used
25 Not used
26 OVER DLY SPND LMT Over daily spending limit - the requested
authorization, plus the amount of the
approved cash and merchandise
authorizations, exceeds the total daily
spending limit
27 AUTH DEC-EXC ACT Authorization declined-excess activity –
MasterCard response for excessive use
28 3D SECURE REJECTD 3-D Secure rejected - 3-D Secure authorization
was rejected because the authorization
requirements were not met
29 AUTH DEC-SYS ERR Authorization declined-System error –
communication line is disabled
30 CRD INVL FOR MRCH Card invalid for merchant - card could not be
used at the requested merchant. This code is
used primarily for merchant chain code edits
and private label.
31 ACC ON NEG FILE Account on negative file - the account was
found on the negative file for OSCAS accounts
or for merchant stand-ins
Page 810
Code Short Description Long Description
Value
32 AUTH DEC-EXP CD Authorization declined-expired card - the
expiration date on the card is earlier than the
current month and year
33 AUTH REF TO ISS Authorization referred to issuer - invalid
terminal identification, or terminal transaction
with a code 10, or line down
34 INVALID ID NUMBER Invalid identification number - Commercial
card fleet identification number was invalid
35 INVALD DRIVER Invalid driver number - Commercial card fleet
NUM driver number was invalid
36 INVALD VEHICL NUM Invalid vehicle number - Commercial card fleet
vehicle number was invalid
37 EXCDS SPENDING LM Exceeds spending limit - Commercial card
declined for exceeding spending limits
38 COMPANY Company overlimit - Commercial card
OVERLIMIT company credit limit exceeded
39 FAMILY CARD Family card overlimit - Relationship processing
OVLMT account is overlimit
40 INAS-INVALID PIN INAS-invalid PIN - MasterCard response when
PIN is invalid
41 DELINQ ACC DIV Delinquent account diversion - Commercial
card diversion account is delinquent
42 FAMILY CARD INVAL Family card invalid - Relationship processing
account is not valid or is statused
43 OVERLIMIT DIV Overlimit diversion - Commercial card
diversion account is overlimit
44 DELINQ & OV DIV Delinquent and overlimit diversion -
Commercial card diversion account is
delinquent and overlimit
45 EXCDS SPEND DIV DIV Exceeds spending limit diversion -
Commercial card diversion account has
exceeded spending limits
46 ALWY REFR CD SET Always refer code set - always refer flag has
been set on the account
47 OVERLIMIT PAY FLT Overlimit payment float - assigned by batch
Page 811
Code Short Description Long Description
Value
payment float process
48 EXT STAT DIV ACCT External status diversion account -
Commercial card diversion account has an
external status
49 INVALID CVC2/CVV2 Invalid Card Validation Code 2/Card
Verification Value 2 - authorization request
contained an invalid CVC2/CVV2
50 TRK1 NAME Track 1 name mismatch - cardholder name in
MISMATC track 1 of authorization does not match name
on the cardholder account record
51 VERIFY ORDER Reserved for restricted use
52 CHP ATHNTCTN FAIL Chip authentication failed - Visa performed
chip authentication and it failed
53 3D SECURE INVALID 3-D Secure invalid - 3-D Secure authorization
declined due to CAVV validation failure
54 UCAF DECLINED Universal Cardholder Authentication Field
declined - authorization request was declined
due to UCAF validation failure
55 Not used
56 Not used
57 Not used
58 PI NOT FOUND Presentation instrument not found - the
cardholder ‘s presentation instrument cannot
be located in the system, and the
authorization is rejected
59 PIN # INVALID PIN number invalid - the entered PIN is invalid
60 PIN SERV UNAVLBL PIN service unavailable - the PIN service was
unavailable
61 EXC PIN ATTEMPTS Excessive PIN attempts - the number of invalid
PIN attempts is greater than the number of
PIN attempts allowed in a day
62 PI AUTH PROHIBITD Presentation instrument authorization
prohibited - presentation instrument external
status is A
63 CLOSED PI Closed account presentation instrument –
Page 812
Code Short Description Long Description
Value
presentation instrument external status is C
64 LOST PI PI Lost card presentation instrument –
presentation instrument external status is L
65 STOLEN PI PI Stolen card presentation instrument –
presentation instrument external status is U
66 ERROR Error - the Card Verification Value (CVV) was
invalid, or the encryption was invalid
67 OVER MRCH TOT Over merchandise total limit - the requested
LMT merchandise authorization, added to
outstanding authorizations, exceeds the total
merchandise limit
68 ACCOUNT ON CWB Account on Combined Warning Bulletin – the
cardholder ‘s account is flagged as being on
the warning bulletin
69 SERVICE NOT AVAIL Service not available - merchant response for
service not available
70 TRANS NOT Transaction not allowed - right-time payment
ALLOWED reversal does not match a previous right-time
payment
71 SYSTEM DOWN System down - reserved for NYCE debit card
transactions only
72 PARTIAL APPROVAL A part of the requested authorization amount
has been approved
73 ACCT NOT ON FILE Account not on file - the cardholder ‘s account
cannot be located on the System, and the
authorization is rejected
74 INVALID ACCT Invalid account - account number was invalid
75 NEW/REISSUE New/reissue - the plastic is new or reissued
for the cardholder and this is the first time
used; positive identification is requested
76 ISS. CENTER DOWN Issuer center down - communication lines
unavailable from issuing system
77 AUTH FLAG = Y Authorization flag is a Y - the authorization
flag on the cardholder ‘s account is set to Y.
An authorization for this account will always
Page 813
Code Short Description Long Description
Value
be declined.
78 PICK UP CARD Pick up card - OSCAS processing response was
to pick up the card
79 **** STOP Stop payment on check cash advances – an
PAYMENT authorization for a check cash advance can be
stopped. This is the error when the
authorization is processed.
80 UNABLE TO AUTH Unable to authorize - the authorization is for a
cash advance and the cardholder ‘s account
cannot be used for this type of authorization
81 CVL-INVALID MRCH Commercial Card Vendor List-invalid merchant
– a commercial card cardholder attempted to
use the plastic at a merchant that was not set
up on the Commercial Card Vendor List
82 Not used
83 INV SERVICE CODE Invalid service restriction code - card’s track 2
data contains a service code. This service
code is checked against a table and if there is
not a match, the authorization is rejected.
84 INVALID CVV/CVC Invalid Card Verification Value/Card Validation
Code -
the CVV/CVC was invalid during PIN validation
85 REJECTED CVV/CVC Rejected Card Verification Value/Card
Validation Code
- the CVV/CVC was invalid
86 AUTH PRIO TO VDAT Authorization prior to valid date - the plastic
was used prior to the valid start date for that
plastic
87 ATM INQ RESTRICTD ATM inquiry restricted - authorization request
was an ATM inquiry, which was not allowed
for this cardholder
88 COV - HIGH/LOW Commercial card authorization override
parameters - authorization request has failed
either the low amount or high amount check
89 NO MATCH- No match-preapproved authorization - the
Page 814
Code Short Description Long Description
Value
PREAPPRV cardholder number does not match the
merchant account number on a batch
authorization originated by a manual
authorization
90 EXCESS TRAN POSID Excessive transactions get positive
identification – the cardholder had too many
authorizations. The authorization was
declined and a positive identification was
requested.
91 EXCESS PIN POS ID Excessive PIN attempts get positive
identification – the cardholder had too many
PIN attempts. The authorization was
declined and a positive identification was
requested.
92 CARD VERIFY DECLN Card verify decline - positive identification
cannot be made for authorization-only
93 Reserved for restricted use
94 CARD EXPD ON Card expired on the Cardholder Master File -
MAST the
expiration date stored on the cardholder
account record is earlier than the current
date
95 NRI SUSPECT FRAUD Not received as issued suspect fraud – the
authorization request was suspected of being
fraudulent
96 COUNTERFT Counterfeit suspect fraud - the authorization
SUSPECT request was suspected of being fraudulent
based on a counterfeit strategy
97 KITING SUSPECT Kiting suspect fraud - the authorization
request was
suspected of being fraudulent based on a
kiting strategy
98 LOST/STLN SUSPECT Lost/stolen suspect - the authorization was
suspected of being fraudulent since a lost
record was stored for the cardholder
Page 815
Code Short Description Long Description
Value
99 MISMATCH EXP Mismatch expiration date - the expiration
DATE date from the track data does not match the
expiration date on the cardholder account
record on a swiped card
FD CONSUMER Authorization is blocked due to a control
CONTROL enabled on the account
At cycle time, the System assesses the account’s status and places an appropriate status
flag in the first position. Each of the other flags shift one position to the right, with the
rightmost flag dropping out of the activity history. The table below contains information
about the code that can be found in each of the 12 positions, and the description of that
code.
Code Description
Z Statement not generated because of zero balance and no activity
0-7 No postings during the cycle - The number indicates the number of
cycles delinquent
A-H Debit postings only during the cycle
A Account not delinquent
B Account one cycle delinquent
C Account two cycles delinquent
D Account three cycles delinquent
Page 816
E Account four cycles delinquent
F Account five cycles delinquent
G Account six cycles delinquent
H Account seven cycles delinquent
I-P Credit postings only during the cycle
I Account not delinquent
J Account one cycle delinquent
K Account two cycles delinquent
L Account three cycles delinquent
M Account four cycles delinquent
N Account five cycles delinquent
O Account six cycles delinquent
P Account seven cycles delinquent
Q-X Both debit and credit postings during the cycle
Q Account not delinquent
R Account one cycle delinquent
S Account two cycles delinquent
T Account three cycles delinquent
U Account four cycles delinquent
V Account five cycles delinquent
W Account six cycles delinquent
X Account seven cycles delinquent
Symbols Credit balance during the cycle
% Credit balance with no activity
# Credit balance with debit and credit history
+ Credit balance with debit activity only
- Credit balance with credit activity only
Debit activity is defined as sale and cash advance postings. Credit activity is
defined as payment and return postings.
Page 817
26 Appendix H – AutoPay Flags
The following table contains the definition of the AutoPay Flags referenced in the
Payment on Demand functions 1410 and 1426.
Page 818
1 Unpaid Billed Minimum Payment Due Checking
2 Full Statemented Balance or Unpaid Billed Minimum Checking
Payment Due
3 Reserved for United Kingdom processors Not Applicable
4 Full Statemented Balance Checking
5 Unpaid Billed Minimum Payment Due Savings
6 Full Statemented Balance or Unpaid Billed Minimum Savings
Payment Due
7 Full Statemented Balance Savings
8 Reserved for United Kingdom processors Not Applicable
Page 819
27 Appendix I – Foreign Transaction Handling
When submitting a request for Cycle-to-Date transaction detail or Statemented
transaction detail, the response may contain transactions that were conducted in a
foreign currency. Depending upon Product Control File settings in the First Data system
and other optional settings by the Financial Institution, a currency conversion line may
appear for a foreign currency transaction in addition to the transaction detail line item.
This currency conversion line may also contain the details or otherwise reference an
optional currency conversion fee that the Financial Institution has elected to charge the
cardholder for any transaction done in a foreign currency.
Within the First Data system, there are a number of valid formats and different
appearances for the data contained in these currency conversion and optional fee
statement detail lines. If your Financial Institution is charging an optional currency
conversion fee and/or has cardholders that have transactions in a foreign currency, we
strongly recommend that you test your detailed statement responses to ensure
appropriate interpretation of the information in this description line. The information in
this appendix should be used only as a general guide to foreign transaction
interpretation. Your data may appear differently than the information provided below.
A second transaction line item collection that has the details of the currency
conversion will appear with the same reference number (EXPNRFRNNR) as the
primary transaction line item.
The second transaction line item collection that details the currency conversion
breakdown will have a zero transaction amount node (TRANAMT).
Below is an example of the primary and secondary collections for a recent foreign
transaction:
Page 820
- <COLLECTION>
<odsPscuTAG NAME="DTLDESC">BANK OF AYUDHYA TAK</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">050624</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">15422025F0JM8E9L1</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">050624</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000246.25</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="DTLDESC">2.44 10,000.00 764
0.024625000</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">050624</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">15422025F0JM8E9L1</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">050624</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000000.00</odsPscuTAG>
</COLLECTION>
The description node of the currency conversion line collection contains several
pieces of information regarding the currency conversion and fee. The breakdown is
as follows:
Page 821
A second transaction line item collection that has the details of the currency
conversion will appear after the primary transaction line item, the reference number
node will not contain a value.
The second transaction line item collection that details the currency conversion
breakdown will have a zero transaction amount node (TRANAMT).
- <COLLECTION>
<odsPscuTAG NAME="EXPNRFRNNR">74741985M173P2MWZ</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM">029492</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">050701</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">050629</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000024.44</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">VODAFONE'S ONLINE STORE DUBLIN
IE</odsPscuTAG>
</COLLECTION>
- <COLLECTION>
<odsPscuTAG NAME="DTLAUTHNUM">029492</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">050701</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">050629</odsPscuTAG>
<odsPscuTAG NAME="EXPRNRFRNNR" />
<odsPscuTAG NAME="TRANAMT">00000000000000.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">5182 20.00 978 1.222000000</odsPscuTAG>
</COLLECTION>
The description node of the currency conversion line collection contains several
pieces of information regarding the currency conversion and fee. The breakdown is
as follows:
Page 822
<odsPscuTAG NAME="DTLDESC">5182 20.00 978 1.222000000</odsPscuTAG>
First item: Julian date - 1st digit represents the year and the last 3 digits
represent the number of days since 1/1 of that year (5182 in the example,
representing 7/1/05)
Second item: Amount of transaction in local currency (20.00 in the example)
Third item: Foreign Currency code (978 in the example)
Fourth item: Conversion rate (1.222000000 in the example)
Page 823
27.3 First Data Country and Foreign Currency Codes
Page 824
Country Currency Code
Bouvet Island Norwegian Krone 578
Brazil Brazil Real 986
British Indian Ocean Territory U.S. Dollar 840
British Virgin Islands U.S. Dollar 840
Brunei Darussalam Brunei Dollar 096
Bulgaria Lev 975
Burkina Faso CFA Franc BCEAO 952
Burundi Burundi Franc 108
Cambodia Riel 116
Cameroon, United Republic of CFA Franc BEAC 950
Canada Canadian Dollar 124
Cape Verde Island Cape Verde Escudo 132
Cayman Islands Cayman Islands Dollar 136
Central African Republic CFA Franc BEAC 950
Chad CFA Franc BEAC 950
Chile Chilean Peso 152
China, People’s Republic of Yuan Renminbi 156
Christmas Island Australian Dollar 036
Cocos (Keeling) Islands Australian Dollar 036
Colombia Colombian Peso 170
Comoros Comoro Franc 174
Congo CFA Franc BEAC 950
Congo, Democratic Republic of the Franc Congolais 976
Cook Islands New Zealand Dollar 554
Costa Rica Costa Rican Colon 188
Croatia, Republic of Croatian Kuna 191
Cuba Cuban Peso 192*
Cyprus Cyprus Pound 196
Czech Republic Czech Koruna 203
Denmark Danish Krone 208
Djibouti Djibouti Franc 262
Dominica East Caribbean Dollar 951
Dominican Republic Dominican Peso 214
Page 825
Country Currency Code
East Timor Rupiah 360
East Timor Timor Escudo 626
Ecuador Sucre 218
Ecuador Unidad de Valor Constante 983
Egypt Egyptian Pound 818
El Salvador El Salvador Colon 222
Equatorial Guinea CFA Franc BEAC 950
Eritrea Eritrean Nafka 232*
Estonia Kroon 233
Ethiopia Ethiopian Birr 230
Faeroe Island Danish Krone 208
Falkland Islands (Malvinas) Falkland Islands Pound 238
Fiji Fiji Dollar 242
Finland Euro 978
France Euro 978
France, Metropolitan Euro 978
French Guiana Euro 978
French Polynesia CFP Franc 953
French Southern Territories Euro 978
Gabon CFA Franc BEAC 950
Gambia Dalasi 270
Georgia Georgian Lari 981
Germany, Republic of Euro 978
Ghana Cedi 288
Gibraltar Gibraltar Pound 292
Greece Euro 978
Greenland Danish Krone 208
Grenada East Caribbean Dollar 951
Guadeloupe Euro 978
Guam U.S. Dollar 840
Guatemala Quetzal 320
Guinea Guinea Franc 324
Guinea-Bissau Guinea-Bissau Peso 624
Page 826
Country Currency Code
Guyana Guyana Dollar 328
Haiti Gourde 332
Haiti U.S. Dollar 840
Heard and McDonald Islands Australian Dollar 036
Honduras Lempira 340
Hong Kong Hong Kong Dollar 344
Hungary Forint 348
Iceland Icelandic Krona 352
India Indian Rupee 356
Indonesia Rupiah 360
Iran, Islamic Republic of Iranian Rial 364
Iran Airlines Iranian Airline Rate 365
Iraq Iraqi Dinar 368
Ireland Euro 978
Israel Shekel 376
Italy Euro 978
Ivory Coast CFA Franc BCEAO 952
Jamaica Jamaican Dollar 388
Japan Yen 392
Jordan Jordanian Dinar 400
Kazakhstan Tenge 398
Kenya Kenyan Shilling 404
Kiribati Australian Dollar 036
Korea, Democratic People’s Republic of North Korean Won 408
Korea, Republic of Won 410
Kosovo Euro 978
Kuwait Kuwaiti Dinar 414
Kyrgyzstan Som 417
Lao People’s Democratic Republic Kip 418
Latvia Latvian Lats 428
Lebanon Lebanese Pound 422
Lesotho Loti 426
Lesotho Rand 710
Page 827
Country Currency Code
Liberia Liberian Dollar 430
Libyan Arab Jamahiriya Libyan Dinar 434
Liechtenstein Swiss Franc 756
Lithuania Lithuanian Litas 440
Luxembourg Euro 978
Macau Pataca 446
Macedonia, the former Yugoslav Republic of Denar 807
Madagascar Ariary 969
Malawi Kwacha 454
Malaysia Malaysian Ringgit 458
Maldives Rufiyaa 462
Mali CFA Franc BCEAO 952
Malta Maltese Lira 470
Marshall Islands U.S. Dollar 840
Martinique Euro 978
Mauritania Ouguiya 478
Mauritius Mauritius Rupee 480
Mayotte Euro 978*
Mexico Mexican Peso 484
Micronesia U.S. Dollar 840
Moldova, Republic of Moldovan Leu 498
Monaco Euro 978
Mongolia Tugrik 496
Montserrat East Caribbean Dollar 951
Morocco Moroccan Dirham 504
Mozambique Metical 508
Myanmar Kyat 104
Namibia Namibia Dollar 516
Namibia Rand 710
Nauru Australian Dollar 036
Nepal Nepalese Rupee 524
Netherlands Euro 978
Netherlands Antilles Netherlands Antillian Guilder 532
Page 828
Country Currency Code
New Caledonia CFP Franc 953
New Zealand New Zealand Dollar 554
Nicaragua Cordoba Oro 558
Niger CFA Franc BCEAO 952
Nigeria Naira 566
Niue New Zealand Dollar 554
Norfolk Island Australian Dollar 036
Northern Mariana Islands U.S. Dollar 840
Norway Norwegian Krone 578
Occupied Palestinian Territory U.S. Dollar 840
Oman Rial Omani 512
Pakistan Pakistan Rupee 586
Palau U.S. Dollar 840
Panama Balboa 590
Panama U.S. Dollar 840
Papua New Guinea Kina 598
Paraguay Guarani 600
Peru Nuevo Sol 604
Philippines Philippine Peso 608
Pitcairn New Zealand Dollar 554
Poland Polish New Zloty 985
Portugal Euro 978
Puerto Rico U.S. Dollar 840
Qatar Qatari Rial 634
Reunion Euro 978
Romania Leu 946
Russian Federation Russian Ruble 643
Rwanda Rwanda Franc 646
Saint Helena Saint Helena Pound 654
Saint Kitts-Nevis East Caribbean Dollar 951
Saint Lucia East Caribbean Dollar 951
Saint-Pierre and Miquelon Euro 978
Saint Vincent and the Grenadines East Caribbean Dollar 951
Page 829
Country Currency Code
Samoa Tala 882
San Marino Euro 978
Sao Tome and Principe Dobra 678
Saudi Arabia Saudi Riyal 682
Senegal CFA Franc BCEAO 952
Serbia and Montenegro Serbian Dinar 891
Seychelles Seychelles Rupee 690
Sierra Leone Leone 694
Singapore Singapore Dollar 702
Slovakia Slovak Koruna 703
Slovenia Tolar 705
Solomon Islands Solomon Islands Dollar 090
Somalia Somali Shilling 706
South Africa Rand 710
South Georgia and South Sandwich Islands Pound Sterling 826*
Spain Euro 978
Sri Lanka Sri Lanka Rupee 144
Sudan Sudanese Pound 736
Suriname Surinam Guilder 740
Svalbard and Jan Mayen Islands Norwegian Krone 578
Swaziland Lilangeni 748
Sweden Swedish Krona 752
Switzerland Swiss Franc 756
Syrian Arab Republic Syrian Pound 760
Taiwan (Province of China) New Taiwan Dollar 901
Tajikistan Somoni 972
Tanzania, United Republic of Tanzanian Shilling 834
Thailand Baht 764
Togo CFA Franc BCEAO 952
Tokelau New Zealand Dollar 554
Tonga Pa’anga 776
Trinidad and Tobago Trinidad and Tobago Dollar 780
Tunisia Tunisian Dinar 788
Page 830
Country Currency Code
Turkey Turkish Lira 949
Turkey Pseudo-Turkish Lira 792**
Turkmenistan Manat 795
Turks and Ciacos Islands U.S. Dollar 840
Tuvalu Australian Dollar 036
Uganda Uganda Shilling 800
Ukraine Ukrainian Hryvnia 980
United Arab Emirates U.A.E. Dirham 784
United Kingdom Pound Sterling 826
United States U.S. Dollar 840
U.S. Minor Outlying Islands U.S. Dollar 840
U.S. Virgin Islands U.S. Dollar 840
Uruguay Peso Uraguayo 858
Uzbekistan Uzbekistan Sum 860
Vanuatu Vatu 548
Vatican City Euro 978
Venezuela Bolivar 862
Vietnam Dong 704
Wallis and Futuna Islands CFP Franc 953
Western Sahara Moroccan Dirham 504
Yemen Yemeni Rial 886
Zambia Kwacha 894
Zimbabwe Zimbabwe Dollar 716
* This is the default value if no MasterCard value is present.
** MasterCard uses code 793 to process the Pseudo-Turkish lira through the GCMS System.
Do not enter this code for merchants.
Page 831
28 Appendix J – Statement Data
Use the following information to interpret the information returned in the collections
found in Data eXchange functions that return Statement Information – 1411, 1412,
1413, 1415, 1431, 1432, and 1433.
- <COLLECTION>
<odsPscuTAG NAME="EXPNRFRNNR">24323014LG8PW4HZ5</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000207.33</odsPscuTAG>
Page 832
<odsPscuTAG NAME="DTLDESC">TIRE KINGDOM # 261 COLUMBIA
SC</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">070529</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM">02701A</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070527</odsPscuTAG>
</COLLECTION>
28.1.1 Rules
Authnum is present
ExpNrFrnNr is present
TranDate is present
PostDate is present
DtlDesc is present
TranAmt is greater than zero
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070610</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">-0000000000007.61</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">ADJUSTMENT-PURCHASES</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070610</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">F46250052000IXFRF</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM"></odsPscuTAG>
</COLLECTION>
28.2.1 Rules
The following rules apply for a collection for an adjustment for a purchase:
Page 833
DtlDesc is present
TranAmt is not zero
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070615</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">-0000000012549.89</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC"> BALANCE TRANSFER 9999 9999 9999
9999</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070615</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR"> 00000000000ATNEWA</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM"/>
</COLLECTION>
28.3.1 Rules
The following rules apply for a collection representing a balance transfer transaction:
28.4 Finance
- <COLLECTION>
<odsPscuTAG NAME="EXPNRFRNNR">*FINANCE CHARGE*</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000005.26</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">PURCHASES $5.26 CASH ADVANCE
$0.00</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">070529</odsPscuTAG>
Page 834
<odsPscuTAG NAME="DTLAUTHNUM" />
<odsPscuTAG NAME="TRANDATE">070529</odsPscuTAG>
</COLLECTION>
<COLLECTION>
<odsPscuTAG NAME="EXPNRFRNNR">***FINANCE CHARGE*</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000000.87</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">** $0.87</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">070529</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM" />
<odsPscuTAG NAME="TRANDATE">070529</odsPscuTAG>
</COLLECTION>
28.4.1 Rules
The following rules apply for a collection representing a finance charge transaction:
28.5 Payments
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070516</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070516</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">PAYMENT - THANK YOU</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">7475643482Y50JS9F</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM" />
<odsPscuTAG NAME="TRANAMT">-0000000000130.73</odsPscuTAG>
</COLLECTION>
Page 835
The following is an example of a collection representing an automatic payment:
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070604</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">-0000000000250.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC"> PAYMENT - THANK YOU</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070604</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">F4625004V00CHGDDA</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM" />
</COLLECTION>
28.5.1 Rules
The following rules apply for a collection representing a standard payment transaction:
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070604</odsPscuTAG>
<odsPscuTAG NAME="TRANAMT">00000000000250.00</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">ADJUSTMENT-PAYMENTS</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070604</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">F46250052000RP162</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM">01774A</odsPscuTAG>
</COLLECTION>
28.5.3 Rules
Page 836
Authnum may be present
ExpNrFrnNr is present
TranDate is present
PostDate is present
DtlDesc is present and contains the words ADJUSTMENT-PAYMENTS
TranAmt is greater than zero
28.6 CREDITS
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070521</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070520</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">WM SUPERCENTER SPARTANBURG SC
CREDIT</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR">74226384QAFKWJST4</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM" />
<odsPscuTAG NAME="TRANAMT">-0000000000006.11</odsPscuTAG>
</COLLECTION>
28.6.1 Rules
The following rules apply for a collection representing a standard merchandise credit:
Page 837
28.7 Credit Insurance
- <COLLECTION>
<odsPscuTAG NAME="EXPNRFRNNR" />
<odsPscuTAG NAME="TRANAMT">00000000000016.75</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">CREDIT INSURANCE AT .2250 PER
100.00</odsPscuTAG>
<odsPscuTAG NAME="DTLPOSTDATE">070511</odsPscuTAG>
<odsPscuTAG NAME="DTLAUTHNUM" />
<odsPscuTAG NAME="TRANDATE">070511</odsPscuTAG>
</COLLECTION>
28.7.1 Rules
The following rules apply for a collection representing credit insurance fees and charges:
- <COLLECTION>
<odsPscuTAG NAME="DTLPOSTDATE">070426</odsPscuTAG>
<odsPscuTAG NAME="TRANDATE">070426</odsPscuTAG>
<odsPscuTAG NAME="DTLDESC">LATE FEE</odsPscuTAG>
<odsPscuTAG NAME="EXPNRFRNNR" />
<odsPscuTAG NAME="DTLAUTHNUM" />
<odsPscuTAG NAME="TRANAMT">00000000000005.80</odsPscuTAG>
</COLLECTION>
Page 838
Other fees may include the following in the DTLDESC node:
Page 839
28.8.1 Rules
Page 840
29 Appendix K – Certified SENDATAXML Numbered NonMons
Non-Monetary transactions
The SENDDATAXML function (Function ID 1435) has been certified with the numbered
NonMons listed in the table below. Contact your Account Executive to request support
of NonMons that are not included in the list.
If the value of any parameter passed exceeds the acceptable length, the 1435 request
will fail. All descriptions include the acceptable length of the parameter.
Page 841
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
21 Checking PARAM1 NUMBER: Checking PARAM1=12345678
Account account number; 9102
Number variable length, 17
positions (sets checking
account to
123456789102)
22 Billing Cycle PARAM1 Cycle code PARAM1=4
23 Charge DDA PARAM1 FLAG: Automatic PARAM1=1
Flag Payment Code; Refer to
the Auto Pay Flag in (sets autopay flag
GETDATAXML, Function to 1 – payment will
Id 1426 of Appendix B be applied to the
for a list of valid flags credit card account
from a specified
checking account in
the amount of the
unpaid billed
minimum payment
amount)
PARAM2 CODE: Checking or PARAM2=C
Savings account code;
valid codes are C – (sets code to C for
Checking, S – Savings, Checking)
blank – do not use
automatic payment
feature
Page 842
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM3 ACCOUNT: Checking or PARAM3=12345678
Savings account; 90
variable length, 17
positions (sets account
number to
1234567890 –
optionally, to
delete a checking or
savings account
from automatic
payments, set the
FLAG to 0, set CODE
to C or S and leave
ACCOUNT blank)
24 Savings PARAM1 ACCOUNT: Savings PARAM1=1234567
Account account; variable
Number length, 17 positions (sets savings
account number to
1234567)
28 External PARAM1 Reason code PARAM1=97
Status Reason
Code
Page 843
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
29 Permanent PARAM1 CODE: Assigned PARAM1=123
Collector Collector Identifier, 3
Code positions (numeric (sets perm.
only), can be any value collector code to
– however the following 123)
3 values are reserved:),
can be any value – PARAM1=000
however the following 4
values are reserved: (removes the
088 – Charge off, fraud current permanent
089 – Charge off, collector code on
bankruptcy the account)
099 – Abandonment
000 – Removes the code PARAM1=099
(abandons a
charged-off
account)
PARAM2 ABANDON: If PARAM2=ABANDO
(optional) abandoning a charged- N
off account (using Code
099), this field must (abandons a
contain the word charged-off
“ABANDON” account, no further
monetary or non-
monetary activity is
permitted the day
you make this
entry)
31 Secondary PARAM1 Secondary Cardholder Last%20Suffix,First
Cardholder Name %20MI
Name
Smith,John
Smith%20Jr,John
Smith%20Jr,John%2
Page 844
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
0M
39 Fixed PARAM1 Amount of payment due Param1=15000
Minimum for the account in order
Payment to avoid Minimum payment
Amount Delinquency. amount of $150.00
transaction
Format:
$$$$$$$$$$$¢¢
40 Credit Score PARAM1 SCORE: Credit Score PARAM1=725
Code; Client-defined
code representing an (sets score to 725)
account’s ranking based
on the evaluation of the
applicant’s credit
history – variable
length, 3 positions.
51 Statement PARAM1 Statement Hold Code: PARAM1=W
Hold Code C - Sort hard copy
statements according to
cardholder
account identifier and
mail to you.
D - System-generated
code that represents
default
strategy ZBFD has been
assigned to the
cardholder.
N - Send hard copy
statement to
cardholder.
R - Returned mail; do
not print a hard copy
statement.
S - Send hard copy
Page 845
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
statement to First Data
Fraud
Management Services.
V - Enlarge statement
contents to fit on 11x14
paper and
send to cardholder.
W - Do not print a hard
copy statement.
Instead, produce
the statement only for
CIS (Customer Inquiry
System)
and on microfiche.
Y - Send hard copy
statement to you.
1-9 - Send hard copy
statement to you for
this number of
billing cycles.
53 Transit PARAM1 TRANSIT: Transit PARAM1=12345678
Routing routing number (RTN); 9
Number fixed length, 9 positions,
numeric, required field; (sets the RTN to
if the RTN is set to all 123456789; to set
zeros, the First Data the RTN to zero, set
system uses the number PARAM1=00000000
in the Merchant Daily 0)
Transit Routing Number
parameter in the ACH
Processing section of
PCF for the ACH record
57 Credit Bureau PARAM1 Credit bureau flag PARAM1=1
flag
58 Miscellaneous PARAM1 DATA: Information to PARAM1=ABCD
Page 846
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
Field 1 be placed in
Miscellaneous Field 1 (sets the misc field
on the account – 1 to ABCD)
variable length, four
positions
59 Miscellaneous PARAM1 DATA: Information to PARAM1=ABCDE
Field 2 be placed in
Miscellaneous Field 2 (sets the misc field
on the account – 2 to ABCDE)
variable length, five
positions
60 Miscellaneous PARAM1 DATA: Information to PARAM1=ABCDEFG
Field 3 be placed in
Miscellaneous Field 3 (sets the misc field
on the account – 3 to ABCDEFG)
variable length, seven
positions
61 Cross PARAM1 Cross Reference PARAM1=99999999
Reference 1 number – 16 digit value 9999999
90 Add PARAM1 TRANCODE: Identifies PARAM1=02
Authorized the action being
Users on an requested, the value to (specifies that an
Account be passed is: “02” additional name is
being added to the
**This account)
Page 847
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
NonMon will PARAM2 SEQUENCE: Identifies PARAM2=000
not show the sequence code you
immediately wish to assign to this (specifies that First
in First Data. name, valid entries Data is to assign the
A nightly would include any next available
batch process number between 3 and sequence number)
must run 250 that is not already
before the assigned to a name on
data is the account. This PARAM2=003
reflected in parameter is optional
the host and will be auto- (specifies that the
system. assigned if not additional name
specified. should be assigned
sequence number
003)
PARAM3 NAME: Name of the PARAM3=TEST,USE
individual being added RJ
to the account in Last
Name,First Name MI (sets the additional
format with no space name on the
following the comma account as
separating last name “Test,User J”)
from first name
Page 848
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM4 PLASTIC: Code that PARAM4=0
specifies the type of
plastic to be issued to (specifies that
the cardholder, valid plastics will not be
entries: embossed for this
0 – No plastics cardholder on this
1 – Use parameters in account)
Plastic Products strategy
for plastic type 1 to
emboss plastics on the
account
2 – Use parameters for
plastic type 2
3 – Use parameters for
plastic type 3
4 – Use parameters for
plastic type 4
5 – Use parameters for
plastic type 5
6 – Do not emboss
plastics or create
embossing records –
should be used when
PCF parameter AO AC
EM is set to N
Page 849
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM5 CREDITFLAG: Code that PARAM5=3
represents the type of
account for credit (sets the additional
reporting purposes, user’s credit
valid entries are: reporting flag
2 – Joint contractual should be set to “3”
liability - Authorized User)
3 – Authorized User
4 – Joint
5 – Co-maker
6 – On-behalf of
7 – Maker
PARAM6 PICOUNT: Sets the PARAM6=1
count of presentation
instruments that will be (sets the PI or
issued for the plastic count should
cardholder role be set to 1 for this
name)
PARAM7 INDICATOR: This PARAM7=Y
parameter is for future
use and should be set to (specifies the
“Y” indicator as “Y”)
90 Change an PARAM1 TRANCODE: Identifies PARAM1=07
Additional the action being
Name on an requested, the value to (specifies that an
Account be passed is: “07” additional name is
being changed)
PARAM2 SEQUENCE: Identifies PARAM2=003
**This the sequence code of
NonMon will the name being (specifies that the
not show removed from the name with the
immediately account, 3 numeric sequence of 003
in First Data. positions. should be changed
A nightly on the account)
Page 850
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
batch process PARAM3 NAME: New name of PARAM3=TEST,USE
must run the user on the account RJ
before the in Last Name,First Name
data is MI format with no (sets the additional
reflected in space following the name on the
the host comma separating last account as
system. name from first name “Test,User J”)
91 Designated PARAM1 AMOUNT: Amount PARAM1=10155
Automatic cardholder agreed to
Payment pay via automatic (will set recurring
Amount payment option; viable automatic payment
length, 7 positions, amount to $101.55)
$$$$$¢¢ format
96 ACH PARAM1 FLAG: Checking or PARAM1=C
Prenoting Savings account code;
valid codes are C – (sets code to C for
Checking, S – Savings Checking)
PARAM2 TRANSIT: Transit PARAM2=12345678
routing number for ACH 3
prenoting; fixed length,
9 positions, numeric (sets the TRANSIT
to 123456789)
Page 851
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
for checks to actually
generate
102 User Flags PARAM1 Flag to update PARAM1=1 to
Valid values: update the flag in
0 – All four position 1
1 – Flag 1
2 – Flag 2
3 – Flag 3
4 – Flag 4
PARAM2 Value to post PARAM2=V
V represents card
activation
103 Cross PARAM1 Cross reference field PARAM1=2
Reference Values;
fields 1 and 3 1 – Field 1
2 – Field 3
PARAM2 Cross refence account PARAM2=99999999
number 99999999
105 Miscellaneous PARAM1 DATA: Information to PARAM1=A11C11D
Field 4 be placed in 111
Miscellaneous Field 4
on the account – (sets the misc field
variable length, ten 4 to A11C11D111)
positions
112 Misc Field 2 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 2 – Valid position 4 of Misc
codes are 1 through 5 Field 2)
with each code
representing a change
to that single position in
the field. To change the
entire field, use NM 59.
Page 852
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
113 Misc Field 3 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 3 – Valid position 4 of Misc
codes are 1 through 7 Field 3)
with each code
representing a change
to that single position in
the field. To change the
entire field, use NM 60.
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
114 Misc Field 4 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 4 – Valid position 4 of Misc
codes are 1 through 10 Field 4)
with each code
representing a change
to that single position in
the field. To change the
entire field, use NM
105.
Page 853
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
131 Customer PARAM1 Y – Skip Payment PARAM1=Y
Initiated Skip Blank – do not skip
Pay payment
133 Misc Field 5 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 5 – Valid position 4 of Misc
codes are 1 through 9 Field 5)
with 1 through 8
representing that single PARAM1=9
position in the field and
9 representing a change (will change all data
to the entire field in Misc Field 5)
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
135 Misc Field 6 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 6 – Valid position 4 of Misc
codes are 1 through 13 Field 6)
with 1 through 12
representing that single PARAM1=13
position in the field and
13 representing a (will change all data
change to the entire in Misc Field 6)
field
Page 854
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
136 Mother’s PARAM1 NAME: Last name to be PARAM1=JONES
Maiden Name used for the mother’s
maiden name field on (sets the mother’s
the account – variable maiden name on
length, eight positions, the account to
alpha only JONES)
Page 855
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
146 Marketing PARAM1 Code: PARAM1=7
Information 1 - Change the data for
Billing Address Valid
Indicator
2 - Change the data for
Home Phone Status
Code
3 - Change the data for
Business Phone Status
Code
4 - Change the data for
Deceased flag
This subtransaction is
for batch entry only.
5 - Change the data for
Alternate Language
Code
6 - Reserved for
restricted use
7 - Change the data for
Primary Customer
Solicitation Code
8 - Change the data for
Charge Off Prohibition
Code
9 - Change the data for
Address Relationship
Type Code
10 - Change the data for
Address Bypass
Validation Code
11 - Change the rules
dialer string
identification number
Page 856
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 Data PARAM2=Y
N - No, the address on
the account record is
not valid.
Y - Yes, the address on
the account record is
valid.
blank - Yes, the address
on the account record is
valid.
147 Alternate PARAM1 SUBTRAN: A value PARAM1=02
Financial representing the key
Reporting being updated – valid (specifies that the
Keys entries are: data being
01 – Key 1 submitted will be
02 – Key 2 placed in the field
03 – Key 3 Alternate Financial
04 – Key 4 Reporting Key #2)
PARAM2 DATA: The value to be PARAM2=987
written to the key
specified in PARAM1. (updates the key
Keys 1 and 2 are limited specified in
to 3 alpha/numeric PARAM1 to the
characters. Keys 3 and value “987”)
4 are limited to 5
alpha/numeric
characters.
Page 857
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
148 Misc Field 7 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 7 – Valid position 4 of Misc
codes are 1 through 11 Field 7)
with 1 through 10
representing that single PARAM1=11
position in the field and
11 representing a (will change all data
change to the entire in Misc Field 7)
field
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
149 Misc Field 8 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 8 – Valid position 4 of Misc
codes are 1 through 11 Field 8)
with 1 through 10
representing that single PARAM1=11
position in the field and
11 representing a (will change all data
change to the entire in Misc Field 8)
field
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
154 Promotion/ PARAM1 47 PARAM1=47
Protected Subtrans code
Page 858
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
Balances PARAM2 PBMETHOD – PARAM2=PB0001
Promotion/Protected
balance method
PARAM3 TYPE PARAM3=C
Valid codes:
C-Cash
M-Merchandise
N-Non-Interest Bearing
160 Credit Bureau PARAM1 SCORE: Credit Bureau PARAM1=725
Score score value – fixed
Information length, three positions (sets score to 725)
Required parameter
PARAM2 ID: Credit Bureau Code; PARAM2=3
representing the
specific credit bureau
providing the score –
fixed length, one
position, numeric only.
Valid Codes:
1 - TransUnion
2 - CBI/Equifax
3 - Experian
4 - Reserved for
restricted use only
5 - TransUnion Canada
6 - Equifax Canada
7 - Reserved for future
use
Required parameter
Page 859
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM3 CODE: Credit Bureau PARAM3=0701
Local code from the
Display Credit Bureau
Report screen;
represents the address
and phone number of
the local credit bureau
office, variable length,
four positions
Required parameter
PARAM4 A1: Credit Bureau PARAM4=0
Attribute first code, one
position – this code
indicates the worst
public record on file at
the credit bureau – set
to blank if not using this
field – a value of zero
indicates the best rating
and a value of 9 is the
worst rating
Required parameter
PARAM5 A2: Credit Bureau PARAM5=0
Attribute second code,
one position – this code
indicates the worst
derogatory information
on file at the credit
bureau – set to blank if
not using this field – a
value of zero indicates
the best rating and a
value of 9 is the worst
rating
Required parameter
Page 860
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM6 A3: Credit Bureau PARAM6=4
Attribute third code,
one position – this code
indicates the number of
trade lines the
cardholder has on file at
the credit bureau – set
to blank if not using this
field -
Valid codes:
0 - 1-2 trade lines
1 - 3-5 trade lines
2 - 6-8 trade lines
3 - 9-11 trade lines
4 - 12-14 trade lines
5 - 15-17 trade lines
6 - 18-20 trade lines
7 - 21-24 trade lines
8 - 25-29 trade lines
9 - 30 or more trade
lines
blank - The number of
trade lines is not used.
Required parameter
Page 861
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM7 DATE: Credit Bureau PARAM7=100511
Score Date – fixed
length, six positions,
YYMMDD format
Less than or equal to
current date but not
older than one year,
and
greater than the last
date posted on the
account
Required parameter
PARAM8 REASON1: Credit PARAM8=01
Bureau first reason
code, determines the
specific reason you
want communicated to
the cardholder to justify
the credit bureau’s
score for this account –
variable length, 2
positions
PARAM9 REASON2: Credit PARAM9=05
Bureau second reason
code, determines the
specific reason you
want communicated to
the cardholder to justify
the credit bureau’s
score for this account –
variable length, 2
positions
Page 862
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM10 REASON3: Credit PARAM10=15
Bureau third reason
code, determines the
specific reason you
want communicated to
the cardholder to justify
the credit bureau’s
score for this account –
variable length, 2
positions
PARAM11 REASON4: Credit PARAM11=19
Bureau fourth reason
code, determines the
specific reason you
want communicated to
the cardholder to justify
the credit bureau’s
score for this account –
variable length, 2
positions
168 Strategey PARAM1 CA – Indicates PARAM1=CA
Reallocation – Cardholder Account
Cardholder PARAM2 Portfolio – Identifier of PARAM2=1234
Account the Pricing portfilio
168 Strategy PARAM1 CP- Indicates PARAM1=CP
Reallocation – Cardholder Pricing
Cardholder PARAM2 Strategy – Pricing PARAM2=1234
Pricing Strategy to assign
PARAM3 Status PARAM3=L
Valid Codes:
L – Lock the Strategy on
the account
Blank – do nothing
Page 863
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM4 Type PARAM4=0
Valid Codes:
0 - Process cash
advance and
merchandise principals
using
the new Product
Control File interest
rate.
1 - Cash advance
balance
Process existing cash
advance principals using
the
current Product Control
File interest rate and
any new
cash advance principals
using the new Product
Control
File interest rate.
2 - Merchandise balance
Process existing
merchandise principals
using the
current Product Control
File interest rate and
any new
merchandise principals
using the new Product
Control
File interest rate.
3 - Cash advance and
merchandise balances
Process existing
merchandise and cash
PSCU – Propriety and Confidential advance Last Revised: 03/31/2023
principal using the Version 23.1
current Product Control
Page 864
File interest
rate and any new
merchandise and cash
advance
principals using the new
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
174 ACS PARAM1 ACS override strategy PARAM1=0001
Overridde Values 0001-0098
176 Misc Field 9 – PARAM1 CODE: Subtransaction PARAM1=4
Single code presenting the
Position position to change in (will only change
Misc Field 9 – Valid position 4 of Misc
codes are 1 through 11 Field 9)
with 1 through 10
representing that single PARAM1=11
position in the field and
11 representing a (will change all data
change to the entire in Misc Field 9)
field
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
177 Misc Field 10 PARAM1 CODE: Subtransaction PARAM1=4
– Single code presenting the
Position position to change in (will only change
Misc Field 10 – Valid position 4 of Misc
codes are 1 through 11 Field 10)
with 1 through 10
representing that single PARAM1=11
position in the field and
11 representing a (will change all data
change to the entire in Misc Field 10)
field
PARAM2 DATA: Information to PARAM2=C
be placed in the
location specified in the (places a “C” in the
CODE parameter designated
(PARAM1) position)
Page 865
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
184 NonDelinque PARAM1 Lower nondelinquent PARAM1=10000
nt Min Pay portion of minimum For $100
Due payment due
Amount
Format:
$$$$$$$$$$$$$$$¢¢
PARAM2 Nondelinquent portion PARAM2=0
of minimum payment
due amount
based on cash advances
Format:
$$$$$$$$$$$$$$$¢¢
189 Secondary PARAM1 DATE: Secondary PARAM1=19600401
Birth Date cardholder’s birth date -
fixed length, eight (sets the secondary
positions, CCYYMMDD cardholder
format birthdate to
04/01/1960)
191 Authorization PARAM1 Authorization strategy PARAM1=A400
Strategy ID id
197 Letter PARAM1 LETTER – Number PARAM1=A9Z1
Request identifying the letter to
send to the cardholder;
fixed length, four
characters, alpha
numeric.
202 Risk Score PARAM1 Score PARAM1=225
209 Approval PARAM1 CODE: User defined PARAM1=56789
Officer code representing the
person at your (sets the approval
institution whom officer listed on the
approved the account account to 56789)
and/or offer – variable
length, seven positions,
Page 866
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
numeric only
216 UPC Upates PARAM1 UPC field to update PARAM1=03
Valid values – 01-12 (updates UPC field
3)
PARAM2 Value for UPC field PARAM2=M
(updates the field
to M)
238 Suspend PARAM1 Code representing PARAM1=99
Fraud Required whether you want to
Strategy restrict this account
from fraud
authorization decision
processing or send this
account to a new
strategy. The value is
edited for a valid
strategy identifier or a
value of 98.
PARAM2 End date - Date you PARAM2=MMDDYY
Required want the System to
remove the restriction
or special strategy
processing. If the travel
ends on May 5 the end
date should be sent as
May 6 to revert the
strategy back to the
default. This will revert
the strategy during
overnight processing
May 5 – May 6.
Page 867
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
next processing day.
The end date must be
less than 30 years from
the current date.
PARAM3 Start Date - Date you PARAM3=MMDDYY
Optional – want the System to
If not begin the suspension of
included normal
strategy is fraud authorization
immediat decision processing or
ely send this account
suspende to a new strategy until
d. the date specified in the
end date in PARAM2.
This is an optional field.
If the start date is not
provided in the request,
the suspension begins
immediately. The
strategy will be
suspended during over
night process on the
start date. If you enter a
future date and that
future date is on a non-
processing date it will
not become effective
until after nightly
processing completes
following the date you
enter in this field.
PARAM4 Valid values: PARAM4=A
Required A – Add
C - Change
Page 868
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
602 Employee PARAM1 Indicator PARAM1=Y
Indicator
637 Cardholder PARAM1 STARTDATE: Minimum PARAM1=050106
Minimum payment due start date
Payment Due in MMDDYY format (sets the cardholder
Date minimum payment
due date to May 1,
2006)
PARAM2 ENDDATE: Minimum PARAM2=050107
payment due end date
in MMDDYY format – (sets the cardholder
leave this field blank if minimum payment
entering a value in due date to May 1,
PARAM3 – CYCLES 2007)
PARAM3 CYCLES: Number of PARAM3=10
cycles, variable length, 2
numeric positions (sets the cardholder
minimum payment
number of cycles to
10)
Page 869
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
638 Cardholder PARAM1 CODE: Code PARAM1=1
Minimum representing the
Payment Due method used to (sets the override
Override calculate the minimum code to 1)
Code payment – Valid entries
include:
1 – Use the largest of 3
amts. for the min. pmt.
* Amount indicated in
the Amount parameter
of PCF (CP PO MP)
* Calculated amount
based on either Percent
parameter of PCF (CP
PO MP) or rate entered
in CHD MIN PAY RT on
NM CL1 multiplied by
stmt. balance
2 – Allow cardholder to
set the min. pmt. (must
be greater than the
amount from option 1
above)
Page 870
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
639 Cardholder PARAM1 SUBTRAN: Code PARAM1=01
Minimum representing the type of
Payment Due information you are (defines the value
Rate/Amount entering into the DATA entered in PARAM2
parameter – valid to be a percentage
entries are: rate)
01 – The data is the
cardholder’s minimum PARAM2=02
pay rate
02 – The data is the (defines the value
cardholder’s future entered in PARAM2
fixed min. pmt. amount to be a dollar
03 – The data is the amount)
cardholder’s fixed min.
pay rate used to
calculate a future fixed
pmt. amt.
PARAM2 DATA: Amount or PARAM2=0100000
percent that
corresponds to the (sets the amount to
SUBTRAN code entered 10% or to
in PARAM1 above – $1000.00)
numeric only, 7
positions PARAM2=0010000
Page 871
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 END: Date the PARAM2=022807
cardholder’s automatic
payment processing to (sets the end date
end, MMDDYY format for automatic
payments to
February 28, 2007)
PARAM1& START and END date PARAM1=000000&
PARAM2 example PARAM2=999999
Page 872
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
or numbers
2 - Control Account
Identifier
Length: variable length,
16 positions
Edits: edited for
numeric values
This is an optional field.
The error message
INVALID SUB CD C FOR
ACCT appears if you
attempt to associate a
control account with
another control
account.
If the Commercial Card
Option parameter in the
Commercial Card
section (AO AC CC) of
the Product Control File
is set to N, you cannot
make changes to the
company ID or control
account number.
The System rejects the
non-monetary
transaction for
subtransaction code 2 if
the Control Account
Plastic Option
parameter in the same
section is set to zero
and the number of
plastics to issue field on
Page 873
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
the control account is
set to a value that is
greater than zero.
If the control account is
new and has not yet
cycled, the non-
monetary transaction is
accepted, and the
control account is
placed on one of the
CD-111-115, Cardholder
Exceptions Reports.
5 - Fleet Restriction
Code - Code
determining where a
fleet card can be used
This is a required field
for fleet card
processors.
If you do not set this
field, the System will set
this field to a value of
zero. Zero is not a valid
value for a card issued
within the Fleet BIN for
MasterCard.
MasterCard valid codes:
1 - Fleet card good for
fuel and other
products
2 - Fleet card good for
fuel only
Visa valid codes:
0 - Fleet card good for
Page 874
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
fuel, maintenance, and
nonfuel products
1 - Fleet card good for
fuel and maintenance
only
2 - Fleet card good for
fuel only
3 - Reserved
4 - Reserved
5 - Reserved
6 - Reserved
7 - Reserved
8 - Reserved
9 - Reserved
Retail fleet valid codes:
0 - The cardholder has
no purchasing
restrictions for the
retail fleet card.
1 - The cardholder can
use the retail fleet card
only for fuel purchases.
2 - The cardholder can
use the retail fleet card
only for fuel and oil
purchases.
3 - The cardholder can
use the retail fleet card
for fuel, oil, and other
related purchases.
Page 875
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
to enter at participating
POS devices
This is a required field
for fleet card
processors.
If you do not set this
field, the System will set
this field to a value of
zero. Zero is not a valid
value for a card issued
within the Fleet BIN for
MasterCard.
MasterCard valid codes:
1 - Prompt for ID and
odometer reading
2 - Prompt for vehicle
ID and odometer
reading
3 - Prompt for driver ID
and odometer reading
4 - Prompt for
odometer reading only
5 - No prompts
Visa valid codes:
0 - Reserved (no
prompt required)
1 - Prompt for ID and
odometer reading
2 - Prompt for vehicle
ID and odometer
reading
3 - Prompt for driver ID
and odometer reading
4 - Prompt for
odometer reading
Page 876
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
5 - No prompt
6 - Prompt for ID
The cardholder can
enter the 6-digit
numeric vehicle,
driver, or generic ID.
7 - Reserved (no
prompt required)
8 - Reserved (no
prompt required)
9 - Reserved (no
prompt required)
Retail fleet valid codes:
0 - No prompt required
1 - Prompt for driver ID
2 - Prompt for
odometer reading
3 - Prompt for vehicle
ID
4 - Prompt for driver ID
and odometer reading
5 - Prompt for vehicle
ID and odometer
reading
6 - Prompt for driver
ID, vehicle ID, and
odometer reading
Page 877
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
699 Expanded PARAM1 CODE PARAM1=20
Phone Valid codes:
Number 10 - Home area code
Information and telephone number
of the cardholder
11 - Business telephone
number of the
cardholder
20 - Mobile telephone
number of the
cardholder
30 - Pager number of
the cardholder
40 - Facsimile number
of the cardholder
50 - Client-defined
telephone number
Page 878
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 Cardholder * PARAM2=01
Cardholder identifier
Valid codes:
01 - Principal cardholder
02 – Secondary
cardholder
PARAM3 DATA – 10 digits phone PARAM3=99955512
number 12
Page 879
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM4 FLAG - Code PARAM4 =Y
determining whether
this telephone number
is valid and/or whether
this telephone number
may be used to
contact the cardholder
Valid codes:
B - The phone number is
valid and available for
SMS (short message
service) text messages
and voice contact.
C - Do not contact
cardholder at this
telephone number
because a cease and
desist agreement has
been filed.
D - This number has
been disconnected.
E - The cardholder is no
longer at this number.
N - The phone number
is not valid.
S - The phone number is
valid and available for
SMS (short message
service) text messages
only.
This code is available
only for client
controlled or mobile
telephone numbers.
U - The phone number
is unlisted.
PSCU – Propriety and Confidential V - The phone number is Last Revised: 03/31/2023
not verified. Version 23.1
X - Do not contact the
customer Page 880
at this
number.
Y - The phone number is
valid and available for
voice contact only.
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM5 Type
Valid codes:
I - Invalid number. An
outbound call will not
be placed to a phone
number containing this
value via the Fraud
Predictive Dialer or the
2Way-ConnectSM
service.
L - Land line. An
outbound call will be
placed to a phone
number
containing this value via
the Fraud Predictive
Dialer or the
2Way-ConnectSM
service dependent upon
the permission defined
within the phone flag
setting for this number.
U - Unknown type. An
outbound call will not
be placed to a phone
number containing this
value via the Fraud
Predictive Dialer or the
2Way-ConnectSM
service.
W - Mobile phone. An
outbound call will be
placed to a phone
number
containing this value via
the Fraud Predictive
PSCU – Propriety and Confidential Dialer or the Last Revised: 03/31/2023
2Way-ConnectSM Version 23.1
service dependent upon
Page 881
the permission defined
within the phone flag
setting for this number.
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
728 Automatic PARAM1 PERCENT: Percent of PARAM1=003500
Payment account balance that
Percent of must be paid, variable (sets the percent of
Balance length, 6 positions balance to be paid
at 35%)
729 Automatic PARAM1 CEILING: Maximum PARAM1=10000
Payment amount an account is
Ceiling expected to pay, viable (sets the maximum
length, 7 positions amount to pay to
$$$$$¢¢ format $100.00)
Page 882
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM3 Payment Type: PARAM3=C
Code designating the
type of account for the
withdrawal of a
demand Automated
Clearinghouse (ACH)
payment, and
designating whether the
cardholder initiated the
transaction
via telephone or via the
Internet
Valid codes:
C - Internet-initiated
transaction to be drawn
from a checking
account
The System enters WEB
in the standard entry
code field
on the transmitted ACH
file.
S - Internet-initiated
transaction to be drawn
from a savings
account
The System enters WEB
in the standard entry
code field
on the transmitted ACH
file.
1 - Telephone-initiated
transaction to be drawn
from a
checking account
Page 883
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
The System enters TEL
in the standard entry
code field on
the transmitted ACH
file.
The System validates all
transit routing numbers
for
telephone-initiated
transactions against the
Thomson
Routing and Transit
Number File before
sending the ACH
file to the Federal
Reserve. You must set
the ACH
Delivery Option
parameter in the
Automatic Payments
(AO CH AP) section of
the Product Control File
to F to use
this feature.
2 - Telephone-initiated
transaction to be drawn
from a
savings account
The System enters TEL
in the standard entry
code field on
the transmitted ACH
file.
The System validates all
transit routing numbers
Page 884
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
for
telephone-initiated
transactions against the
Thomson
Routing and Transit
Number File before
sending the ACH
file to the Federal
Reserve. You must set
the ACH
Delivery Option
parameter in the
Automatic Payments
(AO CH AP) section of
the Product Control File
to F to use
this feature.
3 - Any transaction to
be drawn from a
business checking
demand deposit
account (DDA).
The System enters CCD
in the standard entry
code field
on the transmitted ACH
file.
4 - Any transaction to
be drawn from a
business savings
DDA.
The System enters CCD
in the standard entry
code field
on the transmitted ACH
Page 885
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
file.
5 - Telephone-initiated
transaction via touch-
tone entry only,
with no verbal
authorization, to be
drawn from a checking
account
This option uses the
Prearranged Payment
and Deposit
(PPD) ACH file format.
The System enters PPA
in the
standard entry code
field on the transmitted
ACH file.
The System validates all
transit routing numbers
for
telephone-initiated
transactions against the
Thomson
Routing and Transit
Number File before
sending the ACH
file to the Federal
Reserve. You must set
the ACH
Delivery Option
parameter in the
Automatic Payments
(AO CH AP) section of
the Product Control File
to F to use
Page 886
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
this feature.
6 - Telephone-initiated
transaction via touch-
tone entry only,
with no verbal
authorization, to be
drawn from a savings
account
This option uses the
Prearranged Payment
and Deposit
(PPD) ACH file format.
The System enters PPA
in the
standard entry code
field on the transmitted
ACH file.
The System validates all
transit routing numbers
for
telephone-initiated
transactions against the
Thomson
Routing and Transit
Number File before
sending the ACH
file to the Federal
Reserve. You must set
the ACH
Delivery Option
parameter in the
Automatic Payments
(AO CH AP) section of
the Product Control File
to F to use
Page 887
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
this feature.
791
Page 888
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
791 Autopay PARAM1 Subtrans code 70 PARAM1=70
Entollment
Status
Page 889
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 Enrollment type: PARAM2=T
P - Paper
T - Telephone
W - Web
blank - Either not
enrolled or the
enrollment source is not
known
Page 890
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
792 Previous Exp PARAM1 Subtransaction code. PARAM1=42
Date Single Valid value : 42
Entity
Page 891
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 Previous Expiration PARAM2=0621
Date
Format MMYY
Page 892
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
793 Email Address PARAM1 CODE - subtransaction PARAM1=01
Changes code
Valid codes:
01 - cardholder home e-
mail address
02 - Status code
indicating whether the
home e-mail
address is valid
03 - Code representing
whether you can solicit
the
cardholder using this
home e-mail address
04 - Cardholder work e-
mail address
05 - Indicator
designating whether the
work e-mail address
is valid
06 - Indicator
designating whether
you can solicit the
cardholder using this
work e-mail address
Page 893
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
PARAM2 01 – Primary Cardholder PARAM2=01
PARAM3 Data associated with PARAM3=
the PARAM1 value [email protected]
Valid Values: g
01 - Cardholder home e-
mail address
Valid Value for
PARAM3:
Email address
02 - Status code
indicating whether the
home e-mail address is
valid
Valid values for
PARAM3:
N -No, the e-mail
address is not
valid.
Y -Yes, the e-
mail address is
valid.
03 - Code representing
whether you can solicit
the cardholder using
this home e-mail
address
Valid values for
PARAM3:
N - No, you
cannot solicit
the cardholder
using this e-mail
address.
Y - Yes, you can
solicit the
Page 894
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
cardholder using
this e-mail
address.
04 - Cardholder work e-
mail address
Valid Value for
PARAM3:
Email address
05 - Indicator
designating whether the
work e-mail address is
valid
Valid values for
PARAM3:
N - No, the e-
mail address is
not valid.
Y - Yes, the e-
mail address is
valid.
06 - Indicator
designating whether
you can solicit the
cardholder using this
work e-mail address
Valid values for
PARAM3:
N - No, you
cannot solicit
the cardholder
using this e-mail
address.
Y - Yes, you can
solicit the
cardholder using
Page 895
NonMon NonMon NonMon Description Example
Number Description Paramete
rs
this e-mail
address.
PARAM4 Email address PARAM4=abc@def.
com
Page 896
PI Non-Monetary transactions
The SENDDATAXML function (Function ID 1435) has been certified with the numbered PI
NonMons listed in the table below. The Data eXchange request for PI NonMons must
include the PINONMON=Y parameter in addition to the parameters listed below.
If the value of any parameter passed exceeds the acceptable length, the 1435 request
will fail. All descriptions include the acceptable length of the parameter.
When using the PI NonMon functions for a separate entity account, the actual PIID must
be used in the CARDNUMBER parameter.
Page 897
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
this account.
2 - Use the parameters
in the Plastic Products
strategy for plastic type
2 to emboss plastics on
this account.
3 - Use the parameters
in the Plastic Products
strategy for plastic type
3 to emboss plastics on
this account.
4 - Use the parameters
in the Plastic Products
strategy for plastic type
4 to emboss plastics on
this account.
5 - Use the parameters
in the Plastic Products
strategy for plastic type
5 to emboss plastics on
this account.
PARAM- Cardholder role code: PARAM-
CUST_ROLE 01 – Primary CUST_ROLE_CD=01
_CD 02 - Secondary
03 – Authorized
PARAM- Member Sequence ID PARAM-
MBR_SQNC 00001 – Primary MBR_SQNC_ID=000
_ID 00002 – Secondary 01
00003-09999 –
Authorized
42 PIN Mailer PARAM- Member Sequence ID PARAM-
Request MBR_SQNC 00003-09999 – MBR_SQNC_ID=000
_ID Authorized 03
PARAM- PIN Mailer Code PARAM-
PIN_MALR_ Valid value – 9 for PIN_MALR_CD=9
Page 898
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
CD authorized users
145 Personal PARAM- Personalized Embossing PARAM-
Emboss PRSN_EMBS text PRSN_EMBS_TX=Pe
Code _TX rsonalized%20Text
PARAM- Valid Values- PARAM-
CUST_ROLE 01 – Primary CUST_ROLE_CD=01
_CD 02 – Secondary
03 – Authorized
PARAM- Valid Values PARAM-
MBR_SQNC 00001 – Primary MBR_SQNC_ID=000
_ID 00002 – Secondary 01
00003 – 09999 -
Authorized
194 Force PARAM- Valid codes: PARAM-
emboss NAME_EMB 0 - Emboss plastics for NAME_EMBS_CD=1
S_CD all active cardholder
presentation instrument
identifiers on a nondual
account, or emboss
plastics for all active
cardholder presentation
instrument identifiers
on the drive side of a
dual account
You must select this
option if you use card
activation. Be aware
that the System will
deactivate all existing
plastics on the account,
or all existing plastics on
a dual account’s drive
side.
1 - Emboss plastic(s) for
the principal cardholder
Page 899
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
on a nondual account,
or for the principal
cardholder on the drive
side of a dual account
2 - Emboss plastic(s) for
the secondary
cardholder on a
nondual
account, or for the
secondary cardholder
on the drive side of a
dual
account
This code will not post
unless a secondary
cardholder presentation
instrument identifier is
on the account record.
3 - Emboss a plastic for
the name entered in the
NAME field, or for the
name that corresponds
with the identifier
entered in the
SEQUENCE field for the
nondual account or for
the drive side of a
dual account
If you use this option,
the System checks the
principal and secondary
cardholder names, and
the additional
cardholder names to
find an exact match for
Page 900
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
the name to emboss.
PARAM- Plastic Count PARAM-PI_CT=1
PI_CT
PARAM- Card holder name – PARAM-
NAME_EMBS required when PARAM- NAME_EMBS_TX=P
_TX
NAME_EMBS_CD=3 rimary,Testaccount
PARAM- Member Sequence ID PARAM-
MBR_SQNC_ 00001-Primary MBR_SQNC_ID=000
ID
00002-Secondary 01
00003-09999 –
Authorized
Required when PARAM-
NAME_EMBS_CD is not
equal to 0.
PARAM- Card activation code – PARAM-
CARD_ACTV Valid only for Separate CARD_ACTV_CD=Y
_CD
Entity
Valid codes:
A - Process card
activation for the plastic
according to existing
activation controls.
N - Do not process the
plastic using existing
card activation controls.
Y - Process card
activation for the plastic
according to existing
activation controls.
blank - Process card
activation for the plastic
according to existing
activation controls.
200 Force PARAM- Valid codes: PARAM-
Page 901
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
Emboss NAME_EMB 0 - Emboss plastics for NAME_EMBS_CD=1
Plastic and S_CD all active cardholder
Rush presentation instrument
identifiers on a nondual
account, or emboss
plastics for all active
cardholder presentation
instrument identifiers
on the drive side of a
dual account
You must select this
option if you use card
activation. Be aware
that the System will
deactivate all existing
plastics on the account,
or all existing plastics on
a dual account’s drive
side.
1 - Emboss plastic(s) for
the principal cardholder
on a nondual account,
or for the principal
cardholder on the drive
side of a dual account
2 - Emboss plastic(s) for
the secondary
cardholder on a
nondual
account, or for the
secondary cardholder
on the drive side of a
dual
account
This code will not post
Page 902
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
unless a secondary
cardholder presentation
instrument identifier is
on the account record.
3 - Emboss a plastic for
the name entered in the
NAME field, or for the
name that corresponds
with the identifier
entered in the
SEQUENCE field for the
nondual account or for
the drive side of a
dual account
If you use this option,
the System checks the
principal and secondary
cardholder names, and
the additional
cardholder names to
find an exact match for
the name to emboss.
PARAM- Plastic count PARAM-PI_CT=1
PI_CT
PARAM- Card holder name –
NAME_EMB required when PARAM-
S_TX NAME_EMBS_CD=3
PARAM- Valid Codes:
RUSH_MAIL AU - Send plastics to
_CD you via UPS® Next Day
Air® shipment
BA - Mail plastics to
you via DHL*
BC - Mail plastics to
you via certified mail
Page 903
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
BF - Mail plastics to you
via FedEx
BP - Mail plastics to you
via postal express
BR - Mail plastics to
you via registered mail
BU - Send plastics to
you via UPS® Next Day
Air Saver® shipment.
B1 - Mail plastics to you
via first class mail
CA - Mail plastics to
cardholder via DHL*
CC - Mail plastics to
cardholder via certified
mail
CF - Mail plastics to
cardholder via FedEx
CP - Mail plastics to
cardholder via postal
express
CR - Mail plastics to
cardholder via
registered mail
CU - Send plastics to
cardholder via UPS®
Next Day Air Saver®
shipment
C1 - Mail plastics to
cardholder via first
class mail.
DU - Send plastics to
cardholder via UPS®
Next Day Air®
shipment.
Page 904
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
XA - Mail plastics to
cardholder for Saturday
delivery via Airborne
XF - Mail plastics to
cardholder for Saturday
delivery via FedEx
XU - Send plastics to
cardholder for Saturday
delivery via UPS® Next
Day Air® shipment.
ZA - Mail plastics to you
for Saturday delivery
via Airborne
ZF - Mail plastics to you
for Saturday delivery
via FedEx
blank - Do not expedite
new plastics
ZU - Send plastics to
you for Saturday
delivery via UPS® Next
Day Air® shipment.
Page 905
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
PARAM- Card activation code – PARAM-
CARD_ACTV Required for Separate CARD_ACTV_CD=A
_CD Entity
Valid codes:
A - Process card
activation for the plastic
according to existing
activation controls.
N - Do not process the
plastic using existing
card activation controls.
Y - Process card
activation for the plastic
according to existing
activation controls.
blank - Process card
activation for the plastic
according to existing
activation controls.
229 Last Plastic PARAM- Date of last plastic PARAM-
Date PI_MALR_D Format: PI_MALR_DT=0316
T MMDDYY 21
PARAM- Customer role code PARAM-
CUST_ROLE 01 – Primary CUST_ROLE_CD=01
_CD 02 – Secondary
03 – Authorized
PARAM- Member Sequence ID PARAM-
MBR_SQNC 00001 – Primary MBR_SQNC_ID=000
_ID 00002 – Secondary 01
00003 – 09999 –
Authorized
782 PI Status PARAM- 16 PARAM-
SUB_TRANS SUB_TRANS_CD=16
_CD
Page 906
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
PARAM- A – Authorization PARAM-
PI_STTS_CD prohibited PI_STTS_CD=A
PARAM- Member Sequence ID PARAM-
MBR_SQNC 00001 – Primary MBR_SQNC_ID=000
_ID 00002 – Secondary 01
00003 – 09999 –
Authorized
PI Type PARAM- 35 PARAM-
SUB_TRAN_ SUB_TRAN_CD=35
CD
PARAM- PI Type PARAM-PI_TYPE=08
PI_TYPE 06 for Contactless and
EMV
08 for EMV only
PARAM- Customer Role Code PARAM-
ROLE_CD 01 – Primary ROLE_CD=01
02 – Secondary
03 – Authorized
PARAM- Member Sequence PARAM-
MBR_SQNC Code MBR_SQNCE_CD=0
_CD 00001 – Primary 0001
00002 – Secondary
00003-09999 –
Authorized
Previous PARAM- 43 PARAM-
Expiration SUB_TRAN_ SUB_TRAN_CD=43
Date CD
PARAM- Previous expiration date PARAM-
PRIR_EXPR_ YYYYMMDD PRIR_EXPR_DT=202
DT 30430
PARAM- Customer Role Cod PARAM-
CUST_ROLE 01-Primary CUST_ROLE_CD=03
_CD 02-Secondary
03-Authorized
Page 907
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
PARAM- Member Sequence PARAM-
MBR_SQNC Number MBR_SQNC_ID=000
_ID 00001-Primary 04
00002-Secondary
00003-09999 –
Authorized
Travel PARAM- Subtrans code to set the PARAM-
Strategy – SUB_TRAN_ expiration date of the SUB_TRAN_CD=48
Set CD fraud strategy
Expiration PARAM- Data the suspended PARAM-
date PI_FRAD_ST strategy will expire PI_FRAD_STGY_EXP
(subtrans GY_EXPR_D R_DT=YYYYMMDD
48) must be T
executed PARAM- Customer Role Code: PARAM-
first before CUST_ROLE 01 – Primary CUST_ROLE_CD=01
Subtrans 47 _CD 02 – Secondary
03 – Authorized
PARAM- Member Sequence: PARAM-
MBR_SQNC 00001 – Primary MBR_SQNC_ID=000
_ID 00002 – Secondary 01
00003-09999 –
Authorized
Travel PARAM- Sub Trans Code for PARAM-
Strategy – SUB_TRAN_ setting the suspension SUB_TRAN_CD=47
Set CD strategy and start date
suspension PARAM- Fraud strategy to PARAM-
strategy and PI_FRAD_ST suspend to during PI_FRAD_STGY_ID=
start date GY_ID period of travel 75
PARAM- Start date for the period PARAM-
PI_FRAD_ST of travel PI_FRAD_STGY_STR
GY_STRT_D T_DT=YYYYMMDD
T
PARAM- Customer Role Code: PARAM-
CUST_ROLE 01 – Primary CUST_ROLE_CD=01
Page 908
PI NonMon NonMon Description Example
NonMon Description Parameters
Number
_CD 02 – Secondary
03 – Authorized
PARAM- Member Sequence: PARAM-
MBR_SQNC 00001 – Primary MBR_SQNC_ID=000
_ID 00002 – Secondary 01
00003-09999 –
Authorized
Page 909
30 Appendix L – Special Characters
Some characters present the possibility of being misunderstood within URLs for various
reasons. These characters should also always be encoded.
Page 910
URL encoding of a character consists of a "%" symbol, followed by the two-digit
hexadecimal representation (case-insensitive) of the ISO-Latin code point for the
character.
31.1 MasterCard
Page 911
Minor Outlying Islands, Vanuatu, Vietnam, Wallis and
Futuna Islands
Region D Europe
Albania, Andorra, Antarctica, Armenia, Austria, Azerbaijan,
Belarus, Belgium, Belize, Bosnia and Herzegovina,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark,
Estonia, Faeroe Islands, Falkland Islands
(Malvinas), Finland, France, French Guiana, Georgia,
Germany, Gibraltar, Greece, Greenland, Guadeloupe,
Hungary, Iceland, Ireland, Israel, Italy, Kazakhstan,
Kyrgyzstan, Latvia, Liechtenstein, Lithuania,
Luxembourg, Macedonia (Former Yugoslav Republic of),
Malta, Martinique, Moldova, Monaco, Netherlands, Norway,
Poland, Portugal, Reunion, Romania, Russian Federation,
Saint Helena, San Marino, Slovakia, Slovenia, South
Georgia and South Sandwich Islands, Spain, Svalbard and
Jan Mayen Islands, Sweden, Switzerland, Tajikistan,
Turkey, Turkmenistan, Ukraine, United Kingdom,
Uzbekistan, Vatican City State, Western Sahara,
Yugoslavia
Region E South Asia, Middle East and Africa
Algeria, Angola, Bahrain, Benin, Botswana, Bouvet Island,
Burkina Faso, Burundi, Cameroon (United Republic of),
Cape Verde Island, Central African Republic, Chad,
Comoro Islands, Congo, Congo (Democratic Republic of
the), Djibouti, Egypt, Equatorial Guinea, Eritrea, Ethiopia,
French Southern Territories, Gabon, Gambia, Ghana,
Guinea, Guinea-Bissau, Iran, Iraq, Ivory Coast, Jordan,
Kenya, Kuwait, Lebanon, Lesotho, Liberia, Libyan Arab
Jamahiriya, Madagascar, Malawi, Mali, Mauritania,
Mauritius, Morocco, Mozambique, Namibia, Niger, Nigeria,
Occupied Palestinian Territory, Oman, Pakistan, Qatar,
Rwanda, Sao Tome and Principe, Saudi Arabia, Senegal,
Seychelles, Sierra Leone, Somalia, South Africa, Sudan,
Swaziland, Syrian Arab Republic, Tanzania (United
Republic of), Togo, Tunisia, Uganda, United Arab Emirates,
Yemen, Zaire, Zambia, Zimbabwe
Region Z All Regions (1 and A-E) *
*Use Region Z for merchant processing only, not for listing
accounts
Page 912
31.2 Visa
Page 913
Greenland, Guernsey, Hungary, Iceland, Ireland, Isle of
Man, Israel, Italy, Jersy, Kazakhstan, Kyrgyzstan, Latvia,
Liechtenstein, Lithuania, Luxembourg, Macedonia (the
former Yugoslav Republic of), Malta, Moldova (Republic
of), Monaco, Netherlands, Norway, Poland, Portugal,
Romania, Russian Federation, San Marino, Slovakia,
Slovenia, Spain, Sweden, Switzerland, Tajikistan, Turkey,
Ukraine, United Kingdom, Uzbekistan, Yugoslavia
Region F Latin America
Anguilla, Antigua Barbuda, Argentina, Bahamas, Barbados,
Belize, Bermuda, Bolivia, Brazil, British Virgin Islands,
Cayman Islands, Chile, Columbia, Costa Rica, Cuba,
Dominica, Dominican Republic, Ecuador, El Salvador,
Falkland Islands, French Guiana, Grenada, Guadeloupe,
Guatemala, Guyana, Haiti, Honduras, Jamaica, Martinique,
Mexico, Montserrat, Netherland Antilles, Nicaragua,
Panama, Paraguay, Peru, Puerto Rico, Surinam, St.
Kitts/Nevis Islands, St. Lucia, St. Vincent and the
Grenadines, Trinidad and Tobago, Turks and Caicos
Islands, Uruguay, U.S. Virgin Islands, Venezuela
Region Y All non-U.S. regions (A, B, C, E, F)
You cannot manually enter region code Y. Region Y is a
Visa-defined region that displays when you enter non-U.S.
regions A, B, C, E, and F on the WC, Visa Warning Bulletin
transaction. Region 0 is automatically entered when you
enter a non-U.S. region.
Page 914
Appendix N – Authorization Type Codes and Transaction Type
Codes
Authorization type codes
AA - Authorization adjustment
AC - Activation code notification message for token provisioning via step-up
authentication processing
AD - Authorization adjustment declined
AP - Preauthorization request approved
AS - Account status inquiry service or payment account status inquiry
BC - Cash authorization approved on the secondary central processing unit
(CPU) and sent to the primary CPU as a manual authorization
BM - Merchandise authorization approved on the secondary CPU and sent to
primary CPU as a manual authorization
CA - Cash advance authorization approved
CB - Cash advance authorization declined on the secondary CPU and sent to
the primary CPU as a manual authorization
CD - Cash advance authorization declined
CE - Cash advance authorization approved by expansion
CO - Override declined cash advance
CP - Cash advance authorization approved by positive identification
CS - Cash referral
CT - Cash advance authorization approved by name
CX - Cash advance authorization manually declined
DA - Duplicate authorization
DC - Cash authorization approved without issuer contact
DM - Merchandise authorization approved without issuer contact
DP - Preauthorization request denied
EC - Balance inquiry approved
IA - Issuer’s adjustment
IV - Reserved for restricted use
MA - Merchandise authorization approved
AUTH GRANTED appears in the DESC field if the authorization was
approved for the requested amount. PARTIAL APPROVAL appears in
the DESC field if the authorization approval amount was less than the
requested amount.
MB - Merchandise authorization declined on the secondary CPU and sent to
the primary CPU as a manual authorization
MC - Right-time credit or return
Page 915
MD - Merchandise authorization declined
ME - Merchandise authorization approved by expansion
MI - Right-time payment
MO - Override declined merchandise authorization
MP - Merchandise authorization approved by positive identification
MR - Right-time pay/reversal
MS - Merchandise referral
MT - Merchandise authorization approved by name
MX - Merchandise authorization manually declined
PA - Permanent authorization request
PP - Visa® and Mastercard® person-to-person payment transaction approval
PR - Visa and Mastercard person-to-person payment transaction reversal
PX - Visa and Mastercard person-to-person payment transaction decline
PZ - Permanent authorization adjustment
QA - Merchandise return adjustment
QD - Merchandise return declined
QQ - Reserved for restricted use
QR - Merchandise return approved
QZ - Merchandise return adjustment declined
TA - Account status check via a token provisioning request resulted in an
approved response
TM - Token maintenance, such as activation, deactivation, suspension, or
exception.
TN - Token has been granted, linked to the cardholder account, and
provisioned
VA - Private label ETC return posted at the time of return
XC - Manual override cash advance authorization
XM - Manual override merchandise authorization
Page 916
280 - Specific credit amount adjustment
281 - Cash advance item charge refund
282 - Late charge refund
283 - Merchandise finance charge refund
284 - Cash advance finance charge refund
286 - Merchandise item charge refund
287 - Overlimit charge refund
400 - Account transfer
401 - Reserved for First Data use only
This transaction code indicates that an adjustment transaction was posted
during an account transfer.
900 - Finance charge (item charge)
910 - Monetary transaction that has been memo posted to the account
(Commercial Card accounts only)
This transaction code is also used for memo details identifying the diverted
from account number.
911 - Memo posted return, return reversal, or return amount adjustment
(Commercial Card accounts only)
912 - Memo posted payment, payment reversal, payment amount
adjustment, or other monetary adjustment to the account
(Commercial Card accounts only)
947 - IVA tax (Latin America), late charge, or surcharge (Australia) detail
948 - Foreign transaction fee
959 - Reserved for restricted use
960 - Reserved for restricted use
961 - Late charge
962 - Credit insurance charge
963 - Finance charge (cash or merchandise)
964 - Merchandise finance charge
965 - Overlimit account message
966 - Reserved for restricted use – Statement Messages
967 - Account Level ProcessingSM strategy change message
976 - Reserved for restricted use
977 - Rebate redeemed (CoBrand accounts only)
978 - Reserved for restricted use
979 - Reserved for restricted use
981 - Account balance details for MULTRAN accounts
984 - Backdated cash advance finance charge
985 - Backdated payment interest adjustments
986 - Cash advance item charge
987 - Merchandise item charge
Page 917
988 - Overlimit charge
989 - Interest earned or credit interest
990 - Service charge or statement charge
991 - Cash advance item charge
992 - Fee or finance charge rebates
993 - Backdated payment or cash advance adjustments
994 - Skip payment certificate message
997 - Retail special details
998 - Airline itinerary special details
999 - For First Data use only
Page 918
3004 Travel Trans World Airlines (Visa Only)
3005 Travel British Airways
3006 Travel Japan Airlines
3007 Travel Air France
3008 Travel Lufthansa
3009 Travel Air Canada
3010 Travel Royal Dutch Airlines (KLM)
3011 Travel Aeroflot
3012 Travel Qantas
3013 Travel Alitalia
3014 Travel Saudi Arabian Airlines
3015 Travel Swiss International Air
3016 Travel Scandinavian Airline System (SAS)
3017 Travel South African Airways
3018 Travel Varig (Brazil)
3019 Travel Germanwings GMBH (MC effective now, Visa – 10/2006)
3020 Travel Air India
3021 Travel Air Algerie
3022 Travel Philippine Airlines
3023 Travel Mexicana
3024 Travel Pakistan International
3025 Travel Air New Zealand
3026 Travel Emirates Airlines
3027 Travel Union De Transports Aeriens (UTA/INTERAIR)
3028 Travel Air Malta
3029 Travel SN Brussels Airlines
3030 Travel Aerolineas Argentinas
3031 Travel Olympic Airways
3032 Travel El Al
3033 Travel Ansett Airlines
3034 Travel Australian Airlines
3035 Travel Tap Air Portugal (TAP)
3036 Travel Viacao Aerea Sao Paulo (VASP)
3037 Travel Egyptair
3038 Travel Kuwait Airways
3039 Travel Avianca
Page 919
3040 Travel Gulf Air (Bahrain)
3041 Travel Balkan-Bulgarian Airlines
3042 Travel Finnair
3043 Travel Aer Lingus
3044 Travel Air Lanka
3045 Travel Nigeria Airways
3046 Travel Cruzeiro Do Sul (Brazil)
3047 Travel Turk Hava Yollari (THY) (Turkey)
3048 Travel Royal Air Maroc
3049 Travel Tunis Air
3050 Travel Icelandair
3051 Travel Austrian Airlines
3052 Travel Lanchile
3053 Travel Aviacion Y Comercio (Aviaco) (Spain)
3054 Travel Linea Aerea Del Cobre (Ladeco) (Chile)
3055 Travel Lloyd Aero Boliviano (LAB) (Bolivia)
3056 Travel Quebecaire
3057 Travel Virgin America
3058 Travel Delta
3059 Travel DBA Luftfahrtgesellschaft MBH
3060 Travel Northwest
3061 Travel Continental
3062 Travel Hapag-Lloyd Express
3063 Travel Us Airways
3064 Travel Adria Airways
3065 Travel Airinter
3066 Travel Southwest
3067 Travel Vanguard Airlines
3068 Travel Air Astana
3069 Travel SUN COUNTRY AIRLINES
3071 Travel Air British Columbia
3072 Travel CEBU Pacific
3075 Travel Singapore Airlines
3076 Travel Aeromexico
3077 Travel Thai Airways
3078 Travel China Airlines
Page 920
3079 Travel Jetstar Airways
3081 Travel Nordair (Visa Only)
3082 Travel Korean Airlines
3083 Travel Air Afrique
3084 Travel Eva Airlines
3085 Travel Midwest Express Airlines, Inc
3087 Travel Metro Airlines
3088 Travel Croatia Airlines
3089 Travel Transaero
3090 Travel Uni Airways Corporation
3094 Travel Zambia Airways
3096 Travel Air Zimbabwe
3097 Travel Spanair
3098 Travel Asiana Airlines
3099 Travel Cathay Pacific
3100 Travel Malaysian Airline System
3102 Travel Iberia
3103 Travel Garuda (Indonesia)
3106 Travel Braathens S.A.F.E. (Norway)
3110 Travel Wings Airways
3111 Travel British Midland
3112 Travel Windward Island
3115 Travel Tower Air (Visa Only)
3117 Travel Venezolana International De Aviacion (Visa Only)
3118 Travel Valley Airlines (Visa Only)
3125 Travel Tan
3126 Travel Talair (Visa Only)
3127 Travel TACA International
3129 Travel Surinam Airway
3130 Travel Sun World International
3131 Travel VLM Airlines
3132 Travel Frontier Airlines
3133 Travel Sunbelt Airlines (Visa Only)
3135 Travel Sudan Airways
3136 Travel Qatar Airways
3137 Travel Singleton
Page 921
3138 Travel Simmons Airlines
3143 Travel Scenic Airlines (Visa Only)
3144 Travel Virgin Atlantic
3145 Travel San Juan Airlines (Visa Only)
3146 Travel LUXAIR
3148 Travel Air Littoral SA
3151 Travel Air Zaire
3154 Travel Princeville (Visa Only)
3156 Travel Go Fly Ltd.
3159 Travel Provincetown-Boston Airways (PBA)
3161 Travel All Nipon Airways
3164 Travel Norontair
3165 Travel New York Helicopter (Visa Only)
3167 Travel Aero Continente - Aerocontinente
3170 Travel Mount Cook (Visa Only)
3171 Travel Canadian Airlines International
3172 Travel Nationair
3174 Travel Jetblue
3175 Travel Middle East Air
3176 Travel Metroflight Airlines
3177 Travel Air Tran Airways
3178 Travel Mesa Air
3180 Travel Westjet Airlines Ltd
3181 Travel Malev
3182 Travel Lot (POLAND)
3183 Travel Oman Aviation Services
3184 Travel Liat
3185 Travel Linea Aeropostal Venezolana (Lav) (Venezuela)
3186 Travel Lineas Aereas Paraguayas (Lap) (Paraguay)
3187 Travel Lacsa (Costa Rica)
3188 Travel Virgin Express
3190 Travel Jugoslav Air
3191 Travel Island Airlines
3192 Travel Iran Air
3193 Travel Indian Airlines
3196 Travel Hawaiian Air
Page 922
3197 Travel Havasu Airlines
3200 Travel Guyana Airways
3203 Travel Golden Pacific Air (Visa Only)
3204 Travel Freedom Air
3206 Travel China Eastern Airlines
3211 Travel Norwegian Air Shuttle
3212 Travel Dominicana
3213 Travel Malmo Aviation
3215 Travel Dan Air Services (Visa Only)
3216 Travel Cumberland Airlines (Visa Only)
3217 Travel Ceskoslovenske Aerolinie (CSA)
3218 Travel Crown Air (Visa Only)
3219 Travel Compania Panamena De Aviacion (COPA)
3220 Travel Compania Faucett
3221 Travel Transportes Aeros Militares Ecuatorianos
3222 Travel Command Airways
3223 Travel Comair
3226 Travel Skyways Air
3228 Travel Cayman Airways
3229 Travel Saeta (Sociedad Ecuatorianos De Transportes Aereos)
3231 Travel Sahsa (Servicio Aero De Honduras)
3233 Travel Capitol Air (Visa Only)
3234 Travel British West Indies Airways (BWIA)
3235 Travel Brockway Air (Visa Only)
3236 Travel Air Arabia Airlines
3238 Travel Bemidji Airlines (Visa only)
3239 Travel Bar Harbor Airlines
3240 Travel Bahamasair
3241 Travel Aviateca (Guatemala)
3242 Travel Avensa
3243 Travel Austrian Air Service
3245 Travel Easyjet Airlines
3246 Travel Ryanair
3247 Travel Gol Airlways
3248 Travel Tam Airlines
3251 Travel Aloha Airlines
Page 923
3252 Travel Antilean Airlines (ALM)
3253 Travel America West
3254 Travel Us Air Shuttle (Visa Only)
3256 Travel Alaska Airlines
3259 Travel American Trans Air
3260 Travel Spirit Airlines
3261 Travel Air China
3262 Travel Reno Air Inc (Visa only)
3263 Travel Asc Airline (M/C Only)
3266 Travel Air Seychelles
3267 Travel Air Panama
3280 Travel Air Jamaica
3282 Travel Air Djibouti
3284 Travel Aero Virgin Islands
3285 Travel Aero Peru
3286 Travel Aerolineas Nicaraguensis
3287 Travel Aero Coach Aviation
3291 Travel Ariana Afghan
3292 Travel Cyprus Airways
3293 Travel Equatoriana
3294 Travel Ethiopian Airlines
3295 Travel Kenya Airways
3296 Travel Air Berlin PLC & Co. Luftverkehrs KG (MC effective now,
3297 Travel Tarom Romanian Air Transport
3298 Travel Air Mauritius
3299 Travel Travel
3300 Travel Travel
3301 Travel Wizz Air (New Airline)
3302 Travel Travel
3303 Travel Travel
3304 Travel Travel
3305 Travel Travel
3306 Travel Travel
3307 Travel Travel
3308 Travel Travel
3309 Travel Travel
Page 924
3310 Travel Travel
3311 Travel Travel
3312 Travel Travel
3313 Travel Travel
3314 Travel Travel
3315 Travel Travel
3316 Travel Travel
3317 Travel Travel
3318 Travel Travel
3319 Travel Travel
3320 Travel Travel
3321 Travel Travel
3322 Travel Travel
3323 Travel Travel
3324 Travel Travel
3325 Travel Travel
3326 Travel Travel
3327 Travel Travel
3328 Travel Travel
3329 Travel Travel
3330 Travel Travel
3331 Travel Travel
3332 Travel Travel
3333 Travel Travel
3334 Travel Travel
3335 Travel Travel
3336 Travel Travel
3337 Travel Travel
3338 Travel Travel
3339 Travel Travel
3340 Travel Travel
3341 Travel Travel
3342 Travel Travel
3343 Travel Travel
3344 Travel Travel
3345 Travel Travel
Page 925
3346 Travel Travel
3347 Travel Travel
3348 Travel Travel
3349 Travel Travel
3350 Travel Travel
3351 -3500 Travel Car Rental
3351 Travel Affiliated Auto Rental
3352 Travel American Intl Rent-A-Car
3353 Travel Brooks Rent-A-Car
3354 Travel Action Auto Rental
3355 Travel Sixt Car Rental
3357 Travel Hertz
3359 Travel Payless Car Rental
3360 Travel Snappy Car Rental
3361 Travel Airways Rent-A-Car
3362 Travel Altra Auto Rental
3364 Travel Agency Rent-A-Car
3366 Travel Budget Rent-A-Car
3368 Travel Holiday Rent-A-Car
3370 Travel Rent-A-Wreck
3374 Travel Accent Rent-A-Car
3376 Travel Ajax Rent-A-Car
3380 Travel Triangle Rent A Car
3381 Travel Europ Car
3385 Travel Tropical Rent-A-Car
3386 Travel Showcase Rental Cars
3387 Travel Alamo Rent-A-Car
3388 Travel Merchants Rent-A-Car
3389 Travel Avis Rent-A-Car
3390 Travel Dollar Rent-A-Car
3391 Travel Europe By Car
3393 Travel National Car Rental
3394 Travel Kemwall Group Rent-A-Car
3395 Travel Thrifty Car Rental
3396 Travel Tilden Rent-A-Car
3398 Travel Econo-Car Rent-A-Car
Page 926
3400 Travel Auto Host Car Rentals
3405 Travel Enterprise Rent-A-Car
3409 Travel General Rent-A-Car
3412 Travel A-1 Rent-A-Car
3414 Travel Godfrey Natl Rent-A-Car (Visa Only)
3419 Travel Travel
3420 Travel Ansa Intl Rent-A-Car
3421 Travel Allstate Rent-A-Car
3423 Travel Avcar Rent-A-Car
3425 Travel Automate Rent-A-Car
3427 Travel Avon Rent-A-Car
3428 Travel Carey Rent-A-Car
3429 Travel Insurance Rent-A-Car
3430 Travel Major Rent-A-Car
3431 Travel Replacement Rent-A-Car
3432 Travel Reserve Rent-A-Car
3433 Travel Ugly Duckling Rent-A-Car
3434 Travel USA Rent-A-Car
3435 Travel Value Rent-A-Car
3436 Travel Autohansa Rent-A-Car
3437 Travel Cite Rent-A-Car (Visa Only)
3438 Travel Interent Rent-A-Car
3439 Travel Milleville Rent-A-Car
3440 Travel Travel
3441 Travel Advantage Rent-A-Car
3442 Travel Travel
3443 Travel Travel
3444 Travel Travel
3445 Travel Travel
3446 Travel Travel
3447 Travel Travel
3448 Travel Travel
3449 Travel Travel
3450 Travel Travel
3451 Travel Travel
3452 Travel Travel
Page 927
3453 Travel Travel
3454 Travel Travel
3455 Travel Travel
3456 Travel Travel
3457 Travel Travel
3458 Travel Travel
3459 Travel Travel
3460 Travel Travel
3461 Travel Travel
3462 Travel Travel
3463 Travel Travel
3464 Travel Travel
3465 Travel Travel
3466 Travel Travel
3467 Travel Travel
3468 Travel Travel
3469 Travel Travel
3470 Travel Travel
3471 Travel Travel
3472 Travel Travel
3473 Travel Travel
3474 Travel Travel
3475 Travel Travel
3476 Travel Travel
3477 Travel Travel
3478 Travel Travel
3479 Travel Travel
3480 Travel Travel
3481 Travel Travel
3482 Travel Travel
3483 Travel Travel
3484 Travel Travel
3485 Travel Travel
3486 Travel Travel
3487 Travel Travel
3488 Travel Travel
Page 928
3489 Travel Travel
3490 Travel Travel
3491 Travel Travel
3492 Travel Travel
3493 Travel Travel
3494 Travel Travel
3495 Travel Travel
3496 Travel Travel
3497 Travel Travel
3498 Travel Travel
3499 Travel Travel
3500 Travel Travel
3501 - 3790 Travel Hotels/Motels/Inns/Resorts
3501 Travel Holiday Inn Express / Holiday Inn
3502 Travel Best Western Hotels
3503 Travel Sheraton Hotels
3504 Travel Hilton Hotels
3505 Travel Forte Hotels
3506 Travel Golden Tulip Hotels
3507 Travel Friendship Inns
3508 Travel Quality Inns / Quality Suites
3509 Travel Marriott
3510 Travel Days Inn / Daystop
3511 Travel Arabella Hotels
3512 Travel Inter-Continental Hotels
3513 Travel Westin Hotels
3514 Travel Amerisuites
3515 Travel Rodeway Inns
3516 Travel La Quinta Motor Inns
3517 Travel Americana Hotels
3518 Travel Sol Hotels
3519 Travel Pullman International Hotels
3520 Travel Meridien Hotels
3521 Travel Royal Lahaina Resort
3522 Travel Tokyo Hotel
Page 929
3523 Travel Peninsula Hotels
3524 Travel Welcomgroup Hotels
3525 Travel Dunfey Hotels
3526 Travel Prince Hotels
3527 Travel Downtowner-Passport Hotels
3528 Travel Red Lion Hotels / Red Lion Inns
3529 Travel CP Hotels
3530 Travel Renaissance Hotels
3531 Travel Kauai Coconut Beach Resort
3532 Travel Royal Kona Resort
3533 Travel Hotel IBIS
3534 Travel Southern Pacific Hotels
3535 Travel Hilton International
3536 Travel AMFAC Hotels
3537 Travel ANA Hotels
3538 Travel Concorde Hotels
3539 Travel Summerfield Suites Hotel
3540 Travel Iberotel Hotels
3541 Travel Hotel Okura
3542 Travel Royal Hotels
3543 Travel Four Seasons Hotels
3544 Travel CIGA Hotels
3545 Travel Shangri-La International
3546 Travel Sierra Suites Hotels
3547 Travel The Breakers Resort
3548 Travel Hotels Melia
3549 Travel Auberge Des Governeurs
3550 Travel Regal 8 Inns
3551 Age Restricted Mirage Hotel And Casino
3552 Travel Coast Hotels
3553 Travel Parks Inns International
3554 Travel Pinehurst Resort
3555 Age Restricted Treasure Island Hotel And Casino
3556 Travel Barton Creek Resort
3557 Travel Manhattan East Suite Hotels
3558 Travel Jolly Hotels
Page 930
3559 Travel Candlewood Suites
3560 Age Restricted Aladdin Resort And Casino
3561 Travel Golden Nugget
3562 Travel Comfort Inns
3563 Travel Journey's End Motels
3564 Age Restricted Sam's Town Hotel And Casino
3565 Travel Relax Inns
3566 Travel Garden Place Hotel
3567 Travel Soho Grand Hotel
3568 Travel Ladbroke Hotels
3569 Travel Tribeca Grand Hotel
3570 Travel Forum Hotels
3571 Travel Grand Wailea Resort
3572 Travel Miyako Hotels
3573 Travel Sandman Hotels
3574 Travel Venture Inn
3575 Travel Vagabond Hotels
3576 Travel La Quinta Resort
3577 Travel Mandarin Oriental Hotel
3578 Travel Frankenmuth Bavarian
3579 Travel Hotel Mercure
3580 Travel Hotel Del Coronado
3581 Travel Delta Hotels
3582 Age Restricted California Hotel And Casino
3583 Travel SAS Hotels
3584 Travel Princess Hotels International
3585 Travel Hungar Hotels
3586 Travel Sokos Hotel
3587 Travel Doral Hotels
3588 Travel Helmsley Hotels
3589 Travel Doral Golf Resort
3590 Travel Fairmont Hotels
3591 Travel Sonesta Hotels
3592 Travel Omni Hotels
3593 Travel Cunard Hotels
3594 Travel Arizona Biltmore
Page 931
3595 Travel Hospitality Inns
3596 Travel Wynn Las Vegas
3597 Age Restricted Riverside Resort Hotel And Casino
3598 Travel Regent International Hotels
3599 Travel Pannonia Hotels
3600 Travel Saddlebrook Resort – Tampa
3601 Travel Trade Winds Resort
3602 Travel Hudson Hotel
3603 Travel Noah's Hotel (MELBN)
3604 Travel Hilton Garden Inn
3605 Travel Jurys Doyle Hotel Group (M/C only)
3606 Travel Jefferson Hotel (M/C only)
3607 Travel Fountainebleau Resorts
3608 Travel Gaylord Opryland (MC effective now, Visa – 10/2006)
3609 Travel Gaylord Palms (MC effective now, Visa – 10/2006)
3610 Travel Gaylord Texan Hotel
3611 Travel Cmon Inns
3612 Travel Movenpick Hotels
Microtel Inns & Suites (MC effective now, Visa –
3613 Travel
10/2006)
3614 Travel AmericInn (MC only effective 6/2006)
3615 Travel Travelodge
3616 Travel Hermitage
3617 Travel America’s Best Value
3618 Travel Great Wolf
3619 Travel Aloft
3620 Travel Binion's Horshoe Club
3621 Travel Extended Stay
3622 Travel Merlin Hotel (Perth)
3623 Travel Dorint Hotels
3624 Age Restricted Lady Luck Hotel And Casino
3625 Travel Hotel Universale
3626 Travel Studio Plus
3627 Travel Extended Stay America
3628 Age Restricted Excalibur Hotel And Casino
3629 Travel Dan Hotels
Page 932
3630 Travel Extended Stay Deluxe
3631 Travel Sleep Inn
3632 Travel The Phoenician
3633 Travel Rank Hotels
3634 Travel Swissotel
3635 Travel Reso Hotels
3636 Travel Sarova Hotels
3637 Travel Ramada Inns
3638 Travel Ho Jo Inn / Howard Johnson
3639 Travel Mount Charlotte Thistle
3640 Travel Hyatt Hotels
3641 Travel Sofitel Hotels
3642 Travel Novotel Sieh (Accor)
3643 Travel Steigenberger Hotels
3644 Travel Econo Lodges
3645 Travel Queens Moat Houses
3646 Travel Swallow Hotels
3647 Travel Husa Hotels
3648 Travel De Vere Hotels
3649 Travel Radisson Hotels
3650 Travel Red Roof Inns
3651 Travel Imperial London Hotels
3652 Travel Embassy Hotels
3653 Travel Penta Hotels
3654 Travel Loews Hotels
3655 Travel Scandic Hotels
3656 Travel Sara Hotels
3657 Travel Oberoi Hotels
3658 Travel Otani Hotels
3659 Travel Taj Hotels International
3660 Travel Knights Inn
3661 Travel Metropole Hotels
3662 Age Restricted Circus Circus Hotel And Casino
3663 Travel Hoteles El Presidente
3664 Travel Flag Inn
3665 Travel Hampton Inns
Page 933
3666 Travel Stakis Hotels
3667 Age Restricted Luxor Hotel And Casino
3668 Travel Maritim Hotels
3669 Age Restricted Eldorado Hotel And Casino
3670 Travel Arcade Hotels
3671 Travel Arctia Hotels
3672 Travel Campanile Hotels
3673 Travel Ibusz Hotels
3674 Travel Rantasipi Hotels
3675 Travel Interhotel Cedok
3676 Age Restricted Monte Carlo Hotel And Casino
3677 Travel Climat De France Hotels
3678 Travel Cumulus Hotels
3679 Age Restricted Silver Lagacy Hotel And Casino
3680 Travel Hoteis Othan
3681 Travel Adams Mark Hotels
3682 Age Restricted Sahara Hotel And Casino
3683 Travel Bradbury Suites
3684 Travel Budget Host Inns
3685 Travel Budgetel Inns
3686 Travel Susse Chalets
3687 Travel Clarion Hotel
3688 Travel Compri Hotel
3689 Travel Consort Hotel
3690 Travel Courtyard By Marriott
3691 Travel Dillon Inn
3692 Travel Doubletree Guest Suites / Doubletree Hotels)
3693 Travel Drury Inn
3694 Travel Economy Inns Of America
3695 Travel Embassy Suites
3696 Travel Excel Inn
3697 Travel Fairfield Hotel
3698 Travel Harley Hotel
3699 Travel Midway Motor Lodge
3700 Travel Motel 6
3701 Travel La Mansion Del Rio
Page 934
3702 Travel The Registry Hotels
3703 Travel Residence Inns
3704 Travel Royce Hotel
3705 Travel Sandman Inn
3706 Travel Shilo Inn
3707 Travel Shoney's Inn
3708 Age Restricted Virgin River Hotel And Casino
3709 Travel Super 8 Motel
3710 Travel The Ritz Carlton
3711 Travel Flag Inns (Australia)
3712 Age Restricted Buffalo Bill's Hotel And Casino
3713 Travel Quality Pacific Hotel
3714 Travel Four Seasons Hotel (Australia)
3715 Travel Fairfield Inn
3716 Travel Carlton Hotels
3717 Travel City Lodge Hotels
3718 Travel Karos Hotels
3719 Travel Protea Hotels
3720 Travel Southern Sun Hotels
3721 Travel Hilton Conrad
3722 Travel Wyndham
3723 Travel Rica Hotels
3724 Travel Inter Nor Hotels
3725 Travel Sea Pines Plantation / Sea Pines Resort
3726 Travel Rio Suites
3727 Travel Broadmoor Hotel
3728 Age Restricted Bally's Hotel And Casino
3729 Travel John Ascuaga's Nugget
3730 Travel MGM Grand Hotel
3731 Age Restricted Harrah's Hotels And Casinos
3732 Travel Opryland Hotel
3733 Travel Boca Raton Resort
3734 Travel Harvey/Bristol Hotels
3735 Travel Masters Economy Inns
3736 Travel Colorado Belle/Edgewater Resort
3737 Age Restricted Riviera Hotel And Casino
Page 935
3738 Age Restricted Tropicana Resort And Casino
3739 Travel Woodside Hotels And Resorts
3740 Travel Townplace Suites
3741 Travel Millennium Hotels
3742 Travel Club Med
3743 Travel Biltmore Hotel & Suites
3744 Travel Carefree Resorts
3745 Travel St. Regis Hotel
3746 Travel The Eliot Hotel
3747 Travel Club Corp/Club Resorts
3748 Travel Wellesley Inns
3749 Travel The Beverly Hills Hotel
3750 Travel Crowne Plaza Hotels
3751 Travel Homewood Suites
3752 Travel Peabody Hotels
3753 Travel Greenbriar Resorts
3754 Travel Amelia Island Plantation
3755 Travel The Homestead
3756 Travel South Seas Resorts
3757 Travel Canyon Ranch
3758 Travel Kahala Mandarin Oriental Hotel
3759 Travel The Orchid At Mauna Lani
3760 Travel Halekulani Hotel/Waikiki Parc
3761 Age Restricted Primadonna Hotel And Casino
3762 Age Restricted Whiskey Pete's Hotel And Casino
3763 Travel Chateau Elan Winery And Resort
3764 Age Restricted Beau Rivage Hotel And Casino
3765 Travel Bellagio
3766 Age Restricted Fremont Hotel And Casino
3767 Age Restricted Main Street Station Hotel And Casino
3768 Age Restricted Silver Star Hotel And Casino
3769 Age Restricted Stratosphere Hotel And Casino
3770 Travel Springhill Suites
3771 Age Restricted Caesars Hotel And Casino
3772 Travel Nemacolin Woodlands
3773 Age Restricted The Venetian Resort Hotel Casino
Page 936
3774 Age Restricted New York--New York Hotel And Casino
3775 Travel Sand’s Resort
3776 Travel Nevele Grande Resort And Country Club
3777 Travel Mandalay Bay Resort
3778 Travel Four Points Hotels
3779 Travel W Hotels
3780 Travel Disney Resorts
3781 Travel Patricia Grand Resort Hotels
3782 Travel Rosen Hotels And Resorts
3783 Travel Town And Country Resort
3784 Travel First Hospitality Hotels
3785 Travel Outrigger Hotels And Resorts
3786 Travel Ohana Hotels Of Hawaii
3787 Travel Caribe Royale Resorts
3788 Travel Ala Moana Hotels
3789 Travel Smugglers' Notch Resort
3790 Travel Raffles Hotels
3791 Travel Staybridge Suites
3792 Age Restricted Claridge Casino Hotel
3793 Travel Flamingo Hotels
3794 Age Restricted Grand Casino Hotels
3795 Travel Paris Las Vegas Hotel
3796 Age Restricted Peppermill Hotel Casino
3797 Travel Atlantic City Hilton Resorts
3798 Travel Embassy Vacation Resort
3799 Travel Hale Koa Hotel
3800 Travel Homestead Suites
3801 Travel Wilderness Hotel and Golf Resort
3802 Travel The Palace Hotel
3803 Travel The Wigwam Golf Resort and Spa
3804 Travel The Diplomat Country Club and Spa
3805 Travel The Atlantic
3806 Travel Princeville Resort
3807 Travel Element
3808 Travel LXR (Luxury Resorts)
3809 Travel Settle Inn
Page 937
3810 Travel La Costa Resort
3811 Travel Premier Travel Inns
3812 Travel Hyatt Place
3813 Travel Hotel Indigo
3814 Travel The Roosevelt Hotel NY
3815 Travel Nickelodeon Family Suites by Holiday Inn
3816 Travel Home2Suites
3817 Travel Affinia
3818 Travel Mainstay Suites
3819 Travel Oxford Suites
3820 Travel Jumeirah Essex House
3821 Travel Caribe Royal
3822 Travel Crossland
3823 Travel Grand Sierra Resort
3824 Travel Aria
3825 Travel Vdara
3826 Travel Autograph
3827 Travel Galt House
3828 Travel Cosmopolitan of Las Vegas
3829 Travel Country Inn By Carlson
3830 Travel Park Plaza Hotel
3831 Travel Waldorf
3834 Travel Baymont Inn & Suites
3835 Travel Dolce (New Hotel)
3836 Travel Hawthorne Suites by Wyndham
4011 Travel Railroads
Local And Suburban Commuter Passenger
4111 Travel
Transportation, Including Ferries
4112 Travel Passenger Railways (T&E In Us Only)
4119 Personal Care Ambulance Services
4121 Travel Taxicabs And Limousines
4131 Travel Bus Lines
Motor Freight Carriers and Trucking - Local and Long
4214 Travel
Distance, Moving
4215 Household Courier Services
Page 938
Public Warehousing and Storage – Farm Products,
4225 Household
Refrigerated Goods,
4411 Travel Steamship And Cruise Lines
4457 Travel Boat Rentals And Leasing
4468 Travel Marinas, Marine Service, And Supplies
4511 Travel Airlines And Air Carriers – Not Elsewhere Classified
4582 Travel Airports, Flying Fields And Airport Terminals
4722 Travel Travel Agencies And Tour Operators
Package Tour Operators – Germany Only (Not Available
4723 Travel
For Use In The US) (Visa Only)
4761 Travel "Telemarketing of Travel Related Services and Vitamins"
4784 Travel Tolls And Bridge Fees
4789 Travel Transportation Services (Not Elsewhere Classified)
"Telecommunication Equipment Including Telephone
4812 Household
Sales"
"Key-Entry Telecom Merchant providing single local and
4813 Household long-distance phone calls using a central access number
in a non-face-to-face environment using key entry"
"Telecommunication Services including but not limited
4814 Household
to prepaid phone services and recurring phone services"
4815 Household Household
4816 Household Computer Network/Information Services
4821 Household Telegraph Services
"Wire Transfer Money Orders (V, D, G, X) Money
4829 Household
Transfer (M)"
"Cable, Satellite, and Other Pay Television and Radio
4899 Household
Services"
4900 Household Utilities - Electric, Gas, Heating Oil, Water, Sanitary
5013 Department Stores Motor Vehicle Supplies And New Parts
5021 Department Stores Office And Commercial Furniture
5039 Department Stores Construction Materials (Not Elsewhere Classified)
"Office, Photographic, Photocopy and Microfilm
5044 Department Stores
Equipment"
5045 Department Stores "Computers, Computer Peripheral Equipment, Software"
5046 Department Stores Commercial Equipment (Not Elsewhere Classified)
Page 939
"Dental/Laboratory/Medical/Ophthalmic Hospital
5047 Department Stores
Equipment and Supplies"
5051 Department Stores Metal Service Centers And Offices
5065 Department Stores Electrical Parts And Equipment
5072 Department Stores Hardware, Equipment And Supplies
5074 Department Stores Plumbing And Heating Equipment And Supplies
5085 Department Stores Industrial Supplies Not Elsewhere Classified
5094 Department Stores Precious Stones And Metals, Watches And Jewelry
5099 Department Stores Durable Goods (Not Elsewhere Classified)
5111 Department Stores Stationary, Office Supplies, Printing And Writing Paper
5122 Department Stores Drugs, Drug Proprietors and Druggists Sundries
5131 Department Stores Piece Goods, Notions, And Other Dry Goods
5137 Department Stores Men’s, Women’s, and Children’s Uniforms and
5139 Department Stores Commercial Footwear
5169 Department Stores Chemicals And Allied Products (Not Elsewhere Classified)
5172 Fuel Merchant Petroleum And Petroleum Products
5192 Department Stores Books, Periodicals, And Newspapers
5193 Department Stores Florists Supplies, Nursery Stock And Flowers
5198 Department Stores Paints, Varnishes And Supplies
5199 Department Stores Department Stores
5200 Department Stores Home Supply Warehouse Stores
5211 Department Stores Lumber And Building Materials Stores
5231 Department Stores Glass, Paint, And Wallpaper Stores
5251 Department Stores Hardware Stores
5261 Department Stores Nurseries And Lawn And Garden Supply Stores
5271 Department Stores Mobile Home Dealers
5299 Fuel Merchant Warehouse Club Gas
5300 Department Stores Wholesale Clubs
5309 Department Stores Duty Free Stores
5310 Department Stores Discount Stores
5311 Department Stores Department Stores
5331 Department Stores Variety Stores
5399 Department Stores Miscellaneous General Merchandise
5411 Groceries Grocery Stores And Supermarkets
5422 Groceries Freezer And Locker Meat Provisions
5441 Groceries Candy, Nut, And Confectionery Stores
Page 940
5451 Groceries Dairy Products Stores
5462 Groceries Bakeries
Miscellaneous Food Stores – Convenience Stores &
5499 Groceries
Specialty Markets
"Automobile and Truck Dealers–Sales, Service, Repairs,
5511 Department Stores
Parts and Leasing"
5521 Department Stores Automobile and Truck Dealers–(Used Only)–Sales
5531 Department Stores Auto and Home Supply Stores
5532 Department Stores Automotive Tire Stores
5533 Department Stores Automotive Parts and Accessories Stores
5541 Fuel Merchant Service Stations
5542 Fuel Merchant Automated Fuel Dispenser
5551 Department Stores Boat Dealers
5561 Entertainment Camper Dealers, Recreational and Utility Trailers
5571 Department Stores Motorcycle Shops and Dealers
5592 Department Stores Motor Home Dealers
5598 Department Stores Snowmobile Dealers
Miscellaneous Automotive, Aircraft, And Farm
5599 Department Stores
Equipment Dealers (Not Elsewhere Classified)
5611 Department Stores Men's and Boy's Clothing and Accessories Stores
5621 Department Stores Wone's Ready to Wear Stores
5631 Department Stores Women's Accessory And Specialty Shops
5641 Department Stores Children's And Infants Wear Stores
5651 Department Stores Family Clothing Stores
5655 Department Stores Sports And Riding Apparel Stores
5661 Department Stores Shoe Stores
5681 Department Stores Furriers And Fur Shops
5691 Department Stores Men’s And Women’s Clothing Stores
5697 Department Stores Tailors, Seamstresses, Mending And Alterations
5698 Department Stores Wig And Toupee Stores
5699 Department Stores Miscellaneous Apparel And Accessory Shops
Furniture, Home Furnishings, And Equipment Stores,
5712 Household
Except Appliances
5713 Household Floor Covering Stores
5714 Household Drapery, Window Covering, And Upholstery Stores
5718 Household Fireplace, Fireplace Screens And Accessories Stores
Page 941
5719 Household Miscellaneous House Furnishing Specialty Stores
5722 Household Household Appliance Stores
5732 Department Stores Electronics Stores
5733 Department Stores Music Stores–Musical Instruments, Pianos & Sheet Music
5734 Department Stores Computer Software Stores
5735 Department Stores Record Stores
5811 Restaurants Caterers
5812 Restaurants Eating Places And Restaurants
Drinking Places (Alcoholic Beverages) – Bars, Taverns,
5813 Age Restricted
Nightclubs, Cocktail Lounges, And Discotheque
5814 Restaurants Fast Food Restaurants
5815 Entertainment Digital Goods: Books, Movies, Music
5816 Entertainment Digital Goods: Games
5817 Entertainment Digital Goods: Applications (Excludes Games)
5912 Personal Care Drug Stores And Pharmacies
5921 Age Restricted Package Stores – Beer, Wine, And Liquor
5931 Department Stores Used Merchandise And Secondhand Stores
5932 Department Stores Antique Stores – Sales, Repairs and Restoration Services
5933 Department Stores Pawn Shops
5935 Department Stores Wrecking Ans Salvage Yards
5937 Department Stores Antique Reproductions
5940 Department Stores Bicycle Shops – Sales And Service
5941 Department Stores Sporting Goods Stores
5942 Department Stores Book Stores
5943 Department Stores Stationary Stores, Office And School Supply Stores
5944 Department Stores Jewelry Stores, Watches, Clocks And Silverware Stores
5945 Department Stores Hobby, Toy, And Games Shops
5946 Department Stores Camera And Photographic Supply Stores
5947 Department Stores Gift, Card, Novelty And Souvenir Shops
5948 Department Stores Luggage And Leather Goods Stores
5949 Department Stores Sewing, Needlework, Fabric And Piece Goods Stores
5950 Department Stores Glassware/Crystal Stores
5960 Department Stores Direct Marketing - Insurance Services
5961 Household Mail Order Houses Including Catalog Order Stores
5962 Department Stores Direct Marketing - Travel
5963 Department Stores Door-To-Door Sales
Page 942
5964 Department Stores Direct Marketing - Catalog Merchant
Direct Marketing - Combination Catalog and Retail
5965 Department Stores
Merchant
5966 Department Stores Direct Marketing - Outbound Tele
5967 Department Stores Direct Marketing - Inbound Tele
5968 Department Stores Direct Marketing - Subscription
5969 Department Stores Direct Marketing - Other
5970 Department Stores Artist’s Supply And Craft Stores
5971 Department Stores Art Dealers And Galleries
5972 Department Stores Stamp And Coin Stores
5973 Department Stores Religious Goods Stores
5974 Household Rubber Stamp Store
5975 Department Stores Hearing Aids Sales and Supplies
5976 Department Stores Orthopedic Goods - Prosthetic Devices
5977 Department Stores Cosmetic Stores
5978 Department Stores Typewriter Stores
Fuel Dealers – Fuel Oil, Wood, Coal, And Liquefied
5983 Fuel Merchant
Petroleum
5992 Department Stores Florists
5993 Age Restricted Cigar Stores And Stands
5994 Department Stores News Dealers And Newsstands
5995 Department Stores Pet Shops, Pet Foods And Suppliers Stores
5996 Department Stores Swimming Pools - Sales And Service
5997 Department Stores Electric Razor Stores - Sales And Service
5998 Department Stores Tent And Awning Shops
5999 Department Stores Miscellaneous And Specialty Retail Stores
6010 Others Manual Cash Disburse
6011 Others Automated Cash Disburse
6012 Others Financial Institutions
6050 Household Quasi Cash–Member Financial Institution
6051 Others Money Orders
6211 Others Security Brokers/Dealers
6236 Travel Aero Servicio Carabobo
6300 Others Insurance Underwriting, Premiums
6381 Household Insurance–Premiums
6399 Others Insurance - Default
Page 943
6513 Others Real Estate Agents and Managers - Rentals
"Remote Stored Value Load — Member Financial
6529 Household
Institution"
6530 Household Remove Stored Value Load — Merchant
6531 Household Household
6532 Household Household
6533 Household Household
6534 Household Household
6535 Household Value Purchase–Member Financial Institution
6536 Household MoneySend Intracountry
6537 Household MoneySend Intercountry
6538 Household MoneySend Funding
6539 Household Funding Transaction (Excluding MoneySend)
"POI (Point of Interaction) Funding Transactions
6540 Household
(Excluding MoneySend)"
6611 Household Overpayments
6760 Household Savings Bonds
Lodging – Hotels, Motels, Resorts, Central Reservation
7011 Travel
Services (Not Elsewhere Classified)
7012 Travel Timeshares
7032 Travel Sporting/Recreation Camps
7033 Travel Trailer Parks, Campgrounds
7210 Household Laundry, Cleaning Services
7211 Household Laundries
7216 Household Dry Cleaners
7217 Household Carpet/Upholstery Cleaning
7221 Household Photographic Studios
7230 Household Barber and Beauty Shops
7251 Household Shoe Repair/Hat Cleaning
7261 Household Funeral Services And Crematories
7273 Age Restricted Dating And Escort Services
7276 Household Tax Preparation Services
7277 Household Counseling Services – Debt, Marriage, And Personal
7278 Household Buying And Shopping Services And Clubs
7279 Household Household
7280 Personal Care Hospital Patient-Personal Funds Withdrawal
Page 944
7295 Household Babysitting Services
7296 Household Clothing Rental – Costumes, Uniforms, Formal Wear
7297 Household Massage Parlors
7298 Household Health And Beauty Spas
Miscellaneous Personal Services – Not Elsewhere
7299 Household
Classified
7311 Others Advertising Services
7321 Others Credit Reporting Agencies
7332 Household Blueprinting and Photocopying Services
7333 Others Commercial Photography, Art and Graphics
7338 Others Quick Copy, Repro, and Blueprint
7339 Others Secretarial Support Services
7341 Household Household
7342 Others Exterminating Services
7349 Others Cleaning and Maintenance
7361 Others Employment/Temp Agencies
7372 Others Computer Programming
7375 Others Information Retrieval Services
7379 Others Computer Repair
7392 Others Consulting, Public Relations
7393 Others Detective Agencies
7394 Others Equipment Rental
7395 Others Photo Developing
7399 Others Miscellaneous Business Services
7511 Travel Truck Stop Transactions (M/C Only)
7512 Travel Automobile Rental Agency
7513 Travel Truck And Utility Trailer Rentals
7519 Travel Motor Home And Recreational Vehicle Rentals
7523 Travel Parking Lots And Garages
"Express Payment Service Merchants–Parking Lots and
7524 Travel
Garages"
7531 Household Auto Body Repair Shops
7534 Household Tire Retreading and Repair
7535 Household Auto Paint Shops
7538 Household Auto Service Shops
7542 Household Car Washes
Page 945
7549 Household Towing Services
7622 Household Electronics Repair Shops
7623 Household Air Conditioning And Refrigeration Repair Shops
7629 Household Electrical And Small Appliance Repair Shops
7631 Household Watch, Clock And Jewelry Repair
7641 Household Furniture-Reupholstery, Repair, And Refinishing
7692 Household Welding Services
7699 Household Miscellaneous Repair Shops And Related Services
7800 Age Restricted Government Owned Lottery
7829 Entertainment Motion Picture & Video Tape Production & Distribution
7832 Entertainment Motion Picture Theaters
7833 Entertainment Motion picture theaters (quick payment services)
7841 Entertainment Video Tape Rental Stores
7911 Entertainment Dance Halls, Studios And Schools
7922 Entertainment Theatrical Producers (Except Motion Pictures)
7929 Entertainment Bands, Orchestras, And Miscellaneous Entertainers –
7932 Entertainment Billiard And Pool Establishments
7933 Entertainment Bowling Alleys
7941 Entertainment Commercial Sports, Professional Sports Club, Athletic
7991 Entertainment Tourists Attractions And Exhibits
7992 Entertainment Public Golf Courses
7993 Entertainment Video Amusement Game Supplies
7994 Entertainment Video Game Arcades/Establishments
7995 Entertainment Betting, Including Lottery Tickets, Casino Gaming Chips,
7996 Entertainment Amusement Parks, Circuses, Carnivals & Fortune Tellers
7997 Entertainment Membership Clubs (Sports, Recreation, Athletic)
7998 Entertainment Aquariums, Seaquariums, Dolphinariums
7999 Entertainment Recreation Services – Not Elsewhere Classified
8011 Personal Care Doctors
8021 Personal Care Dentists, Orthodontists
8031 Personal Care Osteopaths
8041 Personal Care Chiropractors
8042 Personal Care Optometrists, Ophthalmologists
8043 Personal Care Opticians, Eyeglasses
8044 Personal Care Optical Goods and Eyeglasses
8049 Personal Care Chiropodists, Podiatrists
Page 946
8050 Personal Care Nursing/Personal Care
8062 Personal Care Hospitals
8071 Personal Care Medical and Dental Labs
8099 Personal Care Medical Services
8111 Personal Care Legal Services, Attorneys
8211 Others Elementary, Secondary Schools
8220 Others Colleges, Universities
8241 Others Correspondence Schools
8244 Others Business/Secretarial Schools
8249 Others Vocational/Trade Schools
8299 Others Educational Services
8351 Others Child Care Services
Charitable and Social Service Organizations - Fundraising
8398 Others
1.6041-3(p)(2)
8641 Others Civic, Social, Fraternal Associations
8651 Others Political Organizations
8661 Household Organizations, Religious
8675 Others Automobile Associations
8699 Others Membership Organizations
8734 Others Testing Laboratories (Non-Medical)
8743 Others Testing Laboratories (Non-Medical)
8911 Others Architectural/Surveying Services
8931 Others Accounting/Bookkeeping Services
8999 Others Professional Services
9034 Household I-Purchasing Pilot
Court Costs, Including Alimony and Child Support -
9211 Others
Courts of Law
9222 Others Fines - Government Administrative Entities
9223 Others Bail and Bond Payments
9311 Others Tax Payments - Government Agencies
9399 Others Government Services
9401 Household I-Purchasing Pilot
9402 Others Postal Services - Government Only
9405 Others U.S. Federal Government Agencies or Departments
9700 Travel Automated Referral Service
9701 Travel Visa Credential Server
Page 947
9702 Travel GCAS Emergency Services
9751 Department Stores UK Supermarkets, Electronic Hot File
9752 Fuel Merchant UK Petrol Stations, Electronic Hot File
9754 Age Restricted Gambling-Horse, Dog Racing, State Lottery
9950 Others Intra-Company Purchases
Page 948