Visa Platforms Login

• Batch Processing Design: Use batch operations for large-scale user management rather than individual API calls
• Asynchronous Processing: Migration and revalidation operations process asynchronously with status polling
• Error Recovery: Implement appropriate retry logic for batch operations using batch ID targeting
• Resource Management: Monitor processing resources for complex operations like duplicate cleanup
• Audit Trail Maintenance: Enterprise operations maintain detailed audit trails and compliance records

Visa Platforms Login provides comprehensive migration capabilities for transferring existing user data into the GMAP system with detailed status tracking and error recovery mechanisms.

1. Preparation: Prepare user registration requests with appropriate password algorithms and salt values
2. Submission: Submit bulk migration using POST /migrate with migration batch ID
3. Processing: System processes users and saves migration records to the migration repository
4. Monitoring: Check progress using GET /migrate/status with migrationBatchId or migrationId
5. Recovery: Retry failed migrations using POST /migrate/{migrationBatchId} with optional status filter

• Batch Tracking: GET /migrate/batches retrieves migration batch IDs by migration ID and optional status filter
• Status Monitoring: Migration system tracks status at the individual record level with detailed error reporting
• Selective Retry: Failed migrations can be retried by batch ID without reprocessing successful records
• Required Scope: MIGRATE_USERS OAuth2 scope required for all migration operations

• Password Algorithms: Support for multiple password algorithms with salt handling
• User Data: Complete user registration requests including site registration and concierge requests
• Force Update: forceRecordUpdate mechanism for overwriting existing records
• Batch Organization: Migration batch IDs organize related migration operations

Batch processing capabilities enable efficient management of large-scale user operations with appropriate performance and error handling.

Process multiple users for OFAC screening, MOE synchronization, or program enrollment in batch operations.

• Individual Revalidation: POST /user/re-validate for single user with userDetailsId
• Batch Revalidation: POST /user/internal/batch/re-validate for user ID ranges
• Call Types: OFAC (sanctions screening), MOE (system sync), ENROLL_PROGRAM_AND_MOE (combined operations)
• Required Scope: SYSTEM_USER_RW for batch operations, RE_VALIDATE_USER for individual operations

Track user modifications within specified date ranges for audit and synchronization purposes.

• Endpoint: GET /batch/modified-users with date-time range parameters
• Parameters: Start date-time, end date-time, and additional criteria parameter
• Usage: Identify users modified within specific time periods for downstream processing

Administrative operations provide system-level management capabilities for user accounts, duplicate cleanup, and internal system maintenance.

• System Account Deletion: POST /user/internal/system-remove-account with SYSTEM_REMOVE_USER scope
• Site-Specific Removal: POST /user/internal/remove-site for removing user from specific sites
• Activation Email Management: POST /user/internal/send-activation-email with SYSTEM_RESEND_ACTIVATION scope
• Passwordless Registration: POST /user/pwless-login-registration for internal client registrations

Clean up duplicate user accounts with intelligent merging that preserves unique data from both accounts.

• Cleanup Process: POST /user/internal/clean-duplicate-accounts with two userDetailsIds
• Merge Logic: Active or most up-to-date user is retained, other is deleted
• Data Transfer: Site data or assets existing only in deleted account are transferred to retained account
• Processing Time: Operations may take extended time for complex merges and data transfers

Enterprise search capabilities with advanced filtering, pagination, and sorting for large-scale user management.

• Cardholder Search: POST /user/internal/cardholders-details/search by last name or email
• Search Criteria: Query, issuer filtering, input type, and user account status filtering
• Pagination: Configurable page size (max 500, min 1) with maximum 1000 pages
• Sorting: Configurable sort criteria with sortBy and sortOrder requirements
• Results: Include user statistics like days since last login and update timestamps

Generate comprehensive reports for enrollment tracking, concierge activity monitoring, and system health validation.

Generate cardholder enrollment reports for business intelligence and compliance monitoring.

• Endpoint: GET /report/cardholder-enrollment
• Parameters: siteId, from date, to date (all required with minLength 1)
• Response Format: Binary data stream (application/octet-stream) for file download
• Usage: Track enrollment patterns and program adoption by site and date range

Monitor concierge user activity and customer service operations.

• Endpoint: GET /report/active-concierge
• Parameters: from date, to date (both required with minLength 1)
• Response Format: Binary data stream for file download
• Scope Requirement: Appropriate reporting permissions

Validate system connectivity and integration health.

• Connection Testing: GET /connection/test-all tests all system connections
• Response Format: Key-value pairs indicating connection status for each tested system
• Usage: Proactive monitoring of system integration health

DTS integration provides tokenization services for secure handling of sensitive user data with separate token lifecycle management.

• Save Operations: POST /dts/save saves DTS user details into user-mgmt database
• Retrieval: GET /dts/find fetches DTS user details by userDetailsId
• Update Preparation: GET /dts/find-for-update retrieves details for update operations
• Cleanup: DELETE /dts/delete removes DTS user details when no longer needed

• Scope Requirement: USER-ATTRIBUTES_RW OAuth2 scope for DTS operations
• User Association: DTS user details require specific userDetailsId association
• Token Management: DTS tokens are managed separately from main user authentication
• Versioning: DTS maintains separate versioning system alongside main user management