Update Onboarding Data
Update merchant onboarding data after being declined
Overview
Updates the onboarding data for a merchant using the onboarding reference number. This endpoint allows merchants to correct and resubmit their information after their application has been declined.Authentication
This endpoint requires JWT Bearer Token authentication.Authorization Rules
| User Role | Required Merchant Status | Result Status After Update |
|---|---|---|
| Regular User | DECLINED | PENDING |
| Super Admin | APPROVED | APPROVED (no status change) |
| Settlement/Checker Roles | N/A | Not Allowed |
Path Parameters
"550e8400-e29b-41d4-a716-446655440000"referenceNumber returned from the Onboard Merchant endpoint.Request Body
All fields from the original onboarding request are required, except those marked as optional.Core Business Information
"Acme Corporation Inc.""Acme Store""acme-store"CREDIT_CARD, DEBIT_CARD, GCASH, GRABPAY, PAYMAYA, BANK_TRANSFERExample: ["CREDIT_CARD", "DEBIT_CARD", "GCASH"]PHP, USDExample: "PHP""123456789012""Retail""Online retail store selling electronics and gadgets"trueOptional Business Fields
"AUB123456""100000-500000"falsefalsefalseIncorporators
Signatories
Address
Websites
Representatives
Bank Accounts
Response
Success Response
Status Code:200 OK
PENDING (for regular users)Regular users: Status changes from DECLINED → PENDING
Super Admins: Status remains APPROVED"550e8400-e29b-41d4-a716-446655440000"Error Responses
400 Bad Request - Not Declined (Regular User)
400 Bad Request - Not Declined (Regular User)
400400 Bad Request - Not Approved (Super Admin)
400 Bad Request - Not Approved (Super Admin)
400400 Bad Request - Validation Error
400 Bad Request - Validation Error
400400 Bad Request - Business Handle Taken
400 Bad Request - Business Handle Taken
400400 Bad Request - Invalid Reference Number
400 Bad Request - Invalid Reference Number
400400 Bad Request - Record Does Not Exist
400 Bad Request - Record Does Not Exist
400400 Bad Request - Reference Number Mismatch
400 Bad Request - Reference Number Mismatch
400400 Bad Request - Update Failed
400 Bad Request - Update Failed
400401 Unauthorized
401 Unauthorized
Transaction Behavior
The update process includes:- Validating all request parameters
- Checking user authorization and merchant status
- Updating business information
- Updating incorporators and signatories
- Updating addresses and representatives
- Updating bank accounts
- Changing status to PENDING (for regular users)
Validation Rules Summary
Business Type
legalName and businessHandleBank Accounts
NO_ACCOUNT: bankName, accountName, accountNumber, currency requiredBank Type
accountDepositType is BANK: accountType is also requiredWebsite
businessWebsiteUrl provided: isBusinessWebsiteUnderDevelopment requiredStatus Change Flow
Best Practices
Retrieve Current Data First
Retrieve Current Data First
Check Declined Reason
Check Declined Reason
Validate Before Submitting
Validate Before Submitting
Handle Business Handle Conflicts
Handle Business Handle Conflicts
Preserve Optional Fields
Preserve Optional Fields
Use Cases
Fix Declined Application
Update Business Info
Add Missing Documents
Correct Validation Errors
Troubleshooting
Cannot Update APPROVED Merchant
Cannot Update APPROVED Merchant
Unable to update. Merchant is not in declined status.Issue: Regular users cannot update approved merchantsSolution:- Only DECLINED merchants can be updated by regular users
- If you need to update an APPROVED merchant, contact a Super Admin
- To update business details after approval, create a new onboarding request
Transaction Keeps Rolling Back
Transaction Keeps Rolling Back
Failed to update onboarding recordPossible Causes:- Database connectivity issues
- Data integrity constraints violated
- Concurrent updates from multiple sources
- Retry the request after a short delay
- Ensure no concurrent updates are happening
- Contact support if issue persists
Validation Errors on Update
Validation Errors on Update
merchantName is requiredSolution:- Ensure ALL required fields from original onboarding are included
- Don’t just send changed fields - send complete data
- Use retrieve endpoint to get current data first
- Validate against the same rules as initial onboarding
Field Validation Reference
- Text Fields
- Enums
- Patterns
- Arrays
- First/Middle/Last Names: 1-100 chars, Unicode letters, spaces, hyphens, apostrophes
- Email: Valid email format, max 100 chars
- TIN: Numbers only, max 20 chars
- Postal Code: 4-10 digits, numbers only
- Contact Number: Numbers only, max 30 chars
- SSS: Exactly 10 digits
Next Steps
Retrieve Onboarding Data
Retrieve Status
Onboard Merchant
Error Handling
Authorizations
JWT Bearer token authentication
Path Parameters
The onboarding reference number (UUID v4 format)
Body
Trading name or DBA (Doing Business As) name
500List of accepted payment modes
1CREDIT_CARD, DEBIT_CARD, GCASH, GRABPAY, PAYMAYA, BANK_TRANSFER Primary currency for transactions
PHP, USD Tax Identification Number
20^\d+$Business industry category
200Description of services or products offered
Whether the business has a physical store location
List of bank accounts for settlement
1 - 2 elementsLegal registered name of the business (required for non-STARTER types)
500Unique business handle/slug for payment links (required for non-STARTER types)
^([A-Za-z]|[0-9]|_|-)+$List of business incorporators (for non-STARTER types)
1 - 5 elementsList of authorized signatories
1 - 5 elements