AddCustomPaymentv1.0.0
Details
This event must be consumed using an authorization token. The token is utilized to verify that the user has permission to produce the event and set user_id and organization_id within the attributes. Additionally, the event_source and metadata.event_triggered_by are automatically populated by the CF-Worker-User-Event.
- When the success team creates a new custom payment
- event_type: add_custom_payment
- event_name: platzi.sherlock.1.add_custom_payment
- attributes.value: true/false
Id for the event. This is a client auto-generated UUID_V4
Name of the event with format organization.domain.version.action
DateTime when the event was raises. Format YYYY-MM-DDTHH:MM:SSz
Contains arbitrary properties with entity information
Platzian username
Student identifier
Text combining add_custom_payment text and student_id value
Event value
Contains the custom payment data
Student name
Student email
Register type id
Subscription plan id
Recurrence type id
Installments number
Currency id
Amount to pay
Currency code
Current TRM based on currency
Mas currency amount
List of payment methods
Contain fixed properties with event information
Type of the event, used to join common sub events
How to trigger this event
1curl --location 'https://api-c963080767f45828c31f83ca5cd25d36.staging.platzi.com/behavior/v1/' \
2--header 'Content-Type: application/json' \
3--data '{
4 "event_id": "2457207d-a9d8-4b46-aff3-2a8ca385f2f6",
5 "event_name": "platzi.sherlock.1.add_custom_payment",
6 "event_occurred_on": "2023-05-01T22:29:56Z",
7 "attributes": {
8 "username": "organizer",
9 "student_id": 1,
10 "value": "add_custom_payment-1",
11 "key": "true",
12 "payment":{
13 "name":"test test",
14 "email":"test@test.com",
15 "registerType":1,
16 "subscriptionType":1,
17 "recurrenceType":1,
18 "installments":1,
19 "currency":1,
20 "amount":299,
21 "currencyCode":"USD",
22 "currentTrm":1,
23 "currentMax":499,
24 "paymentMethods:[1]
25 }
26 },
27 "metadata": {
28 "event_type": "add_custom_payment"
29 }
30}'
31