API Availability & Testing Considerations

Some APIs depend on external configuration, wallet provider setup, tokenization readiness, fraud event generation, or live BIN/program conditions. These APIs may be visible in the API catalog, but full end-to-end testing in UAT may be limited until the required dependencies are enabled.

Digital Wallet Provisioning / In-App Provisioning

APIs included:

1. Apple In-App Push Provisioning

2. Google In-App Push Provisioning

3. Apple In-App Push Provisioning Verification

4. Google In-App Push Provisioning Verification

Testing limitation: These flows depend on wallet provider configuration, token requestor data, token service provider readiness, and BIN/program setup. In-app provisioning also requires the mobile app and server-side integration to pass encrypted provisioning data to Apple or Google wallet flows.

Card Tokenization

APIs included:

1. Get Card Payment Tokens

2. Get Card Payment Token Devices

3. Unbind Payment Token

4. Update Payment Token Status

5. Update Payment Token Status — Idempotent

Testing limitation:
These APIs depend on tokenized cards or payment tokens already existing in the environment. Without active wallet tokenization events, full lifecycle testing is limited. Therefore, these endpoints also depend on Digital Wallet configuration.

3D Secure Enrollment

APIs included:

1. Create 3DS Credentials

2. List 3DS Credentials

3. Update 3DS Credentials

4. Update 3DS Credential — Idempotent

5. Delete 3DS Credentials

6. Get 3DS Configuration Details

Testing limitation: Full validation depends on 3DS provider setup, authentication method configuration, card/program readiness, and supported UAT scenarios. Required configuration is currently being completed by provider.

Click to Pay

APIs included:

1. Enroll Data

2. Get Payment Instrument Information

3. Enroll Payment Instruments

4. Manage Payment Instrument

5. Manage Consumer Information

6. Delete Consumer Information

7. Delete Payment Instrument

8. Retrieve Consumer and Payment Instruments Information

Testing limitation: These APIs depend on network/payment credential configuration and supported program setup. Full testing can only be completed once Click to Pay configuration is active for the program.

Fraud Alerts & Fraud Event Handling

APIs included:

1. Record Fraud Login Event

2. Submit Fraud Alert Response

Testing limitation: Full validation depends on fraud monitoring configuration, fraud rules being enabled, fraud alert/event generation, webhook or event subscription setup, and supported test scenarios that can trigger fraud-related events. Required configuration is currently being completed by provider.