ALalfredpay
Onboarding

Re-run decisioning after a change

Changed on

Use this after corrected data, a new document or an archetype change. It re-runs the decision on what the customer now looks like.

This is the call for material changes, not a second /verifications.

post/v1/customers/{customerId}/reevaluate

Request

  • Base URL
    https://api.sandbox.alfredpay.io
  • URL
    https://api.sandbox.alfredpay.io/v1/customers/{customerId}/reevaluate
  • Auth
    • HTTP bearer
    • or API key in header api-key and API key in header api-secret

Headers

Idempotency-Keystring uuid required

Required on every state-changing POST, simulators included; the only exempt POST is …/verifications/preflight. Replay (same key, same body) returns the original response with Idempotent-Replayed: true; same key with a different body → 409 idempotency_conflict. Keys are UUIDs, scoped to the API key, retained for 24 hours.

Response

Accepted

idstring
submissionIdstring
type'INDIVIDUAL' | 'BUSINESS'
status'SUBMITTED' | 'IN_REVIEW' | 'APPROVED' | 'REJECTED' | 'RFI'
createdAtstring date-time
updatedAtstring date-time

Changes