| API / Capability Area | APIs to Include | Why Full Testing Is Limited |
|---|---|---|
| Digital Wallet Provisioning / In-App Provisioning |
Apple In-App Push Provisioning
Google In-App Push Provisioning
Apple In-App Push Provisioning Verification
Google In-App Push Provisioning Verification
|
These flows depend on wallet provider configuration, token requestor data, token service provider readiness, and BIN/program setup. In-app provisioning flow requires the mobile app/server to pass encrypted provisioning data to Apple or Google wallet flows. |
| Card Tokenization |
Get Card Payment Tokens
Get Card Payment Token Devices
Unbind Payment Token
Update Payment Token Status
Update Payment Token Status Idempotent
|
These APIs depend on tokenized cards/payment tokens already existing. Without active wallet tokenization events, full lifecycle testing is limited. Therefore, these endpoints also depend on Digital Wallet configuration. |
| 3D Secure Enrollment |
Create 3DS Credentials
List 3DS Credentials
Update 3DS Credentials
Update 3DS Credential – Idempotent
Delete 3DS Credentials
Get 3DS Configuration Details
|
Full validation depends on 3DS provider setup, authentication method configuration, card/program readiness, and supported UAT scenarios. Provider is currently setting up configuration needed. |
| Click to Pay |
Enroll Data
Get Payment Instrument Information
Enroll Payment Instruments
Manage Payment Instrument
Manage Consumer Information
Delete Consumer Information
Delete Payment Instrument
Retrieve Consumer and Payment Instruments Information
|
These APIs depend on network/payment credential configuration and supported program setup. |
| Fraud Alerts & Fraud Event Handling |
Record Fraud Login Event
Submit Fraud Alert Response
|
Full validation depends on fraud monitoring configuration, fraud rules being enabled, alert/event generation, webhook/event subscription setup, and test scenarios that can trigger fraud-related events. Provider is currently setting up configuration needed. |