Payment Method Registration

The payment method registration process allows customers to add debit cards, bank accounts (NIB), or mobile wallets to their Kulpay account. The available fields and validation rules for each payment method type are dynamically configured through the Partner UI Configuration.

Participants

Participant	Role	Channel
Individual Customer	Registers a new payment method	Mobile App
Merchant	Registers a new payment method	Portal Web
KulOffice API	Validates and stores the payment method	—
Payment Provider	Validates ownership (card issuer, bank, wallet provider)	—
Back Office Reviewer	Approves NIB-based payment methods (4-hour SLA)	—

Process Flow

Step-by-Step

Debit Card

1. Customer selects "Debit Card" as the payment method type
2. Enters card details: card number, expiration date, CVV, holder name
3. Card issuer bank sends an OTP for ownership verification
4. Customer enters the received OTP
5. System validates card legitimacy with SIMORede
6. If legitimate, payment method is registered immediately

Bank NIB

1. Customer selects "Bank NIB" as the payment method type
2. Enters the NIB and selects the issuer bank
3. Attaches a document proving NIB ownership (e.g., bank statement)
4. Bank sends an OTP for verification
5. Customer enters the OTP
6. Payment method is submitted for back office approval
7. Reviewer has a 4-hour SLA to process the request
8. Reviewer verifies ownership through the attached document
9. Reviewer approves or rejects the payment method
10. Customer is notified of the outcome

Mobile Wallet

1. Customer selects "Mobile Wallet" as the payment method type
2. Enters the phone number and selects the wallet provider
3. System validates ownership via the eWallet KYC system
4. Wallet provider sends a confirmation OTP
5. Customer enters the OTP
6. Payment method is registered immediately

Related API Endpoints

Endpoint	Purpose
GET /v1/partners	List available partners and their payment method types
GET /v1/partners/{id}	Get partner configuration (required fields, validation rules)
POST /v1/customers/{id}/payment_methods	Create a payment method
GET /v1/customers/{id}/payment_methods	List customer's payment methods
POST /v1/customers/{id}/payment_methods/{id}/status	Activate/deactivate a method
POST /v1/customers/{id}/payment_methods/{id}/transactions	Validate a method (type: validata)

Business Rules

• Only cards with verified ownership are accepted
• NIB-based payment methods require manual back office approval (4-hour SLA)
• Mobile wallets are validated via the eWallet KYC system
• Each payment method type has specific required attributes (defined by partner configuration)
• Payment methods can be activated or deactivated after registration
• Validation rules (regex patterns, min/max sizes) are defined per partner
• Individual customers use the mobile app; merchants use the web portal
• Merchants with active profiles can initiate payments directly from the app