Record consent (consumer)

post

https://www.sandbox.striga.com/api/v1/user/payment-account/consent

Records the user's acceptance of the Payment Account terms.

Re-posting replaces the previous consent record wholesale — send the complete set of fields each time, not a delta. Recording "accepted": false withdraws consent and returns the user to the previous (pre-Payment-Account) behavior for subsequent transactions.

ip defaults to the source IP of this API request. When calling from your backend — the normal integration pattern — pass the end user's IP explicitly, otherwise your server's IP is recorded on the consent record.

dateAccepted defaults to the server time of the call.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

401

Missing or invalid api-key or HMAC signature.

Language

Credentials

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Consent recorded. The response echoes the stored record.

400Validation failure (errorCode 00002 — the message names the offending field, e.g. Invalid userId, accepted must be a boolean; note that accepted must be a JSON boolean — the string "true" is rejected), or the user does not exist (errorCode 30005).

403errorCode 30042: your application does not have the SET_PAYMENT_ACCOUNT_CONSENT permission. errorCode 30043 / 32017: the user's account status blocks the call (inaccessible / terminated). Suspended users can record consent.

404errorCode 30005: the user was not found in this application.