Reverse issuance APISettlement platforms and purchasing teams
Send the details for approval. Stop waiting for an invoice.
The settlement is agreed, but the invoice has not arrived. Let the buyer prepare the transaction details so the supplier can focus on reviewing and approving them.
The buyer prepares. The supplier approves.
Send an approval request with the agreed details instead of exchanging amounts and business information again. The supplier still approves issuance.
Buyer
Prepare the settled transaction details and request reverse issuance.
Supplier
Review the request and approve it personally.
Operations
Track pending approvals, rejections, and issuance results separately.
Choose the approval path that fits your supplier workflow.
Have Bolta send the approval email, or guide suppliers to an approval URL from your service.
| Consideration | Bolta approval email | Approval from your service |
|---|---|---|
| Delivery | Bolta emails the supplier's contact | Your service shares the approval URL |
| Preparation | Start without advance certificate registration | Register the supplier certificate in advance |
| Supplier action | Review and approve from the email | Review and approve at the approval URL |
Pricing and requirements
Before you get started.
Reverse issuance
KRW 200 each
The recipient writes and requests it; the supplier approves
Reverse issuance uses prepaid credit and is separate from the service subscription.
- Issuance proceeds after the supplier approves.
- Simple reverse issuance requires the supplier's certificate to be registered in advance. Email approval can start without preregistration.
Build with your AI tool
Start with the AI tool you already use.
Copy a prompt with official documentation, prerequisites, and test goals into the AI tool you use for your project.
Read the prompt
Integrate this Bolta API into the current project. Send the details for approval. Stop waiting for an invoice. Read the official documentation first and propose an implementation that fits the project's language and structure. https://docs.bolta.io/llms.txt https://docs.bolta.io/docs/api-introduction/quickstart https://docs.bolta.io/docs/api-introduction/usecase-reverse-email https://docs.bolta.io/docs/api-introduction/usecase-reverse-simple https://docs.bolta.io/docs/api-introduction/certificate-registration Prerequisites and scope: - Issuance proceeds after the supplier approves. - Simple reverse issuance requires the supplier's certificate to be registered in advance. Email approval can start without preregistration. Reverse issuance: KRW 200 each Reverse issuance uses prepaid credit and is separate from the service subscription. Read the API key from a server environment variable. Do not ask for secrets in chat. Start with the documented test key and test inputs. Test goals: For the chosen email or simple approval flow, verify pending approval, approval, rejection, and the final issuance result. Do not invent undocumented features or responses. Identify open questions and summarize test results and production-readiness steps.
Questions before you integrate
What if the supplier does not approve?
You can check pending and rejected requests. Issuance proceeds after the supplier approves.
Do we need to build an approval screen?
Use Bolta's approval email or direct the supplier to the approval URL. The documentation explains the setup for each option.
When does the supplier register a certificate?
Email approval starts without advance certificate registration, but still requires supplier approval. Simple reverse issuance requires the supplier's certificate in advance.