charge id):
| Field | Required | Description |
|---|---|---|
payinConfigId | Yes | Value returned by POST /billing/payment-terminal/payin-config as payinConfigId. This ties the charge to Rainforest’s pay-in flow. It is not the same as chargeId / chg_…. |
POST /billing/payment-terminal/payin-config
Include the charge(s) (e.g. full ChargeSummary objects), paymentMedium, merchantAccountId as required by that endpoint.
The response includes payinConfigId (and often sessionKey for browser components; for server-side charge-card you only need payinConfigId).
POST /billing/payment-terminal/charge-card/{paymentMethodId}
Path: Decoda paymentMethodId (e.g. pm_… from the store-details embed).
Body: { "payinConfigId": "<from step 1>" }.
payinConfigId is missing or wrong, Rainforest may respond with an error such as “Field is required” — that refers to the pay-in config id in their API, not chargeId or amount on this endpoint.The tenant you are making this request on behalf of
Your api key
From POST /billing/payment-terminal/payin-config (not the Decoda charge id).