> ## Documentation Index > Fetch the complete documentation index at: https://api-docs.helpyousponsor.com/llms.txt > Use this file to discover all available pages before exploring further. # Continue a Flutterwave v4 campaign charge > Submits PIN or OTP authorization for a previously initialized campaign charge. The controller validates the Redis charge state against client, program, charge id, and optional session id before sending the normalized authorization payload to Flutterwave. It stores the updated charge state and returns the same charge response shape as initialization. ## OpenAPI ````yaml put /frontend/flutterwave-v4/campaign-charge/{client_id}/{program_id}/{charge_id}/{session_id} openapi: 3.0.0 info: title: Gratona API description: >- REST API for the Gratona fundraising platform, including donor, donation, sponsorship, program, event, and integration workflows. Endpoints are organized by tag. Most endpoints require either a Passport bearer token or an issued API key — see the Security Schemes section. contact: name: Gratona Engineering url: https://gratona.com email: devs@gratona.com version: 1.0.0 servers: - url: https://api.gratona.com/v1 description: Server Version 1.0.0 security: [] tags: - name: Auth description: >- Login, signup, logout, password reset, and email verification for admin users and donors. - name: Donors description: >- Donor records: CRUD, profile fields, household linkage, search, filters, merge, and duplicate detection. - name: Donations description: >- Individual donation records, recurring commitments, soft credits, refunds, designations, and exports. - name: Sponsorships description: >- Donor-to-entity sponsorship relationships, lifecycle transitions, and sponsorship-specific filters. - name: Entities description: >- Recipient records (children, families, projects, animals, etc.), their status, and entity-level fields. - name: Programs description: >- Program / campaign configuration: hierarchy, settings, and program-level metadata. - name: Forms description: >- Custom form builder (HysForm), form fields, standardized donor fields, and field migrations. - name: Trips description: >- Mission-trip management: trips, participants, budgets, tasks, e-signatures, fundraising milestones, and background checks. - name: Communications description: >- Email templates, SMS, newsletters, donor email manager, and per-donor notes. - name: Payments description: >- Payment-gateway management (Stripe, PayPal, Flutterwave, QuickBooks). Excludes inbound webhooks — see the Webhooks tag. - name: Reports description: Dashboards, analytics, scheduled reports, and exports. - name: Admin description: >- Client-account administration: users, groups/permissions, settings, integrations, and account lifecycle. - name: Donor Portal description: >- Endpoints consumed by the donor-facing portal (donor login, dashboard, donation history, messages). - name: Recipient Portal description: Endpoints consumed by the recipient-facing portal. - name: Public description: >- Unauthenticated public endpoints: donor signup, public trip pages, peer-to-peer campaigns, public checkout. - name: Webhooks description: >- Inbound webhooks from third parties (Stripe, PayPal, Flutterwave, Checkr, DropboxSign). Annotated minimally for reference; payload shapes are owned by the upstream provider. - name: Client description: Client - name: Email Settings description: Email Settings - name: Admin Dashboard description: Admin Dashboard - name: Historical Archived Updates description: Historical Archived Updates - name: Team & access description: Team & access - name: Files description: Files - name: Wrapped description: Wrapped - name: Donor SignUp description: Donor SignUp - name: Frontend description: Frontend - name: User description: User paths: /frontend/flutterwave-v4/campaign-charge/{client_id}/{program_id}/{charge_id}/{session_id}: put: tags: - Payments summary: Continue a Flutterwave v4 campaign charge description: >- Submits PIN or OTP authorization for a previously initialized campaign charge. The controller validates the Redis charge state against client, program, charge id, and optional session id before sending the normalized authorization payload to Flutterwave. It stores the updated charge state and returns the same charge response shape as initialization. operationId: continueFlutterwaveV4CampaignCharge parameters: - name: client_id in: path description: Client id stored in the Redis charge state. required: true schema: type: integer example: 207 - name: program_id in: path description: Program id stored in the Redis charge state. required: true schema: type: integer example: 11 - name: charge_id in: path description: >- Flutterwave charge id returned by initialization and used as the Redis state key. required: true schema: type: string example: chg_123456 - name: session_id in: path description: >- Optional Redis frontend session id. When supplied, it must match the session stored for the charge. required: true schema: type: string example: 7f2c8f8d64b8a1d4a9e2 requestBody: required: true content: application/json: schema: required: - authorization properties: authorization: description: Authorization must match the charge's current next action. required: - type properties: type: description: 'Required authorization type: pin or otp.' type: string enum: - pin - otp example: otp pin: properties: value: description: Required string when authorization.type is pin. type: string example: '1234' type: object otp: properties: value: description: Required string when authorization.type is otp. type: string example: '123456' type: object type: object type: object responses: '200': description: Flutterwave charge continued. content: application/json: schema: type: object '404': description: Stored charge state was not found for this checkout session. content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' '422': description: Authorization validation failed. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' '500': description: Unexpected checkout failure. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '502': description: Flutterwave provider failure. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: [] components: schemas: NotFoundResponse: title: NotFoundResponse description: >- Returned with HTTP 404 when a resource lookup misses (typically because the id doesn't exist OR is scoped to a different `client_id`). Note: many endpoints intentionally collapse 'not found' and 'forbidden' into a single 404 to avoid leaking which records exist in another tenant. required: - message properties: message: description: >- Human-readable message. Often a more specific string like `Donor not found` or `Trip not found`. type: string example: Not Found status: type: string example: error type: object ValidationErrorResponse: title: ValidationErrorResponse description: >- Returned with HTTP 422 when `Validator::make($data, $rules)` fails. The `errors` map is keyed by the failing field name; each value is an array of human-readable error messages for that field. Most controllers also include a top-level `status: error`. required: - errors properties: errors: description: >- Map of field name to array of validator error messages. Example: `{email: [The email field is required.], amount: [The amount must be a number.]}`. type: object additionalProperties: type: array items: type: string status: description: Always the literal string `error`. type: string example: error message: description: >- Optional summary message — present on some endpoints, absent on others. type: string example: The given data was invalid. nullable: true type: object ErrorResponse: title: ErrorResponse description: >- Generic error envelope used by most controllers. Most error responses pair a human-readable `message` with `status: error`. Some endpoints additionally include `errors` (validator errors), `error` (legacy single-error string), `code`, or domain-specific context fields. required: - message properties: message: description: Human-readable error message. type: string example: Something went wrong. Please try again. status: description: >- Always the literal string `error` for failures. Some endpoints omit this field. type: string example: error error: description: Legacy single error code/string used by older endpoints. type: string example: invalid_request nullable: true code: description: >- Optional application-level error code (not all endpoints populate this). type: string example: DONOR_NOT_FOUND nullable: true type: object ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.