forked from orbcorp/orb-go
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcustomercreditledger.go
More file actions
2675 lines (2412 loc) · 125 KB
/
customercreditledger.go
File metadata and controls
2675 lines (2412 loc) · 125 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
package orb
import (
"context"
"errors"
"fmt"
"net/http"
"net/url"
"reflect"
"time"
"github.com/orbcorp/orb-go/internal/apijson"
"github.com/orbcorp/orb-go/internal/apiquery"
"github.com/orbcorp/orb-go/internal/param"
"github.com/orbcorp/orb-go/internal/requestconfig"
"github.com/orbcorp/orb-go/option"
"github.com/orbcorp/orb-go/packages/pagination"
"github.com/orbcorp/orb-go/shared"
"github.com/tidwall/gjson"
)
// CustomerCreditLedgerService contains methods and other services that help with
// interacting with the orb API.
//
// Note, unlike clients, this service does not read variables from the environment
// automatically. You should not instantiate this service directly, and instead use
// the [NewCustomerCreditLedgerService] method instead.
type CustomerCreditLedgerService struct {
Options []option.RequestOption
}
// NewCustomerCreditLedgerService generates a new service that applies the given
// options to each request. These options are applied after the parent client's
// options (if there is one), and before any request-specific options.
func NewCustomerCreditLedgerService(opts ...option.RequestOption) (r *CustomerCreditLedgerService) {
r = &CustomerCreditLedgerService{}
r.Options = opts
return
}
// The credits ledger provides _auditing_ functionality over Orb's credits system
// with a list of actions that have taken place to modify a customer's credit
// balance. This [paginated endpoint](/api-reference/pagination) lists these
// entries, starting from the most recent ledger entry.
//
// More details on using Orb's real-time credit feature are
// [here](/product-catalog/prepurchase).
//
// There are four major types of modifications to credit balance, detailed below.
//
// ## Increment
//
// Credits (which optionally expire on a future date) can be added via the API
// ([Add Ledger Entry](create-ledger-entry)). The ledger entry for such an action
// will always contain the total eligible starting and ending balance for the
// customer at the time the entry was added to the ledger.
//
// ## Decrement
//
// Deductions can occur as a result of an API call to create a ledger entry (see
// [Add Ledger Entry](create-ledger-entry)), or automatically as a result of
// incurring usage. Both ledger entries present the `decrement` entry type.
//
// As usage for a customer is reported into Orb, credits may be deducted according
// to the customer's plan configuration. An automated deduction of this type will
// result in a ledger entry, also with a starting and ending balance. In order to
// provide better tracing capabilities for automatic deductions, Orb always
// associates each automatic deduction with the `event_id` at the time of
// ingestion, used to pinpoint _why_ credit deduction took place and to ensure that
// credits are never deducted without an associated usage event.
//
// By default, Orb uses an algorithm that automatically deducts from the _soonest
// expiring credit block_ first in order to ensure that all credits are utilized
// appropriately. As an example, if trial credits with an expiration date of 2
// weeks from now are present for a customer, they will be used before any
// deductions take place from a non-expiring credit block.
//
// If there are multiple blocks with the same expiration date, Orb will deduct from
// the block with the _lower cost basis_ first (e.g. trial credits with a \$0 cost
// basis before paid credits with a \$5.00 cost basis).
//
// It's also possible for a single usage event's deduction to _span_ credit blocks.
// In this case, Orb will deduct from the next block, ending at the credit block
// which consists of unexpiring credits. Each of these deductions will lead to a
// _separate_ ledger entry, one per credit block that is deducted from. By default,
// the customer's total credit balance in Orb can be negative as a result of a
// decrement.
//
// ## Expiration change
//
// The expiry of credits can be changed as a result of the API (See
// [Add Ledger Entry](create-ledger-entry)). This will create a ledger entry that
// specifies the balance as well as the initial and target expiry dates.
//
// Note that for this entry type, `starting_balance` will equal `ending_balance`,
// and the `amount` represents the balance transferred. The credit block linked to
// the ledger entry is the source credit block from which there was an expiration
// change.
//
// ## Credits expiry
//
// When a set of credits expire on pre-set expiration date, the customer's balance
// automatically reflects this change and adds an entry to the ledger indicating
// this event. Note that credit expiry should always happen close to a date
// boundary in the customer's timezone.
//
// ## Void initiated
//
// Credit blocks can be voided via the API. The `amount` on this entry corresponds
// to the number of credits that were remaining in the block at time of void.
// `void_reason` will be populated if the void is created with a reason.
//
// ## Void
//
// When a set of credits is voided, the customer's balance automatically reflects
// this change and adds an entry to the ledger indicating this event.
//
// ## Amendment
//
// When credits are added to a customer's balance as a result of a correction, this
// entry will be added to the ledger to indicate the adjustment of credits.
func (r *CustomerCreditLedgerService) List(ctx context.Context, customerID string, query CustomerCreditLedgerListParams, opts ...option.RequestOption) (res *pagination.Page[CustomerCreditLedgerListResponse], err error) {
var raw *http.Response
opts = append(r.Options[:], opts...)
opts = append([]option.RequestOption{option.WithResponseInto(&raw)}, opts...)
if customerID == "" {
err = errors.New("missing required customer_id parameter")
return
}
path := fmt.Sprintf("customers/%s/credits/ledger", customerID)
cfg, err := requestconfig.NewRequestConfig(ctx, http.MethodGet, path, query, &res, opts...)
if err != nil {
return nil, err
}
err = cfg.Execute()
if err != nil {
return nil, err
}
res.SetPageConfig(cfg, raw)
return res, nil
}
// The credits ledger provides _auditing_ functionality over Orb's credits system
// with a list of actions that have taken place to modify a customer's credit
// balance. This [paginated endpoint](/api-reference/pagination) lists these
// entries, starting from the most recent ledger entry.
//
// More details on using Orb's real-time credit feature are
// [here](/product-catalog/prepurchase).
//
// There are four major types of modifications to credit balance, detailed below.
//
// ## Increment
//
// Credits (which optionally expire on a future date) can be added via the API
// ([Add Ledger Entry](create-ledger-entry)). The ledger entry for such an action
// will always contain the total eligible starting and ending balance for the
// customer at the time the entry was added to the ledger.
//
// ## Decrement
//
// Deductions can occur as a result of an API call to create a ledger entry (see
// [Add Ledger Entry](create-ledger-entry)), or automatically as a result of
// incurring usage. Both ledger entries present the `decrement` entry type.
//
// As usage for a customer is reported into Orb, credits may be deducted according
// to the customer's plan configuration. An automated deduction of this type will
// result in a ledger entry, also with a starting and ending balance. In order to
// provide better tracing capabilities for automatic deductions, Orb always
// associates each automatic deduction with the `event_id` at the time of
// ingestion, used to pinpoint _why_ credit deduction took place and to ensure that
// credits are never deducted without an associated usage event.
//
// By default, Orb uses an algorithm that automatically deducts from the _soonest
// expiring credit block_ first in order to ensure that all credits are utilized
// appropriately. As an example, if trial credits with an expiration date of 2
// weeks from now are present for a customer, they will be used before any
// deductions take place from a non-expiring credit block.
//
// If there are multiple blocks with the same expiration date, Orb will deduct from
// the block with the _lower cost basis_ first (e.g. trial credits with a \$0 cost
// basis before paid credits with a \$5.00 cost basis).
//
// It's also possible for a single usage event's deduction to _span_ credit blocks.
// In this case, Orb will deduct from the next block, ending at the credit block
// which consists of unexpiring credits. Each of these deductions will lead to a
// _separate_ ledger entry, one per credit block that is deducted from. By default,
// the customer's total credit balance in Orb can be negative as a result of a
// decrement.
//
// ## Expiration change
//
// The expiry of credits can be changed as a result of the API (See
// [Add Ledger Entry](create-ledger-entry)). This will create a ledger entry that
// specifies the balance as well as the initial and target expiry dates.
//
// Note that for this entry type, `starting_balance` will equal `ending_balance`,
// and the `amount` represents the balance transferred. The credit block linked to
// the ledger entry is the source credit block from which there was an expiration
// change.
//
// ## Credits expiry
//
// When a set of credits expire on pre-set expiration date, the customer's balance
// automatically reflects this change and adds an entry to the ledger indicating
// this event. Note that credit expiry should always happen close to a date
// boundary in the customer's timezone.
//
// ## Void initiated
//
// Credit blocks can be voided via the API. The `amount` on this entry corresponds
// to the number of credits that were remaining in the block at time of void.
// `void_reason` will be populated if the void is created with a reason.
//
// ## Void
//
// When a set of credits is voided, the customer's balance automatically reflects
// this change and adds an entry to the ledger indicating this event.
//
// ## Amendment
//
// When credits are added to a customer's balance as a result of a correction, this
// entry will be added to the ledger to indicate the adjustment of credits.
func (r *CustomerCreditLedgerService) ListAutoPaging(ctx context.Context, customerID string, query CustomerCreditLedgerListParams, opts ...option.RequestOption) *pagination.PageAutoPager[CustomerCreditLedgerListResponse] {
return pagination.NewPageAutoPager(r.List(ctx, customerID, query, opts...))
}
// This endpoint allows you to create a new ledger entry for a specified customer's
// balance. This can be used to increment balance, deduct credits, and change the
// expiry date of existing credits.
//
// ## Effects of adding a ledger entry
//
// 1. After calling this endpoint, [Fetch Credit Balance](fetch-customer-credits)
// will return a credit block that represents the changes (i.e. balance changes
// or transfers).
// 2. A ledger entry will be added to the credits ledger for this customer, and
// therefore returned in the
// [View Credits Ledger](fetch-customer-credits-ledger) response as well as
// serialized in the response to this request. In the case of deductions without
// a specified block, multiple ledger entries may be created if the deduction
// spans credit blocks.
// 3. If `invoice_settings` is specified, an invoice will be created that reflects
// the cost of the credits (based on `amount` and `per_unit_cost_basis`).
//
// ## Adding credits
//
// Adding credits is done by creating an entry of type `increment`. This requires
// the caller to specify a number of credits as well as an optional expiry date in
// `YYYY-MM-DD` format. Orb also recommends specifying a description to assist with
// auditing. When adding credits, the caller can also specify a cost basis
// per-credit, to indicate how much in USD a customer paid for a single credit in a
// block. This can later be used for revenue recognition.
//
// The following snippet illustrates a sample request body to increment credits
// which will expire in January of 2022.
//
// ```json
//
// {
// "entry_type": "increment",
// "amount": 100,
// "expiry_date": "2022-12-28",
// "per_unit_cost_basis": "0.20",
// "description": "Purchased 100 credits"
// }
//
// ```
//
// Note that by default, Orb will always first increment any _negative_ balance in
// existing blocks before adding the remaining amount to the desired credit block.
//
// ### Invoicing for credits
//
// By default, Orb manipulates the credit ledger but does not charge for credits.
// However, if you pass `invoice_settings` in the body of this request, Orb will
// also generate a one-off invoice for the customer for the credits pre-purchase.
// Note that you _must_ provide the `per_unit_cost_basis`, since the total charges
// on the invoice are calculated by multiplying the cost basis with the number of
// credit units added.
//
// ## Deducting Credits
//
// Orb allows you to deduct credits from a customer by creating an entry of type
// `decrement`. Orb matches the algorithm for automatic deductions for determining
// which credit blocks to decrement from. In the case that the deduction leads to
// multiple ledger entries, the response from this endpoint will be the final
// deduction. Orb also optionally allows specifying a description to assist with
// auditing.
//
// The following snippet illustrates a sample request body to decrement credits.
//
// ```json
//
// {
// "entry_type": "decrement",
// "amount": 20,
// "description": "Removing excess credits"
// }
//
// ```
//
// ## Changing credits expiry
//
// If you'd like to change when existing credits expire, you should create a ledger
// entry of type `expiration_change`. For this entry, the required parameter
// `expiry_date` identifies the _originating_ block, and the required parameter
// `target_expiry_date` identifies when the transferred credits should now expire.
// A new credit block will be created with expiry date `target_expiry_date`, with
// the same cost basis data as the original credit block, if present.
//
// Note that the balance of the block with the given `expiry_date` must be at least
// equal to the desired transfer amount determined by the `amount` parameter.
//
// The following snippet illustrates a sample request body to extend the expiration
// date of credits by one year:
//
// ```json
//
// {
// "entry_type": "expiration_change",
// "amount": 10,
// "expiry_date": "2022-12-28",
// "block_id": "UiUhFWeLHPrBY4Ad",
// "target_expiry_date": "2023-12-28",
// "description": "Extending credit validity"
// }
//
// ```
//
// ## Voiding credits
//
// If you'd like to void a credit block, create a ledger entry of type `void`. For
// this entry, `block_id` is required to identify the block, and `amount` indicates
// how many credits to void, up to the block's initial balance. Pass in a
// `void_reason` of `refund` if the void is due to a refund.
//
// ## Amendment
//
// If you'd like to undo a decrement on a credit block, create a ledger entry of
// type `amendment`. For this entry, `block_id` is required to identify the block
// that was originally decremented from, and `amount` indicates how many credits to
// return to the customer, up to the block's initial balance.
func (r *CustomerCreditLedgerService) NewEntry(ctx context.Context, customerID string, body CustomerCreditLedgerNewEntryParams, opts ...option.RequestOption) (res *CustomerCreditLedgerNewEntryResponse, err error) {
opts = append(r.Options[:], opts...)
if customerID == "" {
err = errors.New("missing required customer_id parameter")
return
}
path := fmt.Sprintf("customers/%s/credits/ledger_entry", customerID)
err = requestconfig.ExecuteNewRequest(ctx, http.MethodPost, path, body, &res, opts...)
return
}
// This endpoint allows you to create a new ledger entry for a specified customer's
// balance. This can be used to increment balance, deduct credits, and change the
// expiry date of existing credits.
//
// ## Effects of adding a ledger entry
//
// 1. After calling this endpoint, [Fetch Credit Balance](fetch-customer-credits)
// will return a credit block that represents the changes (i.e. balance changes
// or transfers).
// 2. A ledger entry will be added to the credits ledger for this customer, and
// therefore returned in the
// [View Credits Ledger](fetch-customer-credits-ledger) response as well as
// serialized in the response to this request. In the case of deductions without
// a specified block, multiple ledger entries may be created if the deduction
// spans credit blocks.
// 3. If `invoice_settings` is specified, an invoice will be created that reflects
// the cost of the credits (based on `amount` and `per_unit_cost_basis`).
//
// ## Adding credits
//
// Adding credits is done by creating an entry of type `increment`. This requires
// the caller to specify a number of credits as well as an optional expiry date in
// `YYYY-MM-DD` format. Orb also recommends specifying a description to assist with
// auditing. When adding credits, the caller can also specify a cost basis
// per-credit, to indicate how much in USD a customer paid for a single credit in a
// block. This can later be used for revenue recognition.
//
// The following snippet illustrates a sample request body to increment credits
// which will expire in January of 2022.
//
// ```json
//
// {
// "entry_type": "increment",
// "amount": 100,
// "expiry_date": "2022-12-28",
// "per_unit_cost_basis": "0.20",
// "description": "Purchased 100 credits"
// }
//
// ```
//
// Note that by default, Orb will always first increment any _negative_ balance in
// existing blocks before adding the remaining amount to the desired credit block.
//
// ### Invoicing for credits
//
// By default, Orb manipulates the credit ledger but does not charge for credits.
// However, if you pass `invoice_settings` in the body of this request, Orb will
// also generate a one-off invoice for the customer for the credits pre-purchase.
// Note that you _must_ provide the `per_unit_cost_basis`, since the total charges
// on the invoice are calculated by multiplying the cost basis with the number of
// credit units added.
//
// ## Deducting Credits
//
// Orb allows you to deduct credits from a customer by creating an entry of type
// `decrement`. Orb matches the algorithm for automatic deductions for determining
// which credit blocks to decrement from. In the case that the deduction leads to
// multiple ledger entries, the response from this endpoint will be the final
// deduction. Orb also optionally allows specifying a description to assist with
// auditing.
//
// The following snippet illustrates a sample request body to decrement credits.
//
// ```json
//
// {
// "entry_type": "decrement",
// "amount": 20,
// "description": "Removing excess credits"
// }
//
// ```
//
// ## Changing credits expiry
//
// If you'd like to change when existing credits expire, you should create a ledger
// entry of type `expiration_change`. For this entry, the required parameter
// `expiry_date` identifies the _originating_ block, and the required parameter
// `target_expiry_date` identifies when the transferred credits should now expire.
// A new credit block will be created with expiry date `target_expiry_date`, with
// the same cost basis data as the original credit block, if present.
//
// Note that the balance of the block with the given `expiry_date` must be at least
// equal to the desired transfer amount determined by the `amount` parameter.
//
// The following snippet illustrates a sample request body to extend the expiration
// date of credits by one year:
//
// ```json
//
// {
// "entry_type": "expiration_change",
// "amount": 10,
// "expiry_date": "2022-12-28",
// "block_id": "UiUhFWeLHPrBY4Ad",
// "target_expiry_date": "2023-12-28",
// "description": "Extending credit validity"
// }
//
// ```
//
// ## Voiding credits
//
// If you'd like to void a credit block, create a ledger entry of type `void`. For
// this entry, `block_id` is required to identify the block, and `amount` indicates
// how many credits to void, up to the block's initial balance. Pass in a
// `void_reason` of `refund` if the void is due to a refund.
//
// ## Amendment
//
// If you'd like to undo a decrement on a credit block, create a ledger entry of
// type `amendment`. For this entry, `block_id` is required to identify the block
// that was originally decremented from, and `amount` indicates how many credits to
// return to the customer, up to the block's initial balance.
func (r *CustomerCreditLedgerService) NewEntryByExternalID(ctx context.Context, externalCustomerID string, body CustomerCreditLedgerNewEntryByExternalIDParams, opts ...option.RequestOption) (res *CustomerCreditLedgerNewEntryByExternalIDResponse, err error) {
opts = append(r.Options[:], opts...)
if externalCustomerID == "" {
err = errors.New("missing required external_customer_id parameter")
return
}
path := fmt.Sprintf("customers/external_customer_id/%s/credits/ledger_entry", externalCustomerID)
err = requestconfig.ExecuteNewRequest(ctx, http.MethodPost, path, body, &res, opts...)
return
}
// The credits ledger provides _auditing_ functionality over Orb's credits system
// with a list of actions that have taken place to modify a customer's credit
// balance. This [paginated endpoint](/api-reference/pagination) lists these
// entries, starting from the most recent ledger entry.
//
// More details on using Orb's real-time credit feature are
// [here](/product-catalog/prepurchase).
//
// There are four major types of modifications to credit balance, detailed below.
//
// ## Increment
//
// Credits (which optionally expire on a future date) can be added via the API
// ([Add Ledger Entry](create-ledger-entry)). The ledger entry for such an action
// will always contain the total eligible starting and ending balance for the
// customer at the time the entry was added to the ledger.
//
// ## Decrement
//
// Deductions can occur as a result of an API call to create a ledger entry (see
// [Add Ledger Entry](create-ledger-entry)), or automatically as a result of
// incurring usage. Both ledger entries present the `decrement` entry type.
//
// As usage for a customer is reported into Orb, credits may be deducted according
// to the customer's plan configuration. An automated deduction of this type will
// result in a ledger entry, also with a starting and ending balance. In order to
// provide better tracing capabilities for automatic deductions, Orb always
// associates each automatic deduction with the `event_id` at the time of
// ingestion, used to pinpoint _why_ credit deduction took place and to ensure that
// credits are never deducted without an associated usage event.
//
// By default, Orb uses an algorithm that automatically deducts from the _soonest
// expiring credit block_ first in order to ensure that all credits are utilized
// appropriately. As an example, if trial credits with an expiration date of 2
// weeks from now are present for a customer, they will be used before any
// deductions take place from a non-expiring credit block.
//
// If there are multiple blocks with the same expiration date, Orb will deduct from
// the block with the _lower cost basis_ first (e.g. trial credits with a \$0 cost
// basis before paid credits with a \$5.00 cost basis).
//
// It's also possible for a single usage event's deduction to _span_ credit blocks.
// In this case, Orb will deduct from the next block, ending at the credit block
// which consists of unexpiring credits. Each of these deductions will lead to a
// _separate_ ledger entry, one per credit block that is deducted from. By default,
// the customer's total credit balance in Orb can be negative as a result of a
// decrement.
//
// ## Expiration change
//
// The expiry of credits can be changed as a result of the API (See
// [Add Ledger Entry](create-ledger-entry)). This will create a ledger entry that
// specifies the balance as well as the initial and target expiry dates.
//
// Note that for this entry type, `starting_balance` will equal `ending_balance`,
// and the `amount` represents the balance transferred. The credit block linked to
// the ledger entry is the source credit block from which there was an expiration
// change.
//
// ## Credits expiry
//
// When a set of credits expire on pre-set expiration date, the customer's balance
// automatically reflects this change and adds an entry to the ledger indicating
// this event. Note that credit expiry should always happen close to a date
// boundary in the customer's timezone.
//
// ## Void initiated
//
// Credit blocks can be voided via the API. The `amount` on this entry corresponds
// to the number of credits that were remaining in the block at time of void.
// `void_reason` will be populated if the void is created with a reason.
//
// ## Void
//
// When a set of credits is voided, the customer's balance automatically reflects
// this change and adds an entry to the ledger indicating this event.
//
// ## Amendment
//
// When credits are added to a customer's balance as a result of a correction, this
// entry will be added to the ledger to indicate the adjustment of credits.
func (r *CustomerCreditLedgerService) ListByExternalID(ctx context.Context, externalCustomerID string, query CustomerCreditLedgerListByExternalIDParams, opts ...option.RequestOption) (res *pagination.Page[CustomerCreditLedgerListByExternalIDResponse], err error) {
var raw *http.Response
opts = append(r.Options[:], opts...)
opts = append([]option.RequestOption{option.WithResponseInto(&raw)}, opts...)
if externalCustomerID == "" {
err = errors.New("missing required external_customer_id parameter")
return
}
path := fmt.Sprintf("customers/external_customer_id/%s/credits/ledger", externalCustomerID)
cfg, err := requestconfig.NewRequestConfig(ctx, http.MethodGet, path, query, &res, opts...)
if err != nil {
return nil, err
}
err = cfg.Execute()
if err != nil {
return nil, err
}
res.SetPageConfig(cfg, raw)
return res, nil
}
// The credits ledger provides _auditing_ functionality over Orb's credits system
// with a list of actions that have taken place to modify a customer's credit
// balance. This [paginated endpoint](/api-reference/pagination) lists these
// entries, starting from the most recent ledger entry.
//
// More details on using Orb's real-time credit feature are
// [here](/product-catalog/prepurchase).
//
// There are four major types of modifications to credit balance, detailed below.
//
// ## Increment
//
// Credits (which optionally expire on a future date) can be added via the API
// ([Add Ledger Entry](create-ledger-entry)). The ledger entry for such an action
// will always contain the total eligible starting and ending balance for the
// customer at the time the entry was added to the ledger.
//
// ## Decrement
//
// Deductions can occur as a result of an API call to create a ledger entry (see
// [Add Ledger Entry](create-ledger-entry)), or automatically as a result of
// incurring usage. Both ledger entries present the `decrement` entry type.
//
// As usage for a customer is reported into Orb, credits may be deducted according
// to the customer's plan configuration. An automated deduction of this type will
// result in a ledger entry, also with a starting and ending balance. In order to
// provide better tracing capabilities for automatic deductions, Orb always
// associates each automatic deduction with the `event_id` at the time of
// ingestion, used to pinpoint _why_ credit deduction took place and to ensure that
// credits are never deducted without an associated usage event.
//
// By default, Orb uses an algorithm that automatically deducts from the _soonest
// expiring credit block_ first in order to ensure that all credits are utilized
// appropriately. As an example, if trial credits with an expiration date of 2
// weeks from now are present for a customer, they will be used before any
// deductions take place from a non-expiring credit block.
//
// If there are multiple blocks with the same expiration date, Orb will deduct from
// the block with the _lower cost basis_ first (e.g. trial credits with a \$0 cost
// basis before paid credits with a \$5.00 cost basis).
//
// It's also possible for a single usage event's deduction to _span_ credit blocks.
// In this case, Orb will deduct from the next block, ending at the credit block
// which consists of unexpiring credits. Each of these deductions will lead to a
// _separate_ ledger entry, one per credit block that is deducted from. By default,
// the customer's total credit balance in Orb can be negative as a result of a
// decrement.
//
// ## Expiration change
//
// The expiry of credits can be changed as a result of the API (See
// [Add Ledger Entry](create-ledger-entry)). This will create a ledger entry that
// specifies the balance as well as the initial and target expiry dates.
//
// Note that for this entry type, `starting_balance` will equal `ending_balance`,
// and the `amount` represents the balance transferred. The credit block linked to
// the ledger entry is the source credit block from which there was an expiration
// change.
//
// ## Credits expiry
//
// When a set of credits expire on pre-set expiration date, the customer's balance
// automatically reflects this change and adds an entry to the ledger indicating
// this event. Note that credit expiry should always happen close to a date
// boundary in the customer's timezone.
//
// ## Void initiated
//
// Credit blocks can be voided via the API. The `amount` on this entry corresponds
// to the number of credits that were remaining in the block at time of void.
// `void_reason` will be populated if the void is created with a reason.
//
// ## Void
//
// When a set of credits is voided, the customer's balance automatically reflects
// this change and adds an entry to the ledger indicating this event.
//
// ## Amendment
//
// When credits are added to a customer's balance as a result of a correction, this
// entry will be added to the ledger to indicate the adjustment of credits.
func (r *CustomerCreditLedgerService) ListByExternalIDAutoPaging(ctx context.Context, externalCustomerID string, query CustomerCreditLedgerListByExternalIDParams, opts ...option.RequestOption) *pagination.PageAutoPager[CustomerCreditLedgerListByExternalIDResponse] {
return pagination.NewPageAutoPager(r.ListByExternalID(ctx, externalCustomerID, query, opts...))
}
type AffectedBlock struct {
ID string `json:"id,required"`
ExpiryDate time.Time `json:"expiry_date,required,nullable" format:"date-time"`
PerUnitCostBasis string `json:"per_unit_cost_basis,required,nullable"`
JSON affectedBlockJSON `json:"-"`
}
// affectedBlockJSON contains the JSON metadata for the struct [AffectedBlock]
type affectedBlockJSON struct {
ID apijson.Field
ExpiryDate apijson.Field
PerUnitCostBasis apijson.Field
raw string
ExtraFields map[string]apijson.Field
}
func (r *AffectedBlock) UnmarshalJSON(data []byte) (err error) {
return apijson.UnmarshalRoot(data, r)
}
func (r affectedBlockJSON) RawJSON() string {
return r.raw
}
type AmendmentLedgerEntry struct {
ID string `json:"id,required"`
Amount float64 `json:"amount,required"`
CreatedAt time.Time `json:"created_at,required" format:"date-time"`
CreditBlock AffectedBlock `json:"credit_block,required"`
Currency string `json:"currency,required"`
Customer shared.CustomerMinified `json:"customer,required"`
Description string `json:"description,required,nullable"`
EndingBalance float64 `json:"ending_balance,required"`
EntryStatus AmendmentLedgerEntryEntryStatus `json:"entry_status,required"`
EntryType AmendmentLedgerEntryEntryType `json:"entry_type,required"`
LedgerSequenceNumber int64 `json:"ledger_sequence_number,required"`
// User specified key-value pairs for the resource. If not present, this defaults
// to an empty dictionary. Individual keys can be removed by setting the value to
// `null`, and the entire metadata mapping can be cleared by setting `metadata` to
// `null`.
Metadata map[string]string `json:"metadata,required"`
StartingBalance float64 `json:"starting_balance,required"`
JSON amendmentLedgerEntryJSON `json:"-"`
}
// amendmentLedgerEntryJSON contains the JSON metadata for the struct
// [AmendmentLedgerEntry]
type amendmentLedgerEntryJSON struct {
ID apijson.Field
Amount apijson.Field
CreatedAt apijson.Field
CreditBlock apijson.Field
Currency apijson.Field
Customer apijson.Field
Description apijson.Field
EndingBalance apijson.Field
EntryStatus apijson.Field
EntryType apijson.Field
LedgerSequenceNumber apijson.Field
Metadata apijson.Field
StartingBalance apijson.Field
raw string
ExtraFields map[string]apijson.Field
}
func (r *AmendmentLedgerEntry) UnmarshalJSON(data []byte) (err error) {
return apijson.UnmarshalRoot(data, r)
}
func (r amendmentLedgerEntryJSON) RawJSON() string {
return r.raw
}
func (r AmendmentLedgerEntry) implementsCustomerCreditLedgerListResponse() {}
func (r AmendmentLedgerEntry) implementsCustomerCreditLedgerNewEntryResponse() {}
func (r AmendmentLedgerEntry) implementsCustomerCreditLedgerNewEntryByExternalIDResponse() {}
func (r AmendmentLedgerEntry) implementsCustomerCreditLedgerListByExternalIDResponse() {}
type AmendmentLedgerEntryEntryStatus string
const (
AmendmentLedgerEntryEntryStatusCommitted AmendmentLedgerEntryEntryStatus = "committed"
AmendmentLedgerEntryEntryStatusPending AmendmentLedgerEntryEntryStatus = "pending"
)
func (r AmendmentLedgerEntryEntryStatus) IsKnown() bool {
switch r {
case AmendmentLedgerEntryEntryStatusCommitted, AmendmentLedgerEntryEntryStatusPending:
return true
}
return false
}
type AmendmentLedgerEntryEntryType string
const (
AmendmentLedgerEntryEntryTypeAmendment AmendmentLedgerEntryEntryType = "amendment"
)
func (r AmendmentLedgerEntryEntryType) IsKnown() bool {
switch r {
case AmendmentLedgerEntryEntryTypeAmendment:
return true
}
return false
}
type CreditBlockExpiryLedgerEntry struct {
ID string `json:"id,required"`
Amount float64 `json:"amount,required"`
CreatedAt time.Time `json:"created_at,required" format:"date-time"`
CreditBlock AffectedBlock `json:"credit_block,required"`
Currency string `json:"currency,required"`
Customer shared.CustomerMinified `json:"customer,required"`
Description string `json:"description,required,nullable"`
EndingBalance float64 `json:"ending_balance,required"`
EntryStatus CreditBlockExpiryLedgerEntryEntryStatus `json:"entry_status,required"`
EntryType CreditBlockExpiryLedgerEntryEntryType `json:"entry_type,required"`
LedgerSequenceNumber int64 `json:"ledger_sequence_number,required"`
// User specified key-value pairs for the resource. If not present, this defaults
// to an empty dictionary. Individual keys can be removed by setting the value to
// `null`, and the entire metadata mapping can be cleared by setting `metadata` to
// `null`.
Metadata map[string]string `json:"metadata,required"`
StartingBalance float64 `json:"starting_balance,required"`
JSON creditBlockExpiryLedgerEntryJSON `json:"-"`
}
// creditBlockExpiryLedgerEntryJSON contains the JSON metadata for the struct
// [CreditBlockExpiryLedgerEntry]
type creditBlockExpiryLedgerEntryJSON struct {
ID apijson.Field
Amount apijson.Field
CreatedAt apijson.Field
CreditBlock apijson.Field
Currency apijson.Field
Customer apijson.Field
Description apijson.Field
EndingBalance apijson.Field
EntryStatus apijson.Field
EntryType apijson.Field
LedgerSequenceNumber apijson.Field
Metadata apijson.Field
StartingBalance apijson.Field
raw string
ExtraFields map[string]apijson.Field
}
func (r *CreditBlockExpiryLedgerEntry) UnmarshalJSON(data []byte) (err error) {
return apijson.UnmarshalRoot(data, r)
}
func (r creditBlockExpiryLedgerEntryJSON) RawJSON() string {
return r.raw
}
func (r CreditBlockExpiryLedgerEntry) implementsCustomerCreditLedgerListResponse() {}
func (r CreditBlockExpiryLedgerEntry) implementsCustomerCreditLedgerNewEntryResponse() {}
func (r CreditBlockExpiryLedgerEntry) implementsCustomerCreditLedgerNewEntryByExternalIDResponse() {}
func (r CreditBlockExpiryLedgerEntry) implementsCustomerCreditLedgerListByExternalIDResponse() {}
type CreditBlockExpiryLedgerEntryEntryStatus string
const (
CreditBlockExpiryLedgerEntryEntryStatusCommitted CreditBlockExpiryLedgerEntryEntryStatus = "committed"
CreditBlockExpiryLedgerEntryEntryStatusPending CreditBlockExpiryLedgerEntryEntryStatus = "pending"
)
func (r CreditBlockExpiryLedgerEntryEntryStatus) IsKnown() bool {
switch r {
case CreditBlockExpiryLedgerEntryEntryStatusCommitted, CreditBlockExpiryLedgerEntryEntryStatusPending:
return true
}
return false
}
type CreditBlockExpiryLedgerEntryEntryType string
const (
CreditBlockExpiryLedgerEntryEntryTypeCreditBlockExpiry CreditBlockExpiryLedgerEntryEntryType = "credit_block_expiry"
)
func (r CreditBlockExpiryLedgerEntryEntryType) IsKnown() bool {
switch r {
case CreditBlockExpiryLedgerEntryEntryTypeCreditBlockExpiry:
return true
}
return false
}
type DecrementLedgerEntry struct {
ID string `json:"id,required"`
Amount float64 `json:"amount,required"`
CreatedAt time.Time `json:"created_at,required" format:"date-time"`
CreditBlock AffectedBlock `json:"credit_block,required"`
Currency string `json:"currency,required"`
Customer shared.CustomerMinified `json:"customer,required"`
Description string `json:"description,required,nullable"`
EndingBalance float64 `json:"ending_balance,required"`
EntryStatus DecrementLedgerEntryEntryStatus `json:"entry_status,required"`
EntryType DecrementLedgerEntryEntryType `json:"entry_type,required"`
LedgerSequenceNumber int64 `json:"ledger_sequence_number,required"`
// User specified key-value pairs for the resource. If not present, this defaults
// to an empty dictionary. Individual keys can be removed by setting the value to
// `null`, and the entire metadata mapping can be cleared by setting `metadata` to
// `null`.
Metadata map[string]string `json:"metadata,required"`
StartingBalance float64 `json:"starting_balance,required"`
EventID string `json:"event_id,nullable"`
InvoiceID string `json:"invoice_id,nullable"`
PriceID string `json:"price_id,nullable"`
JSON decrementLedgerEntryJSON `json:"-"`
}
// decrementLedgerEntryJSON contains the JSON metadata for the struct
// [DecrementLedgerEntry]
type decrementLedgerEntryJSON struct {
ID apijson.Field
Amount apijson.Field
CreatedAt apijson.Field
CreditBlock apijson.Field
Currency apijson.Field
Customer apijson.Field
Description apijson.Field
EndingBalance apijson.Field
EntryStatus apijson.Field
EntryType apijson.Field
LedgerSequenceNumber apijson.Field
Metadata apijson.Field
StartingBalance apijson.Field
EventID apijson.Field
InvoiceID apijson.Field
PriceID apijson.Field
raw string
ExtraFields map[string]apijson.Field
}
func (r *DecrementLedgerEntry) UnmarshalJSON(data []byte) (err error) {
return apijson.UnmarshalRoot(data, r)
}
func (r decrementLedgerEntryJSON) RawJSON() string {
return r.raw
}
func (r DecrementLedgerEntry) implementsCustomerCreditLedgerListResponse() {}
func (r DecrementLedgerEntry) implementsCustomerCreditLedgerNewEntryResponse() {}
func (r DecrementLedgerEntry) implementsCustomerCreditLedgerNewEntryByExternalIDResponse() {}
func (r DecrementLedgerEntry) implementsCustomerCreditLedgerListByExternalIDResponse() {}
type DecrementLedgerEntryEntryStatus string
const (
DecrementLedgerEntryEntryStatusCommitted DecrementLedgerEntryEntryStatus = "committed"
DecrementLedgerEntryEntryStatusPending DecrementLedgerEntryEntryStatus = "pending"
)
func (r DecrementLedgerEntryEntryStatus) IsKnown() bool {
switch r {
case DecrementLedgerEntryEntryStatusCommitted, DecrementLedgerEntryEntryStatusPending:
return true
}
return false
}
type DecrementLedgerEntryEntryType string
const (
DecrementLedgerEntryEntryTypeDecrement DecrementLedgerEntryEntryType = "decrement"
)
func (r DecrementLedgerEntryEntryType) IsKnown() bool {
switch r {
case DecrementLedgerEntryEntryTypeDecrement:
return true
}
return false
}
type ExpirationChangeLedgerEntry struct {
ID string `json:"id,required"`
Amount float64 `json:"amount,required"`
CreatedAt time.Time `json:"created_at,required" format:"date-time"`
CreditBlock AffectedBlock `json:"credit_block,required"`
Currency string `json:"currency,required"`
Customer shared.CustomerMinified `json:"customer,required"`
Description string `json:"description,required,nullable"`
EndingBalance float64 `json:"ending_balance,required"`
EntryStatus ExpirationChangeLedgerEntryEntryStatus `json:"entry_status,required"`
EntryType ExpirationChangeLedgerEntryEntryType `json:"entry_type,required"`
LedgerSequenceNumber int64 `json:"ledger_sequence_number,required"`
// User specified key-value pairs for the resource. If not present, this defaults
// to an empty dictionary. Individual keys can be removed by setting the value to
// `null`, and the entire metadata mapping can be cleared by setting `metadata` to
// `null`.
Metadata map[string]string `json:"metadata,required"`
NewBlockExpiryDate time.Time `json:"new_block_expiry_date,required,nullable" format:"date-time"`
StartingBalance float64 `json:"starting_balance,required"`
JSON expirationChangeLedgerEntryJSON `json:"-"`
}
// expirationChangeLedgerEntryJSON contains the JSON metadata for the struct
// [ExpirationChangeLedgerEntry]
type expirationChangeLedgerEntryJSON struct {
ID apijson.Field
Amount apijson.Field
CreatedAt apijson.Field
CreditBlock apijson.Field
Currency apijson.Field
Customer apijson.Field
Description apijson.Field
EndingBalance apijson.Field
EntryStatus apijson.Field
EntryType apijson.Field
LedgerSequenceNumber apijson.Field
Metadata apijson.Field
NewBlockExpiryDate apijson.Field
StartingBalance apijson.Field
raw string
ExtraFields map[string]apijson.Field
}