Approval
Send any tax identifier that is not a special value — anein, or a nit, rfc, cnpj or tax_id outside the US. The business is approved and its account activates. This is the path you build against.
Rejection
Two different failures, and they are worth testing separately because your handling of them differs: Refused outright. The business cannot be onboarded, and sending it again changes nothing. Your product has to tell the customer that this is final rather than offering a retry. Refused on the data. Something in what you sent is wrong or missing. This one is worth retrying, once your customer has supplied the correction.Rejection after acceptance
The application is accepted, and is rejected later on review. It is the most useful one, and the one most integrations skip. This is the shape that breaks flows built on the happy path, because your code has already told the customer they are onboarded by the time the decision arrives. If you test one failure, test this one.A payment that is refused after it was accepted
Send a payout whose amount ends in a particular pair of decimals and the call is accepted, then a later callback fails it. Use it to prove your integration does not treat acceptance as delivery. A refusal can arrive after the payment was taken, as Payout warns.A hold, and what it resolves to
A compliance check can hold a movement before it settles, and the sandbox lets you choose how it ends: one pair of cents holds it and then approves, another holds it and then rejects. They resolve on their own. You do not need anyone at Kira to release one. Test them together, for the reason Holds gives. A held deposit’s amount also stays out of the account’s available balance while it lasts, so a test that leaves one held will look like a payout refused for insufficient balance later.Test value tables
The exact values for each outcome above.