#peepsszn

1 messages · Page 1 of 1 (latest)

tired crowBOT
craggy hinge
#

👋

scarlet ridge
#

hey

craggy hinge
#

Yeah this is currently being discussed internally about what the expected/intended behavior should be here. Basically the way it works currently is that the receipt_number is generated asynchronously after a charge has succeeded as it is based on when the actual receipt has been sent which is also an async process.

scarlet ridge
#

ah alright

craggy hinge
#

For now, you'll want to poll the API if receipt_number is null and wait on hearing from Support for info on what is determined in terms of moving forward.

#

It is possible the generation of this receipt_number is moved earlier in the flow so that it is guaranteed upon the Webhook, but right now that isn't the case.

scarlet ridge
#

so what exaclty would be the best move going forward to get the receipt_number?

#

oh poll the api

craggy hinge
#

Yeah I'd just retrieve the Charge every minute or so until it is present

scarlet ridge
#

sounds good

scarlet ridge
craggy hinge
#

It is being discussed right now.

#

As in -- folks internally are discussing what should the behavior be.

#

There is no active work being done at the moment nor can I guarantee this behavior will change.