How to implement OK Addendum for 3rd Party Partners

Developer Portal documentation for the Oklahoma (OK) State Addendum requirement and document signing sequence.

This guide explains the implementation requirements for the Oklahoma (OK) State Addendum. The addendum is required so Snap Finance applications that fall under Oklahoma state regulations can reach the required OK state compliance state before the customer completes the financing agreement.

Overview

This guide explains the implementation requirements for the Oklahoma (OK) State Addendum. This addendum is required so Snap Finance applications that fall under Oklahoma state regulations can reach the required OK state compliance state before the customer completes the financing agreement.

When an application is subject to Oklahoma requirements, the customer must review and sign an additional disclosure addendum before signing the agreement. Partners must update their signing flow to support multiple documents returned by the Get Payment Plan response and complete them in the required priority order.

How to Implement the Oklahoma (OK) Addendum Requirement

Requirements

For applications subject to Oklahoma regulations, an additional OK disclosure addendum must be presented and signed by the customer before the customer views and signs the standard agreement.

Standard flow for non-OK applications

Customer views and signs the Agreement.

Required flow for Oklahoma applications

Customer views and signs the Addendum — priority 1.
Customer views and signs the Agreement — priority 2.

Important: Both documents must be completed in priority order. Skipping the addendum or signing the documents out of order may prevent the application from meeting the OK state requirement.

Dev Implementation Notes

Backend Enforcement requirements for the Oklahoma Addendum

Backend / API Behavior

The Get Payment Plan response drives the document signing sequence. In the example below, the response includes two documents:

Document	Priority	Required action
Addendum	1	Render first, then sign first
Agreement	2	Render second, then sign second

API Call Sequence

Priority 1 — Addendum
1. Call the addendum render URL from the Get Payment Plan response.
2. Call the addendum sign URL from the Get Payment Plan response.
Priority 2 — Agreement
1. Call the agreement render URL from the Get Payment Plan response.
2. Call the agreement sign URL from the Get Payment Plan response.

Key change: Do not call Get Agreement and Sign Agreement directly for this flow. Instead, read the render and sign URLs from the Get Payment Plan response object and use those URLs dynamically for each document in priority order.

Payment Plan sample response for Oklahoma showing addendum and agreement document URLs and priorities

API Reference

Get Agreement Details

GET {{baseUrl}}/platform/v1/application/{{applicationId}}/agreement?summaryAcceptance=true

Get Payment Plan

GET {{baseUrl}}/platform/v1/application/{{applicationId}}/paymentPlan

Sign Agreement

POST {{baseUrl}}/platform/v1/application/{{applicationId}}/signed