Use authenticated payment state to prepare the next onboarding step without treating a browser redirect as proof of payment.
Contract item
Design decision
Source event key
event ID + invoice ID
Destination outcome
payment status review
Record ownership
The source system owns its authoritative business fields.
Delivery model
Assume duplicates and delayed or out-of-order events until proven otherwise.
Live readiness
Authenticate, sandbox-test, approve data handling, and assign an operator.
Map the fields
Source
Destination
Validation
event.id
dedupe_key
Store processed event
customer
client_reference
Approved mapping
invoice
invoice_reference
Reconcile destination
payment_status
payment_state
Handle refunds and disputes
created
event_time
Re-read current status
Implement the handoff
Create a least-privilege connection using the vendor’s supported authentication method. Keep secrets in the workflow credential store.
Receive and authenticate the event using current vendor guidance. Save a bounded job record, then process asynchronously where the provider’s acknowledgement deadline requires it.
Look up the tenant, source record, and mapping. If any identifier is ambiguous, create a review task instead of guessing.
Apply a durable duplicate-prevention key. Read the destination before retrying an action whose result is unknown.
Write the approved result and reconcile it against the expected business state. Record safe metadata and a reviewable outcome.
Failure and recovery checks
Failure
Expected response
401 / expired authorization
Stop this connection, alert its owner, and reauthorize through the approved process.
429 / rate limit
Respect provider retry guidance and use a bounded backoff queue.
Invalid field or mapping
Quarantine for correction; do not endlessly retry a bad payload.
Timeout after write
Check the destination using the stable reference before repeating the action.
Missed events
Run an approved periodic reconciliation against the source.
Test these integration-specific cases
A duplicate event must not unlock delivery twice.
A checkout cancellation must leave onboarding pending.
A refund must enter the approved reversal process.
The starter files demonstrate transformation and review behavior with synthetic data. They do not include live credentials or pre-authorized vendor accounts. Confirm current API schemas, plan entitlements, region, pagination, and webhook verification in the vendor documentation before connecting a firm.
Available instantly. No account or email required.
Help us make these resources more useful.
With your permission, Google Analytics measures visits and use of our guides and tools. We do not send form text, planner notes, or calculator values. Google receives technical connection and browser information. Your resources work with either choice.