Versions Compared

Old Version 2

changes.mady.by.user J Cobb (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user J Cobb (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sales where TEvo is the buyer are the most common type of sales you can expect to see. These sales can be identified by examining the order in the body for buyer.type=Office & buyer.id=6.

Info

When the buyer.type=Office the fraud_check_status does not matter, even if it is declined.

Sales to a Client

If a seller has a website powered by the TEvo API or they utilize Core to create sales to Clients then any sale where tickets are being sold their client can be identified by examining the order in the body for buyer.type=Client.

...

Note

If the seller utilizes our Riskified fraud service you should ensure the fraud_check_status of the order is approved before creating the order.

If a sale to a buyer.type=Client has a fraud_check_status=pending then we are awaiting an approval or detail from Riskified. Riskified will send TEvo periodic updates, each one of which will trigger a webhook with recipient=seller & event_type=fraud_response_received. The sale should don't not be invoiced until one is received where the fraud_check_status=approved.

Updating Existing Orders

Update to existing orders will have recipient=seller and the event_type will indicate what type of change has been made.

Coming soon…

Processing New Purchases

New purchases which should trigger a Purchase Order in your Point of Sale will have recipient=buyer and event_type=order_accepted.

Coming soon…

Updating Existing Purchases

Update to existing purchases will have recipient=buyer and the event_type will indicate what type of change has been made.

Coming soon…