Page Summary
-
This document outlines the JSON structure for transaction requests sent from GTAF to a DPA for purchasing data plans.
-
The request includes crucial information such as plan ID, a unique transaction ID, offer context, and a callback URL for the DPA to respond.
-
Each field within the JSON object has specific requirements and serves a distinct purpose in facilitating the transaction process.
Body of a transaction request from GTAF to a DPA.
| JSON representation | |
|---|---|
{ "planId" : string , "transactionId" : string , "offerContext" : string , "callbackUrl" : string } |
|
| Fields | |
|---|---|
planId
|
Required. ID of the plan to be purchased. |
transactionId
|
Required. A unique identifier for this particular request. If the DPA receives multiple purchase requests with the same transactionId, all but the first should be rejected. |
offerContext
|
Context for the data plan offer. |
callbackUrl
|
URL for the DPA to call back. |
