Enrollment files a request
CallingPOST /api/enroll_merchant records your intent and persists a descriptor. It does not instantly make that descriptor live with the card network. Provider-side enrollment is a separate step that Chargeblast completes, so every record moves through a lifecycle:
Pending— the enrollment request is on file; the provider has not confirmed yet.Enrolled— live with the provider; alerts route to this descriptor.PendingRemoval— an unenroll was requested for a live descriptor; it stays active until the provider confirms de-registration, then the record is deleted.
Poll
GET /api/enrollment_status for a per-program roll-up (none / pending / enrolled), or GET /api/v2/descriptors for the individual records and their statuses — filterable by program and status, and paginated. GET /api/descriptors remains available.What each program persists
Typical timelines
Provider-side confirmation is not instant. Expect:- Ethoca ~48 hours
- CDRN ~24 hours
- RDR ~2 weeks
- Amex ~4-6 weeks
- Discover ~7 days
Merchant resolution
Passmerchant_id to target a specific existing merchant (list them via GET /api/v2/merchants), or omit it to create a brand-new merchant. The resolved id is returned as merchantId, and merchantCreated tells you whether it was newly created or an existing merchant you targeted.
Unenrolling
POST /api/unenroll splits the outcome:
removed— descriptors that were stillPending(never live) are deleted immediately.queued— descriptors that were live are markedPendingRemovaland stay visible until the provider de-registration confirms, after which the record is deleted.skipped— descriptors you own but whose status was not actionable (Processing/InReview, or already-terminalDisabled/Rejected/Surpressed), left untouched.notFound— ids that do not belong to your account.
