Use Stripe for an invoice reference mismatch
Example: A customer tells the owner it paid one invoice. The account owner wants information about a different invoice with a similar amount.
Keep Stripe as the source for its records. A Righthand can use available information for the decision below.
This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.
The customer task
A customer tells the owner it paid one invoice. The account owner wants information about a different invoice with a similar amount.
Provider documentation. The documentation gives information about invoice states and invoice events. The invoice status values are draft, open, paid, uncollectible, and void.
Make account access explicit
If Stripe is available in Connections, connect the intended account. Give the Righthand access to that connection.
Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.
For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.
Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.
The request to the Righthand
Read the two supplied invoice references.
>
Compare customer and invoice identity.
>
Send the payment claim against its exact reference.
>
Send the owner the result before 3 PM Friday.
>
Use Pacific time.
Use the provider records for the result
Identify the exact invoice and account context. Read state and amounts together. Keep the owner's financial decisions separate from status reporting.
Similar amounts do not establish the same financial obligation.
For a permitted write, examine the resulting account record. A proposal does not establish a completed change.
For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.
An illustrative result and next step
The reported payment names invoice A. The question concerns invoice B, which has a different reference.
The billing owner examines the correct invoice before giving a reply.
Try one account task
- Give the Righthand one identified source record.
- Compare its result with that source.
- Examine the account record after a permitted write.
- Examine the work in Activity.
If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.
When the account tools are sufficient
Use Stripe directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.